Wings - ok, I see. I think this is a classical gateway lag. Has not so much to do with the transmission speed, but with the time the data is "relaxing" somewhere in a router chip.
And yes, ping is a good idea to check the real lag between two machines. ping.exe is an msdos command. you may run it from within blitz:
Execfile "command ping 192.168.0.3"
replace 192.168.0.3 by the LAN ip of your 2nd machine.
This will perform 4 pings (note "ping" was used to check for enemy submarines once upon). Ping is a standard service that in theory every internet client or server supports. It is used to check if the distant machine is alive. It's like "hey, are you there?" and the pinged machine should answer "yep, I'm here!". The time the answer takes will be measured.
Ping became a bit unpopular because it was used several times to attack servers, therefor some strict security suites overreact when pinged.
And yes, ping is a good idea to check the real lag between two machines. ping.exe is an msdos command. you may run it from within blitz:
Execfile "command ping 192.168.0.3"
replace 192.168.0.3 by the LAN ip of your 2nd machine.
This will perform 4 pings (note "ping" was used to check for enemy submarines once upon). Ping is a standard service that in theory every internet client or server supports. It is used to check if the distant machine is alive. It's like "hey, are you there?" and the pinged machine should answer "yep, I'm here!". The time the answer takes will be measured.
Ping became a bit unpopular because it was used several times to attack servers, therefor some strict security suites overreact when pinged.