geoff2005
asked on
DNS Errors using Windows 98 and Asante FriendlyNet FR1104-G
I have three PCs connected to an Asante FriendlyNet FR1104-G router/switch. One runs Windows 98, another Windows 2000 Pro, and the other Windows XP Pro.
When first set up, all three boxes connected without problems to the Internet; about a week later, the 98 box will connect to one or two sites, then fail on a DNS error. A network-monitoring program shows the failed connections stuck at SYN_SENT stage, as though never getting past step one of the three-way handshake.
Rebooting starts the same cycle over again.
Also, the 98 box won't access the router at the default address of 192.168.123.254.
The other two boxes have no problems.
I can ping and tracert any Internet address; I just can't hit it with the browser.
Several automatic accesses at startup, like McAfee checking for updates, show in the network tool as starting and completing normally.
I'm connecting over a Comcast cable system.
So far I've done the following:
Reinstalled IE6sp1 and a patch described as fixing a similar SSL problem (Q305217.exe)
Disabled SSL 3.0
Added and deleted DNS server addresses on the interface
Ran rundll32.exe setupwbv.dll,IE6Maintenanc
Deleted temp files and cookies
Changed switch ports
Ran Anti-Spy Info
Ran McAfee VirusScan
Ran PestPatrol
Ran Browser Hijack Blaster
Ran HijackThis
Ran Spybot S&D
Ran AdAware
Uninstalled ZoneAlarm Pro4
Reinstalled Wsock32.dll
Ran SystemFileChecker
Ran InternetConnectionWizard
Turned off 'Detect proxy settings' - was only calling out to www.wpad.net
Uninstalled Viewpoint Manager and media player
I have noticed the occasional connection to an unknown IP; resoving them gave me names like pacman.prognet.com, 36.70-85-43.reverse.thepla
Could I be getting hit by a reset attack?
Thanks!
When first set up, all three boxes connected without problems to the Internet; about a week later, the 98 box will connect to one or two sites, then fail on a DNS error. A network-monitoring program shows the failed connections stuck at SYN_SENT stage, as though never getting past step one of the three-way handshake.
Rebooting starts the same cycle over again.
Also, the 98 box won't access the router at the default address of 192.168.123.254.
The other two boxes have no problems.
I can ping and tracert any Internet address; I just can't hit it with the browser.
Several automatic accesses at startup, like McAfee checking for updates, show in the network tool as starting and completing normally.
I'm connecting over a Comcast cable system.
So far I've done the following:
Reinstalled IE6sp1 and a patch described as fixing a similar SSL problem (Q305217.exe)
Disabled SSL 3.0
Added and deleted DNS server addresses on the interface
Ran rundll32.exe setupwbv.dll,IE6Maintenanc
Deleted temp files and cookies
Changed switch ports
Ran Anti-Spy Info
Ran McAfee VirusScan
Ran PestPatrol
Ran Browser Hijack Blaster
Ran HijackThis
Ran Spybot S&D
Ran AdAware
Uninstalled ZoneAlarm Pro4
Reinstalled Wsock32.dll
Ran SystemFileChecker
Ran InternetConnectionWizard
Turned off 'Detect proxy settings' - was only calling out to www.wpad.net
Uninstalled Viewpoint Manager and media player
I have noticed the occasional connection to an unknown IP; resoving them gave me names like pacman.prognet.com, 36.70-85-43.reverse.thepla
Could I be getting hit by a reset attack?
Thanks!
Eric - Netminder
Can you post your HijackThis log somewhere (not here -- use the space they have for it and post the link here)?
<<Also, the 98 box won't access the router at the default address of 192.168.123.254. >>
Not sure what you mean by this.
In anycase, start with basic network troubleshooting:
1. Disable any firewalls on the Win 98 machine.
2. Reboot.
3. Click start/run and type WINIPCONFIG.
4. Select the proper adapter, then check the IP address. Should not start with 169. If so, that is an autoconfigure address and your station is not talking to your DHCP server. If you don't have a DHCP server (i.e. the router) and your using static IP's, then somethings wrong witht he TCPIP settings. Uninstall the protocol and re-install.
5. If the IP is OK, then look at the DNS addresses.
6. Look at the HOSTS file in C:\Windows. Only address that should be in there is the loop back 127.0.0.1.
7. Drop to a cmd prompt and ping each of those DNS addresses. If you get high pings or no replies then your going to need to use different DNS servers. You can check which the other boxes are using (use IPCONFIG at the command prompt).
Only once your sure the basic networking is solid can you move on.
<<Also, the 98 box won't access the router at the default address of 192.168.123.254.
The other two boxes have no problems.
I can ping and tracert any Internet address; I just can't hit it with the browser. >>
This rings a bell. I remember the problem, but not the fix<g> I believe it had to do with corrupted registry entires for IE. I see you already reinstalled IE. As a double check, you might want to try installing another browser like FireFox or opera.
Also, I'd check if there are any browser helper objects that shouldn't be there. Open up Spy Bot, go into advanced mode, then select the tools section. You'll find a BHO tool. Take a look at any that are loaded. You may have something that's trying to re-direct you.
HTH,
Jim.
Not sure what you mean by this.
In anycase, start with basic network troubleshooting:
1. Disable any firewalls on the Win 98 machine.
2. Reboot.
3. Click start/run and type WINIPCONFIG.
4. Select the proper adapter, then check the IP address. Should not start with 169. If so, that is an autoconfigure address and your station is not talking to your DHCP server. If you don't have a DHCP server (i.e. the router) and your using static IP's, then somethings wrong witht he TCPIP settings. Uninstall the protocol and re-install.
5. If the IP is OK, then look at the DNS addresses.
6. Look at the HOSTS file in C:\Windows. Only address that should be in there is the loop back 127.0.0.1.
7. Drop to a cmd prompt and ping each of those DNS addresses. If you get high pings or no replies then your going to need to use different DNS servers. You can check which the other boxes are using (use IPCONFIG at the command prompt).
Only once your sure the basic networking is solid can you move on.
<<Also, the 98 box won't access the router at the default address of 192.168.123.254.
The other two boxes have no problems.
I can ping and tracert any Internet address; I just can't hit it with the browser. >>
This rings a bell. I remember the problem, but not the fix<g> I believe it had to do with corrupted registry entires for IE. I see you already reinstalled IE. As a double check, you might want to try installing another browser like FireFox or opera.
Also, I'd check if there are any browser helper objects that shouldn't be there. Open up Spy Bot, go into advanced mode, then select the tools section. You'll find a BHO tool. Take a look at any that are loaded. You may have something that's trying to re-direct you.
HTH,
Jim.
ASKER
Following JDettman's instructions:
1. Firewall was uninstalled.
2. Rebooted.
3. Started winipcfg.
4. Selected adapter; IP address is 192.168.123.103. Not 169.etc. so no action taken.
5. DNS addresses listed are those provided by Comcast: 68.87.66.196 and 68.87.64.196.
6. HOSTS file lists only the 127.0.0.1 loopback; no other entries.
7. Pinged both DNS addresses; avg. time 29ms and 31 ms, respectively.
Installed Firefox 1.0.6; timed out trying to reach start.mozilla.org and www.google.com.
Started Spybot S&D (1.2) in advanced mode; selected BHO tool.
Two found:
ACROIEHELPER.DLL - marked in green as known legitimate program
googletoolbar.dll - marked in black as unknown; disabled it.
Tried IE to www.cnn.com - timed out ('page could not be displayed')
BTW, what I meant about the router is that not only does the 98 box not get out to the Net, but that I can't bring up the browser-accessible admin page to it. The other two machines can reach it.
If the TCP/IP stack is somehow hosed, should I reinstall other modules besides Wsock32.dll?
What's puzzling is that after rebooting, I can sometimes get to two or three sites with IE before the PCBD messages start...
Note to ericpete: I'll get the HijackThis listing out here later today.
Thanks for your help so far.
1. Firewall was uninstalled.
2. Rebooted.
3. Started winipcfg.
4. Selected adapter; IP address is 192.168.123.103. Not 169.etc. so no action taken.
5. DNS addresses listed are those provided by Comcast: 68.87.66.196 and 68.87.64.196.
6. HOSTS file lists only the 127.0.0.1 loopback; no other entries.
7. Pinged both DNS addresses; avg. time 29ms and 31 ms, respectively.
Installed Firefox 1.0.6; timed out trying to reach start.mozilla.org and www.google.com.
Started Spybot S&D (1.2) in advanced mode; selected BHO tool.
Two found:
ACROIEHELPER.DLL - marked in green as known legitimate program
googletoolbar.dll - marked in black as unknown; disabled it.
Tried IE to www.cnn.com - timed out ('page could not be displayed')
BTW, what I meant about the router is that not only does the 98 box not get out to the Net, but that I can't bring up the browser-accessible admin page to it. The other two machines can reach it.
If the TCP/IP stack is somehow hosed, should I reinstall other modules besides Wsock32.dll?
What's puzzling is that after rebooting, I can sometimes get to two or three sites with IE before the PCBD messages start...
Note to ericpete: I'll get the HijackThis listing out here later today.
Thanks for your help so far.
<<BTW, what I meant about the router is that not only does the 98 box not get out to the Net, but that I can't bring up the browser-accessible admin page to it. The other two machines can reach it.>>
In IE, you cannot reach the router using the IP address?
Jim.
In IE, you cannot reach the router using the IP address?
Jim.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That's right - I get the same PCBD message when going directly to the router at 192.168.123.254 with IE and Firefox; I can admin the router from the other two machines.
I'll get going on the MS checklist shortly.
Thanks!
I'll get going on the MS checklist shortly.
Thanks!
ASKER
I followed the MS list - delete all network components, then reinstall NIC drivers and TCP/IP - and that seemed to succeed; I'm writing this on the Win98 box. It took a few tries to get the right driver in and to get the router to assign an address to the box, but all seems to be working now.
Thanks for your help!
Thanks for your help!
<< but all seems to be working now.>>
That's great! Glad to hear your on your way....
Jim.
That's great! Glad to hear your on your way....
Jim.
I had a similar problem some time ago and after many days trying all things, the only solution was do just that. I uninstalled TCP/IP and all network components, deleted some registry keys related to TCP and reinstalled TCP and network. It worked perfectly. This was a very annoying problem and I was almost becoming crazy trying to solve it, googleing without success until I found one or two pages describing this solution.