marcov wrote:(if you know that it is local, you can reduce the timeout with -w <ms>)
Thanks. I had tested that before and saw no effect. Now I retried, and got it to work (no idea what was different...). Interesting:
- without any wait interval (no "-w"), the answer is "host cannot be reached", but the modem responds "no packet lost"
- with a -w 5000, the answer is again "host cannot be reached", "no packets lost"
- with e.g. a -w 500, the answer is "request exceeded timeout", and the modem says "100% of packets lost"
The actual messages will look different, this is my translation - I am running an Italian Windows version.
Based on these observations, I would recommend to use cmd.exe /C ping -w 100 -n 1 NameOfLocalComputer
. If speed is an issue, -w 10
or even -w 1
If the other machine is online, the answer is for all
variants, including a "-w 1
", roughly like this:
Code: Select all
Esecuzione di Ping TheOtherNotebook.blabla.telecomitalia.it [192...] con 32 byte di dati:
Risposta da 192...: byte=32 durata<1ms TTL=128
Statistiche Ping per 192...:
Pacchetti: Trasmessi = 1, Ricevuti = 1,
Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 0ms, Massimo = 0ms, Medio = 0ms
However, "-w 0" reports a "general error".