RRAS question

I'm using Virtual PC to study for 70-291 and have the setup shown in this
picture:
http://www.brigan.com/test/NetworkLayout.jpg

There are 2 VPC's running Server 2003 and 1 running XP Pro. The host is
also XP Pro. The member server and the PC are both joined to the domain,
AD and internal network connectivity works fine.

I'm trying to use the Member Server/RRAS server as a router, to provide
internet access for the Domain Controller (serverDC1) and the PC.

I have a static route configured on the Linksys:
Interface: 192.168.1.1
Destination: 172.16.1.0
Subnet mask: 255.255.255.0
Default Gateway: 192.168.1.98

There is no static route on the RRAS server

I can reach the router from VPC1. But I cannot from ServerDC1. When I try
to ping from the DC to the 192.168.1.1 address I get "destination host
unreachable"
Which to me means it's not even getting routed from the 172.16.1.0 network
to the 192.168.1.0 network.
Which makes no sense, since that same thing works fine for the PC (VPC1)

Why can't my DC reach the router?

TIA

"JohnB" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I'm using Virtual PC to study for 70-291 and have the setup shown in this
> picture:
> http://www.brigan.com/test/NetworkLayout.jpg
>
> There are 2 VPC's running Server 2003 and 1 running XP Pro. The host is
> also XP Pro. The member server and the PC are both joined to the domain,
> AD and internal network connectivity works fine.
>
> I'm trying to use the Member Server/RRAS server as a router, to provide
> internet access for the Domain Controller (serverDC1) and the PC.
>
> I have a static route configured on the Linksys:
> Interface: 192.168.1.1
> Destination: 172.16.1.0
> Subnet mask: 255.255.255.0
> Default Gateway: 192.168.1.98
>
> There is no static route on the RRAS server
>
> I can reach the router from VPC1. But I cannot from ServerDC1. When I
> try to ping from the DC to the 192.168.1.1 address I get "destination host
> unreachable"
> Which to me means it's not even getting routed from the 172.16.1.0 network
> to the 192.168.1.0 network.
> Which makes no sense, since that same thing works fine for the PC (VPC1)
>
> Why can't my DC reach the router?
>
> TIA
>

If one machine on a subnet works and another doesn't, it is usually a
config error.

Do an ipconfig /all on both machines and check what is different (apart
from the IP address). Particularly check the subnet mask and default gateway
settings.

Hmmm..... I can't believe I didn't see this - I didn't have a default
gateway on the DC. I just put that in there and everything is good!

Thanks, now I can stop banging my head against the wall.


"Bill Grant" <not.available@online> wrote in message
news:(E-Mail Removed)...
>
>
> "JohnB" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> I'm using Virtual PC to study for 70-291 and have the setup shown in this
>> picture:
>> http://www.brigan.com/test/NetworkLayout.jpg
>>
>> There are 2 VPC's running Server 2003 and 1 running XP Pro. The host is
>> also XP Pro. The member server and the PC are both joined to the domain,
>> AD and internal network connectivity works fine.
>>
>> I'm trying to use the Member Server/RRAS server as a router, to provide
>> internet access for the Domain Controller (serverDC1) and the PC.
>>
>> I have a static route configured on the Linksys:
>> Interface: 192.168.1.1
>> Destination: 172.16.1.0
>> Subnet mask: 255.255.255.0
>> Default Gateway: 192.168.1.98
>>
>> There is no static route on the RRAS server
>>
>> I can reach the router from VPC1. But I cannot from ServerDC1. When I
>> try to ping from the DC to the 192.168.1.1 address I get "destination
>> host unreachable"
>> Which to me means it's not even getting routed from the 172.16.1.0
>> network to the 192.168.1.0 network.
>> Which makes no sense, since that same thing works fine for the PC (VPC1)
>>
>> Why can't my DC reach the router?
>>
>> TIA
>>
>
> If one machine on a subnet works and another doesn't, it is usually a
> config error.
>
> Do an ipconfig /all on both machines and check what is different (apart
> from the IP address). Particularly check the subnet mask and default
> gateway settings.