• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows XP Pro Dial-Up Networking; connection, but no net

ianbergman

Senior member
This is just my week for posting to AT looking for help 😉

Anyway, I have a friend whose dial-up internet (through Earthlink) just stopped working one day. I spent 2.5 hours at his place the other night, to no avail, which was depressing. Basically, what's happening is he is making a connection, and getting an IP and all the other related info from the server, but has no DNS resolution. It's a WinXP Pro box.

Pinging 216.239.115.141 works like a charm.
Pinging www.cnet.com, nada.

using the nslookup command line tool, I would get the error message "name server not responding." However, I could ping both name servers, as listed in ipconfig, and they worked just fine. Earthlink avowed that there was nothing wrong with their network.

Any ideas? I wish I had had a broadband network available to test through another device (ethernet card), but no such luck at his place. If anyone knows how to fully uninstall and reinstall tcp/up and DNS in winXP, that would be helpful too.

At one point we actually did a repair using the WinXP install program; since this basically guts Windows, I was shocked when it didn't work.

No firewalls active, no spyware, no viruses, no strange processes or services interfering with with the connection that I could find. DNS settings were correct in the dial-up connection, and for kicks we tried to re-create the connection a couple of times with the same results.
 
go to your adapter settings and right click, go to properties, then click the networking tab. go to tcp/ip and set some DNS servers of your won. use 4.2.2.1 and 4.2.2.2
 
Thanks, I'll try the manual DNS servers, but I think the problem is more that DNS in Windows is just plain broken.

It almost seems like something is filtering DNS packets, 'cause nslookup works and the DNS client is running, but there's no communication with the DNS servers.

as I mentioned, no firewalls running, however. Ugh.
 
Back
Top