Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ZEN 3.2 Remote Control - "Console User was not able to access NDS..."

Status
Not open for further replies.

Bandjelek

MIS
Oct 6, 2002
28
NZ
Dear Experts,

In the last two days we have been experiencing a problem with ZEN 3.2 remote control. We can ping the workstation management agent. But as soon as we try to Remote Control or Remote View, it comes up with this message :

"Console User was not able to access NDS for authentication"

Restarting the workstation usually enable us to remote control. But sometimes we need to delete the wks object, run unreg32 and wsreg32. After doing this, we occasionally get :
"Insufficient permissions. Check if the Remote management policy exists for the workstation/user on target workstation and Remote Control is enabled."
But after restarting the workstation, it may work.

We use ZENworks for Desktops 3.2 SP1, Client 4.83SP1, NW6SP3 in the import/removal server. It may worth mentioning that we replaced the server a week ago. We used NWConfig to save the DS data from the old server, then restore it to the new server. The server name & server object is the same for old and new server.

After physically replacing the server, I installed ZfD3.2 (files only, didn't do Schema extension & NDS objects as they're already exist) then applied ZfD3.2 SP1 server part.

Since the server was replaced, wks import & remote control had been working fine for a few days until two days ago when the problem started to happen.

We do remote control from either ConsoleOne or ZEN Workstation Browser 3.2 (Holger Dopp's).

I have done a search on Novell TIDs and the internet but could not find much useful info. Can anyone point me to the right direction?

Thanks,
Bandjelek
 
Somewhat embarrasing :)
timesync.nlm was not running on the server that hosts the master replica of the wks container. The server abended and when it was back online, for some reason that nlm failed to load.
Restarted the server, confirmed timesync running by doing some dstrace, then all was good again.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top