HX50 Web Acceleration Status "Not Operational"

Your advanced diagnostics may narrow this down to Web Acceleration [I] or Web Acceleration [N]. The former is the modem telling you it's got a problem, the latter is the NOC telling your modem THEY have a problem. In the vast majority of cases, it's going to be a NOC problem - and completely out of your control.

Don't know if the HX-series has the capability enabled. But on my HN-series, the issue can sometimes be corrected by a turbo page teardown. To check, turn your browser to the advanced statistics page and look at the directory in the left hand column. If Turbopage is listed, click it. Then click Advanced Cfg. Select Auto, then click the Tear Down button, then the Continue button. But this only works if the NOC has more than one WebAccel server address - and neither you nor I know that. So there's no guarantees that this will work at all in your situation. Can't hurt anything to try though.

//greg//

Hmmmm, I've never seen that. The only .bin files I'm aware of are related to the actual modem firmware. There's one used in the fallback updater too, but that's kinda the same thing. Either you've come across an obvious difference between my HN firmware and your HX firmware, or there's a glitch in your own. But I'm not in a position to say which, that should fall on your provider. Short of that - if the modem is otherwise working - put this back on their doorstep.

As far as your provider's response, lousy weather at the NOC can affect your end too. But having been a satellite controller, I know they're supposed to increase their EIRP to punch through bad weather, thus minimizing the impact to the subscriber network. That said, the NOC operators could have been asleep at the wheel. In short, bad weather at the distant end SHOULD not have been the reason for your issue - and it should NOT have rendered Web Acceleration "Not Operational". Plus - if your issue persists - it wasn't the reason in the first place. HPEP server issues at your provider is a more likely reason.

So that brings us to the question; do you still have this Web Acceleration problem?

//greg//

It's just wierd that the 7000 I had never seemed to be down as much as this Hx is.

James, I sent you an email.

Quick question, If my "pol" is not set correctly will that cause it to give this error?

If the polarisation is not set correctly the receive path at the site is vulnerable to downlink interference from the cross-pol transponder.  This interference might be continuous (e.g. SCPC or TV carrier) or intermittent (e.g. TDMA carrier, occasional use TV tranmissions etc) or non-existent (transponder band unused at the moment).  The effect would be increased errors on the receive path to the remote site.

Regarding the uplink transmit path from the remote site, moderate cross pol error won't have any significant affect on the wanted transmissions to the hub.  Even +/- 45 deg error would only introduce -3dB loss, which might well be taken up by power control. The problem with even small uplink cross-pol error (say +/- 4 deg) is the interference it causes to other people - causing intermittent bursts of errors in other people's services every time this site transmits a TDMA burst.

The polarisation of the feed needs to be checked and if necessary adjusted during initial site commissioning. For W3A the polarisation angle will be about 3.5 deg further clockwise than calculated and the giant scale on the back of the 1.2m dish enables a reasonable initial setting. You can also use an accurate inclinometer placed sideways across the BUC or LNB body.  

Would errors on the remote site receive path cause a problem with "Web Acceleration" software status ?  I don't know.  I suggest BlackSheep5 keeps in communication with the hub to resolve this issue.  In my case the "Web Acceleration" software status went to normal about 30 minutes after power on.  Maybe the hub need to reset something.

Best regards, Eric.

Here is some information intended to help anyone with a Prodelin dish with a mode matched feed (Feed has "505" marking on the top of the horn throat) and a giant circular polarisation scale behind the dish.

On the throat of the horn is a "505" marking.  You must always have the 505 directly away from the feed arm and the fat lump, underneath, towards the feed arm.

You may adjust the polarisation to any required angle (though full 360 deg and for both Horizontal and Vertical) using the scale behind the dish.



If your nominal RX polarisation is Vertical then you may turn the dish by 90 deg and then go backwards by the adjustment amount.  The adjustment direction must be correct (clockwise is positive while facing towards the satellite) but the numerical scale markings may need to be ignored.  Think about the amount of adjustment and use the tick marks to count the amount.  The numbers may be backwards.

These new design Prodelin dishes give superior cross-pol performance to all other single reflector antennas*, but only if you follow these assembly instructions above.

Best regards, Eric.

* except for ERA diamond antennas which use the same mode matched feed.

ya woo hoo

Web Acceleration Client Error (535) - Promise URL Expired

The Web Acceleration Client cannot process this request because a promise URL expired. This error is rare and typically due to a misconfiguration of the prefetch timeout value and/or the promise list timeout value in the Web Acceleration Client settings.

Did all these error messages appear at the same time ?

Re: Terminal receive error (603)

If your terminal is having problems receiving the signal, it is possible that severe weather (i.e. very heavy rain) is the cause, at either the teleport or your site.  Light to moderate rain should not cause an outage. The HX system adapts to temporary fading, and outages should only happen during the most severe rain or if your dish is mispointed so you have little link margin in clear sky conditions.

The message, relating to the error code, fails to mention and emphasise these possibilities:

Intermittent F connectors due to wrong assembly (pin not long enough, braid not contacting, not screwed in properly - firm finger tight is ideal, copper fragments).

Degraded F connectors, pin and cable due to moisture (not sealed and moisture + DC power causes severe corrosion over a few weeks, possibly for some distance down inside the cable.)

Dish mispointed due to wind, vandalism etc.

Note that for a few days either side of the equinoxes you will experience daily sun outages for several minutes as the sun appears to pass across behind the satellite.

Is your receive SQF steady ?  Does the RX flicker or appear to fail briefly and intermittently ?  Are you near to any possible source of intermittent interference - neon signs - air conditioner switches - radar ?

Do the error messages 504 and 535 appear to be related to particular web sites or page content ?  I am particulary concerned that the Google adverts on my forum pages may cause such errors as I am getting a number of 404 errors in my server log just from Hughesnet IP addresses ?  Are you using the BW Turbo acceleration software on your PC ?

Best regards, Eric.

Quote:


The above looks interesting and I will speak tomorrow with BW about it. If you do spot some pattern and can somehow make the error reliably repeatable, do tell us.

One thing I forgot...
Why did your terminal start working again after 2 days ?   If the RX suddenly came good again I wonder if this was this due to a bad LNB F connector. The centre pin should be between 6.35 and 9.53mm long, as measured from the face of the dielectric.  The pin will normally stick out 1.1 to 3.4mm proud of the surrounding rim. Ref: SBCA F connector dimensions - specification - best practices

Having the centre pin too short or too long is a common  fault.
 
Best regards, Eric.

This just in.

Web Acceleration Client Error (509.2) - Upstream TCP Receive Failure (Web Server)

The Web Acceleration Client detected a TCP connection failure while receiving data directly from the web server or proxy server. Retrying the web page may correct the problem.


It stopped working because something was implemented on their end that was suppose to auto download and reboot the modem.

But for some reason it messed up and when mine rebooted I had a sig of 23 and it was decommissioned. I had to manually change my symbol rate to 10 from 12 and I instantly got a sig of 94 then it kept getting stuck on "Downloading files" for hours.


Anytime I can get web accl errors I just clicked on this site and I got one, I hit refresh then it worked.

Web Acceleration Client Error (504) - Suspected Satellite Link Outage

One tab in Firefox, trying to use google search.

Quote:


Thanks for all the help. Currently I am plugged straight into the modem and have one tab open trying to view a Youtube video and it's taking forever.

Web Accleration - Not Operationa
This state indicates that your terminal is not able to bring up the Web Acceleration connection. This may be due to a problem in the Receive or Transmit link or in the BentleyWalkerHX50 Network Operations Center.

If you have two specific DNS specified in your PC then one or both of these may be invalid.

Set your network interface to "Obtain DNS automatically" and repair the PC ethernet interface.

Find the tiny network icon in lower right corner of your screen.

right click the mouse
status (or repair )
properties
scroll down to TCP/IP
properties
Select "Obtain DNS automatically"

Best regards, Eric.

Good morning sir,

As per my email sent to you yesterday:

--
Do you have access to msn/Yahoo/live messenger? If so my ID is included in the mail (can be used for all). I would like to run through your outstanding issues and update accordingly. Whilst Satsig is a truly valuable resource for advice much of the diagnostics are down to speculation and with our input I am sure we can resolve all outstanding issues.
--

I am wholly confident that we can replicate these issues during monitoring directly with you and establish the nature of them. Both configured DNS on this platform are operating without issues so we need to look further along the chain.

Please kindly contact me at your convenience to discuss further.

Regards,

James - Bentley Walker.

Hi,

Failed to recieve the email please could you kindly resend it along with your chat ID and I will add you from my end. Feel free to send your ID as a private message on here.

Regards,

James

I am having the same issues with my HX50. For awhile it was disconnecting all the time, apparently the modem was "hacked". That was fixed, but I still have the Web Accel issues pretty constant. I've had all the errors BlackSheep had. Getting to the point where my company is shopping elsewhere. I've sent at least two emails to the BW technical support, with no replies at all. Love those guys.

Good Afternoon Sir,

I would like to apologize in advance for the difficulties you have faced in contacting our support team and also with the difficulties you have faced with what is normally a very stable system. Mr. Walker has assigned me to your case to ensure you receive a speedy resolution to your problem. I have performed a search of our database for your email address and have been unable to locate your record. If you can please supply the ESN number so that I can proceed with troubleshooting your site.

Also; below are the recommended means of contact for the Bentley Walker support team:
Main Email address: support@bentleywalker.com
Telephone number: +44 23 9231 1118

We also provide live support via MSN Messenger, my direct MSN Messenger contact is below:
gary_del@hotmail.com

We also operate a ticket system (https://80.177.108.80/sitehelpdesk/user/log.asp), I will discuss this further with you and provide login details once we have resolved your initial problems.

Attached to an email to you please find the master contact list which details contacts for each department within Bentley Walker.

I would like to apologize for any inconvenience this issue may have caused you.

Best Regards,

Gary Delaney, Bentley Walker Ltd

Hi

This is BW we have actually found some issues on the Hughes Turbo servers that were causing errors, this has been rectified and customers are reporting vast improvements,. what I suggest you do is check your lat and long settings are accurate and if so then go into the installation menu and range your system , please after you have done this let us know if your seeing improvement if not please email me

Anthony@bentleywalker.com