Slow Performance of NetWare Logon Script on Terminal Server with Gateway Services for NetWare

• Microsoft Windows NT Server versions 4.0, 4.0 SP4, Terminal Server Edition

SYMPTOMS

You may experience very slow NetWare logon script performance on a Terminal Server computer with Gateway Services for NetWare (GSNW) installed.

CAUSE

Microsoft fixed a problem in Terminal Server Edition 4.0 where users had restricted permissions based on the preferred server users logged on to. This caused a problem for users attempting to log on to a server to which the previous user did not have permissions. The previous user's server is used to obtain the address of the current logon user's preferred server, but the server cannot detect the new user's server.

GSNW is modified in Terminal Server Edition so that the process loops through 10 servers, rather than just the first two servers in the list. This behavior can cause very slow logon script performance. A registry key is added, so that you can set the number of logon servers that the Terminal Server computer loops through to a value between 2 and 10.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Windows NT 4.0 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

   Date       Time     Size        File name    Platform
   -----------------------------------------------------
   08/04/99   05:27p   155,760     Nwrdr.sys    (Intel)
   08/13/99   07:43p   1,267,376   Win32k.sys   (Intel)
   08/04/99   05:32p   278,960     Nwrdr.sys    (Alpha)
   08/13/99   07:48p   2,073,136   Win32k.sys   (Alpha) 

STATUS

Microsoft has confirmed this to be a problem in Windows NT 4.0.

MORE INFORMATION

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

After you apply the hotfix, use the following steps to modify the registry:

1. Start Registry Editor (Regedt32.exe).



2. Locate the following registry key:




HKEY_LOCAL_MACHINE\SYSTEM\Current Control Set\Services\nwrdr\Parameters

3. On the Edit menu, click Add Value, and then add the following registry value:

   Value Name: FindServerLessAttempts
   Data Type: REG_DWORD
   Value: Maximum and default is 10. Use a value less than 10, such as 3.

   NOTE: You may have to test values to find the appropriate value for your environment.



4. Quit Registry Editor.



5. Shut down and restart the computer.

Q215475 Slow Performance with GSNW on Terminal Server

Additional query words:

Keywords : kbenv kbbug4.00 kbfix4.00
Version : winnt:4.0,4.0 SP4
Platform : winnt
Issue type : kbbug