Samba Issue.

[Rob Wallner]

Samba has been working flawlessly for us, until recently. Nothing has changed on the server that I know of.

when I try to contect to a share the log file shows: MSC00 rejected the session for name *SMBSERVER with error Not listening for calling name

MSC00 being the server name.

teh smb.conf file is:
# Global parameters
[global]
workgroup = MATSCI.COM
netbios name = MSC00
interfaces = lan1
security = SERVER
min passwd length = 4
password server = msc00
log file = /usr/local/samba/log.%m
hosts allow = 172.17.18.0/255.255.255.0
encrypt passwords = yes

[homes]
comment = Home Directories
read only = No
create mask = 0750
[rwallner]
comment = Robert's Service
path = /home/rwallner
read only = No
[tmp]
comment = temporary files
path = /tmp
read only = yes


I can ping the server from the client and the client from the server.

When I try to run smbclient -L MSC00 - I get:
added interface ip=172.17.18.15 bcast=172.17.18.255 nmask=255.255.255.0
session request to MSC00 failed (Not listening for calling name)
session request to *SMBSERVER failed (Not listening for calling name)

I verified that the smbd and the nmbd services are running

[Erik Windischman]

There are two servers that have to be evaluated, you HP-UX box running SAMBA, and the other server, I assume a Windows box you are trying to relate to. If nothing has changed on the Unix server, then perhaps some cridentials have changed on the Windows server. If you don't administer the Windows server (why would you want to), then you need to contact the responsible party and see what they changed.

[eric roseme]

Try deleting your "hosts allow" parameter in smb.conf, stop/start and retry. If it works, then see if something has changed on the system that you are connecting from (assuming that you are connecting from 172.17.18.0 - if not, then that's your problem).

Also, if you can get away from "security = server", then you should.

Eric Roseme
Hewlett-Packard

[Ivan Ferreira]

I don't understand your configuration:

netbios name = MSC00
security = SERVER
password server = msc00

Why the netbios name of your samba server is the same name of the password server (that should be a windows)?

Also you can try commenting out the line

interfaces = lan1

[Rob Wallner]

When the user authenticates via windows. I have hte user select log in using a different user name . then they use their hpux login id.

[Rob Wallner]

I'm still hacking at this - still no luck.

Evidently this all started when teh server was rebooted. I am not sure if users changed their passwords and their log on credientails changed.

According to the man page: The format of the smbpasswd file used by Samba 2.2 is very similar to
the familiar Unix passwd(5) file. It is an ASCII file containing one
line for each user.

But when I try to cat the file it looks like a binary file. Is this normal or is the file corrupt?

[eric roseme · Accepted solution]

The smbpasswd file (/var/opt/samba/private/smbpasswd) is indeed a text file. I know this sounds silly, but do not mix it up with /opt/samba/bin/smbpasswd. In any case, if you are just synchronizing smbpasswd with /etc/passwd, then there is a syncsmbpasswd utility in /opt/samba/bin that will do it for you, so you can just delete the old one and re-create a new one (assuming that you are running HP CIFS Server, not Opensource).

But that should not be your problem. The log entry is about name resolution, not authentication. Did you remove your "hosts allow" and retry?

Eric

[Rob Wallner]

I did remove it

Now some people can connect and others can't

THe one's that can not connect get this message.

attempt_netbios_session_request: MSC00 rejected the session for name *SMBSERVER with error Not listening for calling name

Here is the current smb.conf

# Global parameters
[global]
workgroup = MATSCI.COM
netbios name = MSC00
encrypt passwords = Yes
min passwd length = 4
log file = /usr/local/samba/log.%m

[homes]
comment = Home Directories
read only = No
create mask = 0750


[alan]
comment = Alan's Service
path = /home/alan
read only = No

[ahuffy]
comment = AlanHufnagel's Service
path = /home/ahuffy
read only = No


[rwallner]
path = /home/rwallner
read only = No

ahuffy & rwallner both work. Alan gets the error? Weird?

[eric roseme]

See the netbios in the log entry? That means it is name resolution, which happens on port 137. I would say to check out /etc/services (137) and /etc/hosts (name-IP) to make sure nothing had been changed prior to the reboot. But since 2 users can connect okay, I would guess that the bad user either has a bad name cached on the client, or a browsing list on that subnet has not been updated, or maybe a WINS server is out of whack. I would first try rebooting the bad client, then try mapping with an IP (\\11.11.11.123\sharename) just to see what happens. I cannot play around to see what kind of log entries whould be intersting until next week.

Eric

[Rob Wallner]

Turned out to be a combination of things. THe samba passwords were not in sync with the system passwords.

ALso the DNS was a problem.

THanks to all that helped.

[Rob Wallner]

!