RRAS not routng in VMware Server 2.x network

[Talligen]

Ok, I've got a bit of a complex problem (at least it is to me). Here's what I've got:

A Windows Server 2008 computer with VMware Server 2.x installed and hosting 3 guests

1) DC1: Windows Server 2008 domain controller
- Nic #1: Host Only, 192.168.91.51, 255.255.255.0, 192.168.91.53
*WIndows shows this as "Domain network"

2) DC2: Windows Server 2008 domain controller
- Nic #1: Host Only, 192.168.91.52, 255.255.255.0, 192.168.91.53
*WIndows shows this as "Domain network"

3) RRAS: Windows Server 2008 routing and remote access server
- Nic #1: Host Only, 192.168.91.53, 255.255.255.0, no GW
*WIndows shows this as "Domain network"
- Nic #2: Bridged, 192.168.254.2, 255.255.255.0, 192.168.254.1
* Windows shows this as "Public network"
- LAN Routing installed and enabled

VMware VMnet1 is 192.168.91.0
WAN network is 192.168.254.0

All servers have firewall turned off, static IPs, and can communicate with each other. They are all joined to the ACME domain, network discovery and file sharing are enabled.

The RRAS server has internet connectivity on Nic #2. Here is the ROUTE PRINT output:

===========================================================================
Interface List
11 ...00 0c 29 13 7b d5 ...... Intel(R) PRO/1000 MT Network Connection #2
10 ...00 0c 29 13 7b cb ...... Intel(R) PRO/1000 MT Network Connection
1 ........................... Software Loopback Interface 1
14 ...00 00 00 00 00 00 00 e0 isatap.{9B720FF9-72B9-4419-8D5C-C23A4ADF5D45}
12 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
13 ...00 00 00 00 00 00 00 e0 isatap.{530CD138-A6A6-472E-8DEB-6650C051B7F9}
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.254.1 192.168.254.2 266
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.91.0 255.255.255.0 On-link 192.168.91.53 266
192.168.91.53 255.255.255.255 On-link 192.168.91.53 266
192.168.91.255 255.255.255.255 On-link 192.168.91.53 266
192.168.254.0 255.255.255.0 On-link 192.168.254.2 266
192.168.254.2 255.255.255.255 On-link 192.168.254.2 266
192.168.254.255 255.255.255.255 On-link 192.168.254.2 266
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.254.2 266
224.0.0.0 240.0.0.0 On-link 192.168.91.53 266
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.254.2 266
255.255.255.255 255.255.255.255 On-link 192.168.91.53 266
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
0.0.0.0 0.0.0.0 192.168.254.1 Default
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 306 ::1/128 On-link
1 306 ff00::/8 On-link
===========================================================================
Persistent Routes:
None

So here's the question/problem...why can't DC1 or DC2 access the internet?

 

[TechyMcSe2k]

Try changing the DC's GW to 192.168.254.2 Since in a previous post you stated that they could ping the outside interface

http://www.samtechconsulting.com

_______________________________________
Great knowledge can be obtained by mastering the Google algorithm.