What happens

When you are attempting to visit a website or an FTP directory that uses a mapped drive instead of the Universal Naming Convention (UNC), you may receive Windows error code 69 instead of the resource you expected to see.

3 things you should do if The network BIOS session limit was ...

Many company intranets will allow employees to access information by way of a website or FTP directory on a Windows Server. Some of these Windows Servers will store the information using a mapped drive on the server that people can connect to. This may cause access problems that result in the Windows error code 69.

Here are the steps a server administrator can use to stop these errors from occurring.

• Log into the Windows IIS Server as the person who is receiving the error message.
• Launch Windows Explorer.
• Browse out to the website files or FTP directory that resides on the mapped drive.
• Right click on the shared drive and check the option to have the drive reconnect at login. This is making the drive connection persistent.

Though, this will resolve the issue, there may be performance issues due to the user’s account going through double authentication.

Microsoft has stated in their support documentation that their recommendation is for the website files or FTP files to be accessed by way of the UNC path instead of by the mapped drive methodology. Web administrators should make all of the intranet or Internet files accessible via the UNC to avoid Windows error 69 happening to users on their network. This solution will allow users to get to the files they need without risking performance degradation due to logging in to the network and the resource separately.

TipFor more information, please see: How to fix BIOS error #69