WFW 3.11 Fails to Connect to SNA Server on Windows NT 3.5 |
After upgrading an SNA Server computer from Microsoft Windows NT version 3.1 to Windows NT version 3.5 or 3.51, Microsoft Windows for Workgroups version 3.11 client computers fail to connect to SNA Server:
SNA Server Error: 546
Cannot establish connection with SNA Server <server name>.
The Microsoft IPX/SPX compatible transport (NWLink) is installed by default
with Microsoft Windows for Workgroups 3.11. When you configure the SNA
Server client to use the "MS Network Client (named pipes)" interface, the
NWLink transport is automatically used. This works fine with a Windows NT
3.1 server.
Under Windows NT 3.5, a new feature, direct hosting, was added to improve
performance. This allows a Windows for Workgroups client to communicate
directly with the server over IPX/SPX, rather than over NetBIOS. However,
applications which use named pipes do not work correctly over direct-hosted
IPX/SPX connections.
To resolve this problem, add the following entry to the [network] section of SYSTEM.INI on the Windows for Workgroups 3.11 client computer:
[network]The client workstation must be rebooted for this change to take effect.
DirectHost=NO
Microsoft has confirmed this to be a problem in Windows NT version 3.5. We are researching this problem and will post new information here as it becomes available.
Additional query words: directhosting wfw wfwg prodsna 2.00 2.10 2.11 nwlink DirectHost
Keywords : sna4
Version : winnt:3.5,3.51
Platform :
Issue type :
Technology : kbWinNTsearch kbWinNTWsearch kbWinNT351search kbWinNT350search kbWinNTW350 kbWinNTW350search kbWinNTW351search kbWinNTW351 kbWinNTSsearch kbWinNTS351 kbWinNTS350 kbWinNTS351search kbWinNTS350search
|
Last Reviewed: October 16, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |