Thank you, Steve.

I should have mentioned, it is a small network used primarily for in-house
development of VB, and web apps. They use all servers internally for
different things, then want the webserver to have it's own public IP because
they host these apps for testing. Aside from the errors of having code on a
public machine, and multi using servers (these aren't things that are going
to change) what would work best given the use?

They currentlly have the cable modem going to a crappy d-link router that
then port forwards 80 -> web server. So they are only using 1 of their 5 ips
right now (for the Dlink, everything else is NAT) and want to utilize more
of them.

-J