Visitor
•
2 Messages
Port is closed even after port forwarding
I am trying to port forward a PAX pinpad device.
I opened the xfinity app --> wifi --> view wifi equipment --> advanced settings -->Port forwarding
I have selected the name of the pinpad device from the dropdown list, selected manual setup, entered the port number as 10009, selected TCP/UDP protocol and clicked next. The message is displayed that says "Port forward added on Generic Brand Android Device". Clicked close button.
I could see the port forwarding is done.
But when I checked the port checker website https://www.yougetsignal.com/tools/open-ports/ it says the port is closed.
There is no firewall that is blocking. I have only one router and I entered the correct IP address.
I am talking to xfinity customer service everyday for the last three days. Each call lasted more than an hour but nobody gave the solution. I even upgraded my plan and modem yesterday but I face the same issue. Can somebody please please help me? My work really depends on this.
flatlander3
Problem Solver
•
1.5K Messages
2 years ago
Depends on what that site uses for a back end, but "Closed" for a utility like nmap usually means it got a closed port response. If a firewall was blocking it, nmap would say "filtered" -- meaning it was unable to get any response at all. That is what is supposed to happen with a firewall, if your firewall works.
Also depends on how the web site was coded, and how they are parsing and reporting the scan result to you.
Additionally, nmap will also say "closed" if the port is open on the firewall, but a service isn't currently running on the target device and handling requests, or if you have the port forward pointed to the wrong internal device.
There are different types of scans. Some try an ICMP ping to see if the host is up before the scan. If that fails (you are blocking ICMP), depending on how the site is coded and reports to you, it may give you a closed message too. nmap has the option "-Pn" to avoid that, and can just assume the host is up and then try the scan.
Another thing about port scanning, is that a lot of gear has built in port scan detection and will close off the offending IP address immediately if you hit a few ports quickly. Only scan one port at a time, and wait a bit before trying it again. If you have Xfinity "advanced security" enabled, it might not like the port either. It's undocumented as to how it works. You could try disabling it for a test.
**One more if nothing else has worked and you can verify you can get to your device internally by it's IP address from within your network. When you change the phone app, that configuration is somehow supposed to magically end up on your gateway -- they disabled local control. How and when exactly that happens is undocumented.
You might try just unplugging your gateway (hard power cycle). Wait a minute to erase volatile memory, then plugging it back in. Perhaps it only loads the config file from Xfinity on a boot, or it's currently stuck.
(edited)
0
0
XfinityKrista
Official Employee
•
1.5K Messages
2 years ago
Hello @Subashree, thank you for taking the time to reach out on social media. I understand your concern, and I'd like the opportunity to check into that for you.
To access your account, will you please send us a direct chat message with your full name and complete service address to “Xfinity Support”. To do so, click on the chat icon located at the top right of this forums page.
Here's the detailed steps to direct message us:
1
0