U

Visitor

 • 

1 Message

Wednesday, May 11th, 2022 2:14 PM

Closed

Cannot Port Forward

Hi I am trying to port forward my WiFi Extender for gaming purposes but I noticed the reserved IP was incorrect to the IP I use to login to the extender. I checked if the port was open but it wasn't. Can someone help please?

Problem Solver

 • 

1.5K Messages

3 years ago

You don't port forward to the extender, unless you are intentionally doing a double nat, and a double port forward on purpose (different subnet inside your internal network subnet).  If you do that though, broadcast traffic between subnets isn't going to work (or airport or xBox) and it's a silly arrangement.  Other ways to do that if you want two internal networks.

For extenders/access points, typically, they're leaching off an existing WiFi signal and repeating it, or are hardwired to your LAN with cat6, and perhaps even have their own SSID (ie Main_WiFi_EXT or something).  They forward DHCP request information from devices to your gateway, that will assign them an IP and will put them on your internal network.  The extender is just invisibly relaying the traffic after that.   

Internet <--> Xfinity Gateway WiFi<--> Device/Computer

or

Internet <--> Xfinity Gateway <--> extender/access point WiFi <--> Device/Computer

You want to know the IP address of the device/Computer/game_console.  That's the IP address you enter for your port forward rule.  It would also help if you manually assigned an IP address on the device/Computer/game_console to something outside of your Gateway's DHCP pool, or reserve a DHCP address for it, so that the IP doesn't change all the time and break your port forwarding rule*.

*Caution.  Port forwarding is a security risk.  You've just invited the entire world.

(edited)

Visitor

 • 

1 Message

@flatlander3​ So when i try to make a minecraft server on my pc I have to port forward, but when i go to my xfinty thing My pc isnt there at all, but when I go to the admin page thing it shows it there but disconnected, idk what to do and I wanted to play sum stuff with my friends. I am using a tp link wifi extender which does show up and port forwarding that doesnt work so idk what I need to do.

Problem Solver

 • 

1.5K Messages

Lot of places where there could be an issue.  Ideally, you want service running on something connected via Ethernet, not WiFi.  It will be more stable with less latency -- which is what you want for gaming.  A few things you can check though:

1. What is the IP address of the machine running the minecraft server?  Is it a DHCP assigned address, or did you set a static IP address for it?  You want that to be a static address outside of the DHCP pool of your gateway.  Then verify it is actually connected to the internet, and using the IP address you assigned.  Can you ping this address from something else?  It should have an IP address on the same subnet as your gateway (ie 10.0.0.xxx) subnet 255.255.255.0 and using your gateway as a default gateway (10.0.0.1).  You gotta check this first to even have a chance at this.

2. Windows firewall might be blocking the minecraft server.  Lot of youtube videos out there on installing and adding an exception for the java binary, and making sure the service is actually running.

3. Xfinity advanced security is buggy and might block ports despite your port forward rule.  Turning it off is also buggy apparently and doesn't always actually shut it off, but make sure it's off -- more on that later.  Power cycle is a good idea after that, then check again to make sure it's still off.  https://forums.xfinity.com/conversations/your-home-network/disabling-advance-security/60de27f0956ec15d99793440

4. If you can't see the device/computer on the xfinity app, can you try adding the rule for your minecraft server from the admin interface on the gateway manually?  The gateway web interface is probably at the 1st IP address at the bottom of your subnet range ie: http://10.0.0.1   https://www.xfinity.com/support/articles/port-forwarding-xfinity-wireless-gateway  I think you need TCP and UDP on port 25565 for minecraft, but you might need two extra rules for UDP ports 19132-19133 as well.  (power cycle again).  See if the rule stuck.

Remember, these port forward rules are for the machine running the minecraft server, not for your extender's IP address.

5.  You can check to see if the port did actually open on your gateway.  3rd party service like https://portchecker.co/

6.  Didn't work?  This part is a bummer, but when dealing with buggy firmware, sometimes it's better to start from a known default state on your gateway, then try one thing at a time starting first with disabling 'Advanced Security' (power cycle).   If you factory default your gateway, it does wipe out the WiFi information at the same time, so you'll have to setup WiFi again too and reconnect everything.

7.  3rd party gear does this much better.  You can save $14 month using something that works.  Port Forwarding is a common problem on these threads.  Something to consider.

(edited)

Official Employee

 • 

915 Messages

Hey there @user_53365e, flatlander3 provided some awesome information regarding your potential issue and we wanted to see if you were still having any trouble with port forwarding.

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

Visitor

 • 

1 Message

3 years ago

The user explained the issue clearly "I noticed the reserved IP was incorrect to the IP I use to login".  I experienced the same issue as well. 

It happens when you change the reserved IP of that forwarding device.  Somehow when Xfinity APP asks you to choose the forwarding device, it still "remembers" the old IP but NOT the latest reserved IP of that device. 

It looks to me that Xfinity keeps a table of "connected devices - IPs", and it does not update the table frequently enough.  You probably need to wait for a "timeout" for the table to update the latest IPs of each connected devices.  A simple bug which can be fixed easily. 

forum icon

New to the Community?

Start Here