Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows VistaWindows XPWindows MeWindows 98Windows 95Virtual PCInternet ExplorerOutlook ExpressWindows MediaSecurity
Related Topics
MS Server ProductsMS OfficePC HardwareMore Topics ...

Windows Forum / Windows XP / Networking and Web / November 2005

Tip: Looking for answers? Try searching our database.

Windows XP drive mapping problem

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
colorado_kevin@hotmail.com - 30 Nov 2005 20:26 GMT
Can anyone help me with this?    Windows 2000 used to pop a password
box for a drive connected to a server in the DMZ.  XP doesn't do that
so the drive isn't active until the user goes into my computer and
clicks on it.  Then they enter the password and all is good.

This network of 20,000 users and over 125 servers. some in Active
Directory,
some in DMZ's, was designed back in Win 2000 days when network drive
mappings
to stand-alone servers resulted in a popup box that clearly asked users
to
supply a user name and password for each resource accessed.  Accounts
in
Active Directory have to change passwords every 90 days, but this can't
be
replicated to stand alone servers. Users can't change their passwords
on
standalone servers anyway, as they don't actually logon to the server.
We
WANT users to be prompted to supply user names and passwords to access
these
very secure boxes! But XP users simply get an unhelpful Mac-like
bubble, not
the good old pop up asking for user names and passwords. As usual,
Microsoft
fixed something that worked fine, by making it worse in the new
release.
Ian - 30 Nov 2005 23:14 GMT
In principle I think this could be achieved with NET USE commands in a
console  box. Not pretty, but it works.

A better solution would be an AutoIt script. (or possibly VBScript) This
would allow the users to enter passwords into  GUI interface, and would then
map the drives with a system-call instead of a NET USE command.  More work
but a lot more elegant.

http://www.autoitscript.com

If security is important, main thing is to ensure that the persistence flag
is off for a system call, or '/persistent:no' is added to the first NET USE
command.  Otherwise the password wil be saved locally.  
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2010 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.