Guest Trecius Posted November 7, 2007 Posted November 7, 2007 Hello, Newsgroupians: I have a Windows Server 2003 computer that we're using in our department. It has two NICs. NIC1 connects to the main network of the facility. We use NIC2 ONLY for our department. I am trying to setup the server to act as a gateway between the two networks. Therefore, I am using Microsoft's NAT wizard to create the gateway. Therefore, if anything that is not on the same subnet of our "localized" network will be passed onto the "main network" through NIC1. A small ASCII depiction: COMP1 192.168.1.100 ---- | COMP2 | NIC2 NIC1 192.168.1.101-------- 192.168.1.1 [MAIN COMP] ----- 192.168.3.1 | COMP3 | 192.168.1.102----- However, once I complete the wizard, I still cannot access anything on the "main network." Am I doing this wrong? Should I be doing something else? Thank you. Trecius P.S. I have also set up the switch's default gateway to be the Windows 2003 server, which is 192.168.1.1
Guest Lanwench [MVP - Exchange] Posted November 7, 2007 Posted November 7, 2007 Re: NAT and Windows Server 2003 Trecius <Trecius@discussions.microsoft.com> wrote: > Hello, Newsgroupians: > > I have a Windows Server 2003 computer that we're using in our > department. > It has two NICs. NIC1 connects to the main network of the facility. > We use NIC2 ONLY for our department. > > I am trying to setup the server to act as a gateway between the two > networks. Might I gently suggest that you abandon this technique, use only one NIC, and get a switch that supports VLANs if you need to secure who sees what? Windows is a perfectly fine server, but isn't really the best device to use as an ersatz router - and dual-NIC servers (w/o teaming/NLB, I mean) are generally not recommended. Sorry I can't help you more with the specific questions you're asking here, but this is the sort of thing I flee from when designing networks. You might have more luck posting in microsoft.public.windows.server.networking. <snip>
Recommended Posts