Hello, I've a subnet behind a Linux router that is also the domain server, WINS server and browse master for the domain: ------ | PC | ----- Host 1 Host 2 ------ | ------------------- --------------------- ------ |--| Domain (samba, |----| Password (samba, | | PC | ----- | master Linux) | | server Solaris | ------ ------------------- --------------------- I've gotten the Win95 PCs to authenticate off Host 1. Host 2 is also a Samba server that provides filespace for the PCs. Host 2 is on a separate Ethernet subnet from the PC subnet... and I my PCs can browse it normally (Samba 1.9.17p2). However, when I set security=server and password server=host2 on Host 1, I find that I can login on the PCs using the user's password on either Host1 or Host2. (no encryption) if I type the user's password for Host 2, a level 2 log shows negprot passwd accepted and logs me in - my expected behavior. If I use the users password for Host 1 (which I do not want to do - I want all authentication off Host 2) it still allows me to log onto the domain, even though the logs show negprot password rejected Is this normal behavior? Does security = server mean accept both the local passwd on the domain server AND the password server? Elfredy Cadapan Institute of Computer Science, UP at Los Banos Home page : http://www.uplb.edu.ph/~evc/
> Is this normal behavior? Does security = server mean accept both the > local passwd on the domain server AND the password server?Samba goes back to security = user if negotiation with the server fails. Handy, I suppose, if your password server goes down and you'd like to be able to access your shares. In other news, I'm still having a problem connecting to Samba 1.9.17(p2 or p3) using security = server from Win 95 and NT clients. The password server is NT 3.51. This ONLY happens to users who have restricted client access to the NT password server. I've tried listing the client, the Samba server, the NT server, and my mother's maiden NetBIOS name in the access list to no avail. Is anyone using Samba 1.9.17p2 or greater in a similar situation with success? Giving users unrestricted access solves the problem. Strangely, using smbclient allows me to connect using either the NT password or the unix password. Anyone, anyone, Bueller? - edan -- Edan Idzerda <edan@mtu.edu> System Administrator -- Michigan Technological University, Houghton MI USA