VMing sbs 2003 networking issue

autumn

Active Member
Reaction score
28
Location
Geelong, Victoria, Australia
G day All

I'm just started looking at using Hyper V and VM's. I've done a test conversion of my test server (SBS 2003) usisng the P2V convert from MS and mounted it fine and ran the VM driver and everything seems to running good except the networking. I have removed the old NIC in the device manager so it shouldn't be that, but hey, I've seen funny things happen before.

I have DHCP set up on my router, I've set the virtual switch as a external network. The physical server (server 2012 std) is getting IP addresses and has internet. I did think that the problem might have been that the physical server wasn't activated but now it is and still the same problem. The VM isn't picking up any DHCP addresses, when I set the ip manually (same as the physical test machine) I still have no networking between the phyiscal or VM except the phyiscal test server says there's a conflicting IP address on the network. that said I can't ping or connect to the VM. even from the host machine.

As I said this is the first time I've done it so is there something I'm missing as a newbie to hyper v's VM's?

Thanks

Tim
 
Is the NIC of the SBS guest "connected"? (right click).
Don't forget...SBS will hate being set to "obtain auto"...it's DNS will not function thus the rest of the server and active directory will barf all over the place. NEEDs to be static...and looking at itself for DNS. You want it running DHCP for your network. I'd set the Server12 hyper-v host static too.
 
Thanks Stonecat

Yes it was connected, I can't get back in because of activation at the moment, I'll copy the vhd file back in.

what i have on the host in networking is
first virtual switches
external network - point to secondary network card (which is connected to the netrwork)
"allow management operationg system to share this network adapter" is tick
None thing else is ticked

In network connections (host)
Ethernet 2 is enabled
in the properties of it there is only Hyper v extensible virtual switch tick, nothing else. I've tried enabling IPv6 and IPv4 with client for MS networks but it says they will be disabled because of other conponents installed, I take that to be the virtual switch. Which means I can't set the IP address either.

There is a vEthernet as well, listed as unidentified network. I haven't touch this

Thanks Tim
 
OK I've done a bridge between Lan1 and the Virtual switch and it's working. I've unplug the lan form lan2 and it still works. I take it you should need to do this or is this part of the process?
 
OK I understand that the vitrual switch is bond to the NIC, in my case the virtual switch is bond to NIC2 but to get external access I have had to bridge NIC1 to the virtual switch (listed in the networking). I would have thought that making the virtual swqitch and binding it to NIC2 then all I would need is NIC2 to be connected the network and the virtual NIC would connect to the real network. Or am I missing it? would some images fromthe server help?
 
Thanks Loring

do or don't I need to bridge between NIC1 and Vnic? attached are images of the networking and the virtual switch settings.

Also, when you say to disable the Offloading I take that to be in the guest OS settings or do you mean the vEthernet (as listed in nics on physical) or Ethernet2 which is where the virtual switch is bonded to.

sorry to be a pain
 

Attachments

  • virtual switch.jpg
    virtual switch.jpg
    66.2 KB · Views: 32
  • nics on physical.jpg
    nics on physical.jpg
    32 KB · Views: 29
With Intel NICs, I would recommend turning off offloading on everything except the actual physical cards. Broadcom, on the other hand, is crazy buggy, so we disable it on all. Hit this link, and scroll down to the network section

http://msdn.microsoft.com/en-us/library/dd722835(v=bts.10).aspx

You don't need a bridge on anything. That's just adding a redundant loop in your networking and will probably cause you problems. Remember (especially as you're learning), K.I.S.S.
 
Last edited:
A_G I was actually going to ask what you were doing for the hosts NICs re:offloading....
Was guessing you left it on with Intels....killed it on the rest.
I've been leaving it on with recent model Broadcoms...haven't had driver issues much since 2k8 came out. Try to always get Intels in there anyways...worth the 99 or 140 bucks to add one in.
 
I prefer Intel as well, but a lot of stock configurations are coming with Broadcom. Generally, I go with dual-port Intel cards. Damn things are nearly indestructible and bloody fast.

Even with newer Broadcom, I've run into issues. Year old server at a client location had been running perfectly with '08 R2 and hyper-v. Suddenly a couple of weeks ago, their RDS vm was crawling. Turned off off-loading on the physical nics and problem disappeared instantly.
 
Thanks guys.

I through that I didn't need to do the bridging but that's the only way I've been able to get it to talk to the external network. I'll read those articles and see what I've done or need to do. I'll let you know.

In previous posts you have mentioned about SCVMM is this part of server 2012 std or is it in enterprise or is it separate purchase again? Is it available as part of the Microsoft partner program? You mentioned about running a client on the old phyiscal server to do an online conversion straight in to the hyper v host. I take this would be alot easier that disk2vhd program then copying into the host.

A little hijack here, one my first posting about hyper-v last year, the customer post pone the installation of the new server at the moment and I'm re thinking about the configuration of the RAID's, I had an RAID 0 for the host OS then a RAID 10 for the two guests OS (1 - MSWin SBS Essentials 2011 with exchange, 2 - 2012 Std with a progress DB), do you think I should have two sets of RAIDs (one each for the guests) as one has exchange and the other is a DB?
Again thanks alot for all your help.
 
it would run better with OS on one volume, exchange / database on a different volume, better yet database on 3rd volume by itself if there's a lot of users hitting it.
 
Ok Guys, I don't know what is happening. I've gone through the step by step guide and the Performance Tuning Guidelines in the check list and can't see what's wrong. I did delete the virtual switch in the console and go through the steps as shown.

With the step by step guide the IP addresses on the physical card and the virtual switch are the same IP addresses. Also the DNS setting aren't set. Is that right? I've tried with both same and different IP's and DNS set and not set and still no ping or internet from the guest.

Until I set the DNS in the virtual switch to the gateway the physical machine had no internet.

Should I blow the install away and start from again?

Attached are images of the network settings.
 

Attachments

  • physical bond lan.jpg
    physical bond lan.jpg
    44.6 KB · Views: 37
  • physical server networking.jpg
    physical server networking.jpg
    16.4 KB · Views: 32
  • ping from guest to gateway.jpg
    ping from guest to gateway.jpg
    42.4 KB · Views: 37
  • v switch settings.jpg
    v switch settings.jpg
    44.7 KB · Views: 31
  • virtual lan in guest IP.jpg
    virtual lan in guest IP.jpg
    39.7 KB · Views: 33
OK I don't know what caused the issue the the 2003 SBS test server wouldn't connect to the network. even after another p2v conversion it was still doing the same. But I've done a 2008 SBS p2v conversion and this is connecting and talking to the network and internet fine.
 
I've done several p2v's with sbs03....the setups I have are typical of the example in the link I gave above..didn't have the complication your screenshots show. Not sure what's hanging yours up. Maybe if you get time (non production hours)....wipe those clean and rebuild the connections from scratch.
 
Back
Top