Winsock Call Fails When User Does Not Have Local Administrator Rights

ID: Q245678

The information in this article applies to:

Microsoft Windows NT Server version 4.0 SP6
Microsoft Windows NT Workstation version 4.0 SP6
Microsoft Windows NT Server, Enterprise Edition version 4.0 SP6

SYMPTOMS

After you apply Windows NT 4.0 Service Pack 6, Winsock calls may not work properly. Generally the problem manifests itself when a program attempts to connect to a server. You may see an application layer error like:

Could not connect to server.

or

Access denied.

CAUSE

The problem only occurs if the user does not have full administrative rights to the computer.

RESOLUTION

Windows NT 4 Service Pack 6a has been released to fix this problem. A hotfix is available to update SP6 systems to SP6a. For more information, please click the ariticle link below to view the article in the Microsoft Knowledge Base:

Q246009 Windows NT 4.0 Service Pack 6a Available

For more information about how to download files from the Microsoft Download Center, please visit the Download Center at the following Web address

http://www.microsoft.com/downloads/search.asp

and then click How to use the Microsoft Download Center.
The English-language version of this fix should have the following file attributes or later:


   Date        Time     Size       File name   Platform
   -----------------------------------------------------
   11/11/1999  05:18p    66,352    Afd.sys     x86
   11/11/1999  05:23p   115,184    Afd.sys     Alpha

STATUS

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

Additional query words: winsock connection refused lotus notes

Keywords : kbbug4.00 kbfix4.00
Version : winnt:4.0 SP6
Platform : winnt
Issue type : kbbug