wenn Du eine hinreichend aktuelle Version von Samba nutzt, ist das kein
Problem. Vor allem die letzten Sicherheitslücken in Samba sollten jeden
ja dazu gebracht haben, die aktuellste Version auf seinem Fileserver
einzusetzen.
Back in those days of stone-axes and bear-skins, I'd run into trouble with Windows 95 clients being unable to connect with "secured" NT4 SP4 servers. I fixed it then by setting the servers back to using NTLM.
Today, my problem was that by default Vista only used NTLMv2, and not NTLM or LM authentication. My NAS setup, like many NAS appliances, relies on a firmware-based Linux and Samba for its CIFS (Common Internet File System) file server.
FAQ Samba
Frage 1: Zugriff mit Windows Vista auf Samba-Server der Version 2
Frage 2: Zugriff mit Windows XP auf Samba-Server
Antwort 1
Um sich mit Windows Vista erfolgreich an einem Samba-Fileserver, der Samba 2.x verwendet, zu authentifizieren, müssen folgende Anpassungen vorgenommen werden
rotocols operate essentially the same way; the only difference is the password hash. The actual challenge-response computation is fairly simple. The client requests authentication and the authentication server responds with an 8-byte challenge. The challenge is just a piece of random data. The client encrypts the challenge using the OW
When Vista Home Premium doesn't play well with Samba, these two fixes (registry tweak and supplying workgroup\username instead of just username) seem to help. Also helps not to forget whatpassword you're meant to be using halfway through trying to find a fix -_-
1. Run regedit
2. Find the key KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Lsa
3. Set LmCompatibilityLevel to 1
if doesn't work try \\ip address instead of \\computer name
Wednesday, January 9, 2008
A reader called Ed had the known problem of accessing Leopard files shares form Windows Vista. He took a suggestion for the reverse (Macs accessing Windows), but it worked:
I was unable to authenticate to my file shares on Leopard 10.5.1 from Windows Vista Ultimate. Received eDSAuthFailed messages in my samba log on leopard. I solved these problems by using MACHOSTNAME\accountname instead of using machostname\accountname as was suggested on your website.
If you've seen this work please let us know.