"Access Denied" Attempting to Run File on LM/X Server

ID: Q157114


The information in this article applies to:
  • Microsoft Windows 95


SYMPTOMS

When you are using a Windows 95-based computer to connect to a LAN Manager for Unix (LM/X) server, you may receive an "Access denied" error message when you try to run a file that has only Read and Execute permissions.


CAUSE

When a Windows 95-based computer connects to a server using the SMB (Server Message Block) protocol for file and print sharing, it negotiates a dialect level for the connection. Some LM/X servers support only older dialect levels.

When an older dialect is negotiated (the Microsoft Networks 3.0 dialect in this case, also known as Core SMB), the Windows 95 client must use only those SMB commands supported by the down-level server. In this case, the Windows 95 client issues an "open" SMB command, requesting open mode 23 or execute mode. However, the "open" command supports only read, write, and read/write mode, making it an illegal SMB command.


RESOLUTION

A supported fix for Windows 95 that corrects this problem is now available from Microsoft, but has not been fully regression tested and should be applied only to computers experiencing this specific problem. To resolve this problem immediately, contact Microsoft Technical Support to obtain the fix.

For a complete list of Microsoft Technical Support phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/support/supportnet/default.asp
This fix for Windows 95 should have the following file attributes (or later):

   File name     Version    Date      Time      Size
   ----------------------------------------------------------
   VREDIR.VXD    4.00.960   9/20/96   10:00am   140,403 bytes 
NOTE: If you contact Microsoft to obtain this fix, a fee may be charged. This fee is refundable if it is determined that you only require the fix you requested. However, this fee is non-refundable if you request additional technical support, if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If Your Product Is Eligible for No-Charge Technical Support


STATUS

Microsoft has confirmed this to be a problem in Microsoft Windows 95 and Microsoft Windows 98.

This issue is not resolved in Microsoft Windows 98.


MORE INFORMATION

For additional information about issues resolved by updates to this component, please see the following articles in the Microsoft Knowledge Base:

Q183493 Batch File Calling CD Command May Not Run on HPFS

Q174371 Possible Database File Damage When Data Is Appended

Q172594 Cannot Connect to Server with 15 Characters and Period in Name

Q167712 Fatal Exception Error in VREDIR with DCOM Program

Q165403 Windows 95 Update Prevents Sending Clear-Text Password Over Net

Q165402 Windows 95 Update to Encrypt Passwords in Memory

Q161100 File May Be Truncated When Copied to a Full Network Drive

Q160807 Cannot Connect to Windows NT Server with Many Shares

Q156497 Duplicate Print Output on PC-LAN Server from Windows 95 Client

Q152186 Possible Network Data Corruption If Locking Not Used

Q150215 Disabling Automatic Network Shortcut Resolution

Q148367 Possible Network File Corruption with Redirector Caching

Q142803 Locking Error or Computer Hangs Accessing Network Database Files

Q140558 Deleting Files on Samba Servers May Delete Local Files Instead

Q138249 Updated Vredir.vxd Corrects Errors Running Files on LMX

Q138014 File May Be Truncated to Zero Bytes When Copied Onto Itself

Q136834 Error Copying Read-Only Files to Core SMB Server
For additional information about Windows 95 updates, please see the following article in the Microsoft Knowledge Base:
Q161020 Implementing Windows 95 Updates

Additional query words:

Keywords : win95
Version : WINDOWS:95
Platform : WINDOWS
Issue type :


Last Reviewed: January 11, 2000
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.