I guess we all learn somehow, but this guy had WAY MORE experience than I had. He had been working on it for a few hours already when a two-minute test would have shown the issue. only to discover that changes he made months early never got saved and were only in the running config, which got dumped during the previous night's lengthy power failure. After him arguing more, he finally relented and checked the router. I calmly explained that if it worked locally and from another computer with the firewalls off or on internally, it had to be the router. He argued that it could not be possible because it had been working for months. Then he tried from an external computer and it failed, so I told him that his Cisco router was blocking port 25 inbound. I told him to telnet to port 25 from the server, then from a workstation, and they both worked. He was about to remove/reinstall Exchange when I yelled STOP! at him. For example, I was helping a fellow tech once whose client's SBS server could not receive email from the Internet, but it worked locally and had been working for months for external mail. I find it amusing sometimes when people don't check if it works locally before wasting hours checking external access. I am still waiting for the OP's response to my telnet suggestions. If it does answer, then start looking at your router. You need to ensure your server is answering on that port from within your network before potentially wasting time with the router - telnet to the internal IP address and port you are using from another machine on the internal network and make sure it answers. Something behind your router needs to be answering on that port for your port scanning service to show it open. 'I went ahead and tried running the server anyway' The ping test is just verify if the Netgear really is the first device seen, which it should be if the xfinity is just a bridge. If it does not, then your xfinity is blocking inbound traffic still. Now enable ping responses on the Netgear WAN and ping again from an external computer to the NoIP name. If the Netgear is set not to respond to ping, you should not get an answer. Next, ping your NoIP name from an external computer.

From an external computer, ping your NoIP name and make sure it returns the same IP address. Once the above has been confirmed, go to Īnd record its results for your WAN IP. These steps will eliminate any local firewalls being a cause of problems and will verify if the desired ports and services can respond at all. 'Could not open connection to the host'), move to another computer on the same subnet and try it.

If that works (i.e., you get a blank command box with a blinking cursor vs. The first thing you should do is on the server itself, try to telnet to its local IP address on the desired target port (assuming its using TCP. Which one do you really have, a static or a dynamic IP for the Netgear's WAN? If you have dynamic IP service, you cannot just pick a static IP to use. You initially stated, 'I have a set static IP and am using NoIP as my DNS Service' and then you just asked 'Would it benefit me to try just a static internet IP and DNS?'.

Would it benefit me to try just a static internet IP and DNS? Yet the Dynamic DNS service is still enabled with NoIP and is connected as far as I can tell.

In the internet tab of my router the Internet IP is set to dynamic and same with the DNS, both saying they are getting them from ISP. My xfinity modem is already in bridge mode with my netgear router being the only active router on our network.

No ip duc not working