Vista host, Windows guests, 2.2.0 update networking issues
Posted: 20. Apr 2009, 19:38
Host OS: Windows Vista Home Premium
Guests OSs: Windows XP Pro, Vista Business, Server 2003
Problem: With the last version, I used remote desktop with my virtual machines (remotely connected to the virtual machines). I updated and first had to figure out how to get it to start a guest at all since it said I was out of memory (nowhere near out but it thought so). After reducing memory for the guest (which worked fine before with more), I find out the network interfaces for the virtual machines were butchered. It doesn't come remotely close to working. I tried playing with the new settings and not a single setting lets it get an address from the DHCP server that is also serving my host OS like it used to. Someone mentioned "bridged" is like the old setting that acted basically as a pass-thru with the host but unfortunately, "bridged" does not work at all - it does not even allow it to remain selected and click OK to close the settings page.
So my question is this: how do I use these new networking types to get it back to the way it was? For example, if the host OS is given the address 192.168.3.100, the virtual machine could receive 192.168.3.101. Now it isn't possible. And if it can't be fixed, can I safely uninstall 2.2.0, find the old version again and go back to it since 2.2.0 has some serious issues? I really like being able to use the memory I have instead of being told there isn't enough when there is and I would like to be able to remotely connect again (not understanding why it is a perfectly functional setup had to be messed with either).
RN
Guests OSs: Windows XP Pro, Vista Business, Server 2003
Problem: With the last version, I used remote desktop with my virtual machines (remotely connected to the virtual machines). I updated and first had to figure out how to get it to start a guest at all since it said I was out of memory (nowhere near out but it thought so). After reducing memory for the guest (which worked fine before with more), I find out the network interfaces for the virtual machines were butchered. It doesn't come remotely close to working. I tried playing with the new settings and not a single setting lets it get an address from the DHCP server that is also serving my host OS like it used to. Someone mentioned "bridged" is like the old setting that acted basically as a pass-thru with the host but unfortunately, "bridged" does not work at all - it does not even allow it to remain selected and click OK to close the settings page.
So my question is this: how do I use these new networking types to get it back to the way it was? For example, if the host OS is given the address 192.168.3.100, the virtual machine could receive 192.168.3.101. Now it isn't possible. And if it can't be fixed, can I safely uninstall 2.2.0, find the old version again and go back to it since 2.2.0 has some serious issues? I really like being able to use the memory I have instead of being told there isn't enough when there is and I would like to be able to remotely connect again (not understanding why it is a perfectly functional setup had to be messed with either).
RN