I have a new Windows 7 Pro (SP1) client that was recently delivered from Lenovo that needs to access Mac OS X 10.2.8 server share folder through SAMBA, but it won't access to it. I also have XP Pro, 2000 Pro, and older Windows 7 Pro (SP1 installed after purchase), and these have no issues accessing my OS X server. My older Windows 7 Pro clients had problems accessing OS X server when I installed Windows update (KB2536276), but after uninstalling it, I had no problems. I believe the ones recently purchased already have this update pre-installed, and there's no way I can undo the installation of this patch. When I browse the network from my Windows 7 Pro, I can see my OS X server, and when I click on it, I can also see shared folder (meaning I can get inside of the server), however, when I click on the folder to connect, it says: \\FILESERVER\Network Share is not accessible. You might not have permission to use this network resource. Contact administrator of this server to find out if you have access permissions. The specified server cannot perform the requested operation. When I try to map Network Drive to connect, it says: The network folder specified is currently mapped using a different user name and password. To connect using a different user name and password, first disconnect any existing mappings to this network share. I've changed the local security policies on Windows 7 to "LM & LTLM Responses" and disabled 128 bit encryption, and also changed the registry value of "LanmanWorkstation - EnablePlainTextPassword" to "0". On Mac OS X server, I checked SAMBA configuration and confirmed that the security is user base and encrypt password is set to "yes." LANMAN auth is also set as "yes" as well. Can anyone tell what I am doing wrong in this? Do I have to upgrade Samba or OS X operating system? Is there any way to work around the issue with Windows 7? (I tried pasting the results from testparm -s of samba.conf file here, but it didn't allow me because of the # of characters.)

1. If problems still exist, one final thing to try is removing the stored credentials for the Samba share. During testing, it's possible that something strange got "stuck" in there. In the Control Panel -> Credential Manager, find and remove the stored credentials for the Samba server 2. To get broader response I would recommend to give information on the Samba version 3. There may be SMB version incomatibility and SMB 1 in W 7 is needed 4. If nothing helps I would use network monitor to catch communication ... Regards Milos

Thanks for responding... I've tried clearing the current credential and add new one, but the result was the same. I think Samba installed on OS X 10.2.8 is 1.0.1 or something like that - I've seen it somewhere when I was checking the setup. I was thinking to upgrade Samba, but I've seen someone saying that upgrading very old versions of Samba to the current version is not very easy that I'd better off buy a new version of OS X, which I really don't feel like doing that - for the fact that there's nothing wrong with other clients (earlier version of Win7, XP, and 2000). I need something to work around this so I can make it work...