Operating System - HP-UX
1830619 Members
2587 Online
110015 Solutions
New Discussion

multi-subnetted network SAMBA CONF in HP-UX 11.11

 
Stan_365
Frequent Advisor

multi-subnetted network SAMBA CONF in HP-UX 11.11

Dear Sir:
We have a Server-sub-network(172.28.100.0) and serveral Client-sub-networks(e.g 172.28.113.0). Is it possible to share FS from HP-UX Server to clients of WIN XP in Client-sub-networks with certain security? The environment is: currently no WINS configured, the clients get IP from local DHCP server so there is no DNS record for the client. Installed CIFS software is "B8725AA A.02.01.01 HP CIFS Server".

If we use "Security = share " the FS is able to be accessed(browse and W/R) from client without restriction. But if we use "Security = user" it keeps on prompt for User/Passwd only. syncsmbpasswd excuted OK. Attached is the smb.conf

Many Thanks,

Stan Du
4 REPLIES 4
Matti_Kurkela
Honored Contributor

Re: multi-subnetted network SAMBA CONF in HP-UX 11.11

The number of subnets should make no difference in security arrangements, only in network browsing. As you can get to the user/password prompt, the clients are obviously finding the server and trying to connect to it.

If you specify only the user name to the username field in the password dialog, Windows thinks you mean CLIENTDOMAIN\username. If that fails, CLIENTHOSTNAME\username is automatically tried. Only if both the client and the server are in the same domain/workgroup, you can use domain-less usernames.

When using "Security = user", try specifying the username as SAMBA\username (matching your workgroup name) or HPUXHOSTNAME\username.

MK
MK
Stan_365
Frequent Advisor

Re: multi-subnetted network SAMBA CONF in HP-UX 11.11

Hi MK,

It is true this is a browsing problem. We had tried SAMBA\Username and HPUXHOSTNAME\username before, but the result was the same. From SAMBA HOW-TO GUide it is suggested to browse across subnetworks by using lmhosts or WINS. But there is no detail info. My questions could be:
1. If we use lmhosts, lmhosts file will only contains "IP_Addr Netbios_name", Netbios_name would be HPUXHOSTNAME by default, IP_Addr is the IP of the samba server. And we must add the "-H" option into startsmb script. Is there anything else that must be set from Server or Client? Name resolution of the Netbios_name from client is OK.
2. If we choose to set the samba server as the WINS, what parameters should be defined in SMB.conf? Is there anything need to do in client?

Stan
Stan_365
Frequent Advisor

Re: multi-subnetted network SAMBA CONF in HP-UX 11.11

We have enabled the SAMBA Server as WINS by "wins support = Yes" in the global parameters in smb.conf, and we have set the XP (SMB Client)'s WINS thru (network property--> TCP/IP Property--> Advanced --> WINS) to the IP of the SAMBA Server. But unfortunately the result is the same!! Who can tell me how the set the SAMBA Server as the WINS, which make to possible to browse accross the multiple subnetworks? Any suggestion is welcome.

Thanks,

Stan
Rita C Workman
Honored Contributor

Re: multi-subnetted network SAMBA CONF in HP-UX 11.11

Not sure, but hope this helps.

When we set up SAMBA on HPUX along time ago, it was intended as a quick backdoor for printing. Hence, I removed security and left it wide open.
But.....as time progressed now we needed some shares to be locked down. In a failover environment I had to make (or re-make) our SAMBA smb.conf somewhat universal.
We currently are running 2.03.02 on HPUX as the host. Windows are the clients.
To lockdown certain shares I set it up like this:
[share_name]
comment = Secured share
path = /dir/sub-dir
public = no
browseable = no
valid users = user1, user2
guest ok = no
writeable = no

Mapped the Windows user, who also had to have the corresponding 'user1' account created with passwd on HPUX. That HPUX account is just an account using /usr/bin/false for shell. Once mapped I just put in login/password and they were in.
Had the manager try and map to the same share (It Mgr) using his account, any guest account or anything he wanted to try and gain unauthorized access. He couldn't, so it seems to be secure.
And to lock out them out I can use passwd -l option.

Hope this helps,
Rita