Issues with port forwarding
Issues with port forwarding
Hi, I see your issue. Even after disabling the Windows firewall, remote access is limited to LAN when you try to forward port 22. It seems the Connectify driver might be causing the problem. You mentioned other servers work on similar ports, like port 221, which suggests the issue could be with your computer setup. I recommend checking the driver configuration and ensuring it's properly installed. Let me know if you need further help!
Apologies for the oversight. To verify your point, try connecting a Windows or another service to the internet (like RDP, IIS, Apache or NGINX) and see if you can reach it remotely. I'm sure I'm repeating myself, but keeping RDP exposed publicly isn't ideal unless you have a specific need. The default port for RDP is 3389, while IIS typically uses port 80. FTP (port 21) and SSH (port 22) are also viable options for testing, as they can be set up swiftly without restarting the server. OpenSSH works well with Windows.
I've used RDP before, but it didn<|pad|> to not work either.
Contacting @Eigenvektor and @leadeater to theatre 1. That seems unusual—I haven’t heard of Connectify or Dispatch, but I’m curious if double NAT is involved. Could this software generate virtual subdomains? Also, do you have several routers or managed switches on your network? My knowledge of Windows Server is limited, though I’ve spoken to two experts who know more than I do.
Some internet service providers limit inbound port access to frequently misused ports such as 21, 22, 25, 3389 and others. This could indicate your ISP is blocking these ports before they reach your router. Consider creating a port forward rule that directs external ports above 1023 to the internal port 22, for example [external IP]:2222 pointing to [internal IP]:22. Once configured, simply connect your application to the external IP and use port 2222 in its settings. If it functions internally, the problem likely lies with your ISP’s port forwarding or filtering settings.
I’ll attempt it, but on another PC within the same LAN I can use port 22, so I don’t believe it’s my ISP or router.
So you can forward port 22 to that other PC and reach it from outside, but it doesn't work on the Windows server? Or am I misunderstand something?
I might have miscommunicated, but I have two Windows Server 2019 machines and require port 22 on one of them. The server needing Connectify is also installed, which might not be crucial but I mentioned it. If I route port 22 to the Connectify-enabled server, I can't access it from outside the network. Forwarding it to the other server without Connectify works fine, as I have VNC installed there and use different ports for it. The same problem recurs when I switch PCs for testing, removing the router forwarding. I use identical software on both, only differing in Connectify installation.