Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Fairly stumped on this one.

I've got a Hyper-V 2008R2 server hosting several server VMs. We're looking to migrate to newer hardware and we want to run Hyper-V 2012.

I've picked up a Proliant ML350 G6, multiple processors, lots of RAM, RAID10. Installed HV Server 2012, setup a couple windows servers on it everything runs great.

Until I try to migrate a Windows 2003 server over from the 2008R2 box. This VM needs to communicate with a Netware 6.5 server via IPX. (I know. Netware 6.5? I'd get them to dump it if I could, but its a long story.) Anyway, for some reason this server moves over just fine, can login to AD, get access to everything with the exception of the IPX resources.

I'm currently just trying to use the CSNW included with 2003, thats been working fine for years on the 2008R2 server, I'd like to avoid adding in the Novell client if possible.

I've tried removing and reloading the integration components, reloading SP2, doing a repair install of 2003 and so many other things I can't even remember.

TL;DR: How can I get a VM running on Hyper-V Server 2012 to communicate via IPX to other network resources?

EDIT:

My new Hyper-V host is running Hyper-V Server 2012. The guest in question is running Windows Server 2003 R2.

This guest has been running on a Hyper-V Server 2008R2 platform for several years and communicating with a Physical Netware 6.5 server exclusively running IPX.

After moving the guest to the new host IPX communication has been unable to function. the IPX protocol loads fine, no errors, but when we try to login to the Netware box we get "The network path was not found."

share|improve this question
    
Ok, so what is the question? I mean, i read it twice, and I do not find a single question in there that needs answer. I also fail to see how the network protocol of a virtual machine has anything to do with the host OS, given that the network of a VM is a virtualized network card. –  TomTom Jan 12 '13 at 20:01
    
Sorry, my problem is that the 2003 Guest needs to communicate with a server running IPX and it can't. As for why the host OS is relevant it seems pretty clear to me that the only change I made was the host OS and everything stopped working. So I'm pretty sure that the problem lies there. –  ErnieTheGeek Jan 12 '13 at 20:17
1  
I am not sure i get it - the virtual network in Hyper-V should be ethernet and not care even about IP, or? I mean, i am not totally sure- i just do not run anything else. But it is a emulated ETHERNET card, not IP. –  TomTom Jan 15 '13 at 16:54
1  
Install wireshark, see if the guest is actually transmitting anything. Then plug the upstream cable or mirror the switchport and see if you can spot the traffic there as well. –  SpacemanSpiff Jan 17 '13 at 4:02
1  
Is the network adapter in the vm synthetic or legacy? –  Nate Jan 17 '13 at 19:26
show 12 more comments

1 Answer 1

I think your best bet is going to be enabling IP on the NW server, to echo Greg. Otherwise, you're going to have to find some way to get the 2012 host machine to be able to speak/bridge/NAT/or otherwise route IPX, and I think that's a non-starter. You can dick around with the guest all you want, but unless the host can pass the protocol through (and you haven't explained how you're doing the networking), you're not going to get anywhere. I don't even feel like looking up the status of IPX under 2012.

/Edit - looks like I'm possibly incorrect in assuming that the HV host needs to speak IPX, assuming you're bridging the network in both scenarios. Hint - when I said "you haven't explained how you're doing the networking", that's the passive-aggressive way of saying "please explain how you're doing the networking". Both on the host side, and for the guests. There could be a lot of reasons your IPX isn't working; without details, I can only guess. By "External network", is that a bridged connection?

share|improve this answer
    
The network is literally the stock config that comes out of the install. 0 customization on this. Its a standalone host running some legacy systems they need to keep around for legal reasons for a few more years. I've just clicked external network, and associated it with one of the ports on the nic. As for enabling IP, the reason we're using IPX is a custom written app that only wants to communicate over IPX. –  ErnieTheGeek Jan 12 '13 at 21:12
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.