SatSig topic:

HX50 Hughes NSS6 Timeouts

(Read 2970 times)

Jun 16^th, 2010 at 6:17pm

I've recently setup two systems (with two more in the works) connected through a load-balancing router that have website timeout issues and Skype dropped calls. The systems are all HX50 with 1.2M Prodelin dishes, 2048 down, 256 up, 20:1 contention ratio connected to NSS6 near Qalat, Afghanistan. Both of my systems maintain 92-93 signal quality and I can download 1.0-3.6 Mbps pretty much any time of the day.

The problem my users have (26 users sharing 2 connections) is that most websites will "timeout" and some are completely inaccessible (wikipedia). I've adjusted DNS timeouts, browser timeouts, and set bandwidth restrictions on all users. My ping reports look like this:

Ping statistics for 74.125.77.99:
Packets: Sent = 150, Received = 149, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 818ms, Maximum = 3746ms, Average = 1432ms

That report is using 512 byte pings.

I'm working with Hughes (via ATS) to try and resolve the situation, but I'm becoming frustrated with the service. Last time I had a BW Starpro 2048/512 system with 35 users and never had this problem. I'm not sure that bandwidth is the problem now, because I can download quickly even with the problems occuring. Any ideas?

Jun 16^th, 2010 at 6:41pm

I would recommend that you continue to work with the Hughes hub (via ATS). Keep on sending them information. If a particular web site can be identified that always times out and maybe another which is never accessible then tell them this and offer to try to access those sites while they watch from their hub end. If they can diagnose the problem then it might solve everything.

It is possible to speculate about a bad DNS server, faulty cache/accelleration computer, misconfigured router, etc., but really the best thing is to get the people responsible (at the Hughes hub in USA?) to resolve the issue by diagnosis.

Best regards, Eric.

Jul 16^th, 2010 at 3:49pm

we to using NSS6 for our HUB. basically this might be network congestion or latency issue. basically hughes system give a priority based on application. default priority for ping fall on 4. since you send continues ping like realtime traffic, your ping might be consider as sensitive latency issue and priority 4 cannot afford that thing.. for a download yes you can download because of effect PEP spoofing tech.