From: Wynne, Conor (Conor.Wynne at domain compaq.com)
Date: Mon 01 Oct 2001 - 12:51:30 IST
DNS - Think that also may be a possibliity, its down to a firewall/dns
problem I feel.
And now you mention it, Its more likely DNS coz its only half configured :)
(and not working, I must have forgotten to disable the service aswell as
vi'ing the /etc/hosts)
The dns server was on the squid box, which is going over to the dark side as
the wife needs a doze box for visual basic programming - and I'm not
donating my athlon, she may notice somethings up if I try and pawn off the
I was just on to the missus she checked route -n, lo and behold it came up
immediately -thats good right?
(bad hangover today so go easy peeps)
It does always give the correct gateway address 192.168.0.1.
Should I actually configure a gateway on a box that gets the info upon
Can anyone clarify this please?
Best Regards and thanks to all who responded.
"The revolution will not be televised"
Gil Scott Heron
Try running route -n so as not to do name resolution. Most likely a DNS
issue that is causing the delay. Was the default route correct when it
did come back ??
-- _______________________________________ Glen Gray Software Engineer a n t e f a c t o t: +353 1 8586006 www.antefacto.com f: +353 1 8586014 181 Parnell Street - Dublin 1 - Ireland
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:12:24 GMT