Re: [Condor-users] 192.168.50.1??

["Ian Chesal" <ICHESAL@xxxxxxxxxx>]

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.

- Ian

-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Finch, Ralph
Sent: August 9, 2006 12:11 PM
To: Condor-Users Mail List
Subject: Re: [Condor-users] 192.168.50.1??

That's the rub, our network is all 136.200.**.**.

Whereas 192.168.50.1 is:

  Search results for: 192.168.50.1

    OrgName:    Internet Assigned Numbers Authority 
    OrgID:      IANA
    Address:    4676 Admiralty Way, Suite 330
    City:       Marina del Rey
    StateProv:  CA
    PostalCode: 90292-6695
    Country:    US

Must of done something a while ago to get some wires crossed; how to
uncross them??

BTW,

Z:\condor\log>condor_config_val COLLECTOR_HOST
condor_config_val COLLECTOR_HOST
delta-mod

Where delta-mod is 136.200.32.102

Ralph

> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx 
> [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Dan Bradley
> Sent: Wednesday, August 09, 2006 8:50 AM
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] 192.168.50.1??
> 
> 
> At appears that the IP address of the machine Condor is running on is 
> 192.168.50.1, and Condor is trying to talk to 
> condor_collector on this 
> same machine.  What is your COLLECTOR_HOST configuration?  
> The best way 
> to find out is this:
> 
> condor_config_val COLLECTOR_HOST
> 
> --Dan
> 
> 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
> >
> >
> >_______________________________________________
> >Condor-users mailing list
> >To unsubscribe, send a message to 
> condor-users-request@xxxxxxxxxxx with a
> >subject: Unsubscribe
> >You can also unsubscribe by visiting
> >https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> >
> >The archives can be found at either
> >https://lists.cs.wisc.edu/archive/condor-users/
> >http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR
> >  
> >
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to 
> condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> 
> The archives can be found at either
> https://lists.cs.wisc.edu/archive/condor-users/
> http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR
> 
> 

_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with
a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users

The archives can be found at either
https://lists.cs.wisc.edu/archive/condor-users/
http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR