Re: [Condor-users] 192.168.50.1??

["Finch, Ralph" <rfinch@xxxxxxxxxxxx>]

Oh, good idea:

d:\>ping 192.168.50.1
ping 192.168.50.1

Pinging 192.168.50.1 with 32 bytes of data:

Reply from 192.168.50.1: bytes=32 time<1ms TTL=128
Reply from 192.168.50.1: bytes=32 time<1ms TTL=128
Reply from 192.168.50.1: bytes=32 time<1ms TTL=128
Reply from 192.168.50.1: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.50.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

So it must be something internal...obviously I don't
understand all the ins-n-outs of IP numbers.

192.168. is a private subnet. Anyone can create a 192.168. subnet and
routers won't let traffic from this subnet cross on to public IP subnets
without a gateway being set up. For example: we have a 192.168. subnet
at my office for all our Condor machines.

Is your condor machine using DHCP? Could one of your admins have changed
DHCP to hand out private subnet IPs (maybe you were running out of
136.200. IPs)? This would explain why Condor all of sudden started
trying to talk to 192.168. addresses. Do delta-mod and it's IP address
resolve both ways?

	> nslookup delta-mod
	> nslookip <what ever IP the last nslookup gave you>

Do you get to the same machine with both calls? If not someone might
have messed up your DNS at your site.

> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx 
> [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of bruce
> Sent: Wednesday, August 09, 2006 10:30 AM
> To: 'Condor-Users Mail List'
> Subject: Re: [Condor-users] 192.168.50.1??
> 
> hi ralph...
> 
> just out of curiosity.. what happens when you ping 192.168.50.1
> 
> i was/am under the impression that 192.168.... are supposed 
> to be internal to your system/firewall... is it possible that 
> some dns entry has changed..

d:\>nslookup delta-mod
nslookup delta-mod
Server:  sacns1.ad.water.ca.gov
Address:  136.200.117.17

Name:    delta-mod.ad.water.ca.gov
Address:  136.200.32.102

d:\>nslookup 136.200.32.102
nslookup 136.200.32.102
Server:  sacns1.ad.water.ca.gov
Address:  136.200.117.17

Name:    delta-mod.ad.water.ca.gov
Address:  136.200.32.102

d:\>nslookup 192.168.50.1
nslookup 192.168.50.1
*** sacns1.ad.water.ca.gov can't find 192.168.50.1: Non-existent domain
Server:  sacns1.ad.water.ca.gov
Address:  136.200.117.17

I is confoozed.
RF

> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx 
> condor-users-bounces@xxxxxxxxxxx on behalf of Ian Chesal
> Sent: Wednesday, August 09, 2006 11:07 AM
> To: 'Condor-Users Mail List'
> Subject: Re: [Condor-users] 192.168.50.1??
> 
> 192.168. is a private subnet. Anyone can create a 192.168. subnet and
> routers won't let traffic from this subnet cross on to public IP
subnets
> without a gateway being set up. For example: we have a 192.168. subnet
> at my office for all our Condor machines.
> 
> Is your condor machine using DHCP? Could one of your admins have
changed
> DHCP to hand out private subnet IPs (maybe you were running out of
> 136.200. IPs)? This would explain why Condor all of sudden started
> trying to talk to 192.168. addresses. Do delta-mod and it's IP address
> resolve both ways?
> 
> 	> nslookup delta-mod
> 	> nslookip <what ever IP the last nslookup gave you>
> 
> Do you get to the same machine with both calls? If not someone might
> have messed up your DNS at your site.


> > Finch, Ralph wrote:
> > 
> > >A few weeks ago--don't know what caused it--condor started 
> trying to
> > >talk to 192.168.50.1.  Over the weekend I upgraded to the 
> > latest version
> > >but it didn't fix matters.  I also had HAD running and 
> > turned all that
> > >off, no joy.
> > >
> > >Any ideas?  This is an all-windows network.
> > >
> > >Ralph Finch, P.E.
> > >Dept. of Water Resources
> > >Bay-Delta Office, Room 215-13
> > >Sacramento, CA  95814
> > >916-653-7552
> > >rfinch@xxxxxxxxxxxx
> > >
> > >8/8 20:42:08 ******************************************************
> > >8/8 20:42:08 ** Condor (CONDOR_MASTER) STARTING UP
> > >8/8 20:42:08 ** z:\condor\condor-6.8.0\bin\condor_master.exe
> > >8/8 20:42:08 ** $CondorVersion: 6.8.0 Jul 19 2006 $
> > >8/8 20:42:08 ** $CondorPlatform: INTEL-WINNT50 $
> > >8/8 20:42:08 ** PID = 3852
> > >8/8 20:42:08 ** Log last touched 8/8 16:29:56
> > >8/8 20:42:08 ******************************************************
> > >8/8 20:42:08 Using config source: z:\Condor\condor_config
> > >8/8 20:42:08 Using local config sources: 
> > >8/8 20:42:08    Z:/Condor/condor_config.local
> > >8/8 20:42:08 DaemonCore: Command Socket at <192.168.50.1:3986>
> > >8/8 20:52:08 WinFirewall: get_CurrentProfile failed: 0x800706d9
> > >8/8 20:52:08 Started DaemonCore process
> > >"Z:/Condor/condor-6.8.0/bin/condor_startd.exe", pid and 
> pgroup = 3492
> > >8/8 20:52:08 Started DaemonCore process
> > >"Z:/Condor/condor-6.8.0/bin/condor_schedd.exe", pid and 
> pgroup = 3372
> > >8/8 20:52:17 attempt to connect to <192.168.50.1:4009> failed
> > >8/8 20:52:33 ERROR: SECMAN:2003:TCP connection to 
> <192.168.50.1:4009>
> > >failed
> > >
> > >8/8 20:52:33 Failed to start non-blocking update to 
> > <192.168.50.1:4008>.
> > >8/8 20:55:16 attempt to connect to <192.168.50.1:4075> failed
> > >8/8 20:55:34 ERROR: SECMAN:2003:TCP connection to 
> <192.168.50.1:4075>
> > >failed