Mapping drives on WindowsME to a domain\user share?

[CommAdmin]

Hi,

New to the forum! Hello!

I have a user who has WindowsME and broadband. I have set him up to connect to my corporate VPN Server, which works great. He can connect, ping stuff, etc... but...

Windows2000 has this version of the 'net use' command which looks like this (to map a share)...

net use * \\servername\sharename /user:domain\user

This will properly authenticate this user to our domain and ask for the password.

When you try this on WindowsME, the flag /user does not exist so it errors out. Other variations of this command on ME are ...

net use o: \\servername\sharename usernameassword

This on ME, comes back with invalid password. But what I really think it is saying is 'failure to authenticate - bad domain name'. The response it gives even violates normal logical security in telling the user that his password is bad - a no no in unix and other password protocols...

How do I assign the correct credentials to the 'net use' command on WindowsME? Is there a way? Help please?

 

[wolluf]

Does the user logon to ME with a username/password which would be valid on the domain? (ie, it exists as a domain user). I'm not even sure this would work over VPN (it would if ME machine was on the LAN). I don't think there is any way of assigning correct credentials to ME's version of net use (but I stand to be corrected if some knows differently!) - it uses current ME logon credentials.

 

[CommAdmin]

Does the user logon to ME with a username/password which would be valid on the domain?

Do you mean that this PC would have to attempt to logon with a valid (on my domain) username, and the logon set to the domain? That can't happen.

He could name a workgroup the same as the domain, create a user of the same username as his valid ID, and try that, but are you saying that would matter? Are workgroups and domains the same thing?? I just get more confused!

There is a 'Start before Logon' option in the Cisco VPN Client, that will let you establish a connection via the VPN and then login to the domain -- I'd like to see someone who actually got that to work in any OS! ;-P

Anyway, I welcome any offers of help, and I appreciate your suggestion, I'll try anything...

-Commadmin

 

[wolluf]

sorry - to clarify. Just needs username and password logon on ME matching one that exists on the doamin. Doesn't have to have logon set to domain. So, if logon is:-

Me_User with password ME_PW, need to have a user set up on the domain with username Me_User and password ME_PW.

Then hopefully the ME net use command will automatically supply these credentials and domain will recognise them as valid domain credentials.

(may also depend on which version of windows server you're running and level of authentication required - I seem to recall 2k and 2k3 server can be set to not authenticate win9x/ME logons where machine is not part of the domain. If this were the case, you would probably need to logon to the domain too).

 

[CommAdmin]

I think that actually has worked in the past for me. I used to have Wme at home... hmmm....

I just talked with the user - and he suggested the best of all fixes... quit trying on the ME machine! I heartily agree'd! Talk about getting off the hook!

He will be reinstalling the VPN Client on an XP machine. Which works with the 'net use * \\server\share /user:--\--' command - thank God!

So where does that leave this thread? Kindof in limbo - unless I can find a WindowsME machine for home and try out this stuff. Maybe I can buy a cheap Dell on ebay and put on my WindowsME license... hmm.....

Thanks for the dialog, and on to more current topics, eh!?