Ping transmit failed, error code 5. - No internet but some network services

Greetings, Megaben !

Use LSP-Fix to repair your LSP layer and hopefully fix your connection
http://www.cexx.org/lspfix.htm


Norton internet security 2006 could cause your connection problem.  After uninstalling it, use SymNRT to remove the remaining hooks.

SymNRT Cleanup Utility
http://service1.symantec.com/SUPPORT/tsgeninfo.nsf/docid/2005033108162039?Open&src=&docid=2004020314035036&nsf=tsgeninfo.nsf&view=docid&dtype=&prod=&ver=&osv=&osv_lvl=



Best wishes!

Many thanks, war1, but...

LSP-fix made its changes, and now there is a slight difference: pinging (any) address results in "pinging oy with 32 bytes of data" where the 'o' looks odd, and the 'y' has 2 dots above it - still get my ping error 5

pinging localhost does return replies - i did not try this before so don't know if there is any change there, however the line reads:
pinging ben2000 [oy] with 32 byts of data
(ben2000 is the name of my pc)

I think I ran symNRT beofre, but in any case downloaded and ran it now.

Also I now get (at startup) a dialog with a microsoft active sync icon "Mobile Devices Properties" The tcp/ip network transport is not installed

I can still bowse the local network using tcpip

Ben

Hi Megaben
from cmd type in ipcofig /release   press enter
then ipconfig /renew
unplug the cable and reboot then plug in the cable again. sometimes the simplest can solve it.
reset the router.

windows xp has a network troubleshoot tool from within network connections-
 run all automated tests and will perform this and provide you with a pass or fail.
Click Start, and then click Help and Support.
2. Under Pick a Help Topic, click Networking and the Web.
3. Under Networking and the Web, click Fixing networking or Web problems, and then click Home and Small Office Networking Troubleshooter.

If the account is not active, use the following command to give the Guest account network access:
net user guest /active:yes
e.  The following text returns after the command:The command completed successfully.

run a scan for corrupt files type in sfc /scannow you will need your xpcd.
Config your tcp/ip to auto.
Do you have a firewall enabled disable it for now.

If you receive any other response, make sure that you are logged on as an Administrator, and then confirm that you typed the command correctly before you try again.
3. After you have verified the configuration, locate the computer name for each computer, and then make sure that a folder is shared. To do this, follow these steps: a.  Click Start, click Run, type sysdm.cpl, and then click OK.
b.  On the Computer Name tab, note the computer name on the "Full computer name" line.
c.  To determine if a folder is shared, click Start, click Run, type fsmgmt.msc, and then click OK.
d.  In the left pane, click Shares.

A list of shared folders appear in the right pane. Make a note of one share name for each computer.
 
4. Test a connection from one computer to another. Click Start, click Run, type \\computername (where computername is the name of another computer on the network), and then press ENTER. A window opens that contains an icon for each shared folder on the other computer. Open one of the shares to confirm that the connection is working. If you cannot open a shared folder, test in the opposite direction between the computers or between other computers to make sure that the problem is not with a particular computer on the network.
5. If you still cannot connect to the other computer, test again, but replace the computername with the name of the local computer. This tests the connection locally. A window appears that displays an icon for each shared folder on the computer. Try to open one of the shares to make sure that you have access.

If the window that contains the shares on the computer does not appear, or if you receive an error message, search the Microsoft Knowledge Base for additional information about the specific error message that you received. To search the Microsoft Knowledge Base, visit the following Microsoft Web site, and then click Support:
http://www.microsoft.com (http://support.microsoft.com/?scid=http%3a%2f%2fwww.microsoft.com)
6. If you do not receive any error messages, or you do not find related information in the Microsoft Knowledge Base, look in the Network Setup Wizard log file for errors in any steps that are not followed by successful operations. To open the log, click Start, click Run, type %SystemRoot%\nsw.log, and then press ENTER. If you find errors in the log, search the Microsoft Knowledge Base for additional information about how to manually configure the computer to have correct settings.
7. If the Nsw.log file does not give you any information about the problem, look in the system log for errors, and investigate those errors.
For additional information about how to use Event Viewer to look for system log entries, click the following article number to view the article in the Microsoft Knowledge Base:
308427 (http://support.microsoft.com/kb/308427/) How to view and manage event logs in Event Viewer in Windows XP

Troubleshooting TCP/IP - Detailed Steps
This article shows how to troubleshoot TCP/IP connectivity between computers on a Windows network.  If you haven’t already done so, disable XP’s Internet Connection Firewall on all local area network connections, and remove all firewall programs on the network.   Improperly configured firewalls are the most common cause of TCP/IP problems.
http://www.practicallynetworked.com/sharing/troubleshoot/


regards M
 

Further observation: since LSP-fix / symNRT dynamic ipaddress allocation fails with the following error :-
an error occurred while renewing interface local area connection 5 : the support for the specifed socket type does not exist in this address family

does this help in  any way to pinpoint the problem?

You should uninstall and reinstall the TCP/IP Stack (Different than Resetting)

http://www.petri.co.il/reinstall_tcp_ip_on_windows_xp.htm

Hope this helps

Hi Guys, still no joy:  In particular...

tmassa99 - this points me to the netsh utility mentioned in my original notes, however on the principle that other attemtps might have made things different, I ran netsh int ip reset again, and also a new command for SP2 which i discovered after re-reading your link netsh winsock reset catalog.. Spurious 'oy' characters on the ping command (see above) now gone, but ping transmit error 5 remains

Merete: SFC already ran, but on the principle that other changes might have made this do something useful, ran it again.  Not sure if this is relevant but I am using an XP Pro CD with SP2 already incorporated (system is SP2, but originally SP0, then SP1....) SFC asks for the CD several times during its scan with a message please insert your windows Cd, retry/ cancel type of dialog box - retry always makes it carry on happily; this happens about 6 times during its scan - very annoying!

Help and support/networking utility does come up with several failures, but doesn't attempt to fix them.  They all seem to relate to the inability to ping anything (apart from localhost) - This definitely seems to me to be some sort of 'hidden firewall' issue, but I have disabled everything I can at startup using msconfig, and problem still exists.

Microsoft knowledgebase has some ping errors, but not error 5 - I am upping the points in the hope of a miriacle!

TIA,

Ben

ok lets get you running that sfc with out a cdrom.

________________________________________
Copying the Source Files
1.      If your WindowsXP source files are already on the computer's hard drive you can skip this section.
2.      Insert your WindowsXP sp1 CD with sp2
3.      If prompted, do not install WindowsXP
4.       Create a directory on the hard drive and copy the entire contents of the CD to that directory
5.      For example, use c:\winxp
---------------------------------------------------------------

Once these files are on your hard drive, you can simply make a few registry changes to point to those locations.
Start Regedit
Go to the follow locations and change the path to wherever you copied the source files.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePackSourcePath
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\SourcePath
  the last one might not be necessary
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SourcePath
 now go to run type in sfc /scannow press enter it should run fine

Here is a well illistrated FAQ on broadband
http://www.dslreports.com/faq/toolquestion?text=1

I think you should try two things:

First, assign a static IP/netmask and gateway...DNS

If you still can't access anything...

TWO:  Try another NIC.  you may have a faulty NIC.  Not dead, but really hosed.

Trying a new NIC of any type, wireless, LAN, etc will confirm that TCP/IP is good (or NOT).

I'm betting on the NIC being shot.

Hi tmassa99,

Static address and change of card were two of my original tests (maybe the change of card wasn't as obvious as it could have been in my original post, but "The system is running XP Pro, and connected via a router.  It was wireless, I replaced with a standard card and exact same problem."

I have since tried both static and dynamic addresses, but it would appear that the problem is more fundamental than that

incidentally, before anyone suggests the router, both this (linux) pc and my wireless xp pro laptop work fine

Merete,

Am copying the CD as I write...but not sure really how this helps, as although unable to run unattended previously it did complete OK.  I am considering running setup from the CD over the top of the existing windows, but again not sure if this will actually help, nor if it is going to require a different CD key as it is a different version of windows (i.e. SP2)

Ben

Fixed it!!

F-Secure had left some hidden devices in device manager, under non plug-and-play drivers - one of which was some sort of firewall driver (remember F-secure had been 'sucessfully' uninstalled...)

It now occurs to me I am connected with no firewall, and no antivirus - I'll sort that out then worry about points.  Thanks all for your input!

Further update: Installing Norton Internet Security 2006 caused this to happen again - 2 of the f-secure hidden keys had come back in some way (internet was working when I started the install, but by the time I came to liveupdate, had stopped again).

Disabling the 2 keys (as opposed to uninstalling) brought the internet back to life, and so far after a restart and full system scan, everything is still OK.  My guess is that uninstalling causes something to notice the keys are gone and to re-awaken them so-to-speak, whereas disabling just stops them working.  I would prefer to have them gone altogether so will look into this further; if  I have a definite result I will update again.  F-Secure website just says to remove - uninstall; I think I could have worked that one out myself!

Ben

Hi Ben good to hear your progress is positive.  
Regards Merete