When you attempt to connect to a share on a Windows 95 based computer from a Windows NT 4.0 workstation or server or Windows 2000, the connection attempt may not succeed and you may receive an Access Denied error message if the following conditions exist:

Windows 95 peer server has user-level security enabled (instead of share-level security), and the security provider is a Windows NT domain.

You are attempting to connect using a UNC name ( \\servername\sharename ) instead of mapping a drive letter to the share.

The Windows NT 4.0 workstation or server has Service Pack 2 or Service Pack 3 installed.

This behavior can also occur with Windows 98-based computers connecting to Windows 95 based computers, and from Win95 with the DFS client installed talking to Win95.

This problem is caused by an interoperability problem between Windows NT 4.0 SP2 or SP3 and Windows 95. Windows NT 4.0 with SP2 or SP3 makes a connection using a null user name, which Windows 95 acting as a server does not handle correctly.

You can resolve by using drive letter mapping or update the problem executable on Win95 peer server. For Win95 and OSR1 acting as server by updating VSERVER.VXD with :

VSERVER.VXD version 4.00.954 dated 4/24/97 108,288 bytes

For Win95 OSR2 and OSR 2.x, you need:

VSERVER.VXD version 4.00.1112 dated 7/24/97 112,904 bytes