Please Help Server Boot Error 30605

Details:
For the past three days since 12/16/15 I have been receiving a "Unable to complete version check 30605 20448 10009 10019. I have tried numerous fixes, and I have tried every suggestion I could find so far through forums and tech support from the game and my ISP. Here are the steps taken so far:

• Updated Drivers
• Reset Router
• Cleared internet History/Cache
• Removed Anti Virus Software
• Lowered all Internet Explorer security to the minimum
• Adjust the security settings under Internet Options > Privacy and Advanced
• Add Ports for port forwarding (supplied by Game Support)
• Added extra ports from forums
• Uninstalled and reinstalled the game (about 12 times now do to ISP requests)
• Ran all in administrator
• gave full control to all users under the security tab of the game file

None of this has worked. I have taken the game over to a friends house and it works perfectly. So I know it is not the game files that are causing this issue.
So I did a tracert to find the hops it takes to connect to the NA Data Hub. After doing this I pinged all the IP address and I did find three giving packet losses.

• 12.83.80.193 75% packet loss (hop 4)
• 12.122.138.17 ggr3.dlstx.ip.att.net 70% packet loss (hop 5)
• 192.205.36.222 100% packet loss (hop 6)

I tried last night with the AT&TConnect support to see if they could reroute me past these three, but I might as well have been speaking to a wall as no one would acknowledge this. They were dead set it is a corrupted file or antivirus software blocking. Does anyone know if this is or could be the issue? If so is there a way for me to get around this?
Also for some reason between 10pm and 10:45pm cst I am able to actually run the game on both my PC and my Laptop. It is a little laggy but it runs.

ISP is AT&T Uverse
Download speed is 7.6 upload is 1.5

On my PC HP Edge:
Graphic card is Nvidia 750
Wired connection
Running window 8.1 (game in compatibility 8 (also tried 7))

On my Laptop Alienware m17x:
Graphic card is Nvidia 950
wifi connection
Running Window 10 (game in compatibility 8 (also tried 7)) used to run perfect in compatibility 8

We've seen such issues in the past with AT&T in different regions. Seeing as you've been able to pinpoint hops with signs of potential congestion issues, there is a strong chance it is the usual routing issues in play. There is a site that tracks error reporting for a lot of services. They provide outage maps for many services as well as links to online support options like social media and forums for them as well. Might be worth looking them up over at www.downdetector.com/companies.

If you just exported your files to an external/flash drive to test at another location it could still be something with your system. Didn't see Windows Defender or Firewall in the list. Could be something there to look at. But considering the history, I'd be more inclined to flush out networking issues between your system and Montreal. You can try a VPN. The free use policy with many may not provide enough for full patching, but you could run the traces to see if it gives an alternate rout and whether version check gets you into the download stage. That could give you something to push AT&T with.

It is possible router/modem issues could be in play as well. May not be practical to swap them to test though. A few things you could try though. Remove the port forwarding and disable UPnP on it also if it is on--the router's built in NAT will manage things fine. Port forwarding is more for getting around security that is blocking unsolicited inbou d traffic and can inject problems when you don't need it. The game establishes an outbound link first and the stateful inspection protocol lets the data back in and NAT directs it back to the originating device.

To that end, there might be some tweaking to the SIP firewall or other router security to loosen securty in play--if the router recently updated firmware that may need to be looked at. Also, may want to turn off IPv6 to make sure it uses NAT and rule out any potential conversion weirdness since SE is still on IPv4.

If you are indeed getting it to run by taking the system to another location and it behaves then it is something specific along the route you are taking on your AT&T connection. Again, testing with a VPN from your location would give you ammo to fire at AT&T if it works. If a VPN is able to bypass problematic routing and makes it work, that pretty much is a lock that they need to address routing issues. It also provides a means to demonstrate it on demand. That is how I ultimately got TWC off their butts last year.

Awesome! Thank you for the feed back. I didn't even think of the VPN, nor did I know to try the other stuff. So trying these when I get home from work! Fingers crossed!