Microsoft KB Archive/100698

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 16:01, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base

Using UNC Under Win 3.1 or WfW 3.1 with Long Server Name

Article ID: 100698

Article Last Modified on 9/30/2003


  • Microsoft LAN Manager 2.2 Standard Edition

This article was previously published under Q100698


When you attempt to load a document (In Word, Notepad, etc.) or execute a program with the File/Run command from a server with a Universal Naming Convention (UNC) name that is longer than 11 characters (for example, \\twelvecharac\public\ the system returns immediately with a dialog indicating that the program/file cannot be found or the path is invalid. If the server name is 11 characters or less, it functions correctly.

A Sniffer trace of frames to or from the workstation shows that when the server name is longer than 11 characters, no attempt is made to access the network.


The OpenFile() Windows function uses a function internal to the Windows kernel to check the length of the file name and returns an error if it is greater than 11.


Applications that use the _lopen() function to open a file should not experience this limitation. Otherwise, you must adjust server name length or work within the limitation.

Additional query words: 2.20 2.2 bug windows unc long name

Keywords: KB100698