Hello I have my IIS server ( Server 2003) multihomed one inteface exposed tothe public and the ohter internal. I have alwaya had problems with gateway issues. The web server seems to get flakey when a defualt gateway isspecified on the internal NIC...so years ago they decisdedto leave this blank. So the website operates correcly but this has now caused browsing and other name resolution problems for those of us that do not resdie on the very same network. So for me I cant ping the box internally and cant setup RDP either so for me to rdp I have to use the external ip essentially you have to be on the same netowk to see this box....if you are on anyother netowrk you cant ping or rdp there must be a better way to have this multihomed setup configured? any suggestions would be appreciated ddecoursey@eriecountygov.org

Rather than having two gateways, which is not appropriate for this configuration, you simply need to add static Routes on this box for your internal network (since you apparently have more than one internal subnet). Here is some information to help you work out the details. Using the Windows Route Command http://www.anitkb.com/2010/03/using-windows-route-command.html How IP Packets are Routed on a Local Area Network http://www.anitkb.com/2010/06/how-ip-packets-are-routed-on-local-area.htmlVisit: anITKB.com, an IT Knowledge Base.

Browsing should work OK on the internal network as long as you have disabled Netbios over TCP/IP on the public NIC (which I hope you have done anyway). The browsing problems with multihomed servers are due to the server (which is probably the master browser) having two IPs associated with its Netbios name. The default gateway issue is a different problem. This affects the routing. The multihomed server should have only one default gateway and that is on the public NIC pointing out to the inernet, so the gateway on the internal NIC should be blank. If you have multiple internal subnets, use specific static routes as [JM] described. Bill