Using Samba with HP-UX 11.00

[Anna van Tatenhove]

I am having real problems configuring Samba on an L class server running HP-UX 11.00 (64-bit).
I have installed the latest HP-UX version as downloaded from the Samba site after having similar problems using the software provided with OS. Setup and installation goes OK, Istart it as a daemon and initially it seems to connect OK. Clients using NT4, NT4 Server, Win95 and Win2k are initially able to connect using the netbios name. and then on rebooting or logging in again, they either can't connect at all or need to use the IP address. The security level is set to server, but I have also tried share level security to no avail. The config file is an exact replica of that used on a Sun box with absolutely no problems at all. Have searched but have found no reference to anyone else experiencing similar problems.
Anna van Tatenhove

[Vincenzo Restuccia]

see http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B8725-90003/B8725-90003_top.html&con=/hpux/onlinedocs/B8725-90003/00/00/6-con.html&toc=/hpux/onlinedocs/B8725-90003/00/00/6-toc.html&searchterms=samba&queryid=20010418-165831

[Vincent Stedema]

Anna,

Did you add an entry to the client's lmhost file? If not, you could give it a try.

Are "lm announce" and "wins support" set to "yes"?

Vincent

[Anna van Tatenhove]

lmhosts - I haven't done that but will give it a try. However, the however the name service switch has been configured for the box. Also all clients use DHCP for WINS. They can all telnet to the box, and ping the box, so the connectivity is certainly there.client's lmhost file? .

Are "lm announce" and "wins support" set to "yes"? No they are not should they be?

[Vincent Stedema]

Anna,

There's a difference between an IP hostname and a NETBIOS name. The IP hostname of a server doesn't have to be the same as its NETBIOS name of the same machine.

I'm not very familiar with WINS via DHCP and I don't know if this translates IP hostnames to NETBIOS. What I do know is that if you don't set "lm announce" to yes, the samba server doesn't announce itself to the Workgroup. That could explain why the Windows machines can't resolve the NETBIOS name of the samba server.

There are a number of things you can try:

1. Set "lm announce" to yes
2. Set "wins support" to yes and specify the samba server as WINS server for the clients.
3. Add an entry to C:\WINDOWS\LMHOSTS, which maps the NETBIOS name of the samba server to its IP address.

You can verify that the NETBIOS name of the samba server is resolved correctly by using the DOS command "nbtstat""

C:\> nbtstat -a
C:\> nbtstat -A

Hope this helps.

Vincent

[Anna van Tatenhove]

Vincent

I tried adding it to the lmhosts file, but in all cases there were no entries in this file in any case.

I turned on LMAnnounce in the registry, again this wasn't on before I turned it on and I find it very strange that we had absolutely no problems connecting to the 2 Sun boxes without these being on.

Neither of these options helped me with my problem.

We won't be setting the box up as a WINS server as we use DHCP for that and all WINS requests go through and NT boxes, 1 in our national office and another in our local office. Neither of the Sun boxes were set up as WINS servers either.

The netbios name and the IP address are being resolved, so that is not the problem.

The problem has become OS specific and is only happening on the Win95 boxes. I have found that if I upgrade these PC's to Win98, my problems are resolved.

[Vincent Stedema]

Anna,

I meant the "lm announce" option in smb.conf, not in the Windows registry. The samba server has to know that it should announce itself to the workgroup.

I haven't got a clue as to why Win95 clients have problems connecting to the Netbios name of the samba server and the Win98 clients don't. It looks like a resolving issue, and setting "lm announce" to "yes" should clear up most issues.

Could you please post the contents of your smb.conf?

Vincent