Server or Tree not found after applying Windows XP sp2

  • 10095407
  • NOVL99735
  • 09-Nov-2004
  • 01-Aug-2005

Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.


Server or Tree not found after applying Windows XP sp2

SLP name resolution fails after applying Windows XP sp2

Slpinfo /d shows DA's as NORSP on bootup

After applying SP2 for Windows XP the client gets tree or server  not found


Windows XP

Novell Client 4.9 SP2 for Windows NT/2000/XP


Not able to communicate with SLP Directory Agent , DA shows as NORSP, Traces show the workstation does seem to be sending requests but the responses never seem to make it back.


The Microsoft Windows Firewall is blocking the reply from the SLP DA. By default, the SRVLOC service (SLP client module that runs on a Windows PC running the Novell Client) communicates using a dynamic UDP port. The SRVLOC service will request the next available dynamic UDP port (usually in the range of 1024-1098) from Windows and then use that as the source port and talk to the discovered DAs on UDP port 427. The Microsoft Windows Firewall isn't blocking the outbound request, but is blocking the inbound replies.


The solution would be either to disable the Microsoft Windows Firewall completely, or add an exception for the SLP Service. You can add an exception under the setting for Windows Firewall ( Control Panel \ Windows Firewall ) under the "Advanced" tab and then clicking on the "Settings" button with the desired network connection(s) checked (usually Local Area Connection). Here you can Add a service which requires the following information:

Description: Novell SLP
Name or IP address: (must be the IP address or might also allow DNS/NetBIOS name of the SLPDA server)
External Port: 427
TCP/UDP radio button (set to UDP)
Internal Port: (leave blank to allow for any internal port since the client uses the next available dynamic port)

NOTE: if the IP address or NDS name of the SLPDA server changed, you would also have to change this exception for every Windows PC running the Microsoft Windows Firewall product.

Some customers have also worked around this by forcing the Novell SRVLOC service (SLP Client) to always use a specific UDP port that is not blocked by the Microsoft Windows Firewall by default. This will change the SRVLOC service behavior and prevent it from using the next available UDP port. If this specified port were already in use, the SRVLOC service will not be able to dynamically change from this port and will fail to load and work properly. The following registry key/value pair will force the SRVLOC service to use the UDP port number specified (stored in hex... 0x000001ab = 427 decimal):

"Slp Port"=dword:000001ab 

NOTE: Forcing the port for the SRVLOC service to 427 is NOT recommended by Novell. This information is provided as a benefit to Novell customers who might have a reason for forcing the port.

NOTE: Do NOT set the SRVLOC service to use UDP port 427 on Windows systems that are acting as an SLPDA since it will default to using this port.