Norton Internet Security / Norton AntiVirus

[poppy052]

Yesterday on 10-06-12, a technician came to my house and changed my modem because of an upgrade to my satellite internet. Everything seemed fine until a few hours later I noticed that I had not received any live updates for several hours. I tried to manually update but received error 8921,254 unable to connect to server. I tried the steps the web support page suggested but no success. The funny thing is I have good internet connection, my son's computer which has NIS 2012 installed is updating fine and we both are connected to the same wireless router. I have checked on the forums and can find only two instances of this error. I used the flush dns suggestion, powering down my modem and router. I even downloaded the intelligent updater and installed the latest definitions from 10-06-12 on my computer with my internet connection. I ran live update, rebooted after that and still receive the same error. I would appreciate any suggestions. Thanks

NIS 2012, Windows Vista SP2 64 bit, IE9 Hp dv7

[poppy052]

If someone has this problem later and all they here is cricket's chirping when trying to find a solution on this forum, I will try to keep them updated. I have been on remote assistance 4 hours today and still no solution."They will contact me within the next 48 hours".  Reinstalling 2012, installing 2013, using the removal tool does not solve the problem. The fixit tool states that I am trying to access an invalid server. The only good thing I have going for me right now is that I can download my updates as mentioned in the previous post. When I find a solution, I will post back and let the next poor soul know. Oh and another good thing is I get to practice on entering all my passwords again on my spanking brand new NIS 2012 Identity Safe.

[peterweb Super Worm Eliminator]

Did you see the post about the ethernet drivers causing this issue?

http://community.norton.com/t5/Norton-360/LiveUpdate-error-8921-254-failed-to-connect-to-server/m-p/...

See if you have any recent Windows Updates that may have updated a network driver.

[poppy052]

Thank you Peterweb, There is someone else on the forum with a similar problem and now I think it is a Hughsnet issue. I am going to try to contact them when I get home from work. Thanks again

[peterweb Super Worm Eliminator]

---

poppy052 wrote:

Thank you Peterweb, There is someone else on the forum with a similar problem and now I think it is a Hughsnet issue. I am going to try to contact them when I get home from work. Thanks again

---

Please keep us up to date in case others come here with the same problem.

[Pete_Pirate · Accepted solution]

Ureka! After a long waste of time with Hughes I was playing around and here is the answer:

It is a HT1000 Modem

1, Logon to the Modem with your browser http://192.168.0.1/cgi-bin/index.cgi?Command=1

2, Go to Web Acceleration Control

3, Dissable Web Acceleration and submit.

I saw a very small drop in upload speed with this off and an increase in download - and NIS works just fine now.

Called back HN to tell them what the fix was and I got another tech in "advanced support" who informed me that "Thats the usual fix" ##!!?? why did I spend an hour on the phone with another guy who had no answers?

[poppy052]

Hey Pete, That did the trick!  Earlier today I posted the question on the Hughes Community forum and one of the forum members suggested that sometimes disabling the web acceleration control would help in accessing some servers. He also stated that it should be temporarily left off. I posted another question about that being a workaround solution in hopes one of the Hughes employees will respond with some kind of a fix for the new Gen 4 customers who are having this problem. I told them about your issue also so they will know that it is not an isolated case. Thanks for posting back and letting us know.

[peterweb Super Worm Eliminator]

Thanks for coming back with the solution.

This may help others with similar problems.

[poppy052]

Just a quick update. If you are a customer of the new Gen 4 with Hughesnet and have been getting this error with Norton, the Hughes engineers are aware if this issue. Hopefully there will be a fix soon.