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
I've picked up a Proliant ML350 G6, multiple processors, lots of RAM, RAID10.
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
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
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?
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
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."