Re: [JBoss-user] Connect exception in LAN when network cord is pu lled

2003-10-15 Thread Meyer-Willner, Bernhard
LAN when network cord is pu lled Could it be a Windows MediaSense problem? Windows 2000 and above has a “feature” called auto-sensing: if you unplug your network cable from your NIC, all associated IP addresses are removed from the routing table! Not good! You can disable this behaviour: Launch

Re: [JBoss-user] Connect exception in LAN when network cord is pu lled

2003-10-14 Thread Bill Burke
Could it be a Windows MediaSense problem? Windows 2000 and above has a “feature” called auto-sensing: if you unplug your network cable from your NIC, all associated IP addresses are removed from the routing table! Not good! You can disable this behaviour: Launch regedit Open HKEY_LOCAL_MACHINE\S

Re: [JBoss-user] Connect exception in LAN when network cord is pu lled

2003-10-14 Thread Scott M Stark
Telneting to localhost should work, but the exception shows the 158.234.148.187 address. Telneting to that address without the cable will show the same problem. Scott Stark Chief Technology Officer JBoss Group, LLC Meyer-Willner, Bernhard wrote:

Re: [JBoss-user] Connect exception in LAN when network cord is pu lled

2003-10-14 Thread Meyer-Willner, Bernhard
Telnetting localhost on our JNDI port works indeed. On a forum thread I saw suggestions like adding an entry to the hosts file on Unix or Windows and/or adding the -Djava.rmi.server.hostname paramter to run.bat/run.sh. Tried it all and didn't help. Is there anything else one could do? -Ursprün