I'm not quite sure where I should have posted this...
I have about 20 people so far that are getting the following message:
>>
An error occurred while reconnecting X: to "\\tree\o\volume"
NetWare Services: The credentials supplied conflict with an existing set of credentials.
This connection has not been restored.
<<
This happens on Win 2000 systems with Novell Client 4.81. We have two trees. The primary tree works fine, but when their mapped drives try to remap to the old tree, the error message pops up. This only happens after a reboot and never after a logout/login.
I have conflicting reportss as to what is fixing it. One is that to unregister and reregister with wsreg the system in the new tree works and the other is that deleting the old tree and and context from the client properties. I honestly don't think either of these is really "working". It seems as though waiting long enough allows the client to discover the old tree.
If the user just browses out to the old tree after receiving the error message, the authenication process occurs normally.
This one is a real pain for me because as far as I know nothing has changed much in either tree or on the systems to cause these systems to behave in this way.
If anyone has any clue as to the direction I should be looking, I would greatly appreciate it.
I have about 20 people so far that are getting the following message:
>>
An error occurred while reconnecting X: to "\\tree\o\volume"
NetWare Services: The credentials supplied conflict with an existing set of credentials.
This connection has not been restored.
<<
This happens on Win 2000 systems with Novell Client 4.81. We have two trees. The primary tree works fine, but when their mapped drives try to remap to the old tree, the error message pops up. This only happens after a reboot and never after a logout/login.
I have conflicting reportss as to what is fixing it. One is that to unregister and reregister with wsreg the system in the new tree works and the other is that deleting the old tree and and context from the client properties. I honestly don't think either of these is really "working". It seems as though waiting long enough allows the client to discover the old tree.
If the user just browses out to the old tree after receiving the error message, the authenication process occurs normally.
This one is a real pain for me because as far as I know nothing has changed much in either tree or on the systems to cause these systems to behave in this way.
If anyone has any clue as to the direction I should be looking, I would greatly appreciate it.