unable to connect to the administrative shares as administrator 1

[megoon]

How can I connect from an w2k machine to the administrative shares of a remote xp client using the same account information of the local administrator of that machine? All computers are member of a workgroup.

I need to administer the remote machines by accessing their local management tools like computer management, security policy, group policy, registry etc.

Each time I try to map c$ or d$ or whatever I receive "wrong password or unknown user" message.

 

[SjrH]

Try the command line -

c:\net use [drive letter]: \\[remote computer name\c$ /user:[remote computer name]\administrator

You should then be prompted to enter the administrator password for that machine.



SjrH - Data Security Storage & Availability Specialist

http://www.sjrh.co.uk

 

[Jump1ng]

You could even specify the password stoping the need for inputing it all the time.

It's very handy to use to map drives through a batch file.

Just use the command like this

NET USE M: \\servername\c$ /userOMAINNAME\administrator passwordhere

We use it to map up drives and backing them up using Win2K NTBACKUP.

 

[megoon]

still access denied with an additional line prompting that system error 5 is occured

 

[bcastner]

. Is the password blank or empty for the admin of the remote machines?

. Are all the clients XP Pro and not Home?

. Is Force Guest active on the remote machines?

If the "force network logons using local accounts to authenticate as Guest" policy is enabled, local accounts must authenticate as a Guest. This policy determines whether a local account that connects directly to a computer on the network must authenticate as a Guest user. You can use this policy to limit the permissions of a local account that is attempting to access system resources on the target computer. If you enable this policy, all local accounts that attempt to connect directly are limited to Guest permissions, which are usually severely restricted.

 

[megoon]

That was it! Force Guest was active on the remote machine.(the default setting by xppro clients which are not member of a domain).

Thank you bcastner.