Advanced Server HOSTMAP Not Working

[Robert Atkinson]

I've added a number of HOSTMAP entries to my AdvSvr installation, but only my entry seems to work.

If I create a file, it correctly gets my VMS username. If other people create a file, the user is always PWRK$GUEST.

I should also point out the I am a local Admin of the AdvSvr server.

Am I correct in thinking that a restart is not required if you add HOSTMAP entries?

Is there any way I can trace why the HOSTMAP isn't being picked up by the server?

Thanks, Rob.

[Karl Rohwedder]

There are some registry entries controlling hostmaps (see recent thread and entry by Brad McCusker), perhaps they are non-default at your site, check with:

REGUTL> sho par * *host*/known

regards kalle

[Robert Atkinson]

Security setting look like this (not sure how this will come out) :-

+------ Advanced Configuration Parameters -------+
| |
| +Open File Caching---------------------------+ |
| | | |
| | [ ] Use Open File Caching | |
| | | |
| | Open File Caching Interval (msec): 500 | |
| +--------------------------------------------+ |
| |
| Files per Client: 12 |
| Byte Range Locks per Client: 6 |
| |
| [ ] Enable Dynamic Security Upgrade |
| |
| +Security Model--------------------------+ |
| | | |
| | (*) Advanced Server Only | |
| | ( ) Advanced Server and OpenVMS | |
| | | |
| +----------------------------------------+ |
| +--------+ +--------+ |
| | OK | | Cancel | |
| +--------+ +--------+ |
+ Save any advanced parameter changes -----------+

[Doug Phillips]

Here are the settings on a system where the VMS username *is* being set as the owner of files/folders created from the client-side for *all* hostmapped users:

-----------
$admin show vers

Advanced Server V7.3A for OpenVMS

$admin/config
...
| (*) Advanced Server Only |
...

$regutl show par * *host*/known

Section Name: vmsserver
Keyword Name: hostmapdefault
Source: Default
Type: String
Default Data: DEFAULT

Section Name: vmsserver
Keyword Name: hostmapdomains
Source: Default
Type: String
Default Data:

Section Name: vmsserver
Keyword Name: hostmapusedatabase
Source: Default
Type: String
Default Data: yes

Section Name: vmsserver
Keyword Name: hostmapusevmsnames
Source: Default
Type: String
Default Data: yes
---------

Are your settings different?

[Robert Atkinson]

Looks to be exactly the same :-

ALPHA_ROB$ mc PWRK$REGUTL.EXE
REGUTL> show par * *host*/known

Section Name: vmsserver
Keyword Name: hostmapdefault
Source: Default
Type: String
Default Data: DEFAULT


Section Name: vmsserver
Keyword Name: hostmapdomains
Source: Default
Type: String
Default Data:


Section Name: vmsserver
Keyword Name: hostmapusedatabase
Source: Default
Type: String
Default Data: yes


Section Name: vmsserver
Keyword Name: hostmapusevmsnames
Source: Default
Type: String
Default Data: yes

REGUTL>

[Karl Rohwedder]

Robert,

pls. post the output of AdmIn> SHOW HOSTMAP.

Are the VMS users o.k. in terms of not disusered, no passwords expired...?

regards Kalle

[Robert Atkinson]

Output below - sorry about the disguising. All of the users are system Operators, all working normally.


ALPHA_ROB$ admin show host

Host Mappings for server "ALPHA":

User Name Host Name
------------------------------------ ----------------
xxxxxxxxxxx xxx
xxxxxxxxx xxx
xxxxxxxx xxx
xxxxxxx xxx
xxxx xxx
xxxxxxxxx xxx
xxxxxxxxxS\Guest PWRK$GUEST
xxxxxxx xxx

Total of 8 host mappings

ALPHA_ROB$

[Brad McCusker]

Rob,

I wish I had more time...

If you haven't alreeady done so, please find that other thread where I talk about hostmaps and read the documentation pointed to in that thread. Hostmaps can be confusing, especially if you only read parts of the doc.

I assume the NT usernames are local, and there is no trust issues in play here?

I assume the users are actually authenticated as their NT username and they are not coming in as guest?

Are the NT user names the same as the VMS names? If not, can you create a dummy NT user and dummy VMS user to see if that behaves as desired?

There should be no need to restart just becuause of adding host maps. If you changed one of the registry settings, then you might need a restart.

There was a way to see the hostmap for a connected user. Does anyone remember if there is an ADMIN command that will sho it? Sho connections?? The tool I'm thinking of may be part of the PWRK SDA extensions - do you use them? Anyone out there use the SDA extensions and can poke around at the connection blocks or elsewhere to see if it shows you the mapping? (Sorry - it might have been some internal tool we had - I just can't remember)

There is no other way to trace the hostmapping that I know of (well, besides running a debug version of the server ;^) )

Brad McCusker
Software Concepts International
www.sciinc.com

[Robert Atkinson]

Cheers Brad. I've got a call in with HP at the moment, but I'll give your suggestions a try in the meantime.

Rob.

[Doug Phillips]

A file that's created or replaced from the client-side will inherit VMS/RMS security according to VMS/RMS rules.

If you have a PATHWORKS ACE on the directory or a file that's being replaced, and/or the dir is owned by the PWRK$GUEST, then the new file will inherit that.

Try setting up a test share with a few files in it (or use an actual share if you have one you can play with), remove all dir/file PATHWORKS ACE's and set the dir/files owner to the VMS username, set the hostmap, and see how things work.

Play with different settings, users and hostmaps and use ADMIN to reestablish the ACE's and see how that works differently.