cancel
Showing results for 
Search instead for 
Did you mean: 

About samba for Tru64

SOLVED
Go to solution
sammysammy
Frequent Advisor

About samba for Tru64

Hi,

I tried to download samba binaries from Tru64, and found the this link:
http://h30097.www3.hp.com/internet/detailed.htm
However there is no download link available in this page.

I also downloaded samba source from samba.org, but there is no autoheader in our Tru64 system.
Here s the error when I tried to compile the source:

# pwd
/usr/local/samba-3.0.25rc3/source
# ./autogen.sh
./autogen.sh: autoheader: not found
./autogen.sh: test: argument expected
#

Can anyone suggest me a way how to install samba in Tru64?

Very appreciate for your attention.
Thanks
Sam
6 REPLIES
sammysammy
Frequent Advisor

Re: About samba for Tru64

Hi, I have compiled samba in the system. Now smbd and nmbd started and running. But from my windows xp I can't see it s published its workgorup name in the Explorer. The network enviornment I am running this Samba consist of NT primary domain (running in 2003 server).

Here is the samba log message:
# more log.nmbd
[2007/05/01 11:53:59, 0] nmbd/nmbd.c:(697)
Netbios nameserver version 3.0.25rc3 started.
Copyright Andrew Tridgell and the Samba Team 1992-2007
[2007/05/01 11:59:43, 0] nmbd/nmbd_become_lmb.c:(396)
*****

Samba name server sambaserver is now a local master browser for workgroup sambaserver on subnet 172.29.1.69

*****
# more log.smbd
[2007/05/01 11:53:58, 0] smbd/server.c:(944)
smbd version 3.0.25rc3 started.
Copyright Andrew Tridgell and the Samba Team 1992-2007
[2007/05/01 11:53:58, 1] smbd/files.c:(192)
file_init: Information only: requested 10000 open files, 4076 are available.
[2007/05/01 11:53:59, 0] smbd/dmapi.c:(71)
Initializing DMAPI: DMAPI Tru64 V5.1A

The smb.conf is written as:
# ./testparm
Load smb config files from /usr/local/samba/lib/smb.conf
Processing section "[homes]"
Processing section "[myshare]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

[global]
workgroup = sambaserver
server string = TEST SERVER
log file = /usr/local/samba/var/log.%m
max log size = 50
dns proxy = No
hosts allow = 172.29.228.103, 127.

[homes]
comment = Home Directories
read only = No
browseable = No

[myshare]
comment = Public shared stuff
path = /usr/local/samba/test01
valid users = mary, fred
guest ok = Yes

Thanks
Sam
Danny Petterson - DK
Trusted Contributor

Re: About samba for Tru64

Hi!

Have you tried to view your share from XP, using Start, Run, \\yoursambaservername?

And if you can, if its accesable?

Please review

http://us4.samba.org/samba/docs/man/Samba-HOWTO-Collection/introduction.html

for the most common thins about configuring samba.

Cheers,
Danny Petterson
sammysammy
Frequent Advisor

Re: About samba for Tru64

Hi,

I am running samba-3.0.25rc3 in Tru64 5.1B.
I compiled Samba source with --with-winbind switch.
My goal of setting up Samba is to allow existing windows user login
this Tru64 server without further asking password if they have already
logged in windows, yet with additional user control by adding a line
"valid users = ..." in each directory section, that way Samba won't
allow every logged on windows user login, only allow windows users
that listed in the "valid users = ..." line.
Therefore I thought joining Samba to the existing NT domain and also
adding a line of "valid users=..." in smb.conf may be the solution.

However when I tried to connect existing NT domain, I got an error:
# ./net rpc join -S 172.10.40.63
open_policy failed: NT_STATUS_ACCESS_DENIED
Password:

Note, I didn't compile Ldap and Kerberos into the Samba.

I welcome any idea about to achieve this goal. If joining the existing NT domain is a must thing to do, then I may be most probably need to compile Ldap and Kerberos in Samba. If this is the case, do I need to further configure OpenLdap and Kerberos in Tru64?

If Openldap and Kerberos is not needed, what should I do to join existing NT/W2K domain?

Here is the configuration of smb.conf file:
# ./testparm
Load smb config files from /usr/local/samba/lib/smb.conf
Processing section "[pubshare]"
Loaded services file OK.
Server role: ROLE_DOMAIN_MEMBER
Press enter to see a dump of your service definitions

[global]
workgroup = HUNTER
server string = TEST SERVER
security = DOMAIN
log file = /usr/local/samba/var/log.%m
max log size = 50
local master = No
dns proxy = No
hosts allow = 172.10.40., 127.

[pubshare]
comment = Public shared stuff
path = /usr/local/samba/test01
valid users = wunsam, ghanen
guest ok = Yes
#

I m very appreciate for every suggestion.

Thanks
S
Rob Leadbeater
Honored Contributor
Solution

Re: About samba for Tru64

Hi Sam,

Can you confirm what type of Windows domain you're trying to join...

You've mentioned NT Domain a few times, but also Windows 2000, which implies Active Directory...

If you have got an NT domain then you probably want to be using security=DOMAIN, and join the domain using net rpc join.

However if you've got a native mode Active Directory then you'll probably be better with security=ADS and join with net ads join. Although you'll almost certainly need to get the Kerberos stuff compiled...

You might also need to get your Tru64 box added to the domain first, through Server Manager or Active Directory Users and Computers.

Hope this helps,

Regards,

Rob
sammysammy
Frequent Advisor

Re: About samba for Tru64

hi, thanks very much for the suggestion.
Do you know how to find out whether the existing domain controller is a windows ADS or not? The windows sys adm is on holiday, and I don't have password login windows server. Basically I don't know which server our existing windows domain controller.
In my windows DOS shell, ipconfig /all returns 2 WINS servers, one is 172.10.0.1 as primary, another is 172.10.0.2 which is a secondary server. I would assumed this two servers are the windows domain controller servers.
If not, how can I find out and more importantly how to find out whether the server is using ADS?

Thanks
Sam
Rob Leadbeater
Honored Contributor

Re: About samba for Tru64

Hmmm... good question !

Just because you've got WINS servers defined doesn't necessarily mean that those are domain controllers.

Probably the easiest way to check is to see whether you have any servers defined as DNS A records for your domain name.

So at a command prompt (on your Windows PC) type in nslookup

nslookup> hunter.com (or whatever your domain name is - I guessed based on your workgroup name)

If you've using Active Directory then that should return the name(s) and IP addresses of your domain controllers. It it returns nothing then you're probably running an NT domain.

Of course this might not always be true, as DNS records can be wrong, so you might want to check with your Windows sysadmin when he returns...

Cheers,

Rob