Hi, just some minor correction (or assumption...):
On 10/27/2006 5:54 AM, Robert Nelson wrote: ... > The reason for the differences is probably caching on the switch. I suspect > that in the same subnet case the arp is failing (so the IP address can't be > converted to an Ethernet address), in the other case the switch is > responding to the arp and a higher level (and longer timeout) is coming into > play, probably the TCP connect timer. I rather suspect that in one case the DNS was already cleared of the host name (message No Route to Host) while in the other case the DNS still had a record for the host and thus the tcp stack had to actually try the connect, and thus rely on the underlying IP timeouts (error message Timeout). Arno -- IT-Service Lehmann [EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
