Home / server / Questions / 466503
Accepted
ErnieTheGeek
Asked: 2013-01-13 11:33:37 +0800 CST

Hyper-V 2012 with Server 2003 Guest that requires IPX

  • 772

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."

windows-server-2003

2 Answers

  1. Best Answer

    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?

    • 2

  2. First of all i am sorry for my language. hope this is some help.

    Win 2003 r2 Enable TC/ip on that sever so it can communicate whit network Install FPNW (File and network for Netware Microsoft produkt) Then you have IPX FPNW is downloadable from Microsoft site and you are license to 1000 concurrent connections

    Disable remote desktop (not compatible whit FPNW) use Another software

    Now its the tricky thing, Firewall..

    If you disable firewall on guest and host system its going to work. But this is dangerus thing to do. So you have to manually open and config guest and host firewall settings..

    Hope this is som clue

    And sorry for my bad language!!

    • -1