World of Warcraft DC's using Verizon Security Suite - fixes?

[Soupy1]

  I am a new Verizon Fios customer and when I originally had the service installeda couple weeks ago,  I did not install the security suite right away.  I was using Norton 360 (Comcast) on my desktop and Windows 7 security services on my laptop.  All was working well in terms of internat access, speeds, and WoW performance. 

  I then proceeded to install the security suite on my desktop and laptop and now WoW DC's after approximately 5 minutes whether I use direct connect (desktop) or wireless (laptop).  Did not have any issues before installing the security suite.  Turning off the features I have access to in the menu's does not help the situation.  Using my laptop on a DSL wireless network at work location is fine with no disconnects. 

  If I am running the Ventrilo client software it drops connection as well and I have to close and relaunch it to get it working again.  The DC and Ventrilo issue happen simultaneously.  The DC's occur even without Ventrilo ruunning.

  Were do I begin as I dread calling support and get pointed to Mcafee and Blizzard when the issue seems to be related to the Verizon router/fios services and probably Mcafee interaction.  Also what is the "cleaner" program to remove Mcafee from my system?

Thank-you in advance for your constructive input.

[daybyday1]

Soupy,

I do have VISS installed and use it now, however I think I will now uninstall it. Husband does not want me to do the router to router because he has his laptop and xbox special ports open and doesn't want to have to go through that again.

so my options are

1) remove VISS

2) cancel FiOS internet and go back to Comcast (Where I never had any problems)

3) Keep things as they are and hope Verizon/Actiontec does a fix.

4) Stop playing MMO's? .. .hrms this really isn't an option for me 😞

[Soupy1]

  Ran my test this evening without reboot.  Didn't DC until we started our raid.  I reset router and rebooted PC and got only one DC.  This occurred when I was just flying (no raid activity) and I was moved to another channel in Ventrilo.  I notice one TX error in the router stats.  Otherwise system ran OK.

  So it appears under the current setup, I have to reboot the secondary router before each raid and things pretty much work.  Not a very good bandage.  I do have some data on the router in terms of config, addresses, etc.  I'm not an expert at networking , so not sure if a setting can be tweaked.

  Unless there is any insight on this, my next step is to do a restore point before VISS and see what happens.  I am also going to look into Fios/Battle.net issues from the WoW forums and see if I can learn anything.  Not sure when I will do the restore - this will just be a windows restore - not an image or backup restore.

[EpicFail1]

I was having te same issue with another MMO.

Are you having corrupted downloads on files over 10MB? Try downloading large files from MS or Java SDK.

It seems like your ONT could be bad

[Daliddar]

I think this is something that Verizon did, I am having the same issues. My problem started back in January so I have there tech come to the house and they checked my router and told me it was my computer. So I canceled my account with Blizzard and saved some money and built a new computer. Got my new computer built went from a XP system to Win 7 even. Reactivated my account about 3 weeks ago and I still have the same issues. I have since taken the steps that have been advised on here I even opened every port on my router with no luck. My DC's happen anywhere from 5 minutes to 20 minutes after I start playing.

[Soupy1]

---

@Daliddar wrote:

I think this is something that Verizon did, I am having the same issues. My problem started back in January so I have there tech come to the house and they checked my router and told me it was my computer. So I canceled my account with Blizzard and saved some money and built a new computer. Got my new computer built went from a XP system to Win 7 even. Reactivated my account about 3 weeks ago and I still have the same issues. I have since taken the steps that have been advised on here I even opened every port on my router with no luck. My DC's happen anywhere from 5 minutes to 20 minutes after I start playing.

---

  Are you running the VISS (Verizon Security from Mcafee)  or have you ever installed it on your computer?  Just curious since that's when my problems "seemed" to start.  

    I'm at a loss until I get some feedback as the double router solution appears to control whatever is causing DC's, but I don't know why and this would help determine where the problem lies.  I do believe the problem is either marginal signal/hardware tolerance/setting.  I don't think it is server hopping etc.. in my case.

  When my system was installed - the original port at the pole was bad (low to marginal signal) so I think the installer used another one (he said there were 4).  I also had a red light condition that disappeared (not sure exactly what it was and he said they usually ignore it).  All in all he reused my directv cables (spliced them) as he said they were better grade than what he would install.  Initially I had to reset STBs on occasion due to lockup but that has since gone away.  I also had trouble using remote DVR to one of my STBs which also required a reset.

  When I spoke to Verizon tech support they suggested I run an ethernet cable from the ONT to the router and have Verizon activate the Ethernet port just to see if my problem goes away.  Problem is I would interfere with the TV portion in terms of VoD and guide information so I am reluctant to do this.

Next options:

  1.  Hopefully get feedback on results so far

  2.  Do a system restore from safe mode on one of my computers (both had VISS which I removed) and try to run using normal setup  (not sure system restore will provide a clean environment)

  3.  Turn on an older computer I have with WoW installed (mothballed atm), update it etc...  and see what happens or set up an external drive with clean operating system and fresh WoW install.

  4.  Try the ethernet port on ONT

  5.  Talk to tech support (Verizon and possibly Actiontec)

        (I feel this is such a specific issue that I won't get resolution through onsite support, but that is my last option.)

[spacedebris]

This may also be a Moca issue. There have been reports of some connection issues that are tied to the Moca system. There doesnt seem to be a rhyme or reason to it. But there have been some that have found that running Ethernet from the ONT to the router for the internet connection has solved the issue.

This will not effect the VOD. You will still have the coax run to the router, you simply will be using eithernet for the internet portion.

Now since you are seeing an improvement using another router, this is probably not the issue. But you did say that the router has been replaced, right? And it seems you have checked just about everything else, so it looks like grasp at straws time. This may be another thing to look into.

[Soupy1]

---

@spacedebris wrote:

This may also be a Moca issue. There have been reports of some connection issues that are tied to the Moca system. There doesnt seem to be a rhyme or reason to it. But there have been some that have found that running Ethernet from the ONT to the router for the internet connection has solved the issue.

This will not effect the VOD. You will still have the coax run to the router, you simply will be using eithernet for the internet portion.

Now since you are seeing an improvement using another router, this is probably not the issue. But you did say that the router has been replaced, right? And it seems you have checked just about everything else, so it looks like grasp at straws time. This may be another thing to look into.

---

   I still have the original equipment from Verizon.  I think the confusion is that I added my old DIR-655 router to the configuration (plugged the DIR-655 into a LAN port on the Actiontec and my desktop into the DIR-655).  I also contacted Actiontec twice and they feel it is a verizon issue - who knows for sure? 

   I think on the ethernet approach I was going to use my own router in one test and the actiontec in a separate test. If I could do some simple test to see the problem I could make so much more progress.

****

  Another confusing data point,  last night I ran for about an hour using my laptop running WoW (no Vent) over Actiontec wireless with no DCs.  This was in no way equivalent to my raid testing, but under this situation I have normally DC'd frequently.

   Is there any logging I can turn on to help gain insight.  My router does has a variety of logs I can produce and stat collection?

[Daliddar]

i have never installed VSS or mcafee on this computer.

[Soupy1]

     I'm at a loss.  I ran the "fix" configuration in my 25 man raid with a fresh reboot of my DIR-655 and PC but DC'd quite often.  I then direct connected my PC back into the Actiontec and worked for a bit then same DC issues.  I'm thinking this is a signal/hardware issue downstream at this point, but I still want to put in a "clean" pc and see what happens - just haven't had the time.  I left it with the DIR-655 DMZ'd to see if that does anything - although DMZ of PC didn't work before. 

   If I have time, I will set up another PC and see what happens. 

[Soupy1]

         I had another 25 man raid last night, so I decided to reset myActiontec  router, my DIR-655 and PC.  I went in and just reset username/password in router and set up my DIR-655 to DMZ.

         I planned to test the router setup as DMZ, but decided to simply plug my PC directly into the Actiontec.  No DC's occurred last night, so I never did the other test.  Tonight I have a 10 man and keep fingers crossed.  I do not plan to reset anything unless things fail again.

        One thing I did notice was one of my HD-DVR boxes didn't appear in the device list in the actiontec, but it was fine and remote access this morning saw it after I refreshed the screen once.  That box has a long cable run and I doubt it is causing any issues with my internet.

[Soupy1]

      Had another 10 man raid last night and was able see if I would DC.  Night before everything worked after reset, so I would have expected things to just work (yeah right!).

First try:    Using Actiontec (Rev. F)  left in what was working state from night before.  I did perform a remote access for the DVRs earlier in the day and had to refresh before it worked.  DIR-655 still plugged in and DMZ set, PC direct connected to Actiontec with fresh boot.

.  

Result:     I DC'd fairly soon connected to WoW and running Ventrilo.  No raiding, just normal game play.

2nd try:     Switched PC to DIR-655 that was set to DMZ and was just running WoW.

Result:     DC'd again fairly soon.

3rd try:      Reset/power down the Actiontec, DIR-655, and my PC. I noticed the router did not pick up the STBs and this morning I noticed I could not remote access them.  This happened night before, but it was just the Family Room unit.

Result:      Once again everything worked fine all evening.   Latency was around 168ms when I have had it as low as ~65ms.

       The night before,the Actiontec recognized one of the STBs right away but not the one with a long cable run.  I understand it can take a while for them to get picked up - it has been around 14 hours.  I did not reset the STBs though.

       Does it make sense now to try the ONT ethernet test  (have to buy and run a cable)?   or

       Have Verizon come in and test my system after I DC'd (don't reset)?

[spacedebris]

personally, I'd try the ethernet next. That will allow you to test both with and without the verizon equipment in place. You will even be able to connect the computer directly to the ONT and test that. Sounds like you are getting down to the nitty gritty now.

[Soupy1]

   This weekend was another head shaker for me.  Once you think something works .. it doesn't.

    Ran with recycling Router, PC and STBs and DC'd often on Friday evening - direct connect into Actiontec or DIR-655.  This worked two nights in a row too (except I decided to cycle STBs to try to fix remote access).

    Saturday, decided since I was going to try the Ethernet connection I would load on VISS again and see what happens  (since I know how to remove and clean).  Had some initial issues running WoW and Ventrilo, but it finally prompted if WoW could access pc when it tried to block it (I dc'd of course)  and I turned off active scan feature.  Seemed to be ok once that was done, but did DC before that meven just being fairly idle.

     Sunday just did a power cycle of router, PC direct into Actiontec, VISS set active scan off and ran WoW with no issues for the evening.  Latency was slightly higher and a small bit of lag at times.

*****

      Planned to do ethernet test, but cable I had at home ended up being 3' too short - have to wait to get a longer one.  After all if I do the connection I want to do a good test to isolate the MoCA stuff so had to run it to computer room.

       STB access still not working so need to look into that as well, however guide etc... is fine on TVs.

[Soupy1]

   I finally got Cat5e cable run yesterday.  Plan to do a test and probably just use my DIR-655 as the main router.  When I request the Ethernet port to be activated, do I already have to disable the coax based network and release the lease before hand on the Actiontec.  I ask because I would like to activate the port before going home, as I don't know how long it will take to get ahold of tech support.

*****

   I am still having DC issues regardless of what I configure it seems.  In the end, I would like to keep the Actiontec as main and have a simple setup - since it is Rev F.  

[Hubrisnxs]

you will most likely have to call in to tech support to have them release the IP address binding, so that you're dlink will work.

or if you simply leave your actiontec unplugged for 4 hours the lease will automatically expire all by itself without a call to tech support. 

[Soupy1]

    Finally ran the first stage of the ONT --> Ethernet port test.  After releasing lease on Actiontec I turned it off, connected my Cat5e, and within 15 minutes had the ONT Ethernet port turned on and working.  Decided to try the simplest route and test the Actiontec router first.  Ran for about 4 solid hours, then the DC's started to occur regularly - like every 10 minutes.  Finally shut router off for 20 seconds and back on with no DC's for the next hour.  Speed was very good, as well.

   Tonight I will release the lease and plan to use my own DIR-655 router as it worked fine before all this without doing the loop back into the actiontec.  I assume if I DC the issue is the ONT or line/port into it?  If it works fine then time for a replacement router I guess. 

   I still wonder if the STB portion (feed etc...)  of the actiontec or the STB's cause any issues.  I guess the test tonight will tell.

  Your thoughts are welcome and if I should do another type of test let me know.  Maybe I should just do direct connect, but I don't want to really expose my computer that way as it could be hours for a good test.

[Soupy1]

     Ran the test again with my own DIR-655.

      ONT --> Cat5e --> DIR-655   (actiontec just connected to Coax for TV/Phone)

     Release lease from Actiontec  (this works for me)

     Plugged in Cat5e into DIR-655 and obtained lease

     Desktop recognized my pre-verizon network

         (running VISS for this test)

         Computer ran for 5 hours with an early minor DC.  This time it was "normal" as WoW DC'd but Ventrilo was unaffected.

         Turned off real-time scanning

         Ran fine for rest of the night. 

     I have had prior nights with various configs run ok  (like my first test of DIR-655 into lan port of Actiontec which then failed next night).  So I will test this again tonight.  I returned the system back to Actiontec for the day to provide the guide feed.

     I assume if this works for a couple more nights, I will have the Actiontec replaced.  I would prefer to stay out of the advanced configurations since I would want to set up LAN-LAN.  I might get brave and try to set it up just to make testing easier.

[Soupy1]

  Ran second test by releasing lease on Actiontec and switching over to DIR-655.  I had a DC before really doing anything demanding, then all was well for the evening (just like prior evening).

  Guess I'll call tech suppport for a new router ... 

[Soupy1]

  New router ordered - tech support felt I will still have issue if I get another Actiontec, but I may get a westel.

  I set config to LAN - WAN while I wait.  Seems to be working okay for guide, widgets - I know I won't be able to remote program my DVRs but I couldn't anyway.  I followed http://www.dslreports.com/faq/15992.  On my Actiontec my Ethernet light blinks and my WAN (ethernet) also blinks - I believe they use to be solid green before. 

  Tech support advised if I did the Lan-Wan to DMZ the Actiontec - I didn't do that step yet or set any static addresses.

   Download/Upload went from 26/25 with just DIR-655 config (Sunday test) to 26/5 (Monday test connected either to DIR-655 or Actiontec).

  Just ran system for an 30 minutes or so without anything unusual occurring. Next hard test will be Wednesday.

[Soupy1]

     Lan-Wan config ran rock solid - no DCs or issues with Ventrilo or WoW.  Will run again tonight.  I did reservethe actiontec IP/Mac and put in DMZ.

     Got a replacement router - Actiontec Rev. E.  I will try this over the weekend in stand-alone mode and see what happens.  I guess it's good I got a different Rev (have F), but was wishing on a different brand.

Side note:

     I tried the trick to access Parental Controls remotely and it identified my Actiontec and its static IP.  It said it would repair but that didn't work - oh well.

[Soupy1 · Accepted solution]

   Marking this as solved.  Thanks everyone for your guidance.  I still haven't tried replacement router, but if it works I will update thread.

  Solution was to front-end my Fios service using a third party router (DIR-655) connected to the Ethernet port of the ONT.  Verizon activated the port for me.   The DIR handles web traffic, serves IPs, and runs the wi-fi.  I have the Actiontec (WAN port) connected to the DIR-655 (LAN port).  The Actiontec is DMZ'd, manages Coax connection, and handles STBs (IP etc...).   I am running the VISS, but not family protection.

  Currently I do not have remote access to the DVRs but that's a different issue.