Q: Can I use TCP/IP for NetWare communications?

A: NetWare 4.11 includes a TCP/IP protocol stack for the server and the IntranetWare product adds a collection of TCP/IP services and utilities, but the default protocol stack for NetWare's core file and print functions is still Novell's IPX/SPX. Network systems can access TCP/IP services running on NetWare, such as the Novell Web and FTP servers, using a standard TCP/IP client like that included with Windows NT or Windows 95, but they cannot access NetWare server volumes and printers.

Novell is currently moving the NetWare product towards the use of TCP/IP as a native protocol. This capability is expected to be included as part of NetWare 5, currently scheduled for release in the summer of 1998. Until then, the NetWare/IP product makes it possible to use TCP/IP to access core NetWare services.

NetWare/IP is a proprietary TCP/IP implementation that requires special software both on the NetWare server and on the network client systems. The 32-bit IntranetWare clients for Windows NT, 95, and 3.1 all include NetWare/IP client support. You cannot access NetWare/IP servers with a standard TCP/IP client because the product does not actually replace the IPX protocols with TCP/IP; instead, it encapsulates them.

IPX is a network layer protocol like IP, but on a NetWare/IP network entire NetWare Core Protocol messages, including the IPX header, are encapsulated within UDP datagrams for transmission across the TCP/IP network. Thus, a network layer protocol (IPX) is carried within a transport layer protocol (UDP), which is itself carried within another network layer protocol (IP). This obviously violates standard networking practices, which explains the need for a proprietary TCP/IP client.

For more information, see page 465 of TCP/IP Administration.