Virtual server / port forwarding / DMZ is not working at all
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hello community,
I'd bought an Archer VR400 v3 yesterday, and trying to expose a port on my local machine to the internet, but it never worked; here is summary of my situation:
- My local machine is listening on port 4000
- It is accessible from other nodes in the local network.
- I'd setup virtual server on tp-link modem to listen 4000:4000 IP my local machine
Now I expect 192.168.1.1:4000 to be open and responds from local machine, but it is not; the only thing I get is connection refused.
the packet doesn't even reach the local machine, modem doesn't allow and drop connection.
I'd tried to setup on different ports, even changed local management port on modem from 80 to other ports, and tried to use port 80 for my own use-case but then port 80 becomes "connection refused". I tried DMZ that local machine, didn't work; tried port forwarding, didn't work;
The problem is any port other than the tp-link local management console is blocked, modem drops the connection, no matter what. I'd tried turning off the SPI firewall, and it didn't change anything as well.
I have IP static and my modem can be viewed remotely, so if it helps, DM me to give you the credentials to see it for yourself
Make sure that your Internet IP address is public:
The LAN IP address of your local machine shouldn't be 192.168.1.1 (since that's probably the LAN IP address of your VR400).
You need to set the correct LAN IP address of your local machine in the VR400 Virtual Servers (for example if it's 192.168.1.100):
Also set the correct Protocol type - TCP, UDP or ALL.
Thanks you for follow up dear @terziyski
My Ip is public, you can even view my router here (http://91.92.206.172:65535/), but the the problem I stated was that
the virtual server port on modem WAS NOT accessible even from local network; for instance -> 192.168.1.1:4000
if the modem doesn't respond the local port, certainly it wouldn't be accessible from internet.
The ports exposed here ( e.g. 192.168.1.33:54321 ) are accessible from other local machines
Do you have any idea how can I debug this?
What about 192.168.1.33:4000 ? Is this the device (192.168.1.33) that's running the service in question on its port 4000 ?
You should be able to access that from your local network.
According to the virtual server configured if there's a active service at TCP port 4000 on 192.168.1.33 device, you should be able to access it from external network like this:
http://91.92.206.172:4000 if it is a HTTP server.
The other thing you should check is if your public Internet IP address is static or dynamic.
If it is dynamic then on every device reboot or internet session restart you'll receive a different public IP address.
If that's the case you should use the Dynamic DNS feature to register an account (if no-ip.com for example) and use this <your_domain>.no-ip.com for accessing your router from an external network:
My IP is a permanent static IP, no problem on that side; and my server at 192.168.1.33 is listening on 4000, 54321 and 80 ports. ( it's a simple http server ),
I can call it from my machine ( 192.168.1.100 ), but I don't get anything from modem at all.
I think this piece of code worth more than a thousand words:
Refused to connect : (