Re: [SAMBA] Best practice in small office
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Russel, While I can't really say I'm the voice of experience, I've got a 20-computer, 15-user network with samba A few points that I used, and hopefully someone else will set us both straight. Plus we're using Samba 3.x, so YMMV. 1) PST Files. When setting up each new user's Outlook, I move the PST file into Application Data. It's copied over with the profile on login, and back to the samba server on logout. While it's a load on the network during logins, at least Outlook isn't manipulating large PST files over the network all day. 2) My Documents. For each computer (We're using W2K) I just did the following: Join domain. Login as user for first time. W2K auto-created a roaming profile on \\server\username\profile Make \\server\username\MyDocuments Re-map My Docs to the folder on the server Setup outlook, etc. This way other users could access My Documents without digging through the profiles. Plus, keeping them on the server proper meant that if someone forgot to log off for the evening, at least their documents would be backed up and current. As for laptops, still looking for a good solution there. The one laptop I have setup (out of three) uses roaming profiles and offline files for the user's home directory. This is rather kludgy, though, but I don't really know of any way to have someone log onto the domain with a local profile. (Plus she uses regular workstations, so getting info synced between the server and the laptop would be tricky.) [EMAIL PROTECTED] wrote: 8. Best practice in small office (Russell Horn) Hi folks, I've been reading the definitive guide to samba3 and Samba3 by example as well as scouring on line for advice. Sometimes however I find different suggested solutions to the same problem, so perhaps the list can give me some help with current strategies for these issues. We are a small office and are currently going through an IT refurb. Previously we've had a mix of laptops and desktops running Win2k or WinXP with roaming profiles on samba 2.2.3 This has worked pretty well, people tend not to change computer but thee roaming profile has been of help in a couple of hard disk crashes. Our new setup is all XP and mainly desktops - about 15 of them with just three laptop users. My thought is to stick with roaming profiles and configure the desktops not to save the profile data - that should let users swap machines if one dies and at the same tme not leave huge chunks of other users' data on the hard disk. Is that a reasonable strategy? Does it make sense to map My Documents to the user's home folder or is there a benefit to bringing their entire profile over the network at the start of the session then copying it back when they log off? Will I see any great benefit from upgrading to Samba3 or should I stick with what works? We have a couple of laptops that I'd like users to be able to check out if they do need to work outside the office. Ideally I'd like them to be able to ge their data onto the laptop and remove it when they finish using it after a few days. Is there a sensible way to do this with samba or is this really a task for a VPN connection? Final issue is Outlook. If I remember correctly, it doesn't like PST files living on a Samba share. What's the best way for me to deal with these big PST files. As I mentioned we're a relatively small office. We're also running gigabit to the desktops and laptops, so I'm not too concerned about shifting pretty large quantities of data if that makes a difference to how we should proceed. Any thoughts or advice would be really appreciated. Russell. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iQEVAwUBQzqd2PJjqPbXBLJ6AQjKLQf/eTi8iZKw7CjoTZC99hrt05SfnbpdMdNo 6fwndfJ8oM9U3YYZDP2IcldG7XTZhlL3PLnVe/0JlzlTMnoKS38vDf1Wtm4+dHO2 WBJgahvR9dcWstaEADEeZkwfxN7OozmLnd9eh0nGcH9hJKpkudaHRIAcBRlw6UVS fuZpqPxAkJid5BpdTeQZRVdTm6WEyGJgftjTZOExasYTaDyc5JYFk32t6NtfGeWq kB5jv2n5Y0990SO/tEUp1UNZkSh1JUoVyS4mhC7V+IGu4/q4jjD74NDzXHFJX2FE 7BXbklrUoY6/tnjozQyyrUvwy+eKSl9HODbKFqpBTqWZ9Ng5Rd5bjw== =cTQT -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: BUG: Standard Time v. DST calculated wrong by Samba Server
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On a related note, on one system we use a command line utility to do an incremental backup of certain files on the Samba server. It checks the timestamp on two files, and copies the newer over the older one. Every year, right after DST change (Both Spring and Fall,) the utility insists that every file has changed. While this normally doesn't cause problems, it is a hassle to wait for nearly a GB to transfer over the network. (Basically making a backup of a few critical files to the CEO's laptop, and Windows Briefcase kept having a corrupt DB.) I'm presuming the two bugs are related somehow. 3. BUG: Standard Time v. DST calculated wrong by Samba Server (Linda W) Subject: [Samba] BUG: Standard Time v. DST calculated wrong by Samba Server From: Linda W [EMAIL PROTECTED] Date: Sun, 31 Jul 2005 13:21:04 -0700 To: samba@lists.samba.org To: samba@lists.samba.org Content-Transfer-Encoding: 7bit Precedence: list Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=UTF-8; format=flowed MIME-Version: 1.0 Message: 3 FYI, the same bug apears if one mounts the file system using cifs: -rwxr- 1 user 2532415 2000-04-02 00:34:50.0 -0800 fo1.mp3* -rwxr- 1 user 3876671 2000-03-12 21:33:20.0 -0800 fo2.mp3* Linda W wrote: Summary: There appears to be a bug in the time range Samba is using on dates where time is scheduled to Spring Forward from Standard to Daylight Savings time. Might want to review the code for Falling back, as well... Details: This started out with my thinking it was an rsync problem, but it appears to be something to do with how samba is exporting the file time (!? or Windows is reading 1 file). I have 2 files in a windows directory, /tmp/files: fo1.mp3, fo2.mp3. I rsynced them to a directory on a linux box running SuSE 9.1 with samba-3.0.9-2.6. On the linux/samba server, I see times: target ll --full-time total 6264 -rwxr- 1 user 2532415 2000-04-02 01:34:50.0 -0800 fo1.mp3* -rwxr- 1 user 3876671 2000-03-12 22:33:20.0 -0800 fo2.mp3* (which are the same times as on the Windows source dir:) /tmp/files ll --full-time total 6272 -rw-r- 1 user 2532415 2000-04-02 01:34:50.0 -0800 fo1.mp3 -rw-r- 1 user 3876671 2000-03-12 21:33:20.0 -0800 fo2.mp3 But, the Win XP's view of the remote files differs on 1 file: /tmp/files ll --full-time /k/target/ total 7168 -rw-r- 1 user 2532415 2000-04-02 00:34:50.0 -0800 fo1.mp3 ---^ -rw-r- 1 user 3876671 2000-03-12 21:33:20.0 -0800 fo2.mp3 This is 1 file out of 387 that has this problem. The same problem occurs when I use smbmount on the server to mount the exported samba share (but mounted by root): -rwxr-xr-x 1 root 2532415 2000-04-02 00:34:50.0 -0800 fo1.mp3 ---^ -rwxr-xr-x 1 root 3876671 2000-03-12 21:33:20.0 -0800 fo2.mp3 - Note -- same time as seen on the Windows box, but this time it is seen through the linux based smbmounted view. It seems to be a bug related to the the time changing on that date from Standard to Daylight Saving Time. To be more particular, on that date, times in the range =2:00AM and 3:00AM would not exist. It would appear the code for time checking is using the wrong time range on that date. Linda - -- Chad Vincent RhiannonWeb [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Possible new addition to Samba, looking for advice / help.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All, Not 100% sure if this is the place to pose this, but I had an idea that wouldn't add too much bloat to Samba, but would help smaller-network admins like myself monitor what's going on on their network a bit closer. I keep top running in a ssh window on my box to keep an eye on the server. However, I'd like to have Samba information instead of ps -A... So here's the project: Alter smbstatus -b to list number of files (or shares?) open. Create a modified version of top (smbtop?) to use the output from smbstatus -b instead of ps -A. Modifying top shouldn't be too hard, even with my limited C knowledge I could probably handle that. smbstatus might be a little more difficult. Would enough other people use this, or should I bother? I will forewarn everyone that this will be the first non-hello, world coding (HTML doesn't count) that I've done since 1989. - -- Chad Vincent DermaMed Coatings Co. [EMAIL PROTECTED] Ph.330-633-8216 Fx.330-633-2461 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCsEi7zUYktMxfxasRAm3wAJ9Hf26iKkER6JlGbPXRe5j+6LYfxQCgq+dP h/NhQ9RBjhx3QQbJerPt+I4= =Bs7W -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Odd Disconnect problem, again. (Recv failure for 4?)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Setup: Samba 3.0.7-1 on Debian (3.0.9 broke Excel Shared Files, not upgrading unless that bug is squashed, resurrected, re-squashed, burned, etc.) Win2k Pro box running OnStream Echo backup software. Problem: Connection to the share disconnects during backup. Software repeatedly retries last file, fills up tape with partial copies of file, smbstatus shows said file as being open just fine. Software continues backing up files, despite smbstatus showing no other files open. File is not always the same. Samba log errors from last backup: [2005/05/22 01:00:20, 1] smbd/service.c:make_connection_snum(648) server (192.168.123.20) connect to service backup initially as user root (uid=0, gid=0) (pid 1330) [2005/05/22 01:02:40, 0] smbd/nttrans.c:call_nt_transact_ioctl(2269) call_nt_transact_ioctl(0x9009c): Currently not implemented. [2005/05/22 02:23:08, 0] lib/util_sock.c:read_socket_data(384) read_socket_data: recv failure for 4. Error = Connection reset by peer [2005/05/22 02:23:08, 1] smbd/service.c:close_cnum(837) server (192.168.123.20) closed connection to service backup [2005/05/22 02:23:30, 1] smbd/service.c:make_connection_snum(648) server (192.168.123.20) connect to service backup initially as user root (uid=0, gid=0) (pid 1438) [2005/05/22 02:23:30, 0] smbd/nttrans.c:call_nt_transact_ioctl(2269) call_nt_transact_ioctl(0x940cf): Currently not implemented. [2005/05/22 02:39:52, 1] smbd/service.c:make_connection_snum(648) server (192.168.123.20) connect to service netlogon initially as user root (uid=0, gid=0) (pid 1438) [2005/05/22 02:39:52, 1] modules/vfs_extd_audit.c:audit_opendir(141) vfs_extd_audit: opendir . [2005/05/22 02:50:14, 1] smbd/service.c:close_cnum(837) server (192.168.123.20) closed connection to service netlogon And log from backup software: *** Starting Backup Backup Pre-Erase Compressed -- 5/22/2005 - 1:02:58 AM *** F:\Dir\DermaMed Products\Products 2004\Filename-#8-30-04.xls** The network path was not found. F:\Dir\DermaMed Products\Products 2004\Filename-# 4-30-03.xls ** The network path was not found. F:\Dir\DermaMed Products\Products 2004\Filename-#4-30-03.xls** The network path was not found. F:\Dir\DermaMed Products\Products 2004\Filename-#1-23-04.xls** The network path was not found. F:\Dir\DermaMed Products\Products 2004\Filename-#1-23-04.xls** The network path was not found. F:\Dir\DermaMed Products\Products 2004\Filename-# for coater.xls** The network path was not found. F:\Dir\DermaMed Products\Products 2004\Filename-#2-22-04.xls** The network path was not found. F:\Dir\DermaMed Products\Products 2004\Filename-#10-10-03.xls ** The network path was not found. F:\Dir\DermaMed Products\Products 2004\Filename-#7-08-04.xls** The network path was not found. F:\Dir\DermaMed Products\Products 2004\Filename-# 4-01-03 OLD COPY.xls ** The network path was not found. F:\Dir\DermaMed Products\Products 2004\Filename-#6-2-03.xls ** The network path was not found. F:\Dir\DermaMed Products\Products 2004\Filename-#12-11-03.xls ** The network path was not found. F:\Dir\DermaMed Products\Products 2004\Filename-#10-30-04.xls ** The network path was not found. F:\Dir\DermaMed Products\Products 2004\Filename-#5-1-03.xls ** The network path was not found. !!!Repeat this last error many, many times!!! F:\Dir\DermaMed Products\Products 2004\Filename-#5-1-03.xls ** Access is denied. !!!Repeat this error even more times!!! T:\echo\F$\Dir\DermaMed Products\Products 2004\Filename-#5-1-03.xls\656c10ba.xls ** There is not enough space on the disk. ## Prompting for media spanning ## ## Ejecting Media ## T:\echo\F$\Dir\DermaMed Products\Products 2004\Filename-#5-1-03.xls\656c10ba.xls ** The handle is invalid. T:\echo\F$\Dir\DermaMed Products\Products 2004\Filename-#5-1-03.xls\656c10ba.xls ** The handle is invalid. T:\echo\F$\Dir\DermaMed Products\Products 2004\Filename-#5-1-03.xls\656c10ba.xls ** The handle is invalid. F:\Dir\DermaMed Products\Products 2004\Filename-#5-1-03.xls ** The handle is invalid. Backup C:D: Pre-Erase Compressed** Operation Canceled *** Operation complete. Backup C:D: Pre-Erase Compressed -- 5/23/2005 - 8:41:39 AM *** - -- Chad Vincent RhiannonWeb [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCkfQRkDjwkvrkkmURAqMpAJ0dT/Y7enIG0rKLMzLSNbMQahCr1wCfRHFW /+MTiZVXKSd4KXRSHga5/9g= =1el5 -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Excel File Open Issue - Possibly Samba Related
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Would love to, but this is a production environment and I don't have a test server up yet. I just downgraded to 3.0.7. If I get a testing server up before 3.0.12 comes up, I'll try it. Jeremy Allison wrote: On Wed, Mar 09, 2005 at 09:54:29AM -0500, klubarpop wrote: We were having the same problem with Excel ... Different version of Samba. Applying a fix detailed in MS KB # 324491 solved the problem for us. (We use Office 11 although the fix talks about Office 10 -- Office 11 = Office 2003 Office 10 = Office XP for those who don't keep up with such things.) Do a search for QFE_Saskatchewan for the registry key. Anyone have any idea why the key is named Saskatchewan? Hope this helps Ken Lubar -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chad Vincent Sent: Wednesday, March 09, 2005 9:39 AM To: samba@lists.samba.org Subject: Re: [Samba] Excel File Open Issue - Possibly Samba Related -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Okay Problem did not go away. I un-shared (multi-user) the file to clear out the changelog, and the problem did go away. At this point I'm going to assume a malformed entry in the changelog or a changelog that was just too darn big. (Before, size was 25MB, after removing sharing it was 2.5MB and opened in 1/8th the time.) HOWEVER, upon upgrading to 3.0.11 as suggested, now ALL shared (multi-user) Excel files are, at apparent random, displaying a message This file has been locked. To save changes you must save under a different file name and merge(blah, blah) We never had this problem under 3.0.7. I have log level=1 and nothing is showing up in the logs. Ok - I think I may have fixed this in the current SVN code in SAMBA_3_0 without needing the strange registry keys. I'm looking for people willing to test this before the 3.0.12 release. Please give ths code a test and give me some feedback. I can't reproduce the problem here with Office 2003 and the latest SAMBA_3_0 SVN code. Jeremy. - -- Chad Vincent RhiannonWeb [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCMaT5kDjwkvrkkmURAqHmAKCjNw0BGXXJuUCoO95YHPtKzfsPTgCePtki pl7bz8l689Dz1T10VdAPz98= =Bwbl -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Excel File Open Issue - Possibly Samba Related
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Okay Problem did not go away. I un-shared (multi-user) the file to clear out the changelog, and the problem did go away. At this point I'm going to assume a malformed entry in the changelog or a changelog that was just too darn big. (Before, size was 25MB, after removing sharing it was 2.5MB and opened in 1/8th the time.) HOWEVER, upon upgrading to 3.0.11 as suggested, now ALL shared (multi-user) Excel files are, at apparent random, displaying a message This file has been locked. To save changes you must save under a different file name and merge(blah, blah) We never had this problem under 3.0.7. I have log level=1 and nothing is showing up in the logs. (Just for example, user A opens purchasing.xls fine, but B gets the error. B can open schedule.xls fine, but A gets the error. C can open both. Have not seen this behavior on non-shared files.) These files HAVE to be shared, and I have even tried with veto oplocks=/*.xls/ with no apparent change. Jeremy Allison wrote: On Tue, Feb 22, 2005 at 02:45:43PM -0500, Chad Vincent wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Having a workstation with an odd glitch, and I'm hoping someone can help. We have a 35MB shared Excel file with our purchasing history in it. (I know, I've been trying to talk them into a database of some sort, but they'll have none of that...) One workstation in the entire plant is having issues opening it. The file will load, it will change status to [Shared] in the titlebar, then stop. Bad Workstation: Windows 2000 Athlon 1600+ 256MB DDR 333 Soyo Dragon KT333 Ultra Black Realtek 8139 on-board (Also tried PCI 8139) Server: Debian Stable 2x Opteron 240 Broadcom tg3 1000Mb NIC Samba 3.0.7-1 as a PDC You need to upgrade. There have been several fixes in this area to do with the rather strange way Excel uses SMB. None of them should cause the client to disconnect, although a deferred open problem could conceivably do this. It's just that many people are reporting much better results with Excel and 3.0.11. Jeremy. - -- Chad Vincent RhiannonWeb [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCLwp2kDjwkvrkkmURArWdAJ4rEXG9n7LfPJ0SxX/BqIklEQkBRACfQj+5 FK70tlngjkpav/by6+B+LCI= =7xJk -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Excel File Open Issue - Possibly Samba Related
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 We're still on Office 9 (2000), and the article lists Share Workbook as a workaround, and those are the files we're having issues with. As far as why it's named Saskatchewan, that's listed as a time zone, and it's dealing with timestamps... Perhaps tricking the timestamp check? klubarpop wrote: We were having the same problem with Excel ... Different version of Samba. Applying a fix detailed in MS KB # 324491 solved the problem for us. (We use Office 11 although the fix talks about Office 10 -- Office 11 = Office 2003 Office 10 = Office XP for those who don't keep up with such things.) Do a search for QFE_Saskatchewan for the registry key. Anyone have any idea why the key is named Saskatchewan? Hope this helps Ken Lubar -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chad Vincent Sent: Wednesday, March 09, 2005 9:39 AM To: samba@lists.samba.org Subject: Re: [Samba] Excel File Open Issue - Possibly Samba Related Okay Problem did not go away. I un-shared (multi-user) the file to clear out the changelog, and the problem did go away. At this point I'm going to assume a malformed entry in the changelog or a changelog that was just too darn big. (Before, size was 25MB, after removing sharing it was 2.5MB and opened in 1/8th the time.) HOWEVER, upon upgrading to 3.0.11 as suggested, now ALL shared (multi-user) Excel files are, at apparent random, displaying a message This file has been locked. To save changes you must save under a different file name and merge(blah, blah) We never had this problem under 3.0.7. I have log level=1 and nothing is showing up in the logs. (Just for example, user A opens purchasing.xls fine, but B gets the error. B can open schedule.xls fine, but A gets the error. C can open both. Have not seen this behavior on non-shared files.) These files HAVE to be shared, and I have even tried with veto oplocks=/*.xls/ with no apparent change. Jeremy Allison wrote: On Tue, Feb 22, 2005 at 02:45:43PM -0500, Chad Vincent wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Having a workstation with an odd glitch, and I'm hoping someone can help. We have a 35MB shared Excel file with our purchasing history in it. (I know, I've been trying to talk them into a database of some sort, but they'll have none of that...) One workstation in the entire plant is having issues opening it. The file will load, it will change status to [Shared] in the titlebar, then stop. Bad Workstation: Windows 2000 Athlon 1600+ 256MB DDR 333 Soyo Dragon KT333 Ultra Black Realtek 8139 on-board (Also tried PCI 8139) Server: Debian Stable 2x Opteron 240 Broadcom tg3 1000Mb NIC Samba 3.0.7-1 as a PDC You need to upgrade. There have been several fixes in this area to do with the rather strange way Excel uses SMB. None of them should cause the client to disconnect, although a deferred open problem could conceivably do this. It's just that many people are reporting much better results with Excel and 3.0.11. Jeremy. -- Chad Vincent RhiannonWeb [EMAIL PROTECTED] - -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba - -- Chad Vincent RhiannonWeb [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCLxELkDjwkvrkkmURArWgAKCjyFf/19mRdsIjJWmu0mGApHbgpgCgj2Zg BGbhAntuWNavKnGz4YY4tDY= =NM1m -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Excel File Open Issue - Possibly Samba Related
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Agh Don't mean to spam the mailing list, but found these that might be causes of the problem: KB 230556 / 130494 Perhaps Samba isn't changing the lock type fast enough? But with oplocks disabled, that shouldn't matter, I would think. klubarpop wrote: We were having the same problem with Excel ... Different version of Samba. Applying a fix detailed in MS KB # 324491 solved the problem for us. (We use Office 11 although the fix talks about Office 10 -- Office 11 = Office 2003 Office 10 = Office XP for those who don't keep up with such things.) Do a search for QFE_Saskatchewan for the registry key. Anyone have any idea why the key is named Saskatchewan? Hope this helps Ken Lubar -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chad Vincent Sent: Wednesday, March 09, 2005 9:39 AM To: samba@lists.samba.org Subject: Re: [Samba] Excel File Open Issue - Possibly Samba Related Okay Problem did not go away. I un-shared (multi-user) the file to clear out the changelog, and the problem did go away. At this point I'm going to assume a malformed entry in the changelog or a changelog that was just too darn big. (Before, size was 25MB, after removing sharing it was 2.5MB and opened in 1/8th the time.) HOWEVER, upon upgrading to 3.0.11 as suggested, now ALL shared (multi-user) Excel files are, at apparent random, displaying a message This file has been locked. To save changes you must save under a different file name and merge(blah, blah) We never had this problem under 3.0.7. I have log level=1 and nothing is showing up in the logs. (Just for example, user A opens purchasing.xls fine, but B gets the error. B can open schedule.xls fine, but A gets the error. C can open both. Have not seen this behavior on non-shared files.) These files HAVE to be shared, and I have even tried with veto oplocks=/*.xls/ with no apparent change. Jeremy Allison wrote: On Tue, Feb 22, 2005 at 02:45:43PM -0500, Chad Vincent wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Having a workstation with an odd glitch, and I'm hoping someone can help. We have a 35MB shared Excel file with our purchasing history in it. (I know, I've been trying to talk them into a database of some sort, but they'll have none of that...) One workstation in the entire plant is having issues opening it. The file will load, it will change status to [Shared] in the titlebar, then stop. Bad Workstation: Windows 2000 Athlon 1600+ 256MB DDR 333 Soyo Dragon KT333 Ultra Black Realtek 8139 on-board (Also tried PCI 8139) Server: Debian Stable 2x Opteron 240 Broadcom tg3 1000Mb NIC Samba 3.0.7-1 as a PDC You need to upgrade. There have been several fixes in this area to do with the rather strange way Excel uses SMB. None of them should cause the client to disconnect, although a deferred open problem could conceivably do this. It's just that many people are reporting much better results with Excel and 3.0.11. Jeremy. -- Chad Vincent RhiannonWeb [EMAIL PROTECTED] - -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba - -- Chad Vincent RhiannonWeb [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCLxMKkDjwkvrkkmURAnCwAJwJBkbPQ5+oEe2CqzMrQqceCOMUHACfSS3j GF+ib9IK5wXLqn4fW5Yn4n4= =8p16 -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Excel File Open Issue - Possibly Samba Related
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jerry, Thanks much. In the meantime, do we know what version this bug was introduced? If so, is there an archive of older .deb versions so I can downgrade back to 3.0.7 - 3.0.10? Gerald (Jerry) Carter wrote: Chad Vincent wrote: | Okay Problem did not go away. I un-shared (multi-user) the file to | clear out the changelog, and the problem did go away. At this point I'm | going to assume a malformed entry in the changelog or a changelog that | was just too darn big. (Before, size was 25MB, after removing sharing | it was 2.5MB and opened in 1/8th the time.) | | HOWEVER, upon upgrading to 3.0.11 as suggested, now ALL shared | (multi-user) Excel files are, at apparent random, displaying a message | This file has been locked. To save changes you must save under a | different file name and merge(blah, blah) We never had this | problem under 3.0.7. I have log level=1 and nothing is showing up in | the logs. Known issue I'm afraid (or at least a reported one). https://bugzilla.samba.org/bug/2382 We're working on it. cheers, jerry - -- Chad Vincent RhiannonWeb [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCLyXukDjwkvrkkmURAtAEAJ9fcPznLjs50kn+r4J8n7OPEfqbKACfbVT0 HTOfw9+ixrmVzTI8cdEfim4= =Mf8B -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: WINS not updating after swapping network connections
I had the exact same problem when I changed from dynamic IP to Static on the server itself. It added the new IP address AFTER the old one in wins.dat, and only reported the first back to the clients. Try shutting down Samba, deleting wins.dat (May be in either /var/cache/samba/ or /var/lib/samba/ ) then starting Samba up again. Your WINS file will be rebuilt as the clients re-register their addresses. How to actually get it to change on the fly, however, is anybody's guess, as it will re-write the file as-is if you delete / change it while SAMBA is running. It was suggested that it may be a corrupted file, so just deleting it and letting it be re-built may fix the problem, too. At 12:01 PM 4/15/2004 +, you wrote: From: Michael Keightley [EMAIL PROTECTED] Precedence: list Subject: [Samba] WINS not updating after swapping network connections Date: Thu, 15 Apr 2004 12:54:38 +0100 To: [EMAIL PROTECTED] Reply-To: Michael Keightley [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Message: 18 Our domain controller is running Samba 2.2.8a on Solaris 8. We have XP laptops. We swap between a builtin network card, docking port and wireless card. All of these have separate IP addresses. If I say, boot up with the wireless card, then remove it and use the builtin network card, the IP address in wins.dat on the server doesn't change. It still has the IP address of the wireless card. It means you can't browse this machine. Our backup software (BackupPC) also stops working. Should wins.dat not get updated when a machine changes IP address? Below is part of our smb.conf file: [global] workgroup = SAMBA hosts allow = 194.80.198. 192.168.191. 192.168.198. 127. interfaces = 194.80.198.61/255.255.255.128 192.168.191.61/255.255.255.0 192.168.193.61/255.255.255.0 log file = /var/log/samba/%m.log load printers = yes printing = cups printcap name = cups case sensitive = no preserve case = yes short preserve case = yes domain master = yes domain logons = yes local master = yes preferred master = yes name resolve order = wins lmhosts host bcast wins support = yes os level = 65 encrypt passwords = yes nis homedir = true security = user guest account = nobody homedir map = auto_home logon script = netlogon.bat logon path = \\%N\profile\%a\%U logon drive = q: socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=16384 SO_RCVBUF=16384 Michael Chad Vincent Owner RhiannonWEB Phone: 330-283-4681 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] WINS Caching Error?
Here is the problem: Installed Debian Woody Installed Samba 3.02a-1 Setup Samba Setup Network to use Static IP address (Being a PDC / WINS Server and all...) Now I'm getting the following: ifconfig eth0 eth0: Link encap:Ethernet HWaddr: [MAC address here] inet addr:192.168.x.19 Bcast:192.168.x.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 .etc smbclient -L [SERVER] Error connecting to 192.168.x.195 Connection to [SERVER] failed ping [SERVER] PING [SERVER].localdomain (192.168.x.19): 56 data bytes 64 bytes from 192.168.x.19: icmp_seq=0 ttl=64 time=0.0ms **SNIP** cat /etc/hosts **SNIP** 192.168.x.19 [server].localdomain [server] Normally, I wouldn't be too concerned, but apparently this has propagated into WINS, and so we have one computer (so far, we're transitioning to this new server in stages) that cannot connect to the server until the NetBIOS has propagated to it, and I don't want to have to set up a custom LMHOSTS for every client. That's what WINS is for. Also, if it makes any difference, 192.168.x.195 was the last DHCP address on that network card before I changed it to Static IP. Appropriate sections of smb.conf, ask if you need more: [global] interfaces=eth0 192.168.x.19 netbios name=[SERVER] workgroup=DM.NET security=USER socket options=TCP_NODELAY dns proxy=no os level=65 domain master=yes prefered master=yes wins support=yes local master=yes domain logons=yes name resolve order=wins lmhosts bcast host Chad Vincent Owner RhiannonWEB Phone: 330-283-4681 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] WINS Caching Error?
Bringing this back to the ML incase someone else has some insight Removed wins.dat from /var/lib/samba, restarted samba, still no luck. smbclient is still looking at the old address. I just checked, and it rebuilt wins.dat exactly as it was before. A backup copy somewhere, perhaps? [DOMAIN]#1c 1081448833 192.168.x.195 192.168.x.19 e4R [SERVER]#00 1081448833 192.168.x.195 192.168.x.19 66R [SERVER]#03 1081448833 192.168.x.195 192.168.x.19 66R [SERVER]#20 1081448833 192.168.x.195 192.168.x.19 66R *** THEN AN EPIPHANY OCCURS *** Stopped Samba, THEN deleted the wins.dat, then re-started samba. All is right with the world. For now, at least. It must read the cached file on start-up, then re-write it on shutdown. The big question is, though... why aren't the old addresses getting un-registered when new ones are registered with WINS? Or if that's standard, why do the old addresses take precedent over the new ones? At 12:57 PM 4/5/2004 -0500, you wrote: ls /var/cache/samba/ -rw-r--r--1 root root 962 Apr 05 13:27 browse.dat drwxr-xr-x 2 root root 104 Mar 22 09:05 printing No wins.dat. find / wins.dat find: wins.dat: No such file or directory Hmmm. ls /var/cache/samba/ brlock.tdb messages.tdbntforms.tdb share_info.tdb browse.dat namelist.debug ntprinters.tdb smbd.pid connections.tdb nmbd.pidprinting.tdbunexpected.tdb locking.tdb ntdrivers.tdb sessionid.tdb wins.dat I'm still running 2.2.8a, I wonder if 3.x puts its WINS data somewhere else. I just did a quick (and I mean quick) bit of googling, I searched for samba 3 wins.dat and the first entry that comes up is from a guy who is having a similar issue to you, and is using Debian. He shows wins.dat as living in /var/lib/samba instead of /var/cache/samba. You may want to read it: http://lists.samba.org/archive/samba/2003-December/076382.html HTH, --J(K) Chad Vincent Owner RhiannonWEB Phone: 330-283-4681 To: 'Chad Vincent' [EMAIL PROTECTED] Subject: RE: [Samba] WINS Caching Error? It's possible you have a corrupted wins.dat. On my system it's in /var/cache/samba/ and I've sucessfully changed it without trouble (I had an issue similar to yours). Just make your change to the wins.dat and restart Samba. (Make sure you make a backup first -- it worked for me, but it might not for you.) HTH, --J(K) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] a.org] On Behalf Of Chad Vincent Sent: Monday, April 05, 2004 11:26 AM To: [EMAIL PROTECTED] Subject: [Samba] WINS Caching Error? Here is the problem: Installed Debian Woody Installed Samba 3.02a-1 Setup Samba Setup Network to use Static IP address (Being a PDC / WINS Server and all...) Now I'm getting the following: ifconfig eth0 eth0: Link encap:Ethernet HWaddr: [MAC address here] inet addr:192.168.x.19 Bcast:192.168.x.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 .etc smbclient -L [SERVER] Error connecting to 192.168.x.195 Connection to [SERVER] failed ping [SERVER] PING [SERVER].localdomain (192.168.x.19): 56 data bytes 64 bytes from 192.168.x.19: icmp_seq=0 ttl=64 time=0.0ms **SNIP** cat /etc/hosts **SNIP** 192.168.x.19 [server].localdomain [server] Normally, I wouldn't be too concerned, but apparently this has propagated into WINS, and so we have one computer (so far, we're transitioning to this new server in stages) that cannot connect to the server until the NetBIOS has propagated to it, and I don't want to have to set up a custom LMHOSTS for every client. That's what WINS is for. Also, if it makes any difference, 192.168.x.195 was the last DHCP address on that network card before I changed it to Static IP. Appropriate sections of smb.conf, ask if you need more: [global] interfaces=eth0 192.168.x.19 netbios name=[SERVER] workgroup=DM.NET security=USER socket options=TCP_NODELAY dns proxy=no os level=65 domain master=yes prefered master=yes wins support=yes local master=yes domain logons=yes name resolve order=wins lmhosts bcast host Chad Vincent Owner RhiannonWEB Phone: 330-283-4681 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Connection reset by peer / The network is busy
I have seen posts concerning this in the archives, but with no real solution. I've seen it first-hand twice now. I am running Debian Woody, with us3.samba.org's Samba 3 sources added to my apt-sources. 3.0.2a was the first version of Samba installed. The SMB.conf is used off of a previous Test system, then updated to reflect changes in the network as it stands now. The server is fairly bare, with just minimal packages installed. It's only use is for file-sharing and one Access database sharing. (Soon it will also host a MySQL database, hence the horsepower.) It is on a Tyan 2880S motherboard with dual Broadcom GbE ethernet cards, TG3 module. Kernel is 2.4.25-K7-SMP custom, Samba is 3.0.2a I went to copy files over from our old server to the new one via the network... System 1 (pdr, Win98SE) Select files, copy, select new directory on new server, paste. Files copy, re-map network drive, everything's happy. System 2 (My computer, Win2k Pro) Same as above. Slower because my laptop is a piece of garbage, but it's always been that way, even copying local to server. System 3 (Server, Win2k Pro) Same as above for programs share, used for network copies of various programs we use. (ACT, MS Office, etc.) 5.7GB worth of information. Was doubling as a test to make sure the two systems can see each other, as the old server will be used as a jury-rigged nightly-updated mirror in case of panic. System 4 (lab, Win98SE, Via Rhine II NIC) Same as above. Gets about 1/2 way through copying files (800MB of Excel files), and the following occurs: Client beeps: Cannot create or replace [filename]: The network is busy. Server log: [2004/03/26 15:06:23, 0] lib/util_sock.c:read_socket_data(342) read_socket_data: recv failure for 4. Error = Connection reset by peer At which point, the client needs to be completely rebooted before it will re-connect to the server. Added the new server to the WINS list of the client, and started using a domain logon. Error persisted. On this last try, I decided to monitor the progress with smbstatus while the files copied over. First time I ran smbstatus, the client beeped, and the error occured immediately, much sooner in the process than normal. I've tried everything I can think of. We don't have problems of this nature with that system connecting to the old server (Win2k Pro. We were a tiny company then.) I would just break it up into smaller sections, but I would rather fix the problem than workaround if possible. Right now I'm moving over less-used information. However, we are stretching the limits of the old server rapidly, and need to finish the transition soon. The last time I noticed this problem was using Samba 2.999 on Xandros 1.0. Same network, using it as a testbed. Reformatting the system and re-installing Xandros from scratch worked like a charm. Purge / re-install of Samba did not. However, at this point a purge/reinstall of the OS is not an option. Going back to Xandros is also not an option, as it was causing other problems. Also, last time stress-testing Samba by streaming an MP3/OGG playlist would cause this several times a day. I tried the same earlier with no problems from pdr. I'm not ruling out a network problem, but it would be nice to find out more about the specific error so I know where to focus my troubleshooting. ***Begin smb.conf*** [global] workgroup=DM.NET server string=%h server (Samba %v) load printers=no printcap name=cups printing=cups print command=lp -d %p %s; rm %s # invalid users=root log file=/var/log/samba/log.%m max log size= syslog=0 security=USER encrypt passwords=yes socket options=TCP_NODELAY dns proxy=no passwd program=/usr/bin/passwd %u passwd chat=*EntersnewsUNIXspassword:* %nn *RetypesnewsUNIXspassword:* %nn . obey pam restrictions=yes preserve case=yes case sensitive=no short preserve case=yes os level=65 domain master=yes prefered master=yes wins support=yes local master=yes domain logons=yes name resolve order=lmhosts wins bcast host add user script=/usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u veto oplock files=/*.mdb/*.xls/*.mp3/*.ogg/ passdb backend = tdbsam guest username map = /etc/samba/users.map interfaces = eth0 [lab] public=no browseable=yes path=/shared/lab writeable=yes write list=[userlist removed] valid users=[userlist removed] max connections=0 available=yes create mask=0666 directory mask=0777 Chad Vincent Owner RhiannonWEB Phone: 330-283-4681 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
