[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] NETWORK_INTERFACE on Windows not working

Hi Danelle:

Could you set 


and post your logs (and possibly your configuration files as well), this would
help us in determining the problem.


-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx]
On Behalf Of Cline, Danelle
Sent: Wednesday, February 27, 2008 7:03 PM
To: condor-users@xxxxxxxxxxx
Subject: [Condor-users] NETWORK_INTERFACE on Windows not working

Dear condor users,

I'm having some difficulty with my Windows network interface. Hoping you can
offer some help.

I have two network interfaces on my windows machine: one is a private 10.*.*.*
address, and the other is a public 134.*.*.* address.

In my config file I've set: 


This Windows machine joins the pool, but the class add StartdIpAddr for this
machine (with condor_status -l |grep StartdIpAddr ), shows the address still
advertised as the 10.*.*.*  and not the 134.*.*.* address.

According to this, NETWORK_INTERFACE should work, but this doesn't work for me.
Is this a bug in Condor? Am I missing something ?   


"By default, Condor advertises the IP address of the network interface used to
contact the collector, since this is the most likely to be accessible to other
processes that query the same collector. The NETWORK_INTERFACE setting can still
be used to specify the IP address Condor should advertise, even if
BIND_ALL_INTERFACES is set to True. Therefore, some of the considerations
described below regarding what interface should be used in various situations
still apply when deciding what interface is to be advertised. "

Danelle E. Cline, Software Engineer R&D Division        
Monterey Bay Aquarium Research Institute 
(831) 775-1947 voice 
(831) 775-1652 fax 

Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at: