I found the problem. One site had the IP xxx.yy.183.146 and that address was outside the Cobalt valid IP's, so GUI build with ifconfig a route (eth0:2) for each new IP address, so when trying to go to that server (xxx.yy.183.145) it was trying to route with the 146 address. Corrected the error, corrected the problem. Thanks anyway and sorry for masking the real IP address, but was for precaution. Thanks!!
----- Original Message ----- From: "Jeff Lasman" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, July 25, 2003 10:41 AM Subject: Re: [cobalt-developers] No route to host message > Gerald Waugh wrote: > > > > traceroute to xxx.yy.183.145 (xxx.yy.183.145), 30 hops max, 38 byte packets > > > 1 * * * > > > 2 * * * > > > 3 * * * > > > 4 yyy.xx.183.146 (xxx.yy.183.146) 46 bytes to xxx.yy.183.146 2999.946 ms > > > !H 2995.810 ms !H 2999.681 ms !H > > I assure you it doesn't say that at all; "xx" and "yyy" are not > routable. Most likely you're attempting to hide the real address from > us, which has the side-issue of making it impossible for us to test. > > Nevertheless, here's what it all means: > > The routing tables are pointing to 183.146, which has no idea where to > find 183.145. Possibly an ARP cache problem, possibly 183.146 was once > a gateway router address, possibly 183.145 has a bad nic. > > Impossible to test any of these theories without knowing the real > address. > > Jeff > -- > Jeff Lasman, nobaloney.net, P. O. Box 52672, Riverside, CA 92517 US > Internet & Unix/Linux/Sun/Cobalt Consulting +1 909 324-9706 > Our jblists address used on lists is for list email only > To contact us offlist: "http://www.nobaloney.net/contactus.html"; > > _______________________________________________ > cobalt-developers mailing list > [EMAIL PROTECTED] > http://list.cobalt.com/mailman/listinfo/cobalt-developers > > _______________________________________________ cobalt-developers mailing list [EMAIL PROTECTED] http://list.cobalt.com/mailman/listinfo/cobalt-developers
