Hi everyone, When trying to ping on an nt4 server i get the following message: "Ping transmit failed,error code 65" I can ping the loopback adress at the server but when trying to ping it's own ip or any other ip i get this error. Anybody any clues? Roy

reinstall networking piece

Hi Roy, I get the exact same message when trying to ping my own IP address in windows 2000. The exact error I receive is: ============================================= PING: transmit failed, error code 65. PING: transmit failed, error code 65. PING: transmit failed, error code 65. PING: transmit failed, error code 65. Ping statistics for 192.168.0.100: Packets: Sent = 4, Received = 0, Lost = 4 (100 Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms ============================================= I'm using the D-Link DI-704 DSL/Cable Modem Gateway Router and 4port Network Switch from http://comready.com/dlindi7dslca.html, which acts as a standalone server and has file, print, and Internet sharing capabilities. I've tried reinstalling the netwrok card but to no avail. I'm in the process of getting in contact with the manufactorer of my network card but what astonishes me is that I'm able to share the Internet access but don't have any access to any computers on the network. Goog luck on finding your solution! :) - Marty

Roy, Guess what! I figured out the solution to the problem! All you need to do is to uninstall all the components installed for your network card. In my scenarion, I was using Windows 2000 and I did as follows: Right-clicked on "My Network Places" Right-clicked on "Local Area Connection" Took note of the componets installed and uninstalled and then reinstalled all of them. And then, bingo! It worked! If you need any further assistance, feel free to contact me at mordechai21@yahoo.com. - Marty

This error is caused by the TCP/IP configuration. Usually an application using TCP/IP filtering, such as a firewall or a proxy, creates the problem. Just re-install TCP/IP on your computer... + you might have to get rid of the program, messing with your TCP/IP, too, if you don't want the problem to come back. vp

In my case it was a firewall-application called zonealarm. kill -f vsmon.exe or remove zonealarm from autostart and reboot

I had the same error and it was also associated with Zone Alarm. If you were previously running Zone Alarm you have two choices: 1. (If Zone Alarm is still installed.) Start Zone Alarm. Go to the programs tab. Authorize access to the Internet and the Local Network for every program listed. Close Zone Alarm. 2. (If Zone Alarm is uninstalled.) Reinstall Zone Alarm. Go to the Security tab. Move the sliders to the lowest security setting. Close Zone Alarm. If everything is working correctly, uninstall Zone Alarm. Finally, Zone Alarm mentions this in a couple of their FAQS. Good Luck....