topic Re: Samba errors in Operating System - Linux

Samba errors

Edwin Ruiz_2 — Mon, 19 Jan 2004 11:34:55 GMT

Hi! i am configuring newly SAmba on red hat 7.2. when i run smbstatus i get this errors:
[root@salato-apl10 samba]# smbstatus

Samba version 2.2.1a
Service uid gid pid machine
----------------------------------------------

Failed to open byte range locking database
ERROR: Failed to initialise locking database
Can't initialise locking module - exiting

samba is up but i cant to connect with windows

thanks fot ur help

Re: Samba errors

Alexander Chuzhoy — Mon, 19 Jan 2004 11:48:21 GMT

see if iptables service is up and what are the settings..

Re: Samba errors

Jerome Henry — Mon, 19 Jan 2004 12:18:26 GMT

Hi,
This is a known problem.
Go ahead and do the following for a valid user:
smbclient //localhost/'username' -U'username'
Enter the password and make the connection. It if does not work you have a
problem. If it does, then quit out. Then do:
smbstatus
It should now work without trouble.
You see, smbstatus tries to access te lock file, which does not exist until smbd has created it (which happens as soon as you make a connection).
If lockfile exists, run testparms to check your config.
Check your lock directory. The default dir is set to /var/spool/lock on mine.
Older samba releases were in /var/lock, if I remember well. Check also this directory rights

hth
J

Re: Samba errors

Steven E. Protter — Mon, 19 Jan 2004 13:18:26 GMT

in the smb.conf file is a pointer to a log file

Find that file and run this command in a ssh or telnet session

tail -f /name_of_logfile

Then attempt a samba connect from another machine.

This should give you good diagnostics.

You may wish to post the ouput.

Seems Henry has a handle on this, I'd look to him for further guidance. I will monitor anc chime in if anything comes to mind.

Have you done?
smbpasswd -A

SEP

Re: Samba errors

Edwin Ruiz_2 — Tue, 20 Jan 2004 09:49:27 GMT

thanks!
I have my /var/lock/subsys/smb but is empty. testparm command it is susscessfully buy i cant connect to samba. I use #service smb start command is that ok?

Re: Samba errors

Steven E. Protter — Tue, 20 Jan 2004 13:08:15 GMT

actually its

service samba start

to know what to put in the middle, take a look at the /etc/init.d directory

samba's startup file is almost always named samba

You can of course, name it anything you want.

SEP

Re: Samba errors

Alexander Chuzhoy — Tue, 20 Jan 2004 13:15:25 GMT

it's
service smb start

what do you mean you can't connect-from another pc?

then you should try
testparm /etc/samba/smb.conf IP

where IP is the IP address of the pc from which you're trying to connect...

Best regards..

Re: Samba errors

Edwin Ruiz_2 — Tue, 20 Jan 2004 14:28:05 GMT

i am on a winXP machine an i want to access my RH linux server with \\172.21.0.82 but i cant.. i get this message:
the network path was not found.

samba is Up, but i cant to connest

Re: Samba errors

Alexander Chuzhoy — Wed, 21 Jan 2004 01:57:14 GMT

By the way the error you received:
ERROR: Failed to initialise locking database
is not something to be afraid of.

It will be "fixed" after first client's logon.

Now- can you ping to your samba server from the XP client ?

Re: Samba errors

Jerome Henry — Wed, 21 Jan 2004 03:07:45 GMT

What command did you use ?
net use \\your.ip\share ?
Can you find the machine on searching it on your network neighborhood ?

J

Re: Samba errors

Edwin Ruiz_2 — Wed, 21 Jan 2004 14:38:53 GMT

SAmba server it is Up, i use \\172.21.0.82 from start--> run. i cant connect yet.

a week ago i was working fine but i reinstall my server but samba give that errors.

Re: Samba errors

Steven E. Protter — Wed, 21 Jan 2004 15:28:07 GMT

On the server, nothing in the log

tail -f /name_of_logfile

when it fails?

Have you recently run samba or installed a /var/adm/inetd.sec file?

This could block it.

Also

if enhanced logging is not on.

inetd -l
tail -f /var/adm/syslog/syslog.log

This will show the failures with error codes. I should have posted that in the first place.

SEP

Re: Samba errors

Edwin Ruiz_2 — Wed, 21 Jan 2004 17:39:39 GMT

Steven.. it seems that this is for HP-UX i am working on Red Hat linux 7.2

Re: Samba errors

Jerome Henry — Thu, 22 Jan 2004 03:50:25 GMT

Hi,

2 things are to be checked :
Your samba config
Your network connectivity
Could you post your testparm results (shares and access ?). Better than that, check it by yourself, using from your linux shell :
smbclient -L 172.21.0.82 -N
You'll get a list of your shares and accesses.
If you get everyhting you should, try
smbclient //172.21.0.82/sharename
If you get through, then there is nothing wrong with your samba server, issue is on connectivity.
Try to ping your linux box from your XP, try in network neighborhood to 'search' your linux box IP, telle us if you find it and what are the messages...
I WILL work :]]

J

Re: Samba errors

Edwin Ruiz_2 — Thu, 22 Jan 2004 09:25:48 GMT

Thanks! i try smbclient -L 172.21.0.82 -N and work fine, then i try smbclient //172.21.0.82/ias9ir2 and work fine, but when i search from XP machine i cant see my samba server, i get ping but i cant like shared resources.

Please help me

Re: Samba errors

Robert Binkhorst — Thu, 22 Jan 2004 10:14:16 GMT

Samba comes with excellent documentation. Check out the textdocs directory (could be under ./docs). In particular, go through the steps in DIAGNOSIS.txt and WinNT.txt.

Good luck!

Re: Samba errors

Jerome Henry — Thu, 22 Jan 2004 10:36:09 GMT

So,
If I get you clearly, you ping and it works
You search the machine from XP, and you don't find it.
Check on you linux machine that nmbd is running fine, and tell us about its configuration.
Check on you XP box that on TCP/IP protocol you use NBT, that is to say netbios over tcp/ip, and not only tcp/ip.
Check also that
HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\Netlogon\\parameters

RequireSignOrSeal should be at 0 if client is XP pro and samba acting as a pdc.

hth

J

Re: Samba errors

Edwin Ruiz_2 — Thu, 22 Jan 2004 12:18:58 GMT

Windows can connect to samba server for 139 port? if i try telnet 172.21.0.82 139 must be connect?

Re: Samba errors

Jerome Henry — Thu, 22 Jan 2004 13:07:20 GMT

Yes,
but you won't get you shares with telnet
Try
net use \\172.21.0.82 instead

What about nmbd status ?

J

Re: Samba errors

Edwin Ruiz_2 — Thu, 22 Jan 2004 13:23:41 GMT

nmbd is up, when i run

C:\Documents and Settings\edruiz>net use \\172.21.0.82 instead
System error 53 has occurred.

The network path was not found.

I cant make telnet to this port

C:\Documents and Settings\edruiz>telnet 172.21.0.82 139
Connecting To 172.21.0.82...Could not open connection to the host, on port 139:
Connect failed

I i run smbclient -L //172.21.0.82/c$ -U edruiz i can connect to my machine. it is very rarely