Difference between revisions of "Port Forwarding"

Revision as of 18:54, 24 July 2017

When your software is hosted on our cloud server or is not local to your facility there needs to be a port forwarding rule set up by your IT company so that we can access the clock(s) from outside the network. For example, let’s say you have 5 clocks from us and each clock has an internal IP address of 192.168.15.30 through 192.168.15.35 and the public IP address of your facility is 26.59.154.87, your IT company will need to set up the following:

• Port forwarding from 26.59.154.87 on 3001 externally to internal IP of 192.168.15.30 on port 3001
• Port forwarding from 26.59.154.87 on 3002 externally to internal IP of 192.168.15.31 on port 3001
• Port forwarding from 26.59.154.87 on 3003 externally to internal IP of 192.168.15.32 on port 3001
• Port forwarding from 26.59.154.87 on 3004 externally to internal IP of 192.168.15.33 on port 3001
• Port forwarding from 26.59.154.87 on 3005 externally to internal IP of 192.168.15.34 on port 3001
• Port forwarding from 26.59.154.87 on 3006 externally to internal IP of 192.168.15.35 on port 3001

Internally all traffic should be on port 3001. We only need TCP traffic forwarded.

When this is set up correctly, you can test it by using the telnet command at the command prompt and type:

telnet 26.59.154.87 3003

and then hit enter

If the port forwarding is setup correctly, then you should get a blank telnet screen.

There is no need to contact us before this because there is nothing we can do. When you set it up, test it and let us know if it works. If you are able to connect then we will.