Visitor
•
4 Messages
Port Forwarding on 443 doesn't work from LAN network
I have set up port forwarding for port 443 from Xfinity Gateway to my home server. It works fine if the connecting device is not in the home network, but it fails to connect if the device is in my home Xfinity network. I have reached out to Xfinity technical support for this. They have a hard time understanding my issue.
Can anyone help to resolve this issue?
CCKorie
Problem Solver
•
1.1K Messages
3 years ago
Hello there, @ss07. I am sorry to hear you are having issues with this port. Is this the only port that this issue occurs on?
2
0
CCKorie
Problem Solver
•
1.1K Messages
3 years ago
Have you used this port in the past, and it just started having issues, or first time using it? When trying to connect via LAN, do you get any error code or messages?
1
0
user_909945
Visitor
•
4 Messages
3 years ago
I have same issue but with a connection that previously worked. Was this issue resolved?
1
0
ss07
Visitor
•
4 Messages
3 years ago
Is there any resolution for this issue? Otherwise, I have to move out of Xfinity.
0
0
user_909945
Visitor
•
4 Messages
3 years ago
I fought with this issue for days and was unable to get a resolution. I finally purchase a 3rd party modem/router to replace the xfinity unit and was then able to set-up multiple ports for forwarding.
0
0
flatlander3
Problem Solver
•
1.5K Messages
3 years ago
Port forwarding doesn't resolve names. That just blows a hole in your firewall so inbound traffic on your external IP address, and a specific port, ends up on a box you specify.
You can get to the box by opening up a web browser and typing https://INTERNAL IP-ADDRESS:443 though right?
Gateways don't run DNS servers themselves. Some gateways can act as a DNS proxy though. I don't know if Xfinity's can or not, I think they may have removed that when they fixed your DNS servers to 75.75.75.75/76.76.76.76. The internal DHCP server only passes out these addresses to your internal clients and may have no other function. With other gear, you can pass out your gateway internal address (10.0.0.1) for a DNS server to DHCP clients, and if DNS proxy works on it, and then it will resolve internal hostnames while using upstream DNS servers as backups. Not all do this.
You can also resolve your internal network machines by setting up your own internal DNS server, and manually specifying that in a client network configuration. Other gear such as a firewall can run a "resolver" that will automatically map hostnames that connect to the internal DHCP server and append a domain name you specify. You can also setup a "hosts" file on a client machine that points to a box on your internal network, but the can be problematic when connecting to other networks.
You can test the behavior. Get a command prompt and type "nslookup". Then change the server you are using. Point it at your gateway with the "server 10.0.0.1" command. Then enter a hostname on your internal network. If you get nothing, it doesn't have the feature.
1
0