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.

I have a Windows XP 32 bit system, which I used to connect to my Novell Netware 3.1x server, which is a database server.

Now I am planning to migrate from Windows XP to Windows Server 2008 R2 (64 bit), but the issue is that Windows Server 2008 R2 doesn't support the IPX\SPX protocol.

Is there any workaround to make IPX protocol work in Windows Server 2008 R2?

share|improve this question
3  
You cannot be serious.. –  pauska Apr 4 '13 at 15:20
1  
What kind of database service is being run on that box anyway? –  rackandboneman Apr 4 '13 at 15:26
1  
After all this why the heck would you care to upgrade the CLIENT to w2k8r2 that makes no sense at all. –  tony roth Apr 4 '13 at 15:38
    
The only logical answer to this would be a security issue on the xp client, is that correct? –  tony roth Apr 4 '13 at 15:50
1  
yep btrieve forgot about that one! And you could go 20 years without an update on netware 3.1 and it would be still secure... from current attack vectors. –  tony roth Apr 4 '13 at 17:03

2 Answers 2

The workaround would be to configure the Netware server for TCP/IP and drop IPX/SPX. It's 2013! This will probably involve an upgrade, but that Netware 3.1 server is twenty years old now.

share|improve this answer
1  
Or run Netware Gateway Services on an NT 4.0 box! –  mfinni Apr 4 '13 at 15:21
1  
NT 4.0 is just 17 years old, so there seems plenty of headroom before it hits the magical 20... BTW: gateway services for netware were available with Windows 2000 Server too. –  the-wabbit Apr 4 '13 at 15:49
2  
But for ultimate fun, I would advise deploying on NT 4.0 –  mfinni Apr 4 '13 at 16:40
2  
All snark aside, turning on TCP/IP on the NW3.1 server is likely your only choice with Server 2008. Both Btrieve and the Oracle version that runs on Netware of that vintage have TCP/IP support. It isn't great support, but it is there. Novell itself abandoned IPX many years ago, so Microsoft felt justified removing support. –  sysadmin1138 Apr 4 '13 at 17:24

Sure. From this link:

 IPX/SPX has been officially removed from windows server system since
 2008.

 http://technet.microsoft.com/en-us/library/cc753256(WS.10).aspx#BKMK_6



 But based on my experience , here is workaround that install this
 protocol for server 2008 :



 1.       Cope files of path below from server 2003 to same path on server 2008:

 ·         Windows\System32\drivers(nwlnkipx.sys,nwlnkspx.sys)

 ·         Windows\inf(netnwlnk.inf)

 ·         Windows\System32(wshisn.dll,nwprovau.dll)

 2.       perform install new protocol steps on 2008, and you can found that IPX/SPX is listed in viable protocol list.

Being 32 bit drivers, I'm not sure what problems you'll run into on a natively 64 bit OS, but this is a workaround, so I guess issues are not unexpected.

(Having posted that, you really should do like Mark suggested and let obsolete technology rest in peace.)

share|improve this answer
    
I have already tried that way... once coping those file from a XP 64 bit and another time from Win 2003 server 64 bit..and then tried to install the IPX/SPX protocol, but windows keep on saying as digitally unsigned drivers and even though its does get installed, but its properties tab is grayed out –  Anvin Abraham Apr 4 '13 at 15:33
2  
@AnvinAbraham Then it looks like you need to upgrade the Netware server to use TCP/IP. Or, you know, replace it with a server running an operating system that's actually used anymore. I hear good things about a spunky new start-up called Microsoft, as well as some Scandinavian guy named Linus who's started experimenting with writing his own GNU/Unix-like kernel. –  HopelessN00b Apr 4 '13 at 15:44
2  
@AnvinAbraham you would need to disable driver signature enforcement to get the drivers loaded at all. –  the-wabbit Apr 4 '13 at 15:53
    
I tried to install after disabling driver signature enforcement, but with same result.. –  Anvin Abraham Apr 5 '13 at 6:01

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.