Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ping failure on satellite 5

Status
Not open for further replies.

dr186737

MIS
Feb 19, 2004
4
US
I have 2 machines, 1 XP and 1 Win2k. They are both connected to a router and then to a satellite connection. If I ping an IP with the XP machine it succeeds every time but if I ping the same IP with the Win2k it gets intermittent failures, maybe 1 reply out of 4. Any idea why this would be, and what could be modified on the win2k machine to correct it?
 
With ping, the command line parameter can be adjusted for the TTL, your wk2 ping is probably timing out due to the time delays.
 
Average latentcy is about 1500 to 2200 msec on a satellite connection. W2K machines default to a lower wait time on the ping command. When pinging accross a satellite connection, I always use a wait time of 3500 msec.

ping 10.0.0.1 w- 3500

As a side note, certain applications that work great on a LAN, will die on a satellite connection due to the latentcy. Applications with allot of turns (chatty) will cause numerous retransmits and lead to an overall application slowdown.
 
A star from me for you both. That strikes me as the non-obvious solution for the original poster.
Thanks to both.

Bill Castner
 
Bill, I gave you a star... the star makes up for at least one of the posters, where you spend a good bit of time, and they never come back. Thanks
 
technome,

It is not necessary, but I appreciate the thought. I honestly thought you and robertjo24 nailed this issue.

But honestly, the satellite side of things worries me. It just does not act the way any other broadband connection works.

Best wishes, (and thank you),
Bill Castner
 
Yes satellite delays add another dimension to broadband.
Years ago my friend was in charge of a world wide network which used satellite, even for the mainland US. In the end the satellite switching delays caused so many problems they had to switch to extremely expensive T1 lines. My friend also had to deal with the added delay of the radio transmission between the main office to satellite/satellite to remote offices (speed of light), which though small still caused problems. His office only tried the satellite route because 25 years ago T1s were astronomically expensive
 
I appreciate all the info. I was trying to find out why Citrix would fail on a satellite link with w2k and not XP. I understand the wait time but the wait time is not the same as ttl, is that correct? If so, I know I can set a registry entry for TTL but do you know if there is one for wait time?
 
The TTL is refers not only to ping but DNS, multiprocesing, amongst other thing. As far as how XP handle the extra delays as to TCP/IP packets, XP has a more robust TCP/IP stack with more parameter which are adjustable through the registry as a default. Chances are WK2000 can handle the same parameters, but off hand I do not know them



Search on google for tcp/ip packet delay or tcp/ip packet delay satellite
 
Thanks again for all the help. I shall see what I can do with this.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top