Discussion Locked

Windows 2000 connecting to a WinNT Share

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have encountered a problem when using a Windows 2000 server to map two different shares on a Windows NT server. First of all both computers are part of the same domain. Then I logon as the domain administrator on the 2000 server. I then map a share that is setup for single user share level permissions on one of our NT servers. It asks for the username an password for the share and I enter an account that is not the administrator but the specific user that has access to the share. I then proceed to attempt to map an administrative share (ie C$) using the same method but with the domain\administrator user account. However the system gives me an error stating I already have that share mapped using another username and to disconnect it if I would like to remap it using the administrator password. I then disconnect the drive I mapped using the sub administrator account and try to remap the administrative share and it works fine. I could understand this if the shares I am trying to mount were the same but they are two different shares on completely different drives on the same server. I have also found out that if I do map a share with the sub administrator password to the one server and try to map a administrative share from anotherNT 4.0 server on the domain it works fine. The problem I have identified is that when using Windows 2000 server you can only map shares on a NT 4.0 server using a single username. So if you login at a domain admin but map a share as a user without admin access the system reduces your entire permissions to that server to the user you mapped the drive as. Has anybody heard of this? If so what is the resolution?

5 replies

by ntoz

You should utilize the RUNAS commmand to attempt what your doing, its a new feature of Windows 2000.

To create a shortcut using runas command parameters

Right-click the desktop, point to New, and then click Shortcut.
In Type the location ofthe item, type runas and the command parameters you wish to use. See Examples.
Click Next, type a name for the shortcut, and then click Finish.
Examples

To create a shortcut for a command prompt window with administrator credentials, in step2 type:
runas /user:machine name\administrator cmd

where machine name is the name of your computer.

The title bar of this window will say "cmd (running as machine name\administrator)" to indicate the credentials under which it is running.To create a shortcut for a Computer Management window with administrator credentials, in step 2 type:
runas /user:machine name\administrator "mmc %windir%\system32\compmgmt.msc"

where machine name is the name of your computer. Be sure to include the quotation marks.

The Computer Management window provides no indication of the credentials under which it is running. This could cause confusion if you start two or more Computer Management windows in different security contexts.

On Windows 2000 Server, to create a shortcut to Active Directory Users and Computers with domain administrator credentials, in step 2 type:
runas /user:domain name\administrator "mmc %windir%\system32\dsa.msc"

by ntoz

The Active Directory Users and Computers window provides no indication of the credentials under which it is running. This could cause confusion if you start two or more Active Directory Users and Computers windows in different security contexts.

To create a shortcut to a program that will administer a server in another forest, in step 2 type:
runas /netonly /user:domain\username command

where domain\username is a user with enough permissions to administer the server, and command is a command prompt window, program, saved MMC console, or Control Panel item. For example, to create a shortcut for Active Directory Users and Computers, in step 2 type:

runas /netonly /user:domain\username "mmc.exe dsa.msc"

Notes

When you double-click the shortcut, you will be prompted for the password of the user account specified in step 2. Then the program or file will run with the permissions granted to that user. If the user account is Administrator or a member of the Administrators group, you will be able to do administrative tasks in this window.
The runas command allows you to run programs (*.exe), saved MMC consoles (*.msc), and Control Panel items as an administrator while you are logged on to your computer as a member of another group, such as the Users or Power Users group.

by ntoz

The runas command can be used to start any program, MMC console, or Control Panel item as long as the following requirements are met:
You provide the appropriate user account and password information.
The user account has the ability to log on to the computer.
The program, MMC console, or Control Panel item is available on the system and to the user account.
The runas command is usually used to run programs as an administrator, although it is not limited to administrator accounts. Any user with multiple accounts can use runas to run a program, MMC console, or Control Panel item with alternate credentials.
Some applications, such as Windows Explorer, the Printers folder, and desktop items, are launched indirectly by Windows 2000. These applications cannot be started with the runas command.
If the runas command fails, the RunAs service may not be running.

Your problem might be a bug in Windows 2000 as this used to work under NT 4.0

Pete

by natecasp

Yes I do believe it is a bug. Since it did in fact work under NT and now in 2000 it does not. It seems that Windows 2K will only allow a single user credentials to be recognized for each logon on a per server basis. If you could please check this scenario on your servers (if you have any WinNT left) I would greatly appreciate it. Just try to setup a user share with user share level access. Then using the 2000 server login and connect to the share using the administrator. Or logon as the user and try to map any of the administrative shares.

This discussion is closed to new replies.