I  have this error when using ping command on a pc  with win xp "Unable to contact IP driver, error code 2?"
139323
This might be due to winsock2 corruption.you can try the following  Solution \n\n\n#How to determine whether the Winsock2 key is corrupted \n\nTo determine if the symptoms are caused by a problem with the Winsock2 key, use one of the following methods. \n\n\nMethod 1: Use the Netdiag tool \nTo use the Netdiag tool, you must install the Microsoft Windows XP Support Tools. To do so, follow these steps: \nNote \nIf you already have Support Tools installed, go to the second procedure in this section. \nIf you do not have Support Tools installed and you do not have the Windows XP Setup CD, go to Method 2. \nInsert your Windows XP Setup CD \nLocate the Support&#92;Tools folder \nDouble-click the Setup.exe file \nFollow the steps on the screen until you reach the Select An Installation Type screen \nOn the Select An Installation Type screen \nClick Complete \nClick Next \nWhen the installation is complete, follow these steps: \nClick Start \nClick Run \nType the following in the Run box \nCommand \nClick OK \nType \nnetdiag /test:winsock \nPress Enter \nThe Netdiag tool will return the test results for several network components, including the Winsock. \nFor more details about the test, use /v at the end of the netdiag command: netdiag /test:winsock /v \n\nMethod 2: Use the Msinfo32 program \nNote Use this method only if you do not have a Windows XP Setup CD and you do not have Support Tools installed. \nClick Start \nClick Run \nType in the Run box \nMsinfo32 \nClick OK \nExpand Components \nExpand Network \nClick Protocol \nYou will have ten sections under Protocol \nThe section headings will include the following names if the Winsock2 key is undamaged: \nMSAFD Tcpip [TCP/IP] \nMSAFD Tcpip [UDP/IP] \nRSVP UDP Service Provider \nRSVP TCP Service Provider \nMSAFD NetBIOS [&#92;Device&#92;NetBT_Tcpip \nMSAFD NetBIOS [&#92;Device&#92;NetBT_Tcpip \nMSAFD NetBIOS [&#92;Device&#92;NetBT_Tcpip \nMSAFD NetBIOS [&#92;Device&#92;NetBT_Tcpip \nMSAFD NetBIOS [&#92;Device&#92;NetBT_Tcpip \nMSAFD NetBIOS [&#92;Device&#92;NetBT_Tcpip \nIf the names are anything different from those in this list, the Winsock2 key is corrupted, or you have a third-party add-on, such as proxy software, installed. \nIf you have a third-party add-on installed, the name of the add-on will replace the letters "MSAFD" in the list. \nIf there are more than ten sections in the list, you have third-party additions installed. \nIf there are fewer than ten sections, there is information missing. \nNote These entries represent an installation with only the TCP/IP protocol installed. You can have a working Winsock and see additional entries if another protocol is installed. For example, if you install NWLink IPX/SPX, you will see 7 additional sections, for a total of 17. Below is an example heading of one of the new sections: \nMSAFD nwlnkipx [IPX] \nAlso, each of the new sections that are created by installing NWLink IPX/SPX start with "MSAFD." Therefore, there are still only two sections that do not start with those letters. \nIf the Netdiag test fails, or if you determined that there is Winsock corruption by looking at Msinfo32, you must repair the Winsock2 key by using the steps in the next section. \nHow to Recover from Winsock2 Corruption \nTo resolve this issue, delete the corrupted registry keys, and then reinstall the TCP/IP protocol. \nStep 1: Delete the corrupted registry keys \nClick Start \nClick Run \nIn the Open box type \nregedit \nClick OK \nIn Registry Editor, locate the following keys, right-click each key, and then click Delete: \nHKEY_LOCAL_MACHINE&#92;System&#92;CurrentControlSet&#92;Services\n&#92;Winsock\nHKEY_LOCAL_MACHINE&#92;System&#92;CurrentControlSet&#92;Services\n&#92;Winsock2 \nWhen you are prompted to confirm the deletion, click Yes \nNote Restart the computer after you delete the Winsock keys. Doing so causes the Windows XP operating system to create new shell entries for those two keys. If you do not restart the computer aft
35533
If you are getting illegal operation errors, I'm assuming you have Windows 98SE, as this is a common occurance with IE and 98.\n\nIf you actually have XP, then I suggest doing an online virus check at one of the sites I've listed below.  Both are great virus and spyware programs as I have both, one on my home PC and the other on my Notebook.\nSecondly, make sure you have all your microsoft updates too.  These are very important. \n- I hope this works.  Good luck.
398927
i suppose u use windows.\nstart->settings->control panel->network connections->local area connection\nopen it, properties->tcp/ip settings
38816
You are using the same IP as someone else on the network. If your at work, talk to you system administrator about it.  If at home, talk to your Internet service provider about some tech support.  I would give you particulars, but I don't know what kind of connection you are using or what operating system in particular.  \n\nYou could go to the Run menu in the start menu and type winipcfg and see if that brings up the IP configuration tool.  Or, go to network neighborhood and click properties and click your adapter and then more properties and config your IP from there.  Though your probaly best off with contacting support.  Sucks but you probaly should ask again and be a little more specific about your connection, your ISP and operating system.  Worst comes to worse, system restore.  msconfig in the run menu and restore unless its XP
107762
that ip address might be a linksys router, for a home wireless network, or some other type of secure server, have you tried to ping it from a CMD promt
299253
It may crash if you take a hammer and smash it...!!??.\n\n\nno,  xp should not crash with pinging a death. \nIf you ping exit, it will end the cmd programe. But pinging death will not crash computer, nor it will close the cmd.\n\nso, there is something else wrong with your computer.\n\n\n\nmuni
925836
You can send a ping request to any device directly connected to the Internet as long as you know it's IP address. If you are sure you know the person's IP address and it still isn't working then it may be that a firewall on your PC (or his PC), or some OS setting, is blocking the request or the response.\n\nNote also that if your friend's is behind some type of proxy server you may only be able to ping that server.
520138
the 999 error is caused by either you being banned from that site witch lasts 24 hours or the servers are down either or not sure witch in your case i hope that this helps you and I am not sure how to get around this promblem other then tring to reset your IP Address Go to start button go down to run type in cmd and then ipconfig &#92; renew\nturn off your computer and turn back on and try again
440053
run-cmd\nnetsend computername or ip address "massage"
347145
It shouldnt be possible...\nTry start run type "cmd" enter, black window up and type "ping www.yahoo.com" enter, if time < 100ms, and no request time out you should be fine.\nCheck cable connect to modem, \ninstall anti-virus software and update it to latest, do full system scan.
628281
You computer can not locate the server due to a network or LAN failure...\n\nXLMan
1131546
Tell us what command you will be used at command prompt.\n\nIf your PC's IP  is assgined by DHCP( thats like DSL modem/router or from Internet service provider),nothing will happen except Internet connection is closed during the period of "reset" activity.\n\nIf your PC's IP is assigned manually, that IP is supplied by Internet service provider,you must set same IP back to get connected to Internet, otherwise you can not reach Internet.\n\nThink about any computer conneted to this PC.\n\nHope this hepls.
997051
No, ping command use for check connctivity in the network.\n\nNet command show all comuter connect in network\n\nStart > run >Type cmd <enter>\n\nC:&#92;>net\nThe syntax of this command is:\n\n\nNET [ ACCOUNTS | COMPUTER | CONFIG | CONTINUE | FILE | GROUP | HELP |HELPMSG | LOCALGROUP | NAME | PAUSE | PRINT | SEND | SESSION | SHARE | START | STATISTICS | STOP | TIME | USE | USER | VIEW ]\n\nC:&#92;>net view\nServer Name            Remark\n\n-----------------------------------------------------------------\n&#92;&#92;A1\n&#92;&#92;A2\n&#92;&#92;A3\n&#92;&#92;AR1\n&#92;&#92;AR3\n&#92;&#92;BDC\n&#92;&#92;PDC\n&#92;&#92;PROXY\n&#92;&#92;SERVER\n&#92;&#92;D1\n&#92;&#92;DBDC\n&#92;&#92;D2\n&#92;&#92;ADHPSERVER\n&#92;&#92;H1\n&#92;&#92;H2\n&#92;&#92;H3\n&#92;&#92;MBSCAN\n&#92;&#92;N1\n&#92;&#92;N2\n&#92;&#92;P1\n&#92;&#92;R1\n&#92;&#92;R2\n&#92;&#92;S1\n&#92;&#92;S2\n&#92;&#92;S3\n&#92;&#92;S4\n&#92;&#92;S5\n&#92;&#92;SW9\n&#92;&#92;VBWORKSTN\nThe command completed successfully.\n\nShow all the computer in network
159996
put in the exact error message in the ms knoledgebase. \nhttp://search.microsoft.com/results.aspx?mkt=en-US&setlang=en-US&q=Driver_IRQL_not_less...+error+on+win+xp
174890
I really need some more details, but I will assume that you do not know if you have a connection or not.  You need to get to "My Network Places", in XP you will find it in the start menu and on 98 and older it should be on the desktop.  Right click on it and select properties.  It should bring up your possible connection, look for "local area connection" and once again right click on it and select properties.  Scroll down till you see "Internet Protocol (TCP/IP)" High light it and click on the button that says properties, this is the area you want.  Make sure everything will choose IP automatically.  It should also tell you if it has a IP address and what it is, if it does and it is on DHCP, go back to the "My Network Places" window again and right click on "local area connection" again, but this time choose the fix option.  hope that helps.\n\nJohn B.
930424
How many IP address do you have assigned to you? If you only have one that might be your problem.\n\nIf you are running your computer through a router then I am afraid I am not able to help you.
479465
Try start run type "cmd" enter, black window up and type "ping www.yahoo.com" (if yahoo is the site you cant reach) enter, if time < 100ms, and no request time out you should be fine.\nTry other time of the day,\nTry the connection with another machine\nCheck the router setting \nCheck if firewall blocking access