|
|
| SatSig Topics Index › HughesNet and Hughes HX VSATs › web acceleration client error [506] |
SatSig topic: web acceleration client error [506](Read 9393 times) |
|
Oct 19th, 2008 at 1:48pm
just got dish up worked good until i tweaked it for better signal now i get a web acceleration client error [506] when there more than one person it the system is a bw hn7000s i am in mosul iraq the signal degraded from 89 to 73 so i tweaked it back to a strong 94 then the problem with error this is what it shows on the advanced html screen can you help Network Time: SUN OCT 19 14:18:04 2008 ------------------------------------ Adapter Main Statistics: ------------------------ Signal Strength.............. 93 Stream Msg-Ackd/Nakd........ 161891/247 Flags............... 0x00001500 NonStream Msg-Ackd/Nakd..... 231/0 UpTime (d:h:m:s).. 000:05:10:09 Aloha Starts................ 231 WakeUp Aloha Starts.......... 0 Ranging Starts.............. 0 Transport Alarm Bit.......... None Frames Received............. 1610782 Addresses Open............... 7 Frame Errors: CRC/Bad Key... 0/0 Carrier Info........ 007:E:1386 Miscellaneous Problems...... 151 Rate Code........ 256k 1/2 (S) No Receive Outroute Lock.... 15 Inroute Group................ 1 No FLL Lock................. 396 Inroute...................... 0 No Network Timing Sync...... 0 IQoS ID...................... 60283 Rate Code Selection: Selected the highest available rate Ranging Reason: Ranging Done Inroute Group Selection: Not getting IQoS Maps or IQoS value is not in map Receive Status: Receiver operational. ( RxCode 5 ) Transmit Status: Transmitter ready. ( TxCode 8 ) |
|
Oct 19th, 2008 at 3:32pm
I also note the last line in the 2nd column of your Statistics page is absent. Do you know whether or not you're supposed to be on a DVB-S2 outroute? That missing line suggests you're currently receiving DVB-S only. //greg// |
|
Oct 20th, 2008 at 6:09am
i domt know if i should be on s2 or not i will try and check but this is what it shows on the screen Inroutes Configuration FEC Rate Inroute Type Allowed Inroute Symbol Rates 64K 128K 256K 512K 1024K 2048K 1/2 Non-OCM Sequential Non-OCM Turbo OCM Turbo 2/3 Non-OCM Turbo OCM Turbo 4/5 Non-OCM Turbo OCM Turbo i dont know much about internet satellites so please bear with all the questions i have thanks allen |
|
Oct 20th, 2008 at 11:26am
------------------------------------ Network Time: MON OCT 20 12:05:11 2008 ------------------------------------ NOC Diversity : DISABLED (Not Configured) Current NOC/Outroute : HOME/PRIMARY Last Forced Cmd Status : NONE Last NOC Switchover Reason: NO REASON PRIMARY SECONDARY -------------- ------------ NOC ID: 1 1 Satellite Channel Frequency: 13868 (x 100Khz) 16367 (x 100Khz) Receive Symbol Rate: 30000000 Sps 30000000 Sps Framing Mode: DVB-S DVB-S Current State : NORMAL Spacelink Status : GOOD Last SHM Reason : TX FAIL Rx Sync : True Latest SQF : 92 Average SNR : 91 SQF Threshold : 1 Current Poll Loss : 0 Poll Loss Threshold : 10 Last Num Poll Lost : 0 Down Hold Time (sec) : 60 Up Hold Time (sec) : 30 Max Recov Time(sec) : 90 SQF Samples : 92 92 92 91 92 Inrt Poll Loss Hist : 0 0 0 0 0 0 0 0 0 0 0 Tuner Monitor Statistics: ------------------------ Tuner is Primary: YES Lock lost on primary Rx: 0 Lock lost on secondary Rx: 0 Number of Rx switchovers: 0 Attempts to tune to primary Rx: 0 Attempts to tune to Secondary Rx: 0 Lock lost on primary Tx: 0 Lock lost on secondary Tx: 0 Attempts to tune to primary Tx: 0 Attempts to tune to Secondary Tx: 0 Transmitter not responding: 0 Ranging Failures: 0 |
|
Oct 20th, 2008 at 11:52am
Ordinarily I'd next have you tell me the ACP/isolation validation numbers, but I noticed you used the letters BW in your text. I've been told their NOC is not equipped with this capability. So you'll have to contact Bently-Walker direct, and ask them to check the isolation on your inroute. While you're waiting for a response from BW, we can move on to the TX/RX Error statistics and Diagnostics Codes. Browse back to https://192.168.0.1/fs/advanced/advanced.html and open Transmitter/TxMonitor. Look at Total Tx Outage Time. Below is a list of the TX Error codes that constitute the cumulative downtime. Note the error codes that occurred most often, and how much of the Total Outage was attributed to those codes. Similar info can be found under Diagnostics/Expert/General/Diag Codes. By themselves, they mean nothing. But one more line down on the directory tree is the Diag Code Analyze. Copy and paste any codes (other than 0000-0000-0000-0005) you want read into the Analyzer. The short side to the Diag tools, is that it's not a very deep archive - none are older than 3 hours. If you want a 24 hour snapshot of the statistical collection, look at Diagnostics/Hourly History. Not that looking at the error or diagnostic codes will in itself fix anything. But they're clues that might lead us into the right direction. Oh, one other thing. Many of the statistics unfortunately zeroize when the modem is restarted or powered down. This is one of several reasons to keep the modem running 24/7. With a few statistical exceptions, the longer the modem runs uninterrupted - the more diagnostic data is available. //greg// |
|
Oct 21st, 2008 at 6:30pm
bw says i just exceded the limit is why the error message |
|
Oct 21st, 2008 at 7:34pm
thanks usn Well, the explanation is not consistent with the symptoms. But if you're satisfied with their response, that's all that counts.bw says i just exceded the limit is why the error message //greg// |
|
Email me:eric@satsig.net |