System Error 85 - Mapping Behaviour in XP & Required Privilegs Not Held By The Client.

[K Berrien]

We just rolled out our W2K3 server upgrade (were running NT 4)
network. Most clients are 95/98, many to soon be replaced with XP.
We presently have some 10 XP Pro clients accessing this network, while
XP will grow to dominate, it'll be a mixed environment for some time.

Users have your general login scripts to map to home share, department
share, etc... which is in place for downward compatability. GPO
settings for XP clients are redirecting My Documents to home share,
and Desktop to a desktop share.

Login script:

NET TIME \\SERVERNAME /SET /Y
NET USE H: /HOME /YES
NET USE I: \\SERVERNAME\DEPTSHARE$

ok, simple login script, works great with 95/98 clients. After
logout, the mappings are released, and a second different user can map
on their logins.

On an XP client, first login goes ok, subsequent (even if I unmap
manually the shares) I get System 85 errors, mapping to a letter
already mapped. And its not just the home share (I could see the GPO
mapping for me prior to the script excuting, but it doesn't know about
the department share!).

So whats the behavior in XP for mappings, do they NOT release as in
95/98? If this is the case, I guess I could include a ver command and
skip the mapping(s) on XP machines, but what if I want to change the
mapping, or rename the department share... etc.

Onto question #2.

I see on some of my XP boxes, after the net use command (which works
correctly)

System error 1314 has occurred. A required privilege is not held by
the client.

I've had some XP boxes REALLY REALLY sluggish on network access of
shares, even at the same site (so it's not the WAN - and I've killed
the indexing checks in registry), and wonder if this is part of it.
Though I can't confirm, but the two seem to be related. One box which
is absolutely terrible was wicked quick days ago when the PDC was NT
4, while accessing an NT 4 member server. Now, same member server,
Win2k3 "PDC" blah!

I see there is an SMB Signing bug out there... but I doesn't fit the
symptoms exactly.

TIA.

 

[aginart]

Hi,
Just to say that we have exactly the same problem with the time
synchronisation and also have some difficulties with mapping drives
across domains.
The time problem is due to the fact, as I'm sure you have guessed it,
that you may not have local admin rights on the machine you are loging
onto. I am trying to find out what is the specific privilege required,
as we cannot give all our users full local admin rights on all our
machines! If someone knows the answer, I would be grateful if you could
tell us.
With mapping drives, and especially across domains, there is an issue
with Windows XP that Microsoft is aware of and stil have not found a
solution for.
Mapped drive seem to get disconnected after a while, and the only way
to get them back is to re-boot all the machines involved.
Out of desperation, I mapped the drives using the administrator
username and password as in:
NET USE \\machinename\driveletter password
/USER:my_domain\administrator

My drives seem to get mapped and stay mapped OK.

Cheers
Al

---------------------------------------------------------------------------