[Samba] CIFS hang
I have a Proliant running Red Hat with the 2.6.9-5.ELsmp kernel. We have a Windows 2000 Server who's secondary disc drive is mounted on the Linux box via CIFS using the following command: /sbin/mount.cifs //w2000/docs /var/www/documents -o dir_mode=0777,file_mode=0444,gid=100,uid=501,username=winuser,password=winpass From time to time, for whatever reason, the Windows 2000 Server requires rebooting and if they reboot it without first allowing us to umount the cifs, all requests to the cfis directory will hang. Requests, cd commands, df commands ... all hang ... for as long as three HOURS and they cannot be killed (kill -1, -15, -9) and the smb cannot be restarted. Presumably this is all a result of the calls being hung within the kernel. It has been suggested that we upgrade the kernel to 2.6.9-78.0.13. I'm not generally opposed to upgrades, but I'm hesitant to upgrade to the latest version as a substitute for understanding the root of any problem and engineering a proper fix. Maybe it's the years of Microsoft software, but I believe that upgrading to the latest version has become tech support slang for we have NO IDEA what your problem is, so maybe the latest version will fix it by accident -- but for very sure you'll be so deep in the woods with NEW problems that you'll likely forget about this one entirely. Would anyone have any first hand knowledge of this problem and experience that a later kernel is a solution? Regards Darrel -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Timeout on reconnection?
I have Red Hat Linux RHEL 4 with Samba version 3.0.10-1.4E that mounts a
local Windows 2003 Server disc with the following command:
/sbin/mount.cifs //img1/docs /var/www/documents -o
dir_mode=0777,file_mode=0444,
gid=100,uid=501,username={xxx},password={pp}
The mount succeeds and the mount appears on the output of 'df' and the
documents are accessible and life is as grand as we deserve.
But almost once a day and almost at the same time each day, something
happens and the documents are not accessible and the access programs hang
... and the 'df' command also hangs at the out of the Samba mount
1) img1 is the name of the Windows server and is identified by name in
the /etc/hosts file
2) During the blackout, the Windows Server is up and all the other PC's on
the network CAN STILL access the documents
3) Logs on Linux show nothing of value (that I know what to look for)
4) Event logs on Windows show nothing at that/those times
5) About 15-17 minutes after the hang/blackout occurs, the calls complete
and business returns to normal [sic] until the next time
Stopping restarting Samba doesn't help, probably because the processes
hanging for access don't actually shut down -- but naturally, rebooting
Linux corrects the issue (until the next day)
Is there some sort of timeout/retry settings in play? Any other suggestions?
Darrel
f
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba to Windows 2003 READ errors
I'm running Samba version 3.0.10-1.4E on Red Hat Enterprise Linux ES release 4 (Nahant) Kernel 2.6.9-5.ELsmp on an i686 and I'm trying to connect to a Windows 2003 Server (not a domain controller) as a shared file using EITHER ONE of the following command lines: #smbmount //img1/docs /home/documents -o dmask=777,fmask=0444,gid=100,uid=501,username=documents,password=passd -or- #mount -t cifs //img1/docs /home/documents -o dir_mode=0777,file_mode=0444,gid=100,uid=501,username=documents,password=passd In EITHER case the mount succeeds and I can CD to the directory and all the subdirectories underneath and LS each and every file with no problem. Until I try to read, copy or move the file itself ... in which case I get cp: 1099.tif: read error: Permission denied But I can actually log into the Win2003 system as that user and all my permissions on the directories are fine. So I hit the net and the docs and the forums and everyone says that Windows 2003 has a problem with digital signing. Even Red Hat has an errata on it, saying Local Policies - Security Options - Microsoft network client - digitally sign communications (always) - DISABLED Local Policies - Security Options - Microsoft network client - digitally sign communications (if server agrees) - DISABLED Local Policies - Security Options - Microsoft network server - digitally sign communications (always) - DISABLED Local Policies - Security Options - Microsoft network server - digitally sign communications (if server agrees) - DISABLED Well ... two problems 1) That Eratta talks about CONNECTION failing ... not read errors. -and- 2) There AIN'T NO SUCH entry on my Windows 2003!! Under administrative tools - local security policy -- Security settings -local policies - security I have digitally sign client communications (always) and the same with (when possible) and then two more for server communications. Close enough, right? So I change those reboot No difference So I run regedit search change EVERY similar setting reboot No difference. Since the mount works (either one) and all the directory traversals work just fine ... it will probably comes as no surprise to you that (A) no log file anywhere contains any relevant messages and (B) the DEBUG functions don't work because they MOUNT worked just fine. Oh yeah ... and smbclient works JUST FINE until I find a file and attempt to GET that file ... then I get NT_STATUS_ACCESS_DENIED In triple verification that Windows is functioning, I enabled all sorts of logging and find the following 1) The LOGIN of my documents is logged as success 2) My ACCESS of the directories from Linux is logged as success 3) The READ of the file 1080.TIF - or whatever is logged as SUCCESS by Windows ... yet PERMISSION DENIED by Linux I'm sure it's a Windows problem (it usually is) ... but I'm wondering if anyone has seen THIS PARTICULAR color (error) before? -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.476 / Virus Database: 269.10.19/917 - Release Date: 7/25/2007 1:16 AM -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] I can see share, but it won't let me use my pwd (OSX)
(Apologies if this has already gone to the list. I've been trying to post via the newsgroup and it appears none of my messages went through...so now I'm doing it via the list-serv) I have samba (2.28) running on a linux server (Mandrake 9.2). Neither my win2k machine nor my OSX (panther) machine will see the share via the network browser. In my OSX machine, I CAN connect if I specifically connect to server using the SMB://serverip/ format. It connects, and sees the shares (but only the ones I made...not the default home shares), but refuses my username/pwd. Here's some pertinent parts of my config file: [mp3onserver] comment = mp3s printable = no valid users = mp3,homerj create mode = 0765 writeable = yes path = /home/mp3/ [testshare] qeirw liar = mp3, homerj, @mp3, @homerj path = /home/mp3/ Via webin, I've told Samba to use the Unix usernames and passwords. It all appears to be set up correctly via webmin (the system's users show up as samba users). That all led to a connection, but would get invalid usr/pwd error. So, I made some more adjustments to Samba...namely putting in a default directory. Now I get a different error: the finder cannot complete the operation because some data in smb could not be read or written. (Error code -36). Google isn't turning anything up specific to that other than some mention of rebooting the router a few times (which I tried, to no avail). Any thoughts? -Darrel -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] What should my smbpasswd file look like?
I can not connect to my linux box from my Mac. I get a 'Could not connect to the server because the name or password is not correct' error. I'm not sure where to check to even see what username/pwd samba is using. If I open up my smbpasswd file, it looks like this: drrl:501:xxx:x:[UD]:LCT-402FFFE4: Is there anyway/format that I can add a usr/pwd to this file in plain-text so I can test it? I'm stumped as to how to tell which pwds samba is using for log-ins. -Darrel -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] What should my smbpasswd file look like?
| drrl:501:xxx:\
| x:[UD]:LCT-402FFFE4:
This is a disabled account ('D') with no password ('...').
Ah! Well, that explains my problems. Any idea why they're all
disabled? How does one enable it?
Run these commands as root
~ $ smbpasswd drrl
~ Password:
~ $ smbpasswd -e drrl
I'll try that...does that set the password for Samba?
-Darrel
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
