Dear people,

I'm currently experiencing a samba problem for which I'd like some advice.

The samba server is 3.0.24 on debian 4.0.

The clients are windows xp pc's that use the samba server as a domain controller. Every user has a home directory. There are also a few other shares on the server that are served by samba.

The problem is that users have to reauthenticate at random times when they try to open their home share or another share, sometimes the home dir would not ask for credentials and then the other share would or vice versa.
I only see disconnect messages in the samba logs.
Sometimes, closing a file that is on the share also disconnects the session.


This is what the config looks like:


# Global parameters
workgroup = JES
netbios name = JES-FW
interfaces = eth1
encrypt passwords = Yes
domain logons = Yes
os level = 99
preferred master = Yes
domain master = Yes
logon script = %U.bat
printing = bsd
printcap name = /etc/printcap
load printers = yes
socket options = TCP_NODELAY
security = user
log level = 2
wins support = yes
profile acls = yes
nt acl support = yes
lanman auth = yes
smb ports = 139

[homes]
browseable = no
writeable = yes
force directory mode = 0777
force create mode = 0777
#create mask = 0755

[netlogon]
comment = Network Logon Service
path = /home/netlogon
public = yes
writable = yes
browseable = yes
locking = no
force create mode = 0644
force directory mode = 0755

[data]
comment = data-partitie
path = /data/public
public = yes
writable = yes
force directory mode = 0777
force create mode = 0777

[administratie]
comment = administratie
path = /data/administratie
public = no
writable = yes
force directory mode = 0777
force create mode = 0777
read list = @administratie
write list = @administratie



Thanks for any insight you could provide on this issue.

I'm so new to this stuff that I doubt I'll be of much help, but...

In my adventures with Samba thus far I think the wise thing to do would be to narrow the search as much as possible to figure out who is causing the error.

Is it strictly a behavior of the client side OS?

Is it only an XP behavior? What happens when someone authenticates in Vista? Or Mac OSX?

Is it really a Samba settings issue - or a server side permissions issue - either in Samba or in the chmod or ownership flavor of things.


I don't know if it works for you - but you could try opening up the door a little in your authentication settings and see if the behavior stops... Then you could slowly begin to close the door again and see where it starts.

My suspicion is that it's an XP authentication setting and not something Samba is doing.. Just my 2 cents...

Thanks for the reply,

I can tell you now that there are only windows xp machines overthere and they're not all experiencing this issue in the same degree, some don't even see this problem at all.

The permissons seem to be alright for the setup. (tried with world writable also for testing)

On the other hand, I have a similar setup using same samba version and debian os that doesn't have this problem at all.

So I'm also thinking the local network might pose a problem.
I see this kind of errors in the samba logs: (from the users personal log file <netbiosname>.log file)

[2009/01/28 13:58:31, 0] lib/util_sock.c:get_peer_addr(1221)
getpeername failed. Error was Transport endpoint is not connected
[2009/01/28 13:58:31, 0] lib/util_sock.c:get_peer_addr(1221)
getpeername failed. Error was Transport endpoint is not connected
[2009/01/28 14:06:21, 0] lib/util_sock.c:get_peer_addr(1221)
getpeername failed. Error was Transport endpoint is not connected
[2009/01/28 14:06:21, 0] lib/util_sock.c:get_peer_addr(1221)
getpeername failed. Error was Transport endpoint is not connected