IPX does not only sound like an ancient protocol, it IS an ancient protocol. A very nice protocol, but indeed ancient. a 15-ish years ago I worked with Novell servers and even back then we needed to install additional packages to be able to make (for instance) windows clients be able to communicate with the Novell servers. Especially the NDS account provider (much more sofisticate than AD!) had so many great features.
Some reading on the windows client for Novell: https://www.novell.com/documentation/windows_client/
To get back on topic: @Jesus_Chavez_Bastias, just to satisfy my curiosity, why you decided to use a Novell 6.5 server for your infrastructure? Back in 2003 Novell already moved towards a Linux kernel based environment and leaving most of the ‘old’ Novell ecosystem (inlcuding the IPX-SPX protocols) So to reinstate such a system now is (IMO) quite odd. Chances are that you will find it difficult to find support for the IPX protocol in the first place…
I don’t think that CentOS recognize/support IPX.
Do Novell support any VPN protocol? Maybe… you can have an IPSec direct connection with your server.
Or connect via OpenVPN to Novell Server via IP.
Exist applications mounted over Novell yet sadly. In all Wikis, forum, etc, it says “OpenVPN tap connection support all protocols such as IPX, AppleTalk, etc.” even in OpenVPN documentation but it doesnt work really.
I am trying to conenct my novell server from the same network (using Nethserver as DHCP Server) and it works correctly with IP and IPX to access to my Novell Server, but from differents lan segments connected to nethserver dont work.
Same case with OpenVPN, with TAP and using a bridge with VPN and LAN interfaces, is not working, IPX is not passing into Nethserver.
Try to do that. will be a free headache and that case if you try and fail… welcome to my world
By IP, when OpenVPN is connected, the PING to Novell Server is lost, no reply, but I can PING to all network less my Novell Server (for example PING to Gateway, etc).
When OpenVPN is disconnected, PING is returned to my Novell Server.
Well, after one week to try and try and try… I fixed the problem!. When you work with some virtualization such as Virtualbox, VMWare, etc. PLEASE! dont forget enable the “PROMISCUOS MODE” in each ethernet card when you use OpenVPN.
In the past we confuguratet IPX over VPN but it not easy (from the packt side). What kind of VPN you build? When i remember correctly Client and IPX shoud be in the same IP range, so VPN must be full tranparent (same network like client IP 10.10.10.99 server IP 10.10.10.1)…
1.- Create a OpenVPN Warrior type TAP (why TAP?, because it transport protocols layer 2 like IPX)
2.- Open port 1194 UDP in NethServer
3.- Change Virtualbox (or VMWare) Ethernet cards to promiscuos mode (Because you will transmit Broadcast and Broadcast in VirtualBox and VMWare is disabled by default).
4.- Install Novell Client over Windows XP (because XP still have IPX protocol) with custom option,and choose only IPX.
5.- Connect to VPN and Open the Novell Client and search the trees.
Axel, The same IP segment is correct because you VPN connection is a Bridge Connection.
Normaly you need a direct contakt between the NICS. Than IPX will be transported.
VPN / OpenVPN there are 2 types of contacts tap and tun. Tunnel is tun and a IP Connect that cant working. With Tap you had a chance. Normaly tap let fly the complete (mostly) Ethernet packages across the VPN. Tun uses only the smaller UIP packages.
I didnt know how long the latency is over VPN. That can be a problem. Try it first with a TAP VPN in your local Network before using the Internet …
Sry to be so late to join this conversation, but as one of the few still operating Novell Netware, I feel obliged to provide some input.
NetWare 6.5 kann Bridge IPX segments via IP segments, it’s a further development of their old IPX over IP using encapulation. This was introduced already in NW4.11, before the introduction of PureIP in Netware 5.0…
Naw, moved off from BNC a long time ago, even with NetWare 3.12…
Still kept a Segment in the Office running for tests and/or old NICs, connected to a 3Com Office Connect Switch that still supported BNC.