LabVIEW
TCP/IP over Internet
解決済み
Right. So your router is allowing local private network 192.168.x.x addresses and is isolated with no routing from external addresses such as your 5.154.114.180. Since you have not shown any routing/firewalls etc configuration it is hard to help.
You say all is set up correctly but it doesn't work. It seems that if it isn't working then it is not setup correctly.
You need to have your router at LEAST do port forwarding as far as I can tell from the non-description of your setup.
@sth wrote:
You need to have your router at LEAST do port forwarding as far as I can tell from the non-description of your setup.
Defining a DMZ is port forwarding. it means that all incoming connections go to the DMZ server.
Is the client computer also on the local network? If so, you might not be able to reach the target because not all NAT routers implement a loopback proxy to allow that. You should try from a computer that is physically on the outside.
castek89 wrote:A question, the TCP client requires port forwarding !? Or just the server?
Port forwarding is done on the router. It has nothing to do with client or server configuration.
- The client contacts the public IP of the router
- The router inspects the port forwarding rules and decides where the connection should go
- The router edits the packets with the new destination IP and port, places an entry in the NAT table, and puts the packet on the local network
- The server on the LAN responds and sends it to the gateway (the router in this case).
- The router edits the source IP and port of the outgoing packet to appear to come from the router and sends it to the client.
The server most likely has additional security settings that could block communications:
- The firewall might need to be configured to allow the incoming connection.
- The server settings might need to be configured
- It might only accept connections from the same subnet by default, for example.
There is a difference between DMZ/NAT/Port forwarding. It doesn't really matter for this discussion. NAT is just a dynamic management of the port forwarding based on an outgoing connection.
If you need some address outside your current local network to access the server then you need to set up a static port forwarding rule in your router. This is true for connections from outside trying to start and establish a link inside. You need to forward all incoming connections on port 23149 to go to your local server 192.168.0.168 on the same port.
You say that the server is DMZ. DMZ is usually referred to as within the router not the server. THere MUST be a router between the internet and your server on the private net. You will have to contact your server as the public IP of that private subnet the server is on.
As Christian says, it is significant if you can contact the server on the same private net.
You need to be a lot more specific as to what you are trying to connect to what. I can make some guesses but guessing wrong would just confuse things. "using public IP" is not a clear statement of what and where you are trying to connect from and to and over what port.
If you have a DMZ you will have to manually set up port forwarding so that incoming packets are routed to the correct server. You can set it such that all ports are redirected to a single machine on the private network.
Scott, DMZ is not used here in the classic way. On cheap consumer routers, a default forwarding rule that forwards all ports not otherwise defined to a specific IP is sometimes incorrectly called DMZ.
