25 replies to this topic

[Big Tin Man]

Euklides, on 06 January 2016 - 09:17 AM, said:

Yes that is what I imply, most games do the portforwarding for us these days. I will not pretend to know the details of this issue that you had, because I don't. I've only got knowledge from previous issues I've had similar to yours.
The wireless adapters can open ports on the routers in order to do the menial tasks that is portforwarding, my bet is that MWO upon install communicated what ports it wanted to the adapter, the adapter then proceeded to set these. Then upon removal of the old adapters all settings associated with the it was removed, as the new adapter most likely was identified differently by the router.

So a fresh install of MWO, with all traces of the USB adapter removed should fix this?

[Oderint dum Metuant]

Big Tin Man, on 06 January 2016 - 09:16 AM, said:

Agreed, I didn't think opening ports would be necessary either but I'll be damned if it didn't work.

To the rest of your points:
* USB software was uninstalled, machine rebooted. I have not manually gone through the reg to make sure it is all gone, I will check.
* When you say rebuild TCP/IP stack, do you mean to do a ipconfig /release ipconfig /renew? I did that after USB software uninstalled
* DNS was flushed after USB software uninstalled. Will flush again after reg check
* Just using Windows defender for AV, have not seen a pop up from it in recent memory

@DV--Last time I needed to setup some port forwarding was for Diablo 3 at launch, but Blizzard clearly stated it was necessary for Battle.net.

Any thoughts on just uninstall/reinstalling MWO? I could just set it to download tonight when I go to bed.

I stayed up for Diablo 3 launch (spectacular failure) and am a daily user of battle. Net, I have never opened ports for either.

The last time I opened ports for a game to work was MW3 maybe MW4 at some stage..decades ago!

[Big Tin Man]

DV McKenna, on 06 January 2016 - 02:56 PM, said:

I stayed up for Diablo 3 launch (spectacular failure) and am a daily user of battle. Net, I have never opened ports for either.

The last time I opened ports for a game to work was MW3 maybe MW4 at some stage..decades ago!

I think I opened ports for D3 as part of their advice as they were mitigating their awful launch. Can't remember anything other than ERROR 37.

Edited by Big Tin Man, 06 January 2016 - 04:18 PM.

[Tarl Cabot]

The one issue I have not seen noted here is on routers/gateways, there is not just the NAT but the secondary software firewall/security on said devices. It used to be called SPI, stateful packet inspection. Online games uses UDP communication packets, but if there is a flood of packets the SPI will believe a port(s) is under attack and temp close that port.

And a wireless device with the possible interference from other devices/signals, it is possible that is what is occurring.

Edited by Tarl Cabot, 06 January 2016 - 06:21 PM.

[Big Tin Man]

So the close out the saga, I did the following things tonight:

1. Ran CCleaner and cleared out the registry (oops, been a while, had a lot of crap to clear )
2. Did a netsh int ip reset resetlog.txt to totally reset tcp/ip
3. Reboot
4. Flush DNS
5. Uninstall/Reinstall MWO

After doing all that, I can close the ports and run MWO just fine. Not sure which specific step did the trick, and I figured it was faster just to nuke it all from orbit rather than to check every little step of the way.

Thanks everyone for the help, hopefully this helps someone else in the future.

[Golrar]

Big Tin Man, on 07 January 2016 - 12:10 AM, said:

I figured it was faster just to nuke it all from orbit rather than to check every little step of the way.

It's the only way to be sure.