SNA Win95/NT Client Using Named Pipes Will Not Have the Data
Article ID: 165747
Article Last Modified on 10/22/2003
APPLIES TO
- Microsoft SNA Server 3.0 Service Pack 4
This article was previously published under Q165747
SYMPTOMS
The connection between an SNA Server 3.0 Windows 95 or Windows NT client
using named pipes and an SNA Server is not encrypted even when the Data
Encryption feature is enabled.
CAUSE
The SNA Server was not checking the Data Encryption Flag and was granting
the client access without encryption.
RESOLUTION
The SNA Server will now check the Data Encryption Flag.
STATUS
Microsoft has confirmed this to be a problem in SNA Server version 3.0.
This problem was corrected in the latest Microsoft SNA Server 3.0 U.S.
Service Pack. For information on obtaining the service pack, query on
the following word in the Microsoft Knowledge Base (without the spaces):
Keywords: kbbug kbfix kbnetwork KB165747