Workstation Denied Access Privileges on LANMAN Server (96571)



The information in this article applies to:

  • Microsoft LAN Manager 2.1
  • Microsoft LAN Manager 2.2

This article was previously published under Q96571

SUMMARY

File access privileges are denied to your 3+Share workstation running MS-DOS 5.0 when you connect to a LAN Manager 2.1 server and use the 3+Share redirector (MSREDIR) from the LAN Manager MS-DOS 5.0 Supplemental Disk.

SYMPTOMS

NET USE connects the workstation to the server, but if you run a DIRECTORY the response is "No Files Found," even when there are files in the shared directory. Trying to access a file in the shared directory results in the message "Extended Error 65." Giving the GUEST account READ privileges on the share does not secure privileges for the workstation.

CAUSE

The earlier version of the MSREDIR (used with 3+Share workstations running MS-DOS 3.3) negotiated the protocol on session setup with a LAN Manager 2.1 server to PC Networks Program 1.0. This granted the workstation guest privileges without requiring a registered user name. Under MS-DOS 5.0 and the new MSREDIR, however, the negotiated protocol is Microsoft Networks 3.0, which grants privileges only to workstations with registered user names.

RESOLUTION

There are two workarounds. First, to secure privileges for the workstation, issue the LOGON command (a utility available in Toolkit) before performing the NET USE. The LOGON command registers a user-input name for the workstation and passes that name to the server during the NET USE.

Note: Page 69 of the Toolkit documentation states that LOGON is intended only for 3+Open and LAN Manager 2.1 nodes. This is not true; you also must use it with 3+Share and MS-DOS 5.0.

Second, if your account is set up to use a password, you also can get privileges for your workstation by sending it to the server during the NET USE as follow:
      net use r: \\gold\bar PASSWORD
				

Modification Type:MajorLast Reviewed:9/30/2003
Keywords:KB96571