Page 1 of 1
VB upgrade problems
Posted: 13. May 2009, 07:22
by noelc
Hi I recently upgradely upgraded my VB to 2.2.2. I,m running ubuntu 8.1 as host with Windows XP as system within VB.
Before I upgraded my VB I could acess the net from within XP but now I cant?
Is there a known problem here?
Thx
Re: VB upgrade problems
Posted: 13. May 2009, 14:29
by Sasquatch
Please read the Posting Guide and give more information. With things like "it doesn't work", and no additional information on what you tried, what settings you use etc., we can't help you.
Re: VB upgrade problems
Posted: 14. May 2009, 07:59
by noelc
Ok Thanks,
I have previously read the posting guide and not sure what more I can say other than when I try to connect to the web via windows XP installed within VB 2.2.2 I get the standard windows internet "Cant connect to internet" page.
This was working prior to upgradeing my VB. I,ve tried setting variuos connection settings within internet options connection tab to no avail. I doubt this is the problem as no windows settings were originally touched post VB upgrade.
Appreciate your help. What other information would assist
Re: VB upgrade problems
Posted: 14. May 2009, 08:59
by Sasquatch
You still haven't given the info we need, like VM settings, what networking type, NIC emulation etc. Which version did you upgrade from? Any hints in the VM device manager? IP address in the VM?
There are tons of info you can give us, and you don't.
Re: VB upgrade problems
Posted: 17. May 2009, 11:15
by Lombardo
I have the same issue. Running VB on Fedora10, WindowsXP as a VM. Upgrade to 2.2.2 in use rpm -Uvh (ever worked before). vbox setup - no issues. I found out that sometimes networking is not working. I did change nothing in settings (from previsou 2.1.4). I am using NAT. IP address I always get is 10.0.2.15 and default gateway 10.0.2.2. I am using "AMD PCNET family adapter". What is weird that sometimes it is working, sometimes not. In case, that neworking is broken, I can ping default gateway from windows xp, but nothing far. It seems, that it is always working when: all dynamic network tasks are done in linux before I start VB (I mean, all these DHCP clients, wifi auth, etc). What I have never seen before, that windows XP VM sometimes disappear and status is cancelled. Never had that in 2.1.4... It could have also impact to networking? (because it seems, that always after cancelled status - new try to run VM - that networking is working. I know, my information is not complete... But I really think if it would be better to downgrade (I backupd all VDIs) and wait for 2.2.10 or later... And as I see on the internet - with issues with 2.2.x I am really not alone...