Question Port Forward for Minecraft worked like 3 months ago but won't anymore ?

[Meruem999]

From what I've seen all I know is that nothing will come up through wireshark and the sites I use to see my ip come up with my WAN IP but if I try using the WAN IP to run the server it won't even start. I'm using my preferred IPv4 that starts with a 10. and I cannot change this when I set up my port forward through xfinity anyways. So yeah, I'm stuck.

 

[bill001g]

Not sure how you got this to work before. You do not setup your server with the actual wan IP....that is the whole reason you are using port forwarding in the first place.

So where do you see the 10.x.x.x IP address. This is a private IP not a public one. Is this the IP you see in the wan setting on your router.
It is extremely uncommon to use the 10.x.x.x blocks of IP on the LAN. You can use it but almost all consumer routers use 192.168.x.x ranges.

So if the wan IP is not 10.x.x.x and the value actually matches the sites like whatsmyip then it could be some software update to the port forwarding in the router causing the issue. I would look the ipconfig /all and get the IP and gateway. The gateway IP should be the router lan ip. I would then try the DMZ option in the router and set it to the ip you see in the ipconfig command.

You do not want to use the DMZ settings long term but it will quickly show you if it is just some strange port forwarding rules that is not working correctly.

 

[Meruem999]

Not sure how you got this to work before. You do not setup your server with the actual wan IP....that is the whole reason you are using port forwarding in the first place.

So where do you see the 10.x.x.x IP address. This is a private IP not a public one. Is this the IP you see in the wan setting on your router.
It is extremely uncommon to use the 10.x.x.x blocks of IP on the LAN. You can use it but almost all consumer routers use 192.168.x.x ranges.

So if the wan IP is not 10.x.x.x and the value actually matches the sites like whatsmyip then it could be some software update to the port forwarding in the router causing the issue. I would look the ipconfig /all and get the IP and gateway. The gateway IP should be the router lan ip. I would then try the DMZ option in the router and set it to the ip you see in the ipconfig command.

You do not want to use the DMZ settings long term but it will quickly show you if it is just some strange port forwarding rules that is not working correctly.

I'm guessing it's some software update because the wan IP is normal and matches whatsmyip and I have my IP and gateway, but I tried using DMZ and port checker sites to see if anything popped up but still nothing. I'm not 100% sure thats what you wanted me to check for but thats all I got lol.

 

[Meruem999]

I just tried restarting my router because xfiinity should update my software automatically and it still isn't working idk what im missing tbh

 

[bill001g]

Since you talk about using wireshark you should see the incoming scans. What I would do is setup the dmz option and then use one of the port scanning sites and tell it to scan a range of port number. This will make it easier to see the traffic in wireshark since there will be many packets being sent than scanning just 1 port. It will say they are all blocked but what is more important is that the packets are actually arriving at the machine.

Generally port forwarding does not work for 3 reasons.
1. You do not have a public IP or do not have the correct public IP.
2. The port forwarding rules are messed up in some way.
3. The application program is not actually listening on the port or maybe a firewall or something on the server is blocking the traffic.

You have mostly eliminated #1 and #2 and wireshark will confirm this.