SDS100/SDS200: SDS 200 WAN Connection to Web Server Troubleshooting

[bostonkid]

I have been struggling to set up Proscan to receive outside (WAN) connections on port 5000, with the aim of connecting to my web server outside of my home.
As illustrated in the attached image; my ISP connection enters my house and connects to a Netgear Nighthawk CAX80 in my basement. This modem/router combo has been disabled for any routing capabilities, wifi, and set to bridge mode. I am currently unable to connect to it anywhere on the network by typing in the router's address and can only connect by physically connecting an ethernet cable directly to it in the basement.

Upstairs, in my office, I have an ASUS GT-AX 11000 Pro Tri-band Wifi router, which is the main router for our home. This has ethernet cables, connecting an ASUS Nuc 14 Pro (acting as a home server/ProScan server) and my SDS 200. The SDS 200 is further connected to the NUC via USB cable.

Currently, I can start the web server via ProScan, and connect to it INSIDE my LAN, by navigating a browser window to 192.168.50.174:5000. When attempting to connect to this same open port from outside of my network, the connection is refused. I have used various network monitoring tools, and command line (netstat) prompts to view open/listening ports, and verified that ProScan is indeed listening on port 5000, not just on 127.0.0.0 localhost, but also via 0.0.0.0

My next troubleshooting step was to conduct a deep dive into windows defender on the Asus NUC and verify there was no traffic being restricted on this port, and to add a rule allowing it if so - no problems there. I then connected to my Asus Router and proceeded to verify that port 5000 was being forwarded and not blocked by a router-level firewall - again no issues there. Out of fear that I may have a double NAT connection (either from ISP or the CAX 80 in the basement) I have checked my external WAN IP address through various online tools, making sure there wasn't more than one hop from the same WAN IP I see in ProScan - again, nothing indicating this.

ProScan is giving me no issues with audio configuration over URL or anything else. I am enjoying audio recording and txt logging on the NUC PC without problems. If I navigate to the NUC's ip address and port 5000 from within my LAN, I can connect to the scanner web server without problems, listen to the audio, and even control the scanner remotely. Any outside connection is refused.


I feel as if I've exhausted all troubleshooting steps I can think of and am truly stumped. I have googled and read through several forum posts here, as well as the online manual. Any help would be much appreciated. Thank you in advance!

Jim

 

[Enforcer52]

I also found this page that says you have to use the xfinity app to setup port forwarding, you might want to check it out. It might only apply to their router/modems.

Set up port forwarding using the Xfinity app

Learn how to set up port forwarding using the Xfinity app.

www.xfinity.com

 

[buddrousa]

I am kind of old school also but I just upgraded my own home network to a new Netgear Nighthawk and setup port forwarding for 6 536's and 2 SDS200's I love new speed upgrades.

 

[ProScan]

bostonkid,
I would temporarly disable any firewalls/internet security/antivirus apps then see if it works on port 5000.
I would also try port 80. The port forwarding rule for port 5000, change to port 80.

My next troubleshooting step was to conduct a deep dive into windows defender on the Asus NUC and verify there was no traffic being restricted on this port, and to add a rule allowing it if so -

Turn these off temporarily for a test

 

[bostonkid]

bostonkid,
I would temporarly disable any firewalls/internet security/antivirus apps then see if it works on port 5000.
I would also try port 80. The port forwarding rule for port 5000, change to port 80.



Turn these off temporarily for a test
View attachment 189804

Will do! Thank you very much. I will let you know if this works.

 

[bostonkid]

Everything disabled and still no luck.

 

[buddrousa]

Most ISP's will not let you go out and back in on the same WAN Address.
The test would be your cellphone not connected to your LAN.

 

[Enforcer52]

Just tried to ping 24.91.33.222 returns

Pinging 24.91.33.222 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 24.91.33.222:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Don't know what up with Comcast/Xfinity but certainly something is blocked.

 

[ProScan]

View attachment 189867
Everything disabled and still no luck.

It looks like port 5000 is blocked at your IP. I would try various other ports, starting with 80. Be sure to change the port fowarding rule to match the port set in the Web Server

 

[bostonkid]

It looks like port 5000 is blocked at your IP. I would try various other ports, starting with 80. Be sure to change the port fowarding rule to match the port set in the Web Server

So I have tried port 80, port 6000, port 4500, and various ones. All possible firewall/protection methods are disabled...really at a loss here.
Each time I have tried a new port, I verify it on the LAN, with the new updated port number, it connects flawlessly, and yet from outside - ie cell service, or connecting to 24.91.33.222, ERR_CONNECTION_REFUSED every time. I don't know what's going on.


I did a full powercycle today with the new settings - turned off ProScan PC and Scanner, Router, went to basement and powered down modem. Restarted everything and still no luck.

 

[Enforcer52]

After everything rebooted, after clicking Get My IP in ProScan it still showed 24.91.33.222? Or did you even click it?

At this point you need to get a hold of Comcast/Xfinity and see what's going on with their port forwarding.

 

[bostonkid]

After everything rebooted, after clicking Get My IP in ProScan it still showed 24.91.33.222? Or did you even click it?

At this point you need to get a hold of Comcast/Xfinity and see what's going on with their port forwarding.

Yes - I retained the same WAN IP address - 24.91.33.222 - after rebooting everything. From what I gathered from Xfinity last night - there is no CGNAT on their end in my residential area - each customer gets their own unique IP address. Most of the tutorials/admin options on their site to forward ports is if you have one of their crappy wifi/hotspot routers that is running your network, not a self-provided one, so I wasn't able to modify any ports or forwarding through my Xfinity account.

 

[ProScan]

May want to try tools like this:

Check ALL open ports, scan open ports online free tool

Free online tools for scan open ports without limit of ports count

ports.my-addr.com

Port Checker - Check Open Ports Online

Check open ports with Port Checker Online. Scans the most common ports, and check port forwarding on your router.

dnschecker.org

I see port 8443 open. I believe when it's open, it's in use so you may get an error in ProScan when starting the server on port 8443, stating the port is in use.
My point is that your IP address is reachable and not all ports are blocked.

 

[bostonkid]

May want to try tools like this:

Check ALL open ports, scan open ports online free tool

Free online tools for scan open ports without limit of ports count

ports.my-addr.com

Port Checker - Check Open Ports Online

Check open ports with Port Checker Online. Scans the most common ports, and check port forwarding on your router.

dnschecker.org

I see port 8443 open. I believe when it's open, it's in use so you may get an error in ProScan when starting the server on port 8443, stating the port is in use.
My point is that the IP address is reachable and not all ports are blocked.

Wow I, like Enforcer52, have not been able to find any open ports on my own address with port checker. I will try 8443 now!

 

[bostonkid]

So this is bizarre - I checked 8443 on port checker, like you said, it showed open. I promptly adjusted ProScan to this port, started it up and navigated to local address on 8443 - working again. Went to my WAN ip with same port - now its showing the above; ERR_EMPTY_RESPONSE as opposed to connection refused. Strange. But maybe progress?

 

[ProScan]

I'm running this now on your IP. Check ALL open ports, scan open ports online free tool
Scan method set to slow. They're not kidding.

 

[bostonkid]

Everything working fine on port 8443 locally. I wonder if another process on the network is using this port? Is that why I can't connect from WAN?

 

[ProScan]

Everything working fine on port 8443 locally. I wonder if another process on the network is using this port? Is that why I can't connect from WAN?

I believe so.

 

[bostonkid]

So I ran a PowerShell query of open/listening ports - 8443 is here as well as several others that will most likely come up in your search - I looked up the the PID (process IDs) from the far right column in Task Manager that correspond to the ports open, they often show various windows service-host processes other other administrative system tasks as the owners.

 

[ProScan]

Port 5000 shouldn't be blocked accordingly to this.

Blocked internet ports list

Find out which ports are blocked by Comcast and why.

www.xfinity.com

Perhaps post the issue here

Your Home Network | Xfinity Community Forum

forums.xfinity.com

I wouldn't mention ProScan as that is too specific and then there's always someone that will question ProScan. Just use the term 'server'

 

[ProScan]

View attachment 189876
So I ran a PowerShell query of open/listening ports - 8443 is here as well as several others that will most likely come up in your search - I looked up the the PID (process IDs) from the far right column in Task Manager that correspond to the ports open, they often show various windows service-host processes other other administrative system tasks as the owners.

Perhaps start the web server with port 5000, or any port then see if it shows here. I don't know how valid of a test that would be but maybe another clue.