C
colorado_kevin
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.
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.