I have two local networks (one a VirtualBox internal LAN) and a Win2K VM acting as a router between them. I can ping hosts from one network to the other, but not vice versa.
I am running VirtualBox 4.3.6, with a group of VMs on an internal network (10.0.42.x). All VMs are Windows 2000 Server SP4 (not my first choice, but one makes do with what one has). My laptop is running Windows 7 Home Premium. I am trying to configure one of the servers to route between VirtualBox's internal network and the physical LAN (192.168.1.x) which I'll refer to as the external network for the purposes of this question. The router has a 2nd bridged NIC (so it appears as if it were on the external LAN).
Before anyone asks, as they inevitably do, this is a learning exercise.
- The router VM can ping any destination in both networks.
- My laptop can ping any guest in the virtual network. I did have to manually add a route in order to accomplish this:
route add 10.0.42.0 MASK 255.255.255.0 192.168.1.42. The router appears to be working correctly for traffic going from into the internal network.
- The guests can ping any destination in the internal network, as well as the router's external interface. They cannot, however, reach any host in the external network, such as my laptop or the DSL router (neither of which block ping requests).
Ping requests fail with
Request timed out. A
Tracing route to 192.168.1.69 over a maximum of 30 hops 1 <10 ms <10 ms <10 ms 10.0.42.1 2 * * * Request timed out. 3 * * * Request timed out. ...
192.168.1.69 is my laptop and
10.0.42.1 is the address of the router's external interface. This suggests to me something wrong with the router configuration, but all I've done is configure RRAS for LAN routing and left it at that, and it's not stopping me from pinging into the internal network.
What I think I can rule out
- Firewalls (every host involved responds to pings from somewhere).
- Typos (I've copy pasted extensively to the point of paranoia to avoid mistakes).
What I've tried
- Removing & reconfiguring RRAS.
- Added a default route to the guests (
route add 192.168.1.0 MASK 255.255.255.0 10.0.42.1).
- Added default gateway to router's NICs (didn't think it would help, and it didn't).
More details on request; this question is probably long enough as it is.
Default Gateway (DSL router)
Default Gateway 10.0.42.1
I've included the routing tables for the guest that cannot ping outside its own network (this is actually a different guest (10.0.42.254), but like all guests besides the router, it has the same issue):
Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.0.42.1 10.0.42.254 1 10.0.42.0 255.255.255.0 10.0.42.254 10.0.42.254 1 10.0.42.254 255.255.255.255 127.0.0.1 127.0.0.1 1 10.255.255.255 255.255.255.255 10.0.42.254 10.0.42.254 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.1.0 255.255.255.0 10.0.42.1 10.0.42.254 1 188.8.131.52 184.108.40.206 10.0.42.254 10.0.42.254 1 255.255.255.255 255.255.255.255 10.0.42.254 10.0.42.254 1 Default Gateway: 10.0.42.1