Thin Client and Virtual Machines Thread, Network problem with Hyper-V to VMWare server in Technical; Dear all,
I have just converted a Hyper-V server to a VMWare server (Windows 2008R2). I used the latest converter ...
24th February 2011, 03:49 PM #1
24th February 2011, 09:08 PM #2
I don't think this is a direct Virtualisation issue, however I think its a Windows 2008 has an issue with missing & new virtual NIC device.
Try select "No" when setting IP address also look at Error message when you try to set an IP address on a network adapter may help you resolve the issue.
25th February 2011, 10:15 AM #3
- Rep Power
Thanks apaton... new development...
On another note I forgot to say/didn't think yesterday the server is on a different vlan and I think this is why I can't ping it as I have since converted another vmachine and it works fine!
I found a option on the esxi server to set the network adapters to vlan 4095 to let it access all vlans, is this the right things to do??? Also am I opening the other servers on the default vlan up to the traffic on the other vlan as I don't want traffic going between the to?
25th February 2011, 10:31 AM #4
I've found when importing machines its best to remove all the old hardware - as it does sometimes cause it to get in a tizz
Log in and start a command prompt enter the following commands:
then View->Show Hidden Devices
and remove all the greyed out hardware
Thanks to Domino from:
FatBoy (25th February 2011)
25th February 2011, 11:10 AM #5
25th February 2011, 12:59 PM #6
Setting VLAN to 4095, I've never tried it, but it doesn't sound like the right thing to do.
Originally Posted by FatBoy
The vSwitch configuration can become complex with VLANS and I don't know how your Network switches are configured, try a creating a simple configuration.
Create a new vSwitch with a single NIC on the correct subnet. (No VLAN config)
Change the win2008 VM to use the new vSwitch.
Then test again, might help resolve if its a Windows or VMware configuration issue.
Last edited by apaton; 25th February 2011 at 02:20 PM.
25th February 2011, 03:14 PM #7
- Rep Power
Tried that didn't work but just fixed the problem!!!!
Left the switch alone and moved the network cable to another port setup the vswitch again and didn't tag it on vlan 20 and it worked! Just got to do a bit of testing and I should be ok
Thanks for the input all
By Tricky_Dicky in forum Thin Client and Virtual Machines
Last Post: 14th March 2011, 11:34 AM
By talksr in forum Thin Client and Virtual Machines
Last Post: 28th January 2011, 01:44 PM
By Gardinho in forum Thin Client and Virtual Machines
Last Post: 24th September 2010, 12:39 PM
By phoenixsurfer in forum Thin Client and Virtual Machines
Last Post: 22nd June 2010, 02:32 PM
By FN-GM in forum Thin Client and Virtual Machines
Last Post: 15th July 2009, 02:09 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)