ProScan, Using mobile phone hotspot

[KC9KOA1]

If this has been posted before, I couldn't locate it.

I am looking at ProScan. I have attempted to work with ProScan support and we seem to not be able to come up with a solution, your turn!

When I have my SERVER PC and CLIENT PC on the same network, using my IP and DNS Server, it all works perfectly~ YAY!

When I have the SERVER PC on my home network and the CLIENT PC on my cell phone hotspot, it does not work, like at all! I have also noted that I can not connect to any other published server from the client. I get a code1.

Here is another confusing thing. When I click on "GET MY IP" on the ProScan software, it comes up with a different IP than what my router shows. (not willing to put these in a public forum).

Anyone willing to help can email me KC9KOA@gmail.com

Thanks for your time, KC9KOA~Tom

 

[ProScan]

Instead of asking for help via email, can it be done here so others can chime in and/or learn?

I'm not sure why the "Get My IP" function is different then what your router shows. I would go with the "Get My IP" address because that is echoed back from a http server and is a true indicator. Also canyouseeme.org shows the same as the "Get My IP" function.

You didn't reply to my email so not sure if you understand the screen shot you sent is not of the router Port Forwarding section.
You want to find the Port Forwarding section and tell it to use TCP Only, IP address or name of the computer running the server, & same port# of the server.

{edit} Once you got the Port Forwarding figured out then use canyouseeme.org again. Enter the server port # and click on "Check Port"

 

[KC9KOA1]

Instead of asking for help via email, can it be done here so others can chime in and/or learn?

I'm not sure why the "Get My IP" function is different then what your router shows. I would go with the "Get My IP" address because that is echoed back from a http server and is a true indicator. Also canyouseeme.org shows the same as the "Get My IP" function.

You didn't reply to my email so not sure if you understand the screen shot you sent is not of the router Port Forwarding section.
You want to find the Port Forwarding section and tell it to use TCP Only, IP address or name of the computer running the server, same port# of the server.

I am well aware of the fact that I didnt send you any of the Port Forwarding settings. I sent you the IP settings showing the discrepancy. I set Port forwarding up, properly.When I used the IP from the "Get My IP" noting worked on EITHER network.

 

[KC9KOA1]

Instead of asking for help via email, can it be done here so others can chime in and/or learn?

I'm not sure why the "Get My IP" function is different then what your router shows. I would go with the "Get My IP" address because that is echoed back from a http server and is a true indicator. Also canyouseeme.org shows the same as the "Get My IP" function.

You didn't reply to my email so not sure if you understand the screen shot you sent is not of the router Port Forwarding section.
You want to find the Port Forwarding section and tell it to use TCP Only, IP address or name of the computer running the server, & same port# of the server.

{edit} Once you got the Port Forwarding figured out then use canyouseeme.org again. Enter the server port # and click on "Check Port"

Port forwarding is figured out. I am confident that this is NOT the issue. It has to be something on the Client Side

 

[ProScan]

Port forwarding is figured out. I am confident that this is NOT the issue. It has to be something on the Client Side

Before you work on the client side, the error in canyouseeme.org has to be resolved.
The screenshot in the email is showing Error: I can not see your service on x.x.x.x on port x. Reason: Connection timed out

 

[jonwienke]

Port forwarding is figured out. I am confident that this is NOT the issue.

If canyouseeme is showing an error, then you're wrong, port forwarding isn't working correctly, and until you fix that, nothing else you do will make any difference.

 

[buddrousa]

Ok your network has 2 ADDRESSES
#1 LAN (Local Area Network) the address of your PROSCAN PC in your house.
#2 WAN (Wide Area Network) your INTERNET Address.

If you are home you use your LAN Address the Address of your PROSCAN PC.
If you are away from home you use the WAN ADDRESS which has to have port forwarding setup and test away from your home.

Port Forwarding - Verizon Jetpack 4G LTE Mobile Hotspot - 890L

Here's how to open blocked ports on your Jetpack 890L to allow additional access.

www.verizonwireless.com

 

[ProScan]

His IP addresses looks strange to me. I think he's on a corporate intranet.

Computer IP 172.x.x.x
Outside IP 96.x.x.x
Another computer on same network 10.x.x.x
(Can tell by the RSOIP Client - Client Connections)

 

[KC9KOA1]

His IP addresses looks strange to me. I think he's on a corporate intranet.

Computer IP 172.x.x.x
Outside IP 96.x.x.x
Another computer on same network 10.x.x.x
(Can tell by the RSOIP Client - Client Connections)

My Router has the 10.x.x.x. I have a fiber optic line coming into the house.

 

[buddrousa]

Do you have a friend that does networking?
Like Bob said your network does not look right.
Do you know much about networking?

 

[ProScan]

The strange thing I see is 10.x.x.x is reserved for private(or LAN) networks.

 

[KC9KOA1]

Do you have a friend that does networking?
Like Bob said your network does not look right.
Do you know much about networking?

I set up my own network. I did a full reset just before I started this process. I changed the IP from the normal 192.168.X.X to add extra security. Talking with my ISP, it sounds like I need a static IP.

 

[ProScan]

I set up my own network. I did a full reset just before I started this process. I changed the IP from the normal 192.168.X.X to add extra security. Talking with my ISP, it sounds like I need a static IP.

For a test, Can you change back to the 192 address or do a full reset like you did before. Re-setup the port forwarding and see what happens. I haven't heard of requiring a static IP address before. ISP may be trying to sell you something you don't need.

Who is your ISP?

 

[KC9KOA1]

My ISP is GVTC. Attempted the 192, nothing.

 

[KevinC]

My ISP is GVTC. Attempted the 192, nothing.

For those outside of Texas, that's Guadalupe Valley Telephone Cooperative.

 

[buddrousa]

Thanks Kevin for the update.
The ISP could be blocking ports because if it works in your house and not out of your house it is blocked ports or you do not have port forwarding set up correctly. I am running 16 scanners connected to the same pc and have port forwarding turned on and can connect any or all with no problems.

 

[KC9KOA1]

I followed the directions to the T on setting up port forwarding, including setting a static IP for the scanner and the SERVER PC.

 

[sallen07]

The strange thing I see is 10.x.x.x is reserved for private(or LAN) networks.

RFC 1918 sets aside three blocks of IPv4 addresses for "private" networks. These IPs are not (or at least *shouldnt be* routed on the Internet.

10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)

All of the blocks are functionally the same, and one is free to use any of them on a home network, but consumer-grade networking equipment almost always comes with a 192.168.x block as the default. But there should be no issue with Proscan if the IP isn't a 192.168.x.x address.

As far as the "you need a static IP", while I am not familiar with that ISP, but it is *possible* that they restrict in-bound connections to residential customers as a security measure. If a customer has a static IP (and I'm sure pays extra for it) the assumption is that they know what they are doing and inbound connections are by design.

The other possibility is that the help desk technician was just pointing out the fact that residential service uses DHCP and the IP could change at any time.

 

[sallen07]

His IP addresses looks strange to me. I think he's on a corporate intranet.

Computer IP 172.x.x.x
Outside IP 96.x.x.x
Another computer on same network 10.x.x.x

I would agree that this doesn't look right, not because the internal IPs are not 192.168.x.x, but because two computers on the same network will have addresses in the same subnet unless there are multiple network segments with a device doing routing between them.

 

[KC9KOA1]

I would agree that this doesn't look right, not because the internal IPs are not 192.168.x.x, but because two computers on the same network will have addresses in the same subnet unless there are multiple network segments with a device doing routing between them.

the 10.X.X.X is the router not a pc