Ports and Protocols used by NetWare 5.X and 6.X

Novell NetWare 5.1

Novell NetWare 6.0

Formerly TID 2943773

NCP requests not being routed across WAN links

Servers are not communicating across the WAN

Remote workstations not communicating with the directory agent or migration agent

Migration agent to migration agent communication not working

Configuring router to support SLP or CMD

Migration agent is unreachable

Router IP filters are in place and filtering out the ports used for NetWare IP communication.

TCP and UDP are both used by NetWare 5.1 and NetWare 6.0 for Pure IP connectivity. The following ports are used for communication.

TCP 524 - NCP Requests - Source port will be a high port (1024-65535)
UDP 524 - NCP for time synchronization - Source port will be a high port (1024-65535)
UDP 123 - NTP for time synchronization - Source port will be the same (123)
UDP 427 - SLP Requests - Source port will be the same (427)
TCP 427 - SLP Requests - Source port will be the same (427)
TCP 2302 - CMD - Source port will be a high port (1024-65535)
UDP 2645 - CMD - Source port will be the same (2645)

Note:
An expanded description of the port usage follows:

NCP Requests - TCP 524
If you are running in Pure IP mode (not in compatibility mode (CMD)) and are not dependant on SLP for locating your servers, all communication will happen on this port. If you create an exception to allow a destination TCP port 524 coming in to the NetWare server and a source TCP port 524 going out from the NetWare server you will be covered. The actual source port used by the client making contact to the server will be a high port (1024-65535).

SLP Requests - TCP & UDP 427
If you would like to locate your servers through SLP, then you will need to allow communication through TCP and UDP port 427.  Both the source and destination will be port 427.  The User Agent (UA) will contact the Service Agent (SA) or Directory Agent (DA) using a UDP packet. If the response is larger than one packet can hold then it will respond with as much formation as it can and set the overflow bit. The UA will then connect via TCP and will make the same request again to get the complete response.

CMD Communication - TCP 2302 & UDP 2645
CMD or Compatibility Mode Driver is necessary when an IP device must communicate to an IPX device or an application that is running requires a direct IPX interface. Both the source and destination ports will use the same port number.  All communication destined for an IPX device through a Migration Agent (MA) will use UDP packets.  Devices communicating to the MA for information on services available and routes to those services will use the following protocols:
        A NetWare 5 server running SCMD to MA uses TCP
        A 3.x Client running CMD to MA uses UDP
        Two servers with a MA to MA setup uses UDP