|We recently had to put our helpdesk sever on a public IP address. |
If you don't mind me asking......why?
I don't know your setup but lets take a look at a simple one:
Internet >> SOHO Router >> switch(es) >> Clients/Servers
Now lets say you want to be able to allow remote access from external sites to an internal server located within your LAN.
A typical SOHO router, as well as proving DHCP and NAT will also provid firewall protection. Most, if not all SOHO Router's also allow you to do what's called a port forward which allows you to direct external access to an internal resource. Alternatively, you could also put the server in the DMZ in order to allow external access to it.
So now, with a simple SOHO Router, you can have two different methods for accessing an internal server without hanging it out on the internet with an external IP address.
So I guess what I'm wondering is, why you haven't done something like this (ie: either a port forward to an internal resource or, move the internal resource into the DMZ)?