Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
After setting up my home network consisting of a Win98 desktop, Win2k desktop and Win2k laptop going through a Linksys 4 port router, I am unable to ping any Ip addresses except the loopback 127.0.0.1 with the laptop. The error I get is Ping: transmit failed, error code 65. I can ping fine with the other 2 machines and I have the exact same settings on the 2 Win2k machines. I can also browse the Internet and map to the other 2 machines without a problem with the laptop. Any ideas what would cause this? Any help would be greatly appreciated. Thanks.
Jeff
Did you ever figure this out? I am having the
same problem. PC has 2 NICs. First is connected
to the Net and has no problems, and the second is
connected to another PC via X-over cable. The
second one is the one I am having trouble with.
Swapped NICs, problem stays. However, second NIC
connects fine to other unit via NetBEUI. Weird.
Thanks in advance.
0 
Hi guys, I am having the same problem also. My laptop was upgraded to 2000Prof. Everything worked fine. Connecting through a Linksys 4 router and cable modem. Last weekend I upgraded the home PC, immediately after rebooting I can get into the internet via IE 5.5 but if I let it sit for 15-30 minutes I get 'DNS or server not found', then I try the 127.0.0.1 (works fine) but when I try to ping my Linksys I get the error 65. Any advice would be appreciated. Thanks in advance.
0
Hey guys - try this if you're running on a Win2K box.
http://support.microsoft.com/support/kb/articles/Q239/9/24.ASP?LN=EN-US&SD=gn&FR=0&qry=media%20sense&rnk=3&src=DHCS_MSPSS_gn_SRCH&SPR=WIN2000
Jeff.
0
I have the same problem that just started a couple of days ago on a laptop. Can't ping beyond 127.0.0.1, but incoming pings are echoed nicely. I'll try Jeff's fix, but Jeff -- how the hell did you find it?
0
I had pretty much the same problem with WIN 98SE. The key for me seemed to be the two NIC's in my laptop, the built-in one and a PC card. Since I was only using the PC Card to connecto the network, I cleared the IP address on the built-in one. When I rebooted, the router gave it a dynamic IP even though it's not directly connected to the router. When I released the IP address for the built-in NIC, I could ping all the computers on the network. I set a static IP address above 192.168.1.52 for my PC Card NIC, in case that's relevant. Jeff's posting provided the inspiration: Thanks!
0
Thinking back, this all started when I dialled an ISP and PPTP tunneled into my LAN. I probably had not released the IP from the previous day's LAN connection either. Apparently Windows has IP problems when multiple interfaces get involved. A previous thread (http://computing.net/windows2000/wwwboard/forum/8835.html) offered the solution of reinstalling everything associated with TCP/IP, and that apparently works as well.
0
I tried the registry modification, as well as removing and reinstalling the TCP/IP info. No luck so far. I can connect with applications, but not ping, nor can other machines ping me. I can see the other computers in my network, but can't access any shares. If anyone has any more clues, please email me!
0
I've had the same error as the others. System only had the two NICs put in on the 18th. One to cable modem and the other for inside the network. Tried Win2K SP2 update - made the situation even worse. Couldn't get out onto the Internet until I actually uninstalled SP2. Have also tried the registry hack to no success. Am going to try removing the internal LAN NIC to try and see if I can at least PING then. Will take it a step at a time and maybe instead of using Win2K Internet Connection Sharing, I will probably try a 3rd party software instead.
Would like to know if anyone else is able to solve this issue using Internet Connection sharing though.
0
Have P4 +Win2000Prof the PING 65 error only occurred after trying the SP2 upgrade when I lost all LAN connection. Uninstalled SP2 and still got 65 error BUT most Internet apps still work except IE5.
Tried reg. hack. No difference. Tried removing NIC card and TCP/IP and reinstalling.
NIC is Intel pro 100 - upgraded drivers - no change.
0
ODD! Ran Windoze Media Player (Vers 7) - it could see Internet - suddenly IE5 worked! (Ping error 65 still there.) Upgraded Media player to 7.1 and on reboot PING error dissapeared!! Everything seems to work again EXCEPT still can not connect to other Win98 PC on LAN. I can ping it by IP number but can not see it using network places. "Workgroup problem" now?
0
Add me to the list. Win2k pro. My outlook email doesn't work but forte agent mail does. IE 5.01 works fine. Can't ping anything but the loopback. I uninstalled ip protocol and ms client and everything worked for about two days. It is frustrating because I have a Dell audio receiver that can't connect to the tunes.
0
Getting ping error code 65 here, all my apps seem to be working and I get no err in linux (heh) but in windoze 2k I cant ping anything..
0
Hello,
I had same error when pinging anything other than loopback address. IBM Thinkpad, Xircom10/100 pcmcia and Win 2kpro.
I had zonealarm installed, and incorrectly configured. This was causing the problem in my case. After removing zonealarm and all its associated security services, the problem was resolved.I'm guessing that anything preventing incoming traffic (ie incoming ping response)
like Zonealarm or BlackICE will cause similar problems.cheers
0
Thanks for all the advice here. Even without firewall software running, it was causing the error code 65. I uninstalled both Blackice and Zonealarm. Everything works perfectly. I've reinstalled Zonealarm, inserted the ip addresses of my local machines in the local settings of Zonealarm, and everything is right with the world.
Internet is working again also. Seems the firewall softwares are the issue here.
Also, did the uninstall of all network protocols and clients, etc. as mentioned by someone earlier in this line, that may or may not have helped. But it's easy enough to try.
Good luck.
0
Removing ZoneAlarm fixed it... it was actually the "truevector" service that ZoneAlarm uses that was causing the problem. You could simply disable the service in "manage my computer". (Win2K)
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
