Hey Guys,
I hope this is something very stupidly simple but I have wrecked my brain for the last week trying to figure this out.
To give a little background information:
- I have a desktop with FreeBSD 8.2-current running. I also have a genuine vanilla install of Windows 7 Ultimate. From the FreeBSD desktop I have Samba exporting a number of shares to my Windows machine. I have dictated only valid users (e.g.: authenticated users) can access the shares and this is OK and works. I have left all of the default configuration except for appending my shares to the end of it and restarting Samba for the changes to take affect
I am trying to configure a server now to be an off-site file backup for the office users. This is a Dell 1950 server with two drives in a Gmirror RAID1. I have installed the exact same port with exact same compile options and have also made the necessary changes to Samba to export a share. No matter what I do, the Windows 7 Machine returns an "Access Denied".
The part that is making me wreck my brain is that these are two identical installs and configurations of Samba 3.5.6_2 but I am seeing different logs on client connections and different error messages that should not be happening.
On my FreeBSD desktop I have my "homes" share which is the default share that Samba comes exporting (it does not actually specify a path) along with a number of others. I can run net view \\the_ip on my Windows machine to view all shares that the server is sharing and can see ones that users are not even authenticated to (which is OK that they can see the list).
When I try to execute this on the server Samba instance, I am returned with "Access Denied". When I add the Samba configuration for
I am able to browse the shares (not what I really want but doable I guess). When I add a user the exact same way as I did on my FreeBSD desktop, I am still returned with access denied.
The very odd part I see is that the Samba log on the server calls check_ntlpm_password or something like that whereas the desktop is not. I have successfully added and enabled the user with smbpasswd (I am OK with managing two separate UNIX passwords and Samba passwords)
I have searched for days to see if there has been any patch releases to which this could have affected this latest install but nothing comes up.
Can anyone provide any help?
I hope this is something very stupidly simple but I have wrecked my brain for the last week trying to figure this out.
To give a little background information:
- I have a desktop with FreeBSD 8.2-current running. I also have a genuine vanilla install of Windows 7 Ultimate. From the FreeBSD desktop I have Samba exporting a number of shares to my Windows machine. I have dictated only valid users (e.g.: authenticated users) can access the shares and this is OK and works. I have left all of the default configuration except for appending my shares to the end of it and restarting Samba for the changes to take affect
I am trying to configure a server now to be an off-site file backup for the office users. This is a Dell 1950 server with two drives in a Gmirror RAID1. I have installed the exact same port with exact same compile options and have also made the necessary changes to Samba to export a share. No matter what I do, the Windows 7 Machine returns an "Access Denied".
The part that is making me wreck my brain is that these are two identical installs and configurations of Samba 3.5.6_2 but I am seeing different logs on client connections and different error messages that should not be happening.
On my FreeBSD desktop I have my "homes" share which is the default share that Samba comes exporting (it does not actually specify a path) along with a number of others. I can run net view \\the_ip on my Windows machine to view all shares that the server is sharing and can see ones that users are not even authenticated to (which is OK that they can see the list).
When I try to execute this on the server Samba instance, I am returned with "Access Denied". When I add the Samba configuration for
Code:
map to guest = Bad Password
The very odd part I see is that the Samba log on the server calls check_ntlpm_password or something like that whereas the desktop is not. I have successfully added and enabled the user with smbpasswd (I am OK with managing two separate UNIX passwords and Samba passwords)
I have searched for days to see if there has been any patch releases to which this could have affected this latest install but nothing comes up.
Can anyone provide any help?