Neil, you're looking at the wrong side of the spectrum. The problem you're seeing is not so much with Samba client version as it is with shares you're trying to access.
Out of the box, Windows 2003 is a lot more secure than its predecessor, Windows 2000. By default, Windows 2003 does not support NTLM-based authentication scheme while Windows 2000 does. As a result, "legacy" clients, Linux included, will fail to authenticate with Windows 2003 systems. Luckily, you can relax some of the security policies of Win2k3 to accommodate these clients. Further more, smbmount has been replaced with "mount -t smbfs" which in turn as been replaced with "mount -t cifs" So I believe you should see better results using: # mount -t smbfs -o username=<username> //<win2k3server/sharename /mountpoint OR better still: # mount -t *cifs* -o username=<username> //<win2k3server/sharename /mountpoint On 7/10/07, Neil Loffhagen <[EMAIL PROTECTED]> wrote:
Hi, We have an old Linux box running Redhat 7.2 that make connections to shares on windows 2000 and 2003 servers. All is working fine here. It is running samba-client-2.2.1a-4. I have been tasked to replace this server with updated hardware etc. I have a Linux box that is now running RHEL 4 with samba-client-3.0.10-1 3 installed. For some reason this new server will only connect to the shares on the windows 2000 server but gives permission errors when trying to connect to the shares on the windows 2003 servers. As we are using the same user credentials I'm wondering what the difference is between Sambas 2 and 3 that will not now connect to windows 2003 boxes whereas it will to windows 2000 boxes? Are there any extra parameters that need to be used? Hoping someone can please shed some light on this? The command we are using is: /usr/bin/smbmount server_name/c$ /mnt/serv_check -o username=userid, password=password, uid=500,gid=500 Many thanks, Neil.
-- Regards, Conrad Lawes PXE Guru
