Pages: [1]   Go Down

Author Topic: Problems with remote station port forwarding  (Read 229 times)

VE3HLS

  • Member
  • Posts: 20
    • homeURL
Problems with remote station port forwarding
« on: December 07, 2019, 09:11:20 PM »

Hi All,

I have set up a remote station in the Toronto area that consists of an IC-7300 and a PC running Win4Icom software.  I'm connected to my host's router via Ethernet cable and have configured Ports 50001 and 50001 in the router for Radio Control and Audio Control respectively (both TCP/UDP).  My host computer has a Static IP address.  I'm using noip.com to take care of the internet DNS stuff.

After weeks of support from noip.co and VA2FSQ I still can't connect to the host computer via the internet.  Noip.com's port checker times out when it checks the ports, i.e., they aren't working, and an app I downloaded from PcWinTech.com says the ports ARE working.  Supposedly, the noip.com port checker tries to get to them from outside the home network (like I would be from here in Thailand) while the PcWinTech app runs on the host computer, opens the ports from within the computer and waits for some kind of signal from PcWinTech's server.  All I know is that I cannot connect from my remote computer here in Thailand, so I'm inclined to believe noip.com's port checker.

Noip.com and VA2FSQ have helped me all they can and I'm at my wit's end.  Does anybody out there know about this stuff?  I watched all the videos and read the manuals...it seems set up correctly to me, and according to screenshots I've sent to VA2FSQ and noip.com.

I could sure use some help from one of you network savvy folks!

Thanks in advance!

73,

Ken Alexander, VE3HLS
So Phisai, Thailand
Logged

WB0OEW

  • Member
  • Posts: 3
    • HomeURL
Re: Problems with remote station port forwarding
« Reply #1 on: December 07, 2019, 11:23:32 PM »

Nothing specific but here are a few basic ideas off the top:

1. Instead of port forwarding, set up the router to set your host computer as a DMZ. Just beware this will forward everything to your host, so be sure it has a firewall running.

2. Speaking of firewall, check the host firewall settings and anti-virus programs to see whether they are allowing your ports in.

3. Finally, check your remote outgoing system (in Thailand) to be sure it is sending your ports ok.

Good luck with your project.
Logged

W9IQ

  • Member
  • Posts: 8866
Re: Problems with remote station port forwarding
« Reply #2 on: December 08, 2019, 03:25:29 AM »

Did you ever have this working on a local connection basis (i.e. client also in the Toronto home)?

Are you certain your Thailand ISP or local network is passing the required ports? Many hotels, etc. restrict the available ports to those used for common services.

When you check the IP address returned by noip, does it match the IP address of the Toronto location?

Is the noip client running on the same remote computer or on the router?

Have you looked at the Toronto router's log file to detect any failed port accesses?

Do you have TeamViewer or equivalent installed in Toronto or a person available to help with remote troubleshooting when you are in Thailand?

- Glenn W9IQ

« Last Edit: December 08, 2019, 03:45:59 AM by W9IQ »
Logged
- Glenn W9IQ

God runs electromagnetics on Monday, Wednesday and Friday by the wave theory and the devil runs it on Tuesday, Thursday and Saturday by the Quantum theory.

VE3HLS

  • Member
  • Posts: 20
    • homeURL
Re: Problems with remote station port forwarding
« Reply #3 on: December 08, 2019, 06:29:06 AM »

Nothing specific but here are a few basic ideas off the top:

1. Instead of port forwarding, set up the router to set your host computer as a DMZ. Just beware this will forward everything to your host, so be sure it has a firewall running.

That sounds like a rather risky last resort, so I'll keep that in mind if nothing else works.

2. Speaking of firewall, check the host firewall settings and anti-virus programs to see whether they are allowing your ports in.

I looked and I couldn't find anything to do with port access in Microsoft's firewall settings.  I saw something about Allowed Applications and checked to make sure Win4Icom was in there correctly.  It was.

3. Finally, check your remote outgoing system (in Thailand) to be sure it is sending your ports ok.

Sorry, I have no idea how to check that.  Can you explain how one does that?

Good luck with your project.
Logged

VE3HLS

  • Member
  • Posts: 20
    • homeURL
Re: Problems with remote station port forwarding
« Reply #4 on: December 08, 2019, 06:47:51 AM »

Did you ever have this working on a local connection basis (i.e. client also in the Toronto home)?

Are you certain your Thailand ISP or local network is passing the required ports? Many hotels, etc. restrict the available ports to those used for common services.

When you check the IP address returned by noip, does it match the IP address of the Toronto location?

Is the noip client running on the same remote computer or on the router?

Have you looked at the Toronto router's log file to detect any failed port accesses?

Do you have TeamViewer or equivalent installed in Toronto or a person available to help with remote troubleshooting when you are in Thailand?

- Glenn W9IQ

1.  Yes, When I was in Toronto I was able to control the radio with the software on the computer sitting next to it.  That was via a USB connection between the radio and the computer.  When I got back to Thailand I was able to set up the software so that I could control the radio from anywhere inside the host's home network.  Things only go bad when I try to connect from here.

2.  I don't know if my local ISP does anything like that.  I never considered it and can't imagine why they would.  But you're also not the first person to mention this.  How can I tell?  OH, I should mention that noip's port checking website has to be run from my host computer in Canada and it can't find the ports either.

3.  Yes, noip returns the correct address of the network in Canada.

4.  The noip app runs on my host computer, which is where noip said to install it.

5.  The logfile doesn't say anything about port accesses, successful or otherwise.  The only thing it shows for the last week or so is me logging on and off the router and me creating ports...for which it acknowledges that they are active.

6.  I have complete access to my host computer (and from there to the router) via Chrome Remote Desktop.  One of the smart things I did!

Thanks and 73,

Ken, VE3HLS
Logged

W9IQ

  • Member
  • Posts: 8866
Re: Problems with remote station port forwarding
« Reply #5 on: December 08, 2019, 10:50:31 AM »

Ken,

I can help you with checking if your outgoing ports are being blocked in Thailand. For security reasons, we need to do this off-line. Email me at my call at arrl dot net.

- Glenn W9IQ
Logged
- Glenn W9IQ

God runs electromagnetics on Monday, Wednesday and Friday by the wave theory and the devil runs it on Tuesday, Thursday and Saturday by the Quantum theory.

VE3HLS

  • Member
  • Posts: 20
    • homeURL
Re: Problems with remote station port forwarding
« Reply #6 on: December 19, 2019, 07:30:35 AM »

Ken,

I can help you with checking if your outgoing ports are being blocked in Thailand. For security reasons, we need to do this off-line. Email me at my call at arrl dot net.

- Glenn W9IQ

Hi Glenn,

Thanks, but no need.  I found the problem (Windows firewall on my host computer...duh!) and things are working now.

The problem now is that the rig is very slow to respond, like up to 5 seconds for a band change.  Audio latency is very good and not an issue, but the slow response to radio commands is a deal-breaker.  The Win4Icom author has been very helpful.  He has logged on remotely and says it's fine.  He's a few hundred kilometers away...I'm 12 time zones away.  So it's basically a "law of physics" thing.  My host and I both have fast internet service and I can see that the host system in Canada is only trickling data out to me when I'm connected, well within the capabilities of our respective internet connections.

I also appear to have an antenna issue and have to wait for a ham friend to become available to go take a look.

Sigh!

Thanks and 73,

Ken, VE3HLS
So Phisai, Thailand
blog:  bueng-ken.com
Logged
Pages: [1]   Go Up