On Sunday, December 9, 2001, at 09:32 PM, Tarragon Allen wrote: > On Mon, 10 Dec 2001 13:16, NDPTAL85 wrote: >>>> Yes I have already added the DNS servers into resolve.conf (you can >>>> actually do that via NetConf as well) and it still isn't working. It >>>> was >>>> working before on its own IP and it just decided to "stop" working >>>> for >>>> some reason. I haven't changed anything or installed anything on it >>>> to >>>> prompt it, one day SETI@HOME was just unable to retrieve anymore work >>>> units and the DNS issue was the problem. >>> >>> This has happened to me before, when i accidentilly pulled the cable >>> just >>> enough so it wasnt in right, but the lights still worked from some >>> reason. >>> Does ping by ip etc work? >>> >>> - -- >>> Tom "Tomahawk" Badran >>> Department of Computing, Imperial College >> >> Its not a physical connection problem. When I switch it to DHCP it >> regains full connectivity. > > Ok, basic tests: > > Can you ping your gateway IP? > Does nslookup work? > Can you ping your DNS server(s) as it's set in resolv.conf? > What address are you trying to connect to; can you resolve it with > nslookup? > Can you ping that IP address directly (no DNS lookup)? > Any firewall settings that might get in the way? > Would the DHCP server be set to block/ignore traffic from IP's it hasn't > assigned?
I have 3 other comps behind this router. I can still ssh into the Mandrake box when its on its permanent IP (192.168.0.2) but it cannot resolve anything from that IP. The router isn't set to block anything unusual. All other comps can connect to the next just fine. Its just the Mandrake box. I am going to switch one of my other comps to 192.168.0.2 to rule out that specific IP as being a problem. -------------------------------------------- There is no right way to do the wrong thing. --------------------------------------------
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
