Setting permissions in Advanced Server 6.1 and W2K

[Robert Manning_2]

Hi,

Some time ago I upgraded from Pathworks 6.0D to Advanced Server 6.1. the purpose of this was to migrate my shares onto our W2K domain.

(Upgrading further to 7.3 isn't an option at present because my AlphaCluster is tied to OVMS 6.2-1H3 for the moment.)

The migration was successful and no problems were observed. However, lately I have had problems when trying to set user permissions on Pathworks shares.

The operation fails with the message

"Object Picker cannot open because it cannot determine whether Production01 is joined to a domain."

Acknowledging this message replaces it with

"The user selection dialog could not be opened. The remote procedure call failed and did not execute."

The name Production01 above refers to the alias of the AlphaCluster on which Advanced Server runs. If I use either of the individual server names to map the drive, tha same messages appear.

I have WINS entries on the W2K domain that point to the alias and the servers, and I can log on to the domain via ADMIN to create shares and do internal administration.

However this problem will prevent me from setting access on new or existing shares.

If anyone had any ideas on what's happening and how to get past it, I'd appreciate it.

Thanks,

Bob

[Karl Rohwedder]

Bob,

did you try to set share permission on the VMS side or just from the w2k side?

Your Pathworks server is member serverI assume, so login into it using
ADMIN>login administrator /domain=\\production01
If that is ok. try to view/modify share permissions.
If an error occurs, check to event logs with
ADMIN> SHOW event/sin/fu [/type=sec,sys,appl]

may be your PWRK server has problems to locate the domain controllers, check WINS etc. with ADMIN/CONFIG.

mfg Kalle

[Edwin Gersbach_2]

re:
ADMIN>login administrator /domain=\\production01

remember that here the local administrator password is required - the one given at installation time - rather than the domain administrator password!

However, you may also try to login to the domain (omit the /domain switch) to check things.

Other than that, check the various logfiles in PWRK$LOGS and PWRK$LMLOGS for errors.

Edwin

[Robert Manning_2]

Thanks, guys,

And apologies for the late reply...

Karl:

I checked my setup using ADMIN/CONFIG, and everything looks OK.

I am able to log onto the W2K domain thru ADMIN/LOGON. Once logged in, I can view and change permissions on shares, however the changes don't carry into the W2K side - when I map a share in Windows and check Properties\Security, the changes haven't been added.

Edwin:

I haven't been able to log on as the Administrator of Advanced Server because I don't have that password at the moment.

It'll be Monday before I do, so I'll post again when I've had a chance to try it out.

As for the logfiles, I'll have a good look at them and let you know if I find anything...

Thanks,

Bob

[Robert Manning_2]

Okay, I'm back...

I checked the logfiles in PWRK$ROOT and found the following:

>ty PWRK$KNBDAEMON_POST05.LOG;-1/p

Tue Mar 8 00:03:20 2005 PH Address: AA-00-04-00-09-30
Tue Mar 8 00:03:21 2005 IP Address: 10.3.1.180
Tue Mar 8 00:03:21 2005 NBNS IP Address: 10.3.1.8
Tue Mar 8 00:03:21 2005 KNB Driver linked with succes
sfully
Tue Mar 8 00:03:21 2005 KNB Driver : Starting knblink ...
Tue Mar 8 00:03:21 2005 KNB Driver : Starting knblmhost ...
Tue Mar 8 00:41:42 2005 resolve_name: LMHOSTS Lookup for TT_D070_W2K [20]
failed knbcb 304
Tue Mar 8 00:42:32 2005 resolve_name: LMHOSTS Lookup for 023801 [20]
failed knbcb 303
Tue Mar 8 00:45:41 2005 resolve_name: LMHOSTS Lookup for CGS_IRPT [20]
failed knbcb 300

>ty PWRK$NBDAEMON_POST05.LOG;-1
Tue Mar 8 00:03:20 2005 dllink t_open successful on netbios/streams/dl
Tue Mar 8 00:03:21 2005 dllink t_open successful on netbios/streams/dlpi1
Tue Mar 8 00:03:21 2005 Exiting dllink with success we have one or more dlpi
devices
Tue Mar 8 00:03:21 2005 netbios/streams/nbes opened successfully
Tue Mar 8 00:03:21 2005 Microsoft NetBEUI : Starting nbelink ...
Tue Mar 8 00:03:21 2005 done

There was nothing I could see in any other logs to indicate a problem.

The hosts referred to as failing the LMHOSTS lookup attempt are devices that no longer exist on our network.

Also, I (finally) managed to log in using the account/password that was used to configure Pathworks in the first place, however everything behaved the same.

It doesn't look like a SAM corruption, but I could be wrong?

Bob