Ok, here's the situation, I have several Windows 2000 workstations in my house and I'm trying to get them to access the samba share on my small Linux server.
The linux server is running Mandrake 9.2 and Samba 2.2.4.
I can ping my Windows 2000 workstations from the linux server, but I can't ping the linux server from my Windows 2000 workstations.
I don't have any firewall running on the linux server and "iptables -L" is empty. I can log into the linux server from the Windows 2000 servers using putty and SSH.
I can see the linux server listed in "Network Neighbourhood" from my Windows 2000 workstations.
I have disabled all firewalls on my Windows 2000 workstation (they run ZoneAlarm).
Ok, what happens is when I try to access the linux server from any of the workstations it gives me this message:
Code:
\\server is not accessible.
The account is not authorized to login from this station.
I have "HKLM\System\CurrentControlSet\Services\Lanmanworkstation\EnablePlainTextPassword = 1" on all the work stations and "Send unencrypted password for 3rd party SMB servers" is enabled in the security policies of each workstation.
When I try:
Code:
net use \\server\share /user:gooduser
from the command prompt on one of the workstations I get:
Code:
System error 1240 has occurred.
The account is not authorized to log in from this station.
This is my /etc/samba/smb.conf file:
Code:
#======================= Global Settings =====================================
[global]
# 1. Server Naming Options:
workgroup = HOME
server string = Samba Server %v
# 2. Printing Options:
printcap name = cups
load printers = yes
printing = cups
printer admin = @adm
# 3. Logging Options:
log file = /var/log/samba/log.%m
max log size = 50
# 4. Security and Domain Membership Options:
; hosts allow = 192.168.1. 192.168.2. 127.
hosts allow = 192.168.0.
map to guest = bad user
security = user
; encrypt passwords = yes
; smb passwd file = /etc/samba/smbpasswd
# 5. Browser Control and Networking Options:
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
remote announce = 192.168.0.255
local master = no
# 6. Domain Control Options:
# 7. Name Resolution Options:
wins support = yes
; wins server = w.x.y.z
dns proxy = no
# 8. File Naming Options:
#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = no
writable = yes
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# to allow user 'guest account' to print.
printable = yes
create mode = 0700
[print$]
path = /var/lib/samba/printers
browseable = yes
read only = yes
write list = @adm root
guest ok = yes
[webphotos]
comment = Photos Published on the Web
path = /chroot/httpd/www/photos
valid users = joe sarah
public = yes
writable = yes
Now, if I enable both of these:
Code:
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
and make sure I have the users added with:
Code:
smbpasswd -add gooduser goodpass
And make sure that the windows 2000 workstations are sending encrypted passwords, then I can see the list of shares for the server in "Network Neighbourhood" but only by using the "username@server" format for the user name.
However, I still can't access the share themselves, it gives me:
Code:
Incorrect password or unknown username for:
\\server\share
If I try to connect using the "username@server" user name, and if I just try to use the "username" format, it gives me this:
Code:
\\server\share is not accessible.
The credentials supplied conflict with an existing set of credentials.
If I try to connect directly to \\server\share without accessing it in "Network Neighbourhood" first, I get:
Code:
Incorrect password or unknown username for:
\\server\share
If I try to access it from the command line, I get:
Code:
net use \\server\share /user:joe
The password or user name is invalid for \\server\share.
Type the password for \\server\share:
System error 1326 has occurred.
Logon failure: unknown user name or bad password.
I can't for the life of me figure out why I can't access these file shares from my Windows 2000 workstations. They work perfectly fine from my linux workstations.
Thanks!
