Internal network server 2008 as router RIPv2 does not work

[stan2398]

I have 16 Windows Server 2008 R2 machines configured as routers daisy-chained all on separate subnets (1 subnet per 2 routers). I have connected specific machines by using different names for the internal network segments to correspond to the separate subnets. I want to communicate between machines with RIPv2. I want to eventually insert a Cisco router in the chain and practice with IOS. Well, RIP doesn't work on the current setup. What can be done?

I did figure out how to do this by making changes to the NICs in the guest machines, so it was not a VB problem at all. Anyone interested can email me at stan2398@swbell.net.

[scottgus1]

Except for "Windows Server 2008 R2", "routers", "internal", and possibly "Subnets" I can't understand what you're trying.

Virtualbox just provides virtual networking hardware. What you do with it is up to you. If you can ping over the network, and access shared folders, then the Virtualbox network is connected, and the rest is up to the operating systems and programs installed in the guests.

See the manual, section 6, on the types of networking Virtualbox provides.

[BillG]

I wish I had enough RAM to run 16 vms at once.

Does anyone still use RIP?

[stan2398]

OK, I have found that the problem is caused by network loop(s). The first five routers can ping each other- the rest exceed hop counts or time limits. I have tried to cable each machine to the next one in line by using Internal Network with a unique name to each connection in VirtualBox. Any suggestions for preventing loops in this situation?

Window Server 2008 only uses 512MB per machine. I have 16 GB of memory.

[scottgus1]

Any suggestions for preventing loops in this situation?

Connect carefully.

Once the networks are connected, any further errors will be pebcak errors.