Saved Bookmarks
| 1. |
Solve : Dos newbie? |
|
Answer» *Smack head* *Smack head* http://www.microsoft.com/downloads/details.aspx?familyid=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=endang thats got a lot of tools and they are all command line?Quote from: macdad- on February 03, 2009, 12:41:22 PM dang thats got a lot of tools Many of them are. awesome, gotta download this. and thanks for the link Quote from: Dusty on February 01, 2009, 11:09:49 PM Flux - Welcome to the CH forums.dude thanks for the link. i really appreciate your HELP. im sure these would do.Quote from: macdad- on February 02, 2009, 06:27:04 AM PING -n 1 -w 1000 1.1.1.1 >nul It is actually a very bad practice to ping an IP address that you don't administer or have control over. Besides not being polite (depending on how it is used and how often it could be considered a denial of service attach which I know is not your intent), it is not reliable. For example, I assume by your example that your are expecting 1.1.1.1 to not respond to your ping (ICMP echo request). If the owner of that IP decides to one day enable ICMP echo for that IP address, then your command above would only pause for a few milliseconds. It is much better to ping something that you have control over, such as localhost, or 127.0.0.1. You can use Code: [Select]ping -n 2 localhost >NULto pause for about 1 second (the number should be n+1 where n is the number of seconds to pause because the 1st reply should be INSTANT, and the others will wait 1 second by default). I hope nobody takes offense to this ... just trying to point out a better way. good point |
|