Ip conflict after installing virtual box on Server 2008 r2

Hyper-V specific discussions

Ip conflict after installing virtual box on Server 2008 r2

Veeam Logoby LucasM » Wed Jul 03, 2013 1:55 pm

Hi guys, this is my first post here, so ill try to do my best-

I have 3 servers running on my company, all of them running server 2008 r2. I have about 140 virtual machines virtualized on hyper-v.
But recently, an employee installed Virtual Box on the newest server (we finished installing it last week). And suddenly, all the virtual machines on that server started having network issues. [unidentified network]
I tried uninstalling virtual box, wich is not important to me particularly, but the problem seem to remain. The only way i found to solve this problem, is by changing the static IP from the server to a dynamic one.

Whats the problem? by doing this, we wont be able to log in to the server by using the VPN. When i stay home, the only way to connect via remote desktop to that server, is by the static IP-

Could this be a hyperV vs Virtual box issue ? if i m not mistaken, before installing virtual box the server was running fine.

All answers will be appreciated.

Lucas.
LucasM
Lurker
 
Posts: 1
Liked: never
Joined: Wed Jul 03, 2013 1:33 pm
Full Name: lucas mutuverria

Re: Ip conflict after installing virtual box on Server 2008

Veeam Logoby Vitaliy S. » Thu Jul 04, 2013 7:17 am

Hi Lucas,

Hmm...what network adapter have you chosen for the Virtual Box? How is your VM network configured on the Hyper-V host? If I were you I would also check events on that Windows Server for more info on the root cause of the issue.

P.S. And why did you need virtual box on a Hyper-V server? ;)

Thanks!
Vitaliy S.
Veeam Software
 
Posts: 19539
Liked: 1097 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: Ip conflict after installing virtual box on Server 2008

Veeam Logoby scidoner » Wed Jul 10, 2013 7:14 am

Indeed... what would be the purpose of installing VirtualBox on a Hyper-V box?!

You have a lot of VMs that suggesting to delete the vNetwork/vSwitch on Hyper-V might be a silly one...but you could try that if you don't mind reconfiguring 100+ VMs.
scidoner
Enthusiast
 
Posts: 29
Liked: 6 times
Joined: Sun Jul 07, 2013 4:43 am


Return to Microsoft Hyper-V



Who is online

Users browsing this forum: No registered users and 4 guests