![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
dear lazyweb
Jul. 4th, 2006 03:55 pmHas anyone out there any idea what could fsck routing in XP Pro such that it’ll see the LAN fine, but won’t route through its gateway? It’s running under VMware with bridged networking, but so are five other VMs (W2K, W2K/AS and XP pro, variously) all of which will happily route anywhere.
IP and routing settings look fine; it’s most odd. And irritating.
( working XP Pro VM )
( broken XP Pro VM )
The only difference there that I can see (apart from the IP address) is that the virtual ethernet device is 0x2 on the working box, 0x10003 on the broken one. I don’t have any idea how the interface numbers are assigned (by XP? by VMware?), let alone if they make any difference.
(10.0.0.1 is our dual WAN router, sitting outside the Sonicwall, if anyone is curious)
IP and routing settings look fine; it’s most odd. And irritating.
( working XP Pro VM )
( broken XP Pro VM )
The only difference there that I can see (apart from the IP address) is that the virtual ethernet device is 0x2 on the working box, 0x10003 on the broken one. I don’t have any idea how the interface numbers are assigned (by XP? by VMware?), let alone if they make any difference.
(10.0.0.1 is our dual WAN router, sitting outside the Sonicwall, if anyone is curious)
