Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My office doesn't have a "server guy" in employ, so I'm stuck with having to fix server issues for now.

There are 2 servers in our office, both are file/web servers only accessible via LAN. They are currently on the same network, so no issue there. Problem is, we recently got a static IP to use, but it's with a different ISP, so now we have 2 routers in our office.

I would like to open one of the servers to the public as a web/FTP server. But if I hook a server up to the new router, users will no longer be able to access the files shared on that server (because they're on different networks).

How can I go about making one server accessible to the public using the static IP line, but still able to share the files on it to the users connected to the other network?

The server I want to make public is running Windows Server 2008, the other server Windows Server 2003. And as far as I know, IP addresses are assigned by the router.

I'm just a developer, don't know much about networking.

share|improve this question

migrated from Mar 11 '10 at 16:58

This question came from our site for professional and enthusiast programmers.

I honestly believe you'll be better off paying a professional to handle this for you. By your own admission this is outside of your field of expertise and by the sounds of it you're looking to get this done as a once-off thing. This may sound condescending, but I'd bet that all the answers below are only going to lead to more questions as you probably have no idea what they mean anyway. – ThatGraemeGuy Mar 14 '10 at 12:22

Simply - dont change anything on the server. The router will anyway use NAT.... put in a reverse NAT mapping so that requests to specific ports no the public IP address get forwarded to the server. As you dont change anything on the server, it still is reachable from the office.

That would be - port 80 for http, 443 for https if needed, port 20/21 for FTP.

And get someone you can call for config. Really. And learn from him - develoeprs should know the basics of network admin.

And next time - ask on servervault.

share|improve this answer

If you want a machine to be accessible via both a public and private network the most simple method of setting that up is to install a second network card into the server. That way the machine will be able to communicate with both the private and public networks. Once both network cards are installed you would need to make sure that the server has both a public and private ip address or alternatively is configured to be in the DMZ for the public network or has port forwarding setup for the public network. Then you can configure your web server to serve requests for both the public and private ip addresses. You would also want to make sure that the server has a firewall in place to prevent access to services that should only be accessible via the private network.

Good luck.

share|improve this answer

You could use a dual WAN router like the Draytek 2955, and do port forwarding on that.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.