Questions

Answer for:

Access internal IP remotely

Message 3 of 5

View entire thread
+
0 Votes
robo_dev

In order to access the DHCP server, there must be a firewall rule that does two things, it opens a port for communication and sends external communication to the internal IP address of the server.

So, let's say you were using VNC at port 9000 to goto your DHCP server with an IP address of 192.168.0.2. In a Cisco router you need a rule to open port 9000 inbound and a second NAT (network address translation) rule so requests hitting the WAN interface goto the LAN IP of your server.

Most standard home routers let you do the same thing, typically you have to define a 'custom service or program' (opening the Port) and then assign what LAN IP address gets that service (the NAT rule).

In the case of multiple servers, you would have to open more ports, or else use a single device (or server) to control the other devices.

If you want a solution that's bulletproof and secure, there are KVM-over-IP solutions from MiniComm or Raritan that give you BIOS-level remote access to servers from one device...this lets you actually remotely reconfigure BIOS settings or reboot a really-locked-up server remotely...and they are secure and require nothing to be loaded on each server.

In the example listed above where you were using VNC, you would need to open up a port for each server and have a NAT rule for each server (port 9001,9002, 9003, etc.). Then remotely, it's just a matter of pointing to the correct port number in whatever app you use to do remote control.