| View previous topic :: View next topic |
| Author |
Message |
JerMe
n00b
Joined: 25 Apr 2005
Posts: 18
|
 Posted: Wed Nov 23, 2005 6:34 am Post subject: Samba PDC, WinXP "Multiple Connections" error on l |
 |
|
I followed the Samba PDC HOWTO, and it almost works. Wierd things happen on logoff - WinXP tries to synchronize files from a certain user, no matter what other user I'm logged in as. So if I login then logoff as "user2", WinXP will try to sync "user1" 's files. Because I'm logged in as "user2", it'll try to ask for a password (assuming that XP is trying to sync user1's files), then it gives me this message:
"Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again."
Here's my /etc/samba/smb.conf:
| Code: |
[global]
netbios name = mycomputer
workgroup = mydomain
server string = Network storage
hosts allow = 192.168.0.0/24 127.0.0.0/8
security = user
encrypt passwords = yes
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
interfaces = lo eth0
bind interfaces only = yes
local master = yes
os level = 65
domain master = yes
preferred master = yes
null passwords = no
hide unreadable = yes
hide dot files = yes
domain logons = yes
logon script = login.bat OR %U.bat
logon path = \\%L\profiles\%U
logon drive = H:
logon home = \\%L\%U\.9xprofile
wins support = yes
name resolve order = wins lmhosts host bcast
dns proxy = no
time server = yes
log file = /var/log/samba/log.%m
max log size = 50
smb passwd file = /etc/samba/private/smbpasswd
add user script = /usr/sbin/useradd -m %u
delete user script = /usr/sbin/userdel -r %u
add group script = /usr/sbin/groupadd %g
delete group script = /usr/sbin/groupdel %g
add user to group script = /usr/sbin/usermod -G %g %u
add machine script = /usr/sbin/useradd -s /bin/false -d /dev/null %u
passwd program = /usr/bin/passwd %u
passwd chat = "*New password:*" %n\r "*New password (again):*" %n\r \ "*Password changed*"
unix charset = ISO8859-1
[netlogon]
path = /var/lib/samba/netlogon
guest ok = no
read only = yes
browseable = no
[profiles]
path = /var/lib/samba/profiles
browseable = no
writeable = yes
default case = lower
preserve case = no
short preserve case = no
case sensitive = no
hide files = /desktop.ini/ntuser.ini/NTUSER.*/
write list = @smbusers @root
create mask = 0600
directory mask = 0700
[homes]
path = /home/%U
browseable = no
valid users = %S
read only = no
guest ok = no
inherit permissions = yes
|
Edit: Problem before happened when I had 2 WinXP machines logged into the PDC, I've eliminated the 2nd XP machine from the domain to make things simpler. So I have 1 XP machine connected to the Samba PDC, and I'm still getting the weird sync messages.
Last edited by JerMe on Sat Nov 26, 2005 7:52 am; edited 3 times in total |
|
| Back to top |
|
 |
slam_head
Guru
Joined: 06 Jan 2003
Posts: 449
Location: New York City
|
| Posted: Wed Nov 23, 2005 4:33 pm Post subject: |
|
|
What does the log file say? It should be /var/log/samba/log.netbiosname. A good way to look at the logs would be to run:
| Code: | | grep -v "\[200" log.netbiosname |
This will strip the garbage out of the logs. I would also strongly recommend using tdbsam or even better ldap as your passdb backend. Ldap is a bit more work, but will give you a more robust and scalable system. |
|
| Back to top |
|
|
JerMe
n00b
Joined: 25 Apr 2005
Posts: 18
|
| Posted: Thu Nov 24, 2005 12:04 am Post subject: |
|
|
Here is the samba log for the 1st WinXP computer:
| Code: |
#jer777me@excalibur /var/log/samba $ grep -v "\[200" log.winxp1
winxp1 (192.168.0.102) connect to service profiles initially as user user3 (uid=1003, gid=100) (pid 10170)
winxp1 (192.168.0.102) connect to service netlogon initially as user user3 (uid=1003, gid=100) (pid 10170)
winxp1 (192.168.0.102) connect to service user3 initially as user user3 (uid=1003, gid=100) (pid 10170)
call_nt_transact_ioctl(0x9009c): Currently not implemented.
winxp1 (192.168.0.102) connect to service profiles initially as user user3 (uid=1003, gid=100) (pid 10170)
winxp1 (192.168.0.102) closed connection to service netlogon
winxp1 (192.168.0.102) closed connection to service user3
winxp1 (192.168.0.102) closed connection to service profiles
winxp1 (192.168.0.102) closed connection to service profiles
winxp1 (192.168.0.102) connect to service profiles initially as user user1 (uid=1004, gid=100) (pid 10174)
winxp1 (192.168.0.102) connect to service netlogon initially as user user1 (uid=1004, gid=100) (pid 10174)
winxp1 (192.168.0.102) connect to service user1 initially as user user1 (uid=1004, gid=100) (pid 10174)
winxp1 (192.168.0.102) connect to service profiles initially as user user1 (uid=1004, gid=100) (pid 10174)
winxp1 (192.168.0.102) closed connection to service netlogon
winxp1 (192.168.0.102) closed connection to service user1
winxp1 (192.168.0.102) closed connection to service profiles
winxp1 (192.168.0.102) closed connection to service profiles
winxp1 (192.168.0.102) connect to service profiles initially as user user1 (uid=1004, gid=100) (pid 10174)
winxp1 (192.168.0.102) closed connection to service profiles
winxp1 (192.168.0.102) connect to service netlogon initially as user user1 (uid=1004, gid=100) (pid 10174)
winxp1 (192.168.0.102) connect to service user1 initially as user user1 (uid=1004, gid=100) (pid 10174)
winxp1 (192.168.0.102) connect to service profiles initially as user user1 (uid=1004, gid=100) (pid 10174)
winxp1 (192.168.0.102) connect to service profiles initially as user user1 (uid=1004, gid=100) (pid 10174)
winxp1 (192.168.0.102) closed connection to service netlogon
winxp1 (192.168.0.102) closed connection to service user1
winxp1 (192.168.0.102) closed connection to service profiles
winxp1 (192.168.0.102) closed connection to service profiles
winxp1 (192.168.0.102) connect to service profiles initially as user user3 (uid=1003, gid=100) (pid 10325)
winxp1 (192.168.0.102) connect to service netlogon initially as user user3 (uid=1003, gid=100) (pid 10325)
winxp1 (192.168.0.102) connect to service user3 initially as user user3 (uid=1003, gid=100) (pid 10325)
winxp1 (192.168.0.102) closed connection to service profiles
winxp1 (192.168.0.102) closed connection to service netlogon
winxp1 (192.168.0.102) closed connection to service user3
winxp1 (192.168.0.102) connect to service user3 initially as user user3 (uid=1003, gid=100) (pid 10325)
winxp1 (192.168.0.102) connect to service netlogon initially as user user3 (uid=1003, gid=100) (pid 10325)
winxp1 (192.168.0.102) closed connection to service netlogon
winxp1 (192.168.0.102) connect to service profiles initially as user user3 (uid=1003, gid=100) (pid 10325)
winxp1 (192.168.0.102) connect to service profiles initially as user user3 (uid=1003, gid=100) (pid 10325)
winxp1 (192.168.0.102) closed connection to service user3
winxp1 (192.168.0.102) closed connection to service profiles
winxp1 (192.168.0.102) closed connection to service profiles
write_socket_data: write failure. Error = Connection reset by peer
write_socket: Error writing 4 bytes to socket 27: ERRNO = Connection reset by peer
Error writing 4 bytes to client. -1. (Connection reset by peer)
winxp1 (192.168.0.102) connect to service profiles initially as user user3 (uid=1003, gid=100) (pid 9159)
winxp1 (192.168.0.102) closed connection to service profiles
winxp1 (192.168.0.102) connect to service netlogon initially as user user3 (uid=1003, gid=100) (pid 9159)
winxp1 (192.168.0.102) connect to service user3 initially as user user3 (uid=1003, gid=100) (pid 9159)
winxp1 (192.168.0.102) connect to service profiles initially as user user3 (uid=1003, gid=100) (pid 9159)
winxp1 (192.168.0.102) connect to service profiles initially as user user3 (uid=1003, gid=100) (pid 9159)
winxp1 (192.168.0.102) closed connection to service netlogon
winxp1 (192.168.0.102) closed connection to service user3
winxp1 (192.168.0.102) closed connection to service profiles
winxp1 (192.168.0.102) closed connection to service profiles
winxp1 (192.168.0.102) connect to service profiles initially as user user3 (uid=1003, gid=100) (pid 9424)
winxp1 (192.168.0.102) closed connection to service profiles
winxp1 (192.168.0.102) connect to service netlogon initially as user user3 (uid=1003, gid=100) (pid 9424)
winxp1 (192.168.0.102) connect to service user3 initially as user user3 (uid=1003, gid=100) (pid 9424)
winxp1 (192.168.0.102) connect to service profiles initially as user user3 (uid=1003, gid=100) (pid 9424)
winxp1 (192.168.0.102) connect to service profiles initially as user user3 (uid=1003, gid=100) (pid 9424)
winxp1 (192.168.0.102) closed connection to service netlogon
winxp1 (192.168.0.102) closed connection to service user3
winxp1 (192.168.0.102) closed connection to service profiles
winxp1 (192.168.0.102) closed connection to service profiles
winxp1 (192.168.0.102) connect to service profiles initially as user user1 (uid=1004, gid=100) (pid 9460)
winxp1 (192.168.0.102) connect to service netlogon initially as user user1 (uid=1004, gid=100) (pid 9460)
winxp1 (192.168.0.102) connect to service user1 initially as user user1 (uid=1004, gid=100) (pid 9460)
winxp1 (192.168.0.102) closed connection to service profiles
winxp1 (192.168.0.102) closed connection to service netlogon
winxp1 (192.168.0.102) closed connection to service user1
winxp1 (192.168.0.102) connect to service user1 initially as user user1 (uid=1004, gid=100) (pid 9674)
winxp1 (192.168.0.102) connect to service user1 initially as user user1 (uid=1004, gid=100) (pid 9674)
winxp1 (192.168.0.102) closed connection to service user1
winxp1 (192.168.0.102) closed connection to service user1
winxp1 (192.168.0.102) connect to service profiles initially as user user1 (uid=1004, gid=100) (pid 9674)
winxp1 (192.168.0.102) connect to service profiles initially as user user1 (uid=1004, gid=100) (pid 9674)
winxp1 (192.168.0.102) closed connection to service profiles
winxp1 (192.168.0.102) closed connection to service profiles
winxp1 (192.168.0.102) connect to service profiles initially as user user3 (uid=1003, gid=100) (pid 9677)
winxp1 (192.168.0.102) connect to service netlogon initially as user user3 (uid=1003, gid=100) (pid 9677)
winxp1 (192.168.0.102) connect to service user3 initially as user user3 (uid=1003, gid=100) (pid 9677)
winxp1 (192.168.0.102) closed connection to service profiles
winxp1 (192.168.0.102) closed connection to service netlogon
Unable to connect to CUPS server localhost - Connection refused
Unable to connect to CUPS server localhost - Connection refused
|
Here is the samba log for the 2nd WinXP computer:
| Code: |
#jerme@mycomputer /var/log/samba $ grep -v "\[200" log.winxp2
read_socket_data: recv failure for 4. Error = Connection reset by peer
winxp2 (192.168.0.104) connect to service profiles initially as user user1 (uid=1004, gid=100) (pid 9692)
winxp2 (192.168.0.104) connect to service netlogon initially as user user1 (uid=1004, gid=100) (pid 9692)
winxp2 (192.168.0.104) connect to service user1 initially as user user1 (uid=1004, gid=100) (pid 9692)
winxp2 (192.168.0.104) connect to service user1 initially as user user1 (uid=1004, gid=100) (pid 9692)
winxp2 (192.168.0.104) closed connection to service profiles
winxp2 (192.168.0.104) closed connection to service netlogon
winxp2 (192.168.0.104) closed connection to service user1
winxp2 (192.168.0.104) closed connection to service user1
winxp2 (192.168.0.104) connect to service profiles initially as user user1 (uid=1004, gid=100) (pid 9693)
winxp2 (192.168.0.104) connect to service profiles initially as user user1 (uid=1004, gid=100) (pid 9693)
winxp2 (192.168.0.104) closed connection to service profiles
winxp2 (192.168.0.104) closed connection to service profiles
winxp2 (192.168.0.104) connect to service profiles initially as user user2 (uid=1002, gid=100) (pid 9694)
winxp2 (192.168.0.104) connect to service netlogon initially as user user2 (uid=1002, gid=100) (pid 9694)
winxp2 (192.168.0.104) connect to service user2 initially as user user2 (uid=1002, gid=100) (pid 9694)
winxp2 (192.168.0.104) closed connection to service profiles
winxp2 (192.168.0.104) closed connection to service netlogon
winxp2 (192.168.0.104) closed connection to service user2
winxp2 (192.168.0.104) connect to service profiles initially as user user2 (uid=1002, gid=100) (pid 9696)
winxp2 (192.168.0.104) connect to service profiles initially as user user2 (uid=1002, gid=100) (pid 9696)
winxp2 (192.168.0.104) closed connection to service profiles
winxp2 (192.168.0.104) closed connection to service profiles
|
| slam_head wrote: | | I would also strongly recommend using tdbsam or even better ldap as your passdb backend. Ldap is a bit more work, but will give you a more robust and scalable system. |
I read a bit about LDAP and will get to it, but I wanted to get the Samba PDC up and running first. It appears that everyone's H: drive is working, but the WinXPs trying to sync multiple users at the same time on logoff is an annoyance, and is probably a symptom of a bigger problem with my setup. =( |
|
| Back to top |
|
|
JerMe
n00b
Joined: 25 Apr 2005
Posts: 18
|
| Posted: Sat Nov 26, 2005 7:51 am Post subject: |
|
|
| I removed the 2nd XP machine from the domain. So now, I have one WinXP machine trying to connect to the Samba PDC. No matter what user I login/logoff as (user1, user2, user3, user4), WinXP will always try to sync user1's files on logoff. The sync will fail with the "Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again" error. Why is that? |
|
| Back to top |
|
|
slam_head
Guru
Joined: 06 Jan 2003
Posts: 449
Location: New York City
|
| Posted: Mon Nov 28, 2005 4:57 pm Post subject: |
|
|
| Do you have a wins server defined on the clients networking. It looks like your PDC is acting as a wins server so it would be a good idea to have the clients use it. I would also look at your networking for bad cables and/or connections. Also check to make sure you haven't created any loops with your switches. The switches run a protocol that prevents loops and will automatically down one of the ports of a switching loop is present. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
