DNS no longer working

  • Thread starter Thread starter David Heagy
  • Start date Start date
D

David Heagy

Hello, I'm having a problem on my network, the DNS no longer appears to be
working for one machine in a network of 10 computers.

Things were working fine, then I went on holidays, and when I got back I no
longer had DNS. I can ping everything using the IPs but cannot use the url.
All other computer on the network are working fine.

The machine that is not working is Win XP pro and the server is a win 2000
server with sbs. There is also a firewall (sonwall) that provides DHCP but
the server provides the DNS.

I have tried using the DNS ips that the firewall gets, I can ping them but
they don't work either.

It seems to be something on the XP machine that is stopping the DNS from
working, but I haven't a clue as to what that might be.

Does anyone have any ideas or suggestions on this. Or is more info needed.
Thanks
Dave
 
Hello, I'm having a problem on my network, the DNS no longer appears to be
working for one machine in a network of 10 computers.

Things were working fine, then I went on holidays, and when I got back I no
longer had DNS. I can ping everything using the IPs but cannot use the url.
All other computer on the network are working fine.

The machine that is not working is Win XP pro and the server is a win 2000
server with sbs. There is also a firewall (sonwall) that provides DHCP but
the server provides the DNS.

I have tried using the DNS ips that the firewall gets, I can ping them but
they don't work either.

It seems to be something on the XP machine that is stopping the DNS from
working, but I haven't a clue as to what that might be.

Does anyone have any ideas or suggestions on this. Or is more info needed.
Thanks
Dave

Dave,

DNS resolution is affected by the LSP / Winsock subsystem.
http://support.microsoft.com/?id=318584
http://support.microsoft.com/?id=811259

Give LSP-Fix and WinsockXPFix <http://www.cexx.org/lspfix.htm>, or WinsockFix
<http://www.tacktech.com/display.cfm?ttid=257> a shot.

If XP SP2, Start - Run - "cmd". Type "netsh winsock reset catalog" into the
command window.

If no help yet, reset TCP/IP.
http://support.microsoft.com/?id=299357

Start - Run - "cmd". Type "netsh int ip reset c:\netsh.txt" into the command
window.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top