IPX Isolated Networks

If an IPX server is attached to a LAN segment which has no routers (including dial-in servers), and there are no Novell file servers capable of establishing a non-zero network number, the zero network number must always be used by the server. Including the line, “Assigned Network = 0” in the server's SETUP.TXT file will cause the server to assume it is on an isolated network and not be concerned with the lack of a network number.

Similarly, any workstation attached to a different LAN segment than the server must know its network number before the server can send information to the workstation. If such a workstation can “see” the server but gets no response trying to connect to it, using the NETX operation described below will cure the problem. Note that workstations attached to the same LAN segment as the server will always work, even if they think they are on network zero.

Much experimentation has been done to try to force or trick the IPX provider into accepting a network number of our choice, but all attempts using common means have failed. The only known work-around is to load the server using Novell's NETX.EXE (or the operational equivalent using VLMs). This forces network number discovery. As the workstation attempts to locate a Netware server, the IPX software actively queries all devices on the network to determine the workstation’s network number. In the process, it locates any remote server running NETX. When NETX finds a Netware server, it terminates and stays resident in memory. Once this process is complete, all that then needs to be done is to unload NETX (NETX /u) at the server, and then load Aspen server software.