Win2003 NAT Routing Problem

Community,
I'm trying to setup a Windows 2003 stand alone server as a NAT router to
isolate my lab network away from my corp network. Installed Windows 2003
Standard Server with two NIC Cards. Follwed the Routing and Remote Access
wizard to create a VPN with NAT Routing. This way if I need to get back into
the lab network from the corp network, I could use a VPN connection.

Config:
LAB Nic = 192.168.3.1/24
Corp Nic = 10.10.10.200/8

Problem:
Clients from the lab network can get accross NAT router to the Corp Lan, but
only to hosts in the 10.10.10.0 subnet, they can't get to anything on the
other corp networks (can't get out of the 10.10.10.0 subnet). The Widows
2003 server can ping addresses in the 10.10.10.0 network, but not anything on
the other side of the 10.10.10.0 network. Clients in the 10.10.10.0 network
can get accross to other corp subnets, but clients in other subnets can't
ping my windows 2003 server at 10.10.10.200. I've checked that the Windows
2003 server NIC connected to the corp network has the correct subnet and
router configured. Is there something I need to add to the servers route
table?

--
Thanks
Jim


Jim Fitch

Jim-

Take a look at your route table. Your looking for the default route
(0.0.0.0). It should be pointing out to 10.10.10.1 or whatever your DG is on
the 10 network. Make sure your 192.168.3.0 network does not have a DG.

"Jim Fitch" <(E-Mail Removed)> wrote in message
news:0F92098F-98EF-4CFB-90F8-(E-Mail Removed)...
> Community,
> I'm trying to setup a Windows 2003 stand alone server as a NAT router to
> isolate my lab network away from my corp network. Installed Windows 2003
> Standard Server with two NIC Cards. Follwed the Routing and Remote Access
> wizard to create a VPN with NAT Routing. This way if I need to get back
into
> the lab network from the corp network, I could use a VPN connection.
>
> Config:
> LAB Nic = 192.168.3.1/24
> Corp Nic = 10.10.10.200/8
>
> Problem:
> Clients from the lab network can get accross NAT router to the Corp Lan,
but
> only to hosts in the 10.10.10.0 subnet, they can't get to anything on the
> other corp networks (can't get out of the 10.10.10.0 subnet). The Widows
> 2003 server can ping addresses in the 10.10.10.0 network, but not anything
on
> the other side of the 10.10.10.0 network. Clients in the 10.10.10.0
network
> can get accross to other corp subnets, but clients in other subnets can't
> ping my windows 2003 server at 10.10.10.200. I've checked that the
Windows
> 2003 server NIC connected to the corp network has the correct subnet and
> router configured. Is there something I need to add to the servers route
> table?
>
> --
> Thanks
> Jim

You might also check what subnet mask is being used on your 10.10.10
subnet. If your company is using an 8bit subnet the network would be
10.0.0.0/8 . I suspect that you should be using 10.10.10.0/24 .

Neteng wrote:
> Jim-
>
> Take a look at your route table. Your looking for the default route
> (0.0.0.0). It should be pointing out to 10.10.10.1 or whatever your
> DG is on the 10 network. Make sure your 192.168.3.0 network does not
> have a DG.
>
> "Jim Fitch" <(E-Mail Removed)> wrote in message
> news:0F92098F-98EF-4CFB-90F8-(E-Mail Removed)...
>> Community,
>> I'm trying to setup a Windows 2003 stand alone server as a NAT
>> router to isolate my lab network away from my corp network.
>> Installed Windows 2003 Standard Server with two NIC Cards. Follwed
>> the Routing and Remote Access wizard to create a VPN with NAT
>> Routing. This way if I need to get back into the lab network from
>> the corp network, I could use a VPN connection.
>>
>> Config:
>> LAB Nic = 192.168.3.1/24
>> Corp Nic = 10.10.10.200/8
>>
>> Problem:
>> Clients from the lab network can get accross NAT router to the Corp
>> Lan, but only to hosts in the 10.10.10.0 subnet, they can't get to
>> anything on the other corp networks (can't get out of the 10.10.10.0
>> subnet). The Widows 2003 server can ping addresses in the
>> 10.10.10.0 network, but not anything on the other side of the
>> 10.10.10.0 network. Clients in the 10.10.10.0 network can get
>> accross to other corp subnets, but clients in other subnets can't
>> ping my windows 2003 server at 10.10.10.200. I've checked that the
>> Windows 2003 server NIC connected to the corp network has the
>> correct subnet and router configured. Is there something I need to
>> add to the servers route table?
>>
>> --
>> Thanks
>> Jim