instauratio
November 13th 04, 11:35 PM
I'll try to make this concise,
Mark and Bob both have XP professional, same computers. Bob has mapped
drives (to a windows2000 server) that are setup to connect on startup. This
works and Bob can start his computer and click on a recent word Doc and begin
working. Mark on the other hand also has mapped drives setup to connect to
the server on startup. However, if he clicks on a document in his history
buffer, he is given an error stating that he must authenticate.
If Mark goes directly on startup to the mapped drive and clicks on it, he
receives a prompt for password. When he enters it, he is given full access to
all of his documents and other mapped drives.
Neither are in the domain, they are in workgroup. Why is it that Bob gets
instant access and Mark can't?
My solution is to put them both in the domain and script with "net use".
I'm aware of this solution and intend to use it. My question here though, is
why are these machines behaving differently under the present circumstances?
Mark and Bob both have XP professional, same computers. Bob has mapped
drives (to a windows2000 server) that are setup to connect on startup. This
works and Bob can start his computer and click on a recent word Doc and begin
working. Mark on the other hand also has mapped drives setup to connect to
the server on startup. However, if he clicks on a document in his history
buffer, he is given an error stating that he must authenticate.
If Mark goes directly on startup to the mapped drive and clicks on it, he
receives a prompt for password. When he enters it, he is given full access to
all of his documents and other mapped drives.
Neither are in the domain, they are in workgroup. Why is it that Bob gets
instant access and Mark can't?
My solution is to put them both in the domain and script with "net use".
I'm aware of this solution and intend to use it. My question here though, is
why are these machines behaving differently under the present circumstances?