Using the ROUTE command

  • Thread starter Thread starter Peter
  • Start date Start date
P

Peter

Using the ROUTE command in Windows XP...

....to be able to communicate between VMNET1 och VMNET2.

I cant do this.

Attaching the ipconfig and route print below. What is wrong in this
configuration?

Is the gateway correct and what ROUTE command do i need to type on this host
server to enable routing between these two networks?




C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : homepc
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter VMware Network Adapter VMnet8:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter
for
VMnet8
Physical Address. . . . . . . . . : 00-50-56-C0-00-08
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.233.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Ethernet adapter VMware Network Adapter VMnet1:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter
for
VMnet1
Physical Address. . . . . . . . . : 00-50-56-C0-00-01
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.1

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
Ethe
rnet NIC
Physical Address. . . . . . . . . : 00-0C-6E-AA-0B-96
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 195.67.199.42
195.67.199.43
Lease Obtained. . . . . . . . . . : den 13 juni 2004 18:14:51
Lease Expires . . . . . . . . . . : den 19 januari 2038 05:14:07

Ethernet adapter VMware Network Adapter VMnet2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter
for
VMnet2
Physical Address. . . . . . . . . : 00-50-56-C0-00-02
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.100.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.100.1

C:\>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 50 56 c0 00 08 ...... VMware Virtual Ethernet Adapter for VMnet8
0x3 ...00 50 56 c0 00 01 ...... VMware Virtual Ethernet Adapter for VMnet1
0x4 ...00 0c 6e aa 0b 96 ...... Realtek RTL8139 Family PCI Fast Ethernet
NIC - P
acket Scheduler Miniport
0x10006 ...00 50 56 c0 00 02 ...... VMware Virtual Ethernet Adapter for
VMnet2
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.0.0.1 10.0.0.1 20
0.0.0.0 0.0.0.0 10.0.100.1 10.0.100.1 20
10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1 20
10.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1 20
10.0.100.0 255.255.255.0 10.0.100.1 10.0.100.1 20
10.0.100.1 255.255.255.255 127.0.0.1 127.0.0.1 20
10.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1 20
10.255.255.255 255.255.255.255 10.0.100.1 10.0.100.1 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2 20
192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2 20
192.168.233.0 255.255.255.0 192.168.233.1 192.168.233.1 20
192.168.233.1 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.233.255 255.255.255.255 192.168.233.1 192.168.233.1 20
224.0.0.0 240.0.0.0 10.0.0.1 10.0.0.1 20
224.0.0.0 240.0.0.0 10.0.100.1 10.0.100.1 20
224.0.0.0 240.0.0.0 192.168.0.2 192.168.0.2 20
224.0.0.0 240.0.0.0 192.168.233.1 192.168.233.1 20
255.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1 1
255.255.255.255 255.255.255.255 10.0.100.1 10.0.100.1 1
255.255.255.255 255.255.255.255 192.168.0.2 192.168.0.2 1
255.255.255.255 255.255.255.255 192.168.233.1 192.168.233.1 1
Default Gateway: 10.0.0.1
===========================================================================
Persistent Routes:
None

C:\>
 
In most cases, adding routes to the router has no effect or makes the
situation worse. The problem is almost always somewhere else. To simply
route between two subnets, the router should have both of its default
gateway settings blank, and no added routes.

192.168.1.x dg 192.168.1.1
|
192.168.1.1 dg blank
router
192.168.2.1 dg blank
|
192.168.2.x dg 192.168.2.1

If one subnet has another gateway, the situation changes. And you almost
always need to change something on the "other" router to get it to work.
eg

Internet
|
external router
192.168.1.254
|
192.168.1.x dg 192.168.1.254
|
192.168.1.1 dg 192.168.1.254
router
192.168.2.1 dg blank
|
192.168.2.x dg 192.168.2.1

In this case, you would need to add a static route to the external
router to "bounce" the 192.168.2 traffic back to the internal router to get
routing between subnets. (It would also give 192.168.2 clients Internet
access.) eg

192.168.2.0 255.255.255.0 192.168.1.1

Working with VMs doesn't change anything. The basic TCP/IP rules still
apply.

I agree with David. Some of those groups seem way off topic!

Bill Grant
MVP - Networking

More information than is available from the command line Help can be found
here:

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-
us/route.mspx

Also, its usually not necessary to cross post to so many groups.

--
Doug Knox, MS-MVP Windows Media Center\Windows Powered Smart Display
Win 95/98/Me/XP Tweaks and Fixes
http://www.dougknox.com
 
Back
Top