Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here





Many older (or dos based) programs (games and such) only support IPX.  I would like to implement the IPX protocol over TCP/IP.  This would allow me to set up an "IPX LAN" over the internet.  

I want to specify an IP address or addresses, and connect to them, with what the higher level applications will see to be as a simple IPX netork.

I've heard of and read about KALI, which is supposedly a program that does just what I'm asking for.  I recently heard "rumors" that what I speak of can also be done with no additional networking software.

Any information would greatly be appreciated.

Thank you,


You might want to setup an IPX VPN over IP (something like PPTP or L2TP will do nicely)

I am running the above in order to play Warcraft II over the Internet. However, I make extensive use of Cisco routers to do so, which would fail your "no additional networking software" requirement.

If you are running Windows 2000 pro/server you should have little trouble creating a suitable IPX VPN.


Sorry...outside my realm on this one.  I do know that you could setup a tunnel that would encapsulate IPX within TCP/IP (like docjay has mentioned) but I believe this would take the efforts of both sides to run the same encapsulation protocol (PPTP or L2TP).  I know I route IPX very successfully using a GRE tunnel for all my VPN connections, but this is a Cisco solution.  If you figure a good way out on this, post it as a FAQ this has not been the first time I've seen questions regarding this....

david e
*end users are just like computers, some you can work with...others just need a simple reBOOTing to fix their problems.*


Thanks folks, but I've had no luck.  By the way, to those suggesting server side options, I should have been more clear.  I want to have my machine (a client) act as though it were on an IPX LAN, even though it will be connecting to other machines via the internet or even a TCP/IP LAN.

Thanks again for your suggestions, let's keep at it, there's got to be a work around.


I have found problems with getting ipx to work properly with default windows clients. One solution has been to run an old novell server (2.2 for example) on the network. This seems to get ipx kick started.

Linux can do ipx over ppp. Here's some info i found :-

IPX routing
Here I try to explain more detailed, how IPX routing works.
Every IPX packet has 30-byte header with network, node and socket address for both the destination and the source. IPX packets are encapsulated to MAC (Media Access Control protocol, in our case Ethernet_802.2).

Let some workstation wants to send information to another workstation (server). If both are in same network segment (has same network number), sending workstation sends packet directly. If workstaions are in different networks, the sending workstation must first find a router on its own segment (network) that can forward packets to the segment on which the destination workstation resides.

To find this router, the sending workstation broadcasts a RIP (Routing Information Packet) requesting the fastest route to the destination segment. The router on the sending segment with the shorest path to the destination segment responds to the request (in case of PPP there is only router - Linux box). In its response, the router includes its own network and node address in the IPX header.

When the sending workstation knows the router node address, it addresses and sens packets to the destination workstation as follows:

The sending workstation places the destination node IPX network address - node, address, socket numbers - in the corresponding destination fields of the IPX header.

The sending workstation places its own IPX network address - node, address, socket numbers - in the corresponding source fields of the IPX header, also fill out all other fields in the header.

The sending workstation places the node address of the router that responded to RIP request in the Destination Address field of MAC header (here it's Ethernet 802.2 header, but of cource can be Ethernet_II or Arcnet etc).

The sending workstation places it's own node address in the Source Address field of the MAC header.

The sending workstation sends the packet.

When a router receives an IPX packet:

The router checks the Transport Control fileld of the IPX packet header (to prevent more than 16 hops).

The router checks the IPX header Packet Type field etc.

The router checks IPX header Destination address field to determine how to route the packet. If the packet is addressed to the router, the appropriate socket process handles it internally, otherwise the router forwards the packet.
When a router forwards packet, it can take one of two possible actions. If packet is destined for a network number in which the router is directly connected (just our case, Linux box is directly connected by Ethernet with server), the router does following:

The router places the destination node address from IPX header in the Destination Address field of the MAC header.

The router places its own node address in the Source Address field of the MAC header.

The router increments the Transport Control field of the IPX header and forwards the packet to the destination node segment.
If the router is not directly connected to the segment on which the final destination node besides, it sends the packet (in the analogious way) to the next router in the path to the destination node.


RIP (Routing Information Packet). Routers use RIP to exchange routing information with neighboring routers on an IPX network. A RIP router periodically broadcasts a packet containing all routing information known to router (that's just work of IPX RIP). So all routers in network are synchronized. Workstatios also use RIP to locate the fastes route to a distant network. A workstation initiates a route request by broadcasting a RIP packet and then "listen" for thr RIP response that contains the route information.

SAP (Service Advertising Packet) is conceptually similar to RIP. It provides a means for routers and servers to advertise and exchange sevice (print queues and servers, file servers etc) information. SAP includes up to 7 Server Entrys, where sevice type, Server Name with address (network, node, socket) etc. are described.


Look now, how it woks in our case (PPP).

When IPX over PPP starts, workstation (client) sends SAP request (with sevice type "File Server"). Linux box (as router) answers with SAP packets, where available servers are described. Client waits for SAP packet, where "Preferred Server" is described. There it found address (network, node, socket) of necessary NW server.

Then client sends RIP request, to find route to NW server. Linux box is here only router on this segment and answers.

Client reads RIP answer from Linux box and sends packet, where IPX address is address of server and MAC (Ethernet) address is address of Linux box.

Linux box forwards packet to server.

When server receives packet, it requests (first RIP request to find route, then send packet). Now connection between client and server is established and client can first attach to the server and later user can login to server.

Now client can receive SAP packets and use services like NW server volumes, print servers and queues etc.


I'm using Kahn software... Something like Kali. I think this is the easyest way. Not the best but usable. Try it.


I found the problem on the Windows network that running NWLink and use Cisco GRE Tunnel to setup an IPX VPN over IP.

The problem is that the Windows NT server had poor performance send a large amount of files to Windows 98 clients.

But when I change the MaxPktSize of NWLinkIPX of the NT server, the problem seem to be solve.

But when decode the traffic between the 98 and NT by Sniffer, I found that when the 98 first logon to the NT server, a SMBEcho was send from 98 to NT, but the NT server had not response. And this problem had not occur if the MaxPKtSize of the NT server was keep in default value.

Anyone had the exprience on it, now when the 98 logon to the server, it seem to be wait for the timeout of the SMBEcho, it will wait about 15 seconds to continue the other communication.


Got to www.zone.com

It has the same Virtual IPX room.


  IPX networks are difficult to set up, let alone emulate them over a tcp/ip. You will still need to have network hubs or routers that support IPX and lots of networking cables and a program called novell 4.x.so you can setup network drives.

   It is  difficult to setup an ipx. Ipx's are usually used by schools to share an internet connection with a lowered risk of a virus getting transmited over the network, and home use is not a popular idea for a ipx network so you will find very little information on this subject area.

   I believe it is more worth it i if you just buy a newer program that will support tcp/ip ff your dos program's networking capabilities only support ipx rather than setting up an ipx network to solve your problem.

   Since you mentioned Kali i expect that you want to play either warcraft 1 or 2 over a network. If that is the issue you nshould play starcraft or warcraft 3 instead since they support  tcp/ip.


I have to disagree here about IPX being hard to set up.  In my experiences IPX is a far easier protocol to setup then TCP/IP in a small home environment.  IPX addresing is automatic, there no need for a DHCP server or the admin having to go in to manually set a static address.  There is no ARP equivalent in IPX either. IPX is really a plug it in and forget about it protocol which is exactly the reason most games supported it.  And theres lots of IPX support out there, not just on Novell's site.

You also may want to actually try setting up an IPX network before coming here posting FUD.  You don't need a "Novell 4.x program" to run IPX, I can do it on Windws 95-XP if I have to.  And furthermore all ethernet hubs can carry IPX since hubs only deal with level 2 addressing.  


is there anything similar to that "Kahn" program, only on that will work on XP Home? i simply want to play IPX-only games over my TCP/IP LAN, not even necessarily over the internet.


Heh... I think this problem is still alive and well.  I am attempting to do the same thing with Machines, by Acclaim.

Machines does not even work on Windows XP (home or professional), but I made my own patch by cludging parts of other patches and files created by a working Windows 95 install.

Machines crashes if you attempt to play multiplayer TCP/IP on Windows XP.  It used to work great in Windows 9x.  However, just install IPX/SPX protocol, and you can play just fine.

I'm suprised that Warcraft needs anything other than the IPX/SPX protocol installed.  Machines just works if you install the protocol and start the game.

Anyways, I just want to tunnel IPX over TCP somehow.  Perhaps a VPN would work...?  How do I install one of those?

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close