Unable to connect since switching from Norton to Windows Defender

[Masternecros]

Yesterday I had to switch my Antivirus from Norton to Windows Defender. After making the switch I ran the connection test and received a successful Test Connedection. Later that afternoon when preparing to host my Sunday night game I ran the test again and it failed. The answers to the 8 questions are below:

1. Your LAN IP Address
192.168.0.1
2. The first two sets (octects) of your WAN IP as displayed by Fantasy Grounds and as displayed by your Router
72.192
Note: The Reserved IP Address listed in the port forwarding section of my router differs by one digit in the forth octets compared to the value posted on the Fantasy Grounds start up screen (Internal Address). Not sure if this is pertinent or not just noticed the difference.
3. Whether you are using Wired or Wireless (and not both)
Wired
4. Confirmation that you have set your Adapter in Network and Sharing Centre to Private
My adapter is set to public but this was not changed and I have been able to connect using both Defender/Norton in the past without issue.
5. Confirmation of what AV you are running and whether you have set any exceptions
Windows Defender
I have added an inbound rule to all allow Any connection for Any computer for TCP 1802
6. Post the results of the tracert 8.8.8.8 command (if you have security concerns you can remove this bit once its been responded to)
Screen capture attached to this post.
7. Confirmation as to what you have setup in your Router if changes have been made
Port forwarding applied to port 1802 TCP
8. Confirmation you do or do not have any Virtualisation NICs
Not sure what this is

I am using COX and advanced security is Disabled.

Any help would be appreciated.

[Zacchaeus]

At point 2 you say there is a difference between the internal IP address as noted by FG and the one that you set the port forward rule. Those should both be the same. You need to forward your port to the correct internal IP address of your computer.

I note also that your tracert shows two private IP addresses between you and the internet. Although damned has told me in the past that the second one (the 10.xx) should not necessarily prevent successful port forwarding.

Also of course since you are using Cox make doubly sure that the advanced thing is off and that it hasn't switched itself back on again.

[Trenloe]

1) Is 192.168.0.1 what FG reports as the Internal address? This is more than likely the router, not the computer you're running FG on.

4) Set your network to Private. It doesn't matter if it worked in the past with it public, many security application place restrictions on network connectivity when the network is set to Public.

Please post a screenshot of your router port forwarding.

Thanks.

[Masternecros]

I have confirmed that Advanced Security is disable. With regards to the IP addresses being different, I see no way of changing the Reserved IP address. It comes up by default when I select my PC from the list of devices to apply the Port Forwarding to.

[Masternecros]

1) No, FG reports 192.168.0.85 for the Internal address. My port forwarding lists 192.168.0.84 as the reserved address. My router lists my LAN as 192.168.0.1.

4) I went into Network and Sharing and could not see how to change my Network from Public to Private. Nevermind I figured this out and changed it to Private.
42534

[Zacchaeus]

Your port forwarding rule is not associated with any device. So click on the edit button and select your computer (or whatever else that you need to do to make the rule point at your computer). As mentioned above your PF rule must port forward to your computer otherwise it isn't going to work.

[Masternecros]

Cox Wifi won't let me edit the Port Forwarding to change the device name. I have tried deleting and recreating the port forwarding several times and even though I select my PC as the device it creates it as No Associated Device with the slightly different IP address. I've contacted COX and they are of no help in the matter.

[Trenloe]

Have you tried the steps outlined here: https://svn.fantasygrounds.com/forums/showthread.php?53733-Guide-Port-forwarding-How-to-Cox-Panoramic-Wifi Make sure yo do all the steps - especially assigning the computer to a profile.

If this still doesn't work, please post the result of typing ipconfig in a command prompt.

[Masternecros]

So I can apply the correct Port Forwarding to any other device on my network except the PC I need it on. Is there a Firewall setting that would prevent me from setting up port forwarding on this desktop?

[Zacchaeus]

I'm not seeing what changing your anti virus set up would do that would change things like this. Did you previously have to port forward? Or is this something you are now doing in order to solve an issue? Windows Defender is very good at creating multiple rules for things so make sure that it hasn't got a bunch of them; if it does delete them all and create a new one. Also make sure that you completely uninstalled Norton; it has a habit of leaving bits around - which could create problems.

[Masternecros]

I just did that and went thru the steps of adding port forwarding to my PC. No change in the results. I can apply port forwarding correctly to every other device on my network except this PC. For some reason it Yields the No Assigned Device result instead of the selected device name.

[Trenloe]

Please provide the results of ipconfig as requested.

[Masternecros]

I previously had Port Forwarding set up before switching anti virus. I have deleted what appeared to be duplicate FG rules. Did not fix things. Norton has been completely uninstalled.

[Masternecros]

42559
Sorry, missed that request

[Trenloe]

42559
Sorry, missed that request
Thanks.

That confirms that FG is correctly reading the IP address.

Is there an option to enable UPnP on the router? If so, I'd try the following steps.
1) Reboot the router without making any changes. Let's just get that option out of the way first. Sometime a reboot gets things working properly.
2) Enable UPnP and remove the port forwarding rule. See if that works.
3) Reboot the router again after enabling UPnP and disabling the port forwarding rule - so the old port forwarding rule is definitely removed.

[Masternecros]

Solved it, somehow the PC profile got corrupted so it would not accept port forwarding correctly. I disconnected the PC from the network, forgot it and then reconnected. Once it was discovered I gave it a new name and ran port forwarding as normal and it worked! Hopefully it lasts.

[Trenloe]

Solved it, somehow the PC profile got corrupted so it would not accept port forwarding correctly. I disconnected the PC from the network, forgot it and then reconnected. Once it was discovered I gave it a new name and ran port forwarding as normal and it worked! Hopefully it lasts.
Great news!

[Zacchaeus]

And thanks for reporting the solution.

[Masternecros]

Thanks to both of you for your assistance.