Article ID: 237925
Article Last Modified on 6/24/2004
APPLIES TO
- Microsoft SNA Server 3.0 Service Pack 4
- Microsoft SNA Server 4.0
- Microsoft SNA Server 3.0 Service Pack 2
- Microsoft SNA Server 3.0 Service Pack 3
- Microsoft SNA Server 3.0 Service Pack 4
- Microsoft SNA Server 4.0
- Microsoft SNA Server 4.0 Service Pack 1
- Microsoft SNA Server 4.0 Service Pack 2
This article was previously published under Q237925
SYMPTOMS
When you are running the 16-bit SNA Server client for Windows 3.x and open a host session through the SNA Server computer, you may receive an error indicating that no resources are available. This problem can occur if the client is configured to use a Fully Qualified Domain Name (FQDN) in its TCP/IP configuration.
CAUSE
The SNA Server client for Windows 3.x truncates the Fully Qualified Domain Name (FQDN) of the workstation to the first 15 characters. The is by design, as the FQDN can be up to 255 characters long.
RESOLUTION
To resolve this problem, obtain the latest service pack for SNA Server version 4.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
215838 How to Obtain the Latest SNA Server Version 4.0 Service Pack
STATUS
Microsoft has confirmed that this is a problem in Microsoft SNA Server versions 3.0, 3.0 SP1, 3.0 SP2, 3.0 SP3, 3.0 SP4, 4.0, 4.0 SP1, 4.0 SP2. This problem was first corrected in SNA Server version 4.0 Service Pack 3.
MORE INFORMATION
After you apply the update, the SNA Server client for Windows 3.x will extract the NetBIOS computer name (or host name) from the FQDN when opening a connection to an SNA Server computer. The computer name is limited to 15 characters.
For example, if the client's FQDN is mypc.sales.company.com, the name passed to the SNA Server computer after applying the update will be mypc.
Keywords: kbbug kbfix kbsna400sp3fix kbqfe KB237925
