Verify the Web Server is started by looking at the Status Log in the Web Server tab. It should show "Started".
Great, now the local part works. Send a screenshot of the ER-X port forwarding, with advanced options checked, and interfaces data.See above...
Then you have a firewall on the PC hosting ProScan that is blocking that connection. You need to allow port 5000 through the firewall or disable it.Thank you for chiming in @freqseeker. I could use a little bit more of patience...lol The kicker of all of this is I know I'm going to look back at everything and want to slap myself around for missing something obvious.
I changed the IP addresses and it still didnt work. After checking the Port Checking Tool using the local IP, I did get a connection timed out instead of connection refused...
I am only able to pull up the Virtual Scanner on the laptop that is connected to WiFi but running ProScan. I tried pulling it up on various other devices and laptop and no luck.
The router won't come into play for a local LAN test. I would not recommend disabling any router's firewall.Check if more then one firewall on the computer. Also see if the Router Firewall can be disabled for a test.
Just for a test.The router won't come into play for a local LAN test. I would not recommend disabling any router's firewall.
That's good so Step 1 is okay.I had to start over. I had accidentally changed a setting and wiped my internet out for the last few hours. Finally got it back. I am seeing and controlling the scanner in ProScan. Using the local IP address 192.168.x.xx:5000, I can pull up the scanner on the computer that is running ProScan via a wireless connection.
I would ignore that for now. I've heard of a few others that can't connect to the server using the smart phone WiFi on the same network.I am still not able to connect from my phone using the local IP address while on the WiFi.
So I would focus on this step 2. Use the computer IP address and not the outside address in the Forward-to-address box.Nor can I connect using the Outside IP 24.44.xx.xxx:5000. The connection is still timing out again when using the Port checking tool. I've tried
setting up the port forwarding using both the local and outside IP addresses with no luck.
I don't think so. Only the router uses the outside address.Out of curiosity, can this have anything to do with the computer I'm working with being on WiFi? Could it be grabbing the wrong outside IP address?
Thank you for the suggestion. I went in to Windows Firewall and created a rule to allow port 5000. The only option I had in Windows Defender was to turn it off, which I did. Port forwarding tool still timed out. I then shut off the Firewall and Windows Defender, tried to port forwarding tool again, and still getting a timed out message.Check your firewall to open port 5000 on the PC that ProScan is on...
I don't use windows defender, I use ESET...
Google how to open a port in windows defender... It's out there...
That was my problem using it on my internal network...
It sounds like it. What about the router Port Forwarding Lan Interface? Your screenshot shows switch0. Can you try another setting such as eth1Did I cover all of the steps you guys have generously shared with me?
That is correct. That is your outside or real IP address.On the port checking tool, its grabbing my outside IP address. I'm not able to change that field. I'm assuming that is correct.
Thought so, just making sure.That is correct. That is your outside or real IP address.
Did you change the "Port to Check:" to 5000?