Hi everyone, i have set up a server with samba-2.2.3a-12 (Debian Woody) for a network that is shared with about 100 schools. There are about 50 Clients (WinXP) with only one local user. They are all in the same workgroup. The server has security=user and the about 100 usernames from the schools. So a kid from a given school logs into the Client with the local user (e.g. user=pc, pass=pc), but has to give a special (school-based) username and password if it wants to connect to the shares from the server (There is a link to \\server\ at the desktop). So far so good. Problem: 1. school1 logs into the server with username=school1, gets its /home/schoo1 on the server, does its work and logs out of the client 2. school2 logs into the same client, connects to the server with username=school2 and gets his own /home/school2 on the server and _also_ the /home/school1 from the previously logged in school1. school2 has then read/write access to school1! This just happens sometimes on some clients. I am not very experienced with samba, but I really dont understand, why this happens. Is this a known problem of xp, that it does remember username/password from any further logins, or is it my fault with a bad smb.conf? Is eventually the link to "\\server\" wrong? Should it better be something like "\\server\%u" ,or "\\server\~" ? Btw: I will convert the network in a domain, but it has to run with the workgroup for the next 2-3 weeks, so i hope you guys have an answer for this. Thanks in advance, -- Sebastian Schinzel
Try forcing users to reboot the xp machines rather than just logging off. On 20 Jan 2003 Sebastian Schinzel wrote: Hi everyone, i have set up a server with samba-2.2.3a-12 (Debian Woody) for a network that is shared with about 100 schools. There are about 50 Clients (WinXP) with only one local user. They are all in the same workgroup. The server has security=user and the about 100 usernames from the schools. So a kid from a given school logs into the Client with the local user (e.g. user=pc, pass=pc), but has to give a special (school-based) username and password if it wants to connect to the shares from the server (There is a link to \\server\ at the desktop). So far so good. Problem: 1. school1 logs into the server with username=school1, gets its /home/schoo1 on the server, does its work and logs out of the client 2. school2 logs into the same client, connects to the server with username=school2 and gets his own /home/school2 on the server and _also_ the /home/school1 from the previously logged in school1. school2 has then read/write access to school1! This just happens sometimes on some clients. I am not very experienced with samba, but I really dont understand, why this happens. Is this a known problem of xp, that it does remember username/password from any further logins, or is it my fault with a bad smb.conf? Is eventually the link to "\\server\" wrong? Should it better be something like "\\server\%u" ,or "\\server\~" ? Btw: I will convert the network in a domain, but it has to run with the workgroup for the next 2-3 weeks, so i hope you guys have an answer for this. Thanks in advance, -- Sebastian Schinzel -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
> Try forcing users to reboot the xp machines rather than just logging off.Rebooting does not help. Even shutting down a client and waiting about a hour does not help. I have already tried this a couple of times. What about the link to the server? Do you think i should better use something like "\\server\%u"? Does Windows know something like %u, or is this samba-specific? -- Sebastian Schinzel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 20 Jan 2003, Sebastian Schinzel wrote:> Problem: > 1. school1 logs into the server with username=school1, gets its > /home/schoo1 on the server, does its work and logs out of the client > > 2. school2 logs into the same client, connects to the server with > username=school2 and gets his own /home/school2 on the server and _also_ > the /home/school1 from the previously logged in school1. school2 has > then read/write access to school1! This just happens sometimes on some > clients.Are you running in share mode security? I can think of a couple of possibilities if you were. If so, then I would definitly recommend using "security = user" instead. cheers, jerry ---------------------------------------------------------------------- Hewlett-Packard ------------------------- http://www.hp.com SAMBA Team ---------------------- http://www.samba.org GnuPG Key ---- http://www.plainjoe.org/gpg_public.asc ISBN 0-672-32269-2 "SAMS Teach Yourself Samba in 24 Hours" 2ed "You can never go home again, Oatman, but I guess you can shop there." --John Cusack - "Grosse Point Blank" (1997) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+NUYjIR7qMdg1EfYRAlgqAKDfgUorbgzuEQGQBKn0B35WrfvyswCgkQBo UPxL4aJOKatD8WTkjpG5agw=J2Aw -----END PGP SIGNATURE-----