could someone tell me how to send ping of death through windows xp?
407540
why so you can nuke someones computer
335308
you need a Router that will do the trick. Talk to your local PC guru use yellow pages they can help not very expensive
314449
Try here:\n\nhttp://www.annoyances.org/exec/forum/winxp/r1010197614\n\nor here:\n\nhttp://www.pcguide.com/vb/showthread.php?p=267392#post267392
138463
Just go to the command prompt (on windows XP just type CMD on the START > RUN) and type ping website.com . you will get the IP address. or You can go to dnsstuff.com which can do a whole lot of other things than just getting the IP address.
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.
1032675
You could ping it offcourse. Just type "ping hostname" into the console/prompt.
468286
use this link for microsoft\n\nhttp://www.microsoft.com/windowsxp/using/mobility/getstarted/remoteintro.mspx
1031645
through a wireless network connection.go to control panel -wireless network and follow the instructions.Good luck!
1175593
You need fax modem in your computer. in windows xp just enable software from add/remove and then you can send and receive faxed in windows xp.  if you don't want to use windows faxing service then use winfax, it's a best software.
749887
download this software, it repairs ur TCP and IP,\nIts about 400 kb\n\nhttp://www.download.com/XP-TCP-IP-Repair/3000-2094_4-10410930.html
531184
net send is an xp-only command, so the sender can send it, but the receiving 98/95 box cant see it.... (so 'of course you can' is correct, but not helpful)
550294
Description\nThe /usr/sbin/ping command sends an Internet Control Message Protocol (ICMP) ECHO_REQUEST to obtain an ICMP ECHO_RESPONSE from a host or gateway. The ping command is useful for:\n\nDetermining the status of the network and various foreign hosts. \nTracking and isolating hardware and software problems. \nTesting, measuring, and managing networks.\nIf the host is operational and on the network, it responds to the echo. Each echo request contains an Internet Protocol (IP) and ICMP header, followed by a timeval structure, and enough bytes to fill out the packet. The default is to continuously send echo requests until an Interrupt is received (Ctrl-C).\n\nThe ping command sends one datagram per second and prints one line of output for every response received. The ping command calculates round-trip times and packet loss statistics, and displays a brief summary on completion. The ping command completes when the program times out or on receipt of a SIGINT signal. The Host parameter is either a valid host name or Internet address.\n\nBy default, the ping command will continue to send echo requests to the display until an Interrupt is received (Ctrl-C). The Interrupt key can be changed by using the stty command.\n\nBecause of the load that continuous echo requests can place on the system, repeated requests should be used primarily for problem isolation.\n\nFlags\n\n-c Count Specifies the number of echo requests, as indicated by the Count variable, to be sent (and received). \n-w timeout This option works only with the -c option. It causes ping to wait for a maximum of 'timeout' seconds for a reply (after sending the last packet). \n-d Starts socket-level debugging. \n-D This option causes a hex dump to standard output of ICMP ECHO_REPLY packets. \n-f Specifies flood-ping option. The -f flag "floods" or outputs packets as fast as they come back or one hundred times per second, whichever is more. For every ECHO_REQUEST sent, a . (period) is printed, while for every ECHO_REPLY received, a backspace is printed. This provides a rapid display of how many packets are being dropped. Only the root user may use this option. \n\nNote: This can be very hard on a network and should be used with caution. Flood pinging is only permitted by the root user. The -f flag is incompatible with the -i Wait flag. \n-I a.b.c.d Specifies that the interface specified by a.b.c.d is to be used for outgoing IPv4 multicasts. The -I flag is an uppercase i. \n-o interface Specifies that interface is to be used for outgoing IPv6 multicasts. The interface is specified in the form 'en0', 'tr0' etc. \n-i Wait Waits the number of seconds specified by the Wait variable between the sending of each packet. The default is to wait for one second between each packet. This option is incompatible with the -f flag. \n-L Disables local loopback for multicast pings. \n-l Preload Sends the number of packets specified by the Preload variable as fast as possible before falling into normal mode of behavior (one per second). The -l flag is a lowercase l. \n-n Specifies numeric output only. No attempt is made to look up symbolic names for host addresses. \n-p Pattern Specifies up to 16 'pad' bytes to fill out the packet you send. This is useful for diagnosing data-dependent problems in a network. For example, -p ff fills the packet with all 1's. \n-q Specifies quiet output. Nothing is displayed except the summary lines at startup time and when finished. \n-r Bypasses the routing tables and sends directly to a host on an attached network. If the Host is not on a directly connected network, the ping command generates an error message. This option can be used to ping a local host through an interface that no longer has a route through it. \n-R Specifies record route option. The -R flag includes the RECORD_ROUTE option in the ECHO_REQUEST packet and displays the route buffer on returned packets. \n\nNote: The IP header is only large eno
309302
ok, all you do is go onto command prompt and type in "ping xxx.xxx.xxx", wer xxx.xxx.xxx is watever your friend's ip address is. Then, it will come up with a whole bunch of info and stuff.\n\nalso, if you type in "ping/exe", it gives you a key to some of the acronymes
1053172
First of all, don't be alarmed by the behaviour you are experiencing - what you experience is normal by the symantics of the commands you executed.\n\nTo restore your ping executable to what it was, I'd suggest you try reinstalling your tcp/ip stack, or copy the ping executable from another friend's computer and stick it in the system32 directory.\n   If you chose the former suggestion (reinstalling your tcp/ip stack), here is a guide from the microsoft website: http://support.microsoft.com/?kbid=299357
520268
Am assuming your using XP \n\n1. Install a firewall like ZoneAlarm Wireless. This protects you from inbound and outbound access, not just your brother. :D\n\n2. Get SafeXP from theorica.net and turn-off your sharing and other unsafe features of XP.  This way you can access him, but he can't access you. Sweet! :D SafeXP is, well... safe and free. :D no strings attached.
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
433246
try kill copy, its good, specially for use over a network.\nu'll find it here....\n\nhttp://killprog.narod.ru/killcopye.html