[Samba] Windows bombarding Samba looking for share that does not exist
I have a strange problem and I'm hoping that somebody on the list recognizes what it is. I am running Samba 3.0.23d on a Linux box with 2.6.20.15 kernel. I am connecting from 5 or 6 Windows XP SP 2 boxes. There is a share on the Linux box called Music (Note the UPPER CASE M). The share is accessible to all users who have smbpasswords on the Linux box. Most Windows users are successfully connecting to the share and mapping it as a network drive. However, ONE Windows machine periodically hits the Linux server with thousands of requests to connect to service called music (note the lower case m) instead of Music. There are thousands of error messages in the logs saying Nov 8 02:45:13 fileserver smbd[8516]: [2007/11/08 02:45:13, 0] smbd/service.c:make_connection() Nov 8 02:45:13 fileserver smbd[8516]: johnpc (10.0.0.43) couldn't find service music This occurs several times a day. When other users try to connect to the share, the samba logs clearly show they are connecting to the service Music 2007/11/08 10:19:07, 1] smbd/service.c:make_connection_snum(950) office1 (10.0.0.63) connect to service Music initially as user john (uid=507, gid=529) (pid 17601) Is there any way that the problematic Windows machine could have have been told at one point -- or thought it was told -- to connect to a share called music and that Windows is stubbornly continuing to try to connect? Even after rebooting the Windows box? Windows definitely never saw a share called music by browsing because a share by that name has never existed on the Linux box. Maybe another clue is that there are also some less frequent errors in the logs that say: Nov 5 02:46:13 fileserver smbd[32209]: make_connection: connection to Music denied due to security descriptor. Nov 5 02:46:13 fileserver smbd[32209]: [2007/11/05 02:46:13, 0] smbd/service.c:make_connection_snum(782) As I said, most users have no problem connecting to this share. Hope this rings a bell for somebody out there... Andy Email and AIM finally together. You've gotta check out free AOL Mail! - http://mail.aol.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] nmbd keeps trying to contact IP Address on wrong network
Looking for a solution to this problem. I have Googled all over the place but haven't found a definitive answer. I have a Samba Server that ONCE was on a network where there was SECOND Samba Server with IP Address 192.168.20.3. Today, the FIRST server is on a network with an address range 10.0.0.0/255.255.255.0 and it has no way of finding that SECOND Server 192.168.20.3. However, /var/log/messages is full of errors that say: Nov 4 04:07:29 fileserver nmbd[5248]: [2007/11/04 04:07:29, 0] libsmb/nmblib.c:send_udp(791) Nov 4 04:07:29 fileserver nmbd[5248]: Packet send failed to 192.168.20.3(137) ERRNO=Network is unreachable Nov 4 04:07:29 fileserver nmbd[5248]: [2007/11/04 04:07:29, 0] nmbd/nmbd_packets.c:send_netbios_packet(163) Nov 4 04:07:29 fileserver nmbd[5248]: send_netbios_packet: send_packet() to IP 192.168.20.3 port 137 failed Nov 4 04:07:29 fileserver nmbd[5248]: [2007/11/04 04:07:29, 0] nmbd/nmbd_namequery.c:query_name(245) Nov 4 04:07:29 fileserver nmbd[5248]: query_name: Failed to send packet trying to query name ACCOUNTING1b I can see that the file /var/cache/samba/wins.dat includes a reference to the IP Address 192.168.20.3 (I have seen some postings suggesting that wins.dat can be the cause of this error). If I delete wins.dat and restart samba, the reference to 192.168.20.3 comes back. I can state with total confidence that there are no network interfaces on this machine configured to be in the 192.168.20.x range. In fact, only one of 3 network interfaces is currently active and has an IP Address. Is there any way that I can get this Samba Server to stop looking for 192.168.20.3? -- Andy Email and AIM finally together. You've gotta check out free AOL Mail! - http://mail.aol.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] modification time inconsistency
[EMAIL PROTECTED] wrote: On Wed, Jul 11, 2007 at 12:14:19PM -0400, Chris Smith wrote: On Thursday 21 June 2007, Carlos Knowlton wrote: I have a client with a windows utility that relies on touching (changing the mod time) on zero-length files in a folder for the purpose of judging when that folder was last accessed. This works fine for him on mapped windows servers, and from the local disk, but from a Samba (v3.0.22) volume, the mod time doesn't change unless there was an actual data change within the file. (ie, clicking save in notepad doesn't change the mod time unless he enters some data first.). Tried this out of curiosity and find the same results. It only happens with a zero length file, if the file has any data in it then the timestamp does change by doing a save in notepad (no data change necessary). With a zero length file it doesn't change when the file is on a Samba share. However with a cifs mounted Samba share a touch filename does update the timestamp even for zero length files. I've fixed this for 3.0.25c and later. Jeremy. Hello Jeremy, Any possibility this timestamp issue could be related to an issue I see when accessing Samba 3.0.23d (or 3.0.13 for that matter) from an OS X 10.4.x machine running Thursby's DAVE? There is a specific video editing application that runs on OS X. The application creates a pair of database files (two files) on every volume where audio and video media are store. One file is the actual database. One is a very small file that basically records when the last change was made to the database and how many files should be there. Every time you start the video application, the small file is touched (even if its contents are not modified). I reckon the application is marking when the last time was that it looked at this file. The problem is, the timestamp on the small file usually gets set to the workstation time and not to the server time, whereas the big file always gets set to the server time. If the two times are out of sync, the application can get into a vicious circle in which every time it boots, it sees that the mtime of the small file is earlier than the mtime of the big database file -- and the application thinks this means it has to remake the big database file. On the next start of the application, the same happens again. (This never happens on the Windows XP version of the application, by the way.) Having both server and workstation time exactly synchronized seems to aleviate the problem on OS X. However, it's difficult to enforce what users do to their workstations in terms of configuring NTP. Has something changed in Samba 3.0.25c that would cause the mtimes to always be server time? We don't see this issue with Apple's native SMB client, but then again the native client has some serious performance issues so that's why we don't use it. Regards, Andy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] OSX losses link when samba is restarted
[EMAIL PROTECTED] wrote: We run Samba 3.0.24 on a FC5 and RHEL4-AS systems. Works great with windows clients, and OSX clients work great with it too except for one problem: Whenever I restart samba (with /etc/init.d/smb restart) any OSX client that has a samba share open will lose that connection, and so if a person had a file open and was editing, all changes made since the last save are lost. This of course does NOT happen with windows clients, they are smart enough to recognize the link is reconnected. But OSX losses the link completely, and the share has to be remounted, which is really silly. I'm not sure if there is some smb.conf setting that will fix this for OSX, and not screw things up for windows clients. Or maybe there is an OSX tweek to make on each client? I searched this list for OSX and found no similar problems. Arghgh. Anyone see this behavior and know of a fix. Our OSX clients are 10.4.9. Thanks in advance, Alex This is normal behavior of OS X, I'm afraid. I would love to have a way around it too. Andy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Writing files 2GB from Windows
Can anybody explain why SOME Windows XP applications have trouble writing files larger than 2 GB (or sometimes larger than 4 GB) to Linux Samba shares, when OTHER Windows applications on the same machine do not have difficulty writing large files to the same Samba share? And when the underlying Linux filesystem supports very large files? I have sometimes even found that a SINGLE Windows application can write files larger than 4 GBs while performing SOME operations, but while performing OTHER operations, when a file gets to 2GB or 4GB, you get back a message saying reached file size limit or something similar. And those same operations don't cause any trouble when writing 4GB files to a local hard drive. Is there a setting in smb.conf that can communicate better to Windows applications that large file sizes are supported? Likewise, is there a Windows XP registry setting that can make sure that applications know they can write large files to a Samba share? Help and insight would be appreciated. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Writing files 2GB from Windows
[EMAIL PROTECTED] wrote: Can these applications write large files to the local disk? It could be the fault of the application and not of samba. Yes, you might have missed that I mentioned this below. The applications have no trouble writing big files ( 4 GB) to a local disk. I will also reiterate, I have a case in which the very same application only has trouble under specific circumstances. I am talking about a Video Editing application. The application can capture most formats of video to the Samba share and produce single files that are 20, 40, 80 GBs in size. But when capturing in a couple of specific formats, the capture stops when the file reaches 2 GBs with the message maximum file size reached. There is no such limit when capturing to a local drive. Similarly, when importing certain formats of video, we see that the import stops at 4 GBs with a similar error. Andrew - Original Message - From: AndyLiebman [EMAIL PROTECTED] To: samba samba@lists.samba.org Sent: Friday, May 11, 2007 12:21 PM Subject: [Samba] Writing files 2GB from Windows Can anybody explain why SOME Windows XP applications have trouble writing files larger than 2 GB (or sometimes larger than 4 GB) to Linux Samba shares, when OTHER Windows applications on the same machine do not have difficulty writing large files to the same Samba share? And when the underlying Linux filesystem supports very large files? I have sometimes even found that a SINGLE Windows application can write files larger than 4 GBs while performing SOME operations, but while performing OTHER operations, when a file gets to 2GB or 4GB, you get back a message saying reached file size limit or something similar. And those same operations don't cause any trouble when writing 4GB files to a local hard drive. Is there a setting in smb.conf that can communicate better to Windows applications that large file sizes are supported? Likewise, is there a Windows XP registry setting that can make sure that applications know they can write large files to a Samba share? Help and insight would be appreciated. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Windows Application Overriding Samba Settings
Oops, sorry. I had a typo in my posting. I wrote: Until this new version of the Windows application came out, I never had any issues. ANY folder or file created by the application always had the same permissions: 2750 or 570 (respectively) I should have written: Until this new version of the Windows application came out, I never had any issues. ANY folder or file created by the application always had the same permissions: 2750 or 750 (respectively) I switched a 7 and a 5. Andy Liebman Check out the new AOL. Most comprehensive set of free safety and security tools, free access to millions of high-quality videos from across the web, free AOL Mail and more. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Windows sometimes authenticates with wrong user
Sorry in advance for the long post. But this is a bit of a detective story. We are having an authentication issue with a small number of Windows XP (SP2) machines. The Windows machines are set up to have only a single user -- let's say the user is called Writer. There is no password set up for this user called Writer. User1 logs on to the machine and connects to our Linux Samba Server (3.0.13). None of the shares on the server allow guests (guest ok = no) -- so when connecting to a public share on the server, User1 is prompted for a username and password. User1 supplies his Linux/samba username and password -- the server authenticates him -- and now he can access the public shares. His own private shares also now become visible (home directory, and shares defined with a %u variable in the path). All is fine. This is how things are supposed to work But now, User1 logs off (literally logs off Windows -- back to the Windows user log on screen -- fast user switching is NOT enabled) and a couple of minutes later User2 logs on. When User2 clicks on a public share, on these Windows machines she is NOT asked for a username and password. Instead, she immediately gets access to the public share and can also see and use all of User1's private shares! For some reason, it seems Windows is still telling the Samba Server that it is User1 who is connecting -- Windows has not forgotten that User1 logged out -- and Samba just obliges and serves up User1's shares. We see the same behavior if we disconnect shares via net use * /d. The shares disconnect, but when we connect again we're not asked to authenticate again. This behavior is extremely rare. We have thousands of Windows clients accessing hundreds of Samba Servers. In many of the cases, users log on and log off just as I described above without any problem. But we have a few machines out in the field that just keep behaving in this unexpected way (Note: Unfortunately, it's not always feasible for users to log in on every Windows client where they might work with usernames and passwords that match their Linux/samba names and passwords. We encourage organizations that have users moving around a lot to set up a PDC, but many can't do that so they use our on the spot authentication.) My question is: is there a way to force Windows to clear all knowledge of what user was previously using a machine? I kind of doubt this is a Samba issue. But COULD IT BE POSSIBLE that Samba is matching up a Username to a Mac address or IP address and therefore not recognizing that one user has logged out (disconnecting all network shares) and another logged on? Is there something that can make Samba hold on to thinking User1 is still connected when it's acutally User2? If so, what can we do to correct THIS? Can a switch that's in between the client and server be a culprit? As a related issue -- we produce servers that are deployed in isolated and totally separate environments. The servers ALL go out with the exact same NetBios names. They are essentially clones of one another -- and all have the same set of public shares. We always test the servers in our office before they go out. Over time, a couple of our Windows clients in the office just won't connect to certain public shares on the Samba Machines. We get an error message to the effect of Windows can't find this resource requested or you don't have authority to access this resource. Please consult with your network administrator We don't get a username and password prompt. If we click on a DIFFERENT public share, we get the username and password prompt. After authenticating, we can THEN access the first share that gave us the error. My question is, can Windows machines get stuck thinking that a share called \\Server\ShareA that it ONCE connected to on a Server Serial # 131 is still supposed to be the same share that when we try to connect to \\Server\ShareA on Server Serial # 133 -- and because it's not exactly the same share (how could windows figure that out -- by the Mac Address of the Server?), it throws the error? Again, we cycle many server clones into and out of our place and this is a rare event. But we have a two Windows clients that sometimes seem to resist the switch from one server to another. The Windows clients can be shut down for days, but when we boot them up again and try to connect to a completely different server, we can have this issue. Is there some sort of cache on the Windows clients that we can clear out? By the way, we use Samba 3.0.13 on our systems because of a couple of specific Samba issues that appeared in 3.0.14 and 3.0.20 that affect our software and that haven't yet been resolved. We also do NOT tell Windows to reconnect at logon. Hope somebody can shed some light here. Thanks, Andy -- To unsubscribe from this list go to the following URL and
[Samba] Strange Behavior with Read Only files 3.0.20b
I haven't had a chance to look at the list very carefully for the past few weeks, so I apologize in advance if I'm asking a question that has recently been discussed. I seem to recall there has been some discussion about a similar situation to the one I am in. My situation is that I am having an issue with READ ONLY files -- and seeing very different behavior with Samba 3.0.20b versus 3.0.13. Here's a simple example to show what's happening. I have two users called Jim and Bill. They are both members of the Linux group editors. We have a Linux share called Shared Files, and in that share are three directories -- one called bill, one called jim and one called common We are using the inherit permissions feature of Samba in this Share. And we are focing all files created by bill and jim to be owned by the group editors with the SGID. The bill directory is owned by -u bill -g editors, with permissions rwxr-s The jim directory is owned by -u jim -g editors, with permissions rwxr-s--- The common directory is owned by -u supervisor -g editors with permissions rwxrws--- The way we have set up this Samba share, Jim (working in Windows XP SP2) is able to move a file out of HIS jim directory and put it into the common directory (where all members of editors have write permission). Under Samba 3.0.13, Bill can then move the file out of the common directory and put it in his own bill directory (where only HE has write permission). However, under Samba 3.0.20b, Bill get's an error message saying Access Denied, the file is Read Only. My question is, is the behavior Iwe're seeing with 3.0.20b a BUG? Is the behavior from 3.0.13 a BUG. Which behavior will future Samba version be expected to follow from here after? Thanks in advance for your replies (especially the Samba.org folks). Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Versions and Latest OS X 10.4.3 Tiger Update
Hi all on list, Just thought some of you would like to know how Samba interacts with Apple's latest Tiger OS X 10.4.3 update. With this new OS version, the native, built in SMB/CIFS client seems to connect perfectly to Samba 3.0.13 and 3.0.20b. It DOES NOT connect at all to Samba 3.0.14a. If you are having this trouble with 3.0.14a, it's not your imagination. Curiously, Thursby's AdmitMac3 and DAVE 6 connects fine to 3.0.14a, as well as to 3.0.13, but CANNOT CONNECT to 3.0.20b. I'm sure there's a logical explanation. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] 2 TB Limit and Windows XP Pro?
Does anyone know if Windows XP Pro (Service Pack 2) will have difficulty using a Samba share that is larger than 2 TB? Windows seems to be able to read and write from a share that is larger than 2 TB -- for instance, Windows will tell me that a share is 4 TBs in size, and if I have 1.5 TBs stored on it, it will tell me that 2.5 TB are free. But as soon as 2 TB of data have been written to the share, Windows reports that the share is full and won't write any more. Is this expected behavior? If so, is there any Samba setting to get around this? Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Admit Mac and Samba
Hi Jerry, I sent you some information about AdmitMac a few days ago -- about where to download it. I don't remember what you were specifically going to check out about AdmitMac, but I'm having a problem with it and Samba 3.0.20b that I never had with previous versions (a least up until 3.0.14). Now that I have upgraded my Linux machines to 3.0.20b, I simply cannot connect from any OS X machine running Tiger 10.4.2 and AdmitMac 3. Whereas when the Linux machines were running 3.0.13 and 3.0.14 I COULD connect. Attached is the error log. It's pretty stark. It just says: [2005/10/19 17:59:46, 1] smbd/service.c:make_connection(731) make_connection: refusing to connect with no session setup [2005/10/19 18:02:38, 1] smbd/service.c:make_connection(731) make_connection: refusing to connect with no session setup I'll try to run with log level set to 10 tomorrow to see if I get more information. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Low Latency and Samba
I'm trying to optimize some servers for low latency and low jitter. Do you have a reasonable ideas about specific Samba options that might affect those attributes? In specific, I'm wondering about the socket options. I would think TCP_NODELAY would be helpful in reducing latency. However, I would also think that increasing the size of the SO_RCVBUF and SO_SNDBUF would increase latency (because you would tend to fill up larger buffers before writing incoming data to the filesystem, or you would delay confirmation of writes going back out to the network). What does the jury of Samba experts say about TCP_NODELAY and SO_RCVBUF and SO_SNDBUF these days? Most documents and default smb.conf files that come with distributions have socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 Are these considered magic numbers? I just loaded up the most recent SUSE distribution, SUSE 10, and ITS default smb.conf file does not set any socket options at all. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Speed versus Netatalk from OS X
Does anyone know why, when transferring data via Gigabit Ethernet from OS X to Linux (or vice versa), you get about 50-60 MB/sec with Samba 3.0.X (all versions I've tried, the rate depending on whether you use Jumbo Frames) but you get about 105-110 MB/sec with Apple File Sharing Protocol and Netatalk 2.03? Is there any inherent reason why Samba goes at about half the speed? By the way, I'm talking about connecting with OS X (10.4.2 -- Tiger)'s native SMB/CIFS client. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.0.20 and ADmitMac
In a message dated 10/14/2005 9:23:04 A.M. Eastern Standard Time, [EMAIL PROTECTED] writes: | I'm not able to browse the network let alone join | the OSX machines to the domain. Samba is v3.0.20 | running on FreeBSD 5.4-STABLE. Macs are running | OSX v10.3.9 and are fully patched. I've tried | both ADmitMac v2.1 and 3.0 with same results. | | Any experiences with ADmitMac in the Samba community? Not I. Is there a trial version I could grab for my Mac to test? There IS a trial version. You can use it for 30 days, I believe. Just a note of caution. AdmitMac Version 3 has a bug in it that primarily affects its operation in Tiger (10.4.2). The original release (build 867) would give you mysterious File I/O errors on large and fast file transfers. The current release that you can download (build 868) seems to rigidly clamp down transfer rates to about 9.5 MB/sec -- even over Gigabit Ethernet. By contrast, the original release (build 867) gave you around 55 MB/sec transfer speed over Gigabit. BUT, with the occasional File I/O error that could cause your application to freeze. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.0.20 and ADmitMac
In a message dated 10/14/2005 11:20:49 A.M. Eastern Standard Time, [EMAIL PROTECTED] writes: | There IS a trial version. You can use it for 30 days, I believe. Download URL ? _http://www.thursby.com/evaluations/admitmac.html_ (http://www.thursby.com/evaluations/admitmac.html) Andy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] A possible big security issue
Hi, I am using a mix of Samba 3.0.13 and 3.0.20 on Linux (basically, Mandrake 10 and 10.2). I haven't tested this yet on the 3.0.20 machines, but on the 3.0.13 machines I'm seeing something very disturbing. I have set up a number of shares which are accessible only to members of the group workers. The shares are set to NOT allow guests even read only access. When clicking on the shares in Windows Explore, Samba and/or Windows will prompt the user for a username and password (if the user isn't logged on to his/her Windows workstation with a valid Linux/smb username and password). After supplying a valid username and password, the user can mount the share as a network drive and thereafter all other shares to which he/she has access. However, I have just discovered that if I create a *.bat file, I can run net use to mount the share simply by supplying a valid username. I am never prompted for a password (I can include the password in the net use line -- i.e., net use M: \\netbiosname\sharename password /USER:username But if I simply leave out the password the share mounts all the same. And I can read and write to the share. Seems kind of dangerous to me. I know that windows caches lots of usernames and passwords, so I went to the place where Windows stores those things and deleted the listings for the server in question. After completely rebooting the Windows machine, I was still able to log on via net use without supplying a password. Has this issue been seen before? Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Strategy for tuning so_sndbuf and so_rcvbuf
Are there any tried and true strategies for tuning so_sndbuf and so_rcvbuf settings? In my particular application -- using a Samba server for video editing -- we have seen significant differences in performance when we changes these values. For instance, we need to set so_rcvbuf higher than the value you ALWAYS see in people's smb.conf file. But is there a logical and accurate method for determining what are the best settings on a particular system? And can anyone say with certainty how the following factors would interact with the buffer settings: -- amount of RAM in the system -- amount of data (MB/sec) being read from or written to a fast RAID subsystem -- number of SMB clients connecting to the system simultaneously -- amount of data (MB/sec) being sent to or received from each client Thanks for any suggestions Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba, DFS and Junction Points
Hi Samba List, I believe I need to create a Junction Point on a Windows XP Pro machine that will seamlessly link up to a Samba Share on a Linux Server. From my understanding, the creation of a Junction Point will hide from an application the fact that the space referenced by that junction point is actually located someplace else. While it is possible to create an NTFS Junction Point in Windows that links up to a completely separate local drive (that is, a drive connected to the same Windows XP Pro machine), it is NOT possible to create an NTFS Junction Point that links up to a network share. But it seems it IS possible to create a DFS Junction Point inside Windows that links up to a Samba Share. Is that true? If so, will Windows applications truly not know that the storage space is on a network drive? And if so, can anybody recommend a straightforward how-to on setting up DFS on the Samba side? Your thoughts would be appreciated Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: find_domain_master_name_query_fail
In a message dated 7/18/2005 9:44:25 A.M. Eastern Standard Time, [EMAIL PROTECTED] writes: Please post a copy of your smb.conf [global] workgroup = PUBLISHERS_GROUP netbios name = Aristotle server string = Aristotle map to guest = Bad User log file = /var/log/samba/log.%m max log size = 50 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 max xmit = 65536 use sendfile = yes printcap name = cups dns proxy = No wins support = Yes os level = 65 printer admin = @adm printing = cups include = /etc/samba/smb.%U.conf -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] find_domain_master_name_query_fail
Sorry if this is a duplicate message. The first one went out as an html mail. This is plain text only. -- Can somebody tell me what this error means? It seems I get tons of them every day in my Linux /var/log/messages. Jul 14 20:49:38 localhost nmbd[3584]: Unable to sync browse lists in this workgroup. Jul 14 20:49:38 localhost nmbd[3584]: [2005/07/14 20:49:38, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(353) Jul 14 20:49:38 localhost nmbd[3584]: find_domain_master_name_query_fail: Jul 14 20:49:38 localhost nmbd[3584]: Unable to find the Domain Master Browser name PUBLISHERS_GROUP1b for the workgroup PUBLISHERS_GROUP. Thanks for the advice Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] find_domain_master_name_query_fail
Can somebody tell me what this error means? I get tons of them every day in my Linux /var/log/messages, it seems. Jul 14 20:49:38 localhost nmbd[3584]: Unable to sync browse lists in this workgroup. Jul 14 20:49:38 localhost nmbd[3584]: [2005/07/14 20:49:38, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(353) Jul 14 20:49:38 localhost nmbd[3584]:find_domain_master_name_query_fail: Jul 14 20:49:38 localhost nmbd[3584]: Unable to find the Domain Master Browser name PUBLISHERS_GROUP1b for the workgroup PUBLISHERS_GROUP. Thanks for the advice Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Question about new Inherit Owner option
Apparently there's a new Inherit Owner option for smb.conf that allows you to configure Samba to set the owner of a new file or directory based on owner of the parent directory. That seems like a very useful feature! My question is, does Inherit Owner also work when you MOVE a file from one directory to another? In other words, if a file called text is owned by bob and it's in the bob stuff directory(which is owned by bob), when you move it to the joe stuff directory (which is owned by joe) will the ownership of text change to joe? Or does this only work on newly-created files? And does it work on directories too? Also, when was Inherit Owner introduced? I have Samba 3.0.13 and don't seem to have it there. Was it 3.0.14? Thanks in advance for the answers. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Slightly OT: Making Windows Aps Think Mapped Drives are Local
Sorry if this is slightly off topic for the Samba list, but if anybody knows the answer to this question, it's probably a Samba person... Does anybody know if there a way to make Windows XP think a mapped network drive is a local drive, or at least get Windows to report to all applications that ask that a network drive is a local drive? There must be a whole bunch of registry settings that keep track of these things. I pose this question because I have a number of multimedia applications that will only store and access media files (sound, video, etc.) if those files are located on a local drive. However, I am quite sure that ALL of these applications will work fine if the media files are on a network drive. I believe the above statement because newer versions of the same applications do NOT block using network drives and they work perfectly. At the time the older versions came out, the manufacturer sold its own networked storage and intentionally blocked access to 3rd party storage. Good hints or clues or suggestions would be very much appreciated. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] 10 Gigabit Ethernet and Samba
Do anyone have any experience using 10 Gigabit Ethernet connections with Samba? Specifically, if you have had such an experience, can you share what sorts of optimizations you made to get the maximum data transfer between server and workstation? I am just experimenting with this kind of setup myself and I see a huge GULF between the raw TCP/IP transfers that I can make between two machines and the speeds I get when Samba is in the middle. I just have a gut feeling that Samba buffers are not optimized for the quantity of data of speed of transfer. Perhaps a knowledgeable individual could suggest some Samba variables that might be tuned -- in which direction, and why? Regards, Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Mac/Samba capacity detection problem
Glad I could help :) In a message dated 3/24/2005 2:50:23 P.M. Eastern Standard Time, [EMAIL PROTECTED] writes: I tried the quota option, that did the trick! thank you! Carlos -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Mac/Samba capacity detection problem
Your problem is the following... OS X 10.3.x can't cope with seeing Samba shares that are larger than 2 TB. If the Mac sees anything larger, in the info listing on the share, it will tell you the true size (i.e., 2.8 TB), but then it will tell you there is 0 space left. Don't get me started on what a piece of (fill in the blank) Macs are for networking. And Netatalk is no picnic either. You'll have the same problem with large shares and AFP. Anyway, the solution is to either: a) partition your hard drive so that any given share can't have more than 2 TB of space or b) use quotas, and set the quota for the user or group that owns the share to be smaller than 2 TB. I use option b. Works like a charm. Took me about 4 months to realize this was the problem. Hope I can save you some headaches and heartaches. Andy Liebman In a message dated 3/23/2005 5:17:58 P.M. Eastern Standard Time, [EMAIL PROTECTED] writes: Hi, We are having a problem between Linux 2.6.9-prep #12 SMP Mon Dec 6 12:08:34 CST 2004 x86_64 x86_64 x86_64 GNU/Linux (Samba version 3.0.9-1.fc3) and MAC OS X 10.3.5 Samba version 3.0.0rc2 Basically the issue is that the Mac reports the Linux share as being full, and won't allow files to be copied. We are able to work around it using this method: Create a folder on the Linux share with the same name as the folder to be copied from MAC. Then when you try copy and paste, it will let you select Replace. Here's what I'm getting with the DF command: Linux server with plenty of free space: [EMAIL PROTECTED] ~]# df -H Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg00-lv00 5.0T2.3T 2.8T 45%/home Macs with mounted Linux drive shows erroneous drive space: [cinemac:/sbin] root# df -H FilesystemSize Used Avail Capacity Mounted on //[EMAIL PROTECTED]/SOURCE 602G 2.2T -1.6T 365% /Volumes/Source sincityedit:/Volumes/source root# df -H FilesystemSize Used Avail Capacity Mounted on //[EMAIL PROTECTED]/SOURCE602G2.2T -1.6T 365% /Volumes/source Windows mapped drive to Linux shows correct free space: Directory of Y:\ 03/22/2005 09:51a DIR . 12/30/2004 10:00a DIR .. 03/22/2005 10:16a DIR _Admin 0 File(s) 0 bytes 3 Dir(s) 2,765,958,938,624 bytes free I'm not sure what I can do to isolate the problem. Can you give me some advice? Thanks, Carlos -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Thursby's DAVE and Symlinks
Does anybody here have any experience with Thursby's DAVE and symlinks on a Samba Server? When I connect to my Linux Samba Server via DAVE (running on Mac OS X 10.3.8), I can see all the links that I have made to files that reside in other directories on the Linux Server. However, Mac OS X thinks they are aliases. And when I try to open them, I get back a Mac error saying The alias xyz could not be opened because the original item cannot be found. This behavior is very different than what I get on Windows XP or Windows 2000 -- and for that matter, the native OS X SMB/CIFS client -- which treat symlinks just as any other file. The reason I'm trying to use DAVE is because of huge performance issues with the Native Mac OS X SMB/CIFS implementation. The Apple version is absolutely useless for my particular application. DAVE performs much better. However, I have to sort out this links thing. Anybody have any ideas? Is there something that can be set on the Linux/Samba server side that will make DAVE behave the way I want? Thanks for your thoughts Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba and Preallocated Files
A question about capturing videos to a Samba share... When Apple's Final Cut Pro captures video files, it pre-allocates file space on the destination volume. If you capture to a local volume that's physically attached to a Macintosh, or if you capture to a network volume via AFP (Apple File Sharing Protocol), you can see that Final Cut instantly creates a file of the anticipated size on the destination volume at the moment just before capture begins (the anticipated size is based on the maximum capture time limit set by a user). However, when capturing videos to a Windows or Samba share, Final Cut actually will write out dummy data to a file, and then presumably it replaces the dummy data with real data as the capture moves along. Effectively, this makes Samba and Windows shares useless for capturing Final Cut videos. Because, for instance, if you expect to capture a 20-minute DV clip, it will take approximately 10 minutes to create the pre-allocated file before capturing even begins -- even when you are connecting via a dedicated Gigabit Ethernet link. The process seems to chug along unbelievably slowly. And if you were capturing uncompressed video (which has about 5x the data rate of DV video) well, the wait would be interminable. Can anybody on this list see a way to allow Final Cut to instantly create that pre allocated file space that it wants to create on a Samba share? Are their any Samba settings that could make this possible? It would be a coup for Samba! BTW, Apple's IMovie doesn't go through this pre allocation business. But, alas, IMovie doesn't capture timecode data, so Final Cut users who want to work with Samba shares can't simply switch to IMovie for capturing their videos. Hoping for an insightful reply, Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba and Preallocated Files
In a message dated 3/15/2005 1:00:38 P.M. Eastern Standard Time, [EMAIL PROTECTED] writes: On Tue, Mar 15, 2005 at 06:31:19AM -0500, [EMAIL PROTECTED] wrote: A question about capturing videos to a Samba share... When Apple's Final Cut Pro captures video files, it pre-allocates file space on the destination volume. If you capture to a local volume that's physically attached to a Macintosh, or if you capture to a network volume via AFP (Apple File Sharing Protocol), you can see that Final Cut instantly creates a file of the anticipated size on the destination volume at the moment just before capture begins (the anticipated size is based on the maximum capture time limit set by a user). However, when capturing videos to a Windows or Samba share, Final Cut actually will write out dummy data to a file, and then presumably it replaces the dummy data with real data as the capture moves along. Effectively, this makes Samba and Windows shares useless for capturing Final Cut videos. Because, for instance, if you expect to capture a 20-minute DV clip, it will take approximately 10 minutes to create the pre-allocated file before capturing even begins -- even when you are connecting via a dedicated Gigabit Ethernet link. The process seems to chug along unbelievably slowly. And if you were capturing uncompressed video (which has about 5x the data rate of DV video) well, the wait would be interminable. Can anybody on this list see a way to allow Final Cut to instantly create that pre allocated file space that it wants to create on a Samba share? Are their any Samba settings that could make this possible? It would be a coup for Samba! BTW, Apple's IMovie doesn't go through this pre allocation business. But, alas, IMovie doesn't capture timecode data, so Final Cut users who want to work with Samba shares can't simply switch to IMovie for capturing their videos. That's a Mac client issue. We do support sparse pre-allocation on the server side. I'd raise it as a bug with Apple. Jeremy. Jeremy, Isn't the Mac Samba Client compiled from a stock Samba samba.org source code? And if so, shouldn't it behave as any other Samba client. Or is Apple doing their own thing with the Samba client? I've been Googling for information to see if it's possible to compile my own Samba for OS X and haven't come up with much. If it IS an Apple bug, I would bet dollars to doughnuts that Apple will quietly neglect the issue. In my experience with the company, they don't want to do ANYTHING that will help non-Apple products compete with Apple storage devices. They will simply leave it broken. That's not to say that it's the Samba Team's job to fix it. I've just been dealing with Apple Final Cut Pro developers for a long time and I know of what I speak! All I've gotten out of them is it's the Quicktime API that's responsible, and they'll have to change Quicktime to change the behavior when writing to a Samba share. Does that ring true to you? Have you heard of XSan and XServe RAID? Regards, Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Documentation on Displaying Quotas
Hi John (and others on the list) Can I suggest that you add some information to the new Samba docs explaining how to make Linux (or I suppose other Unix) group quotas be reflected in My Computer and/or Explorer when a Windows user accesses a share that is supposed to controlled by a quota? Here was my particular situation this past week. I was setting quotas based on Linux groups. Each Linux group had one main directory on a storage volume. Inside that directory, each member of the group had his/her own directory. All files that went into either the group's directory or the user's sub-directories were set (via a sticky GID) to always belong to the particular Linux group. So, on the Linux side, the quotas worked perfectly. Set the quota to 200 GBs and when the total files stored in the Group's directory, including the user's subdirectories, reached 200 GBs, no more files could be written to the Group or User directories. The question was, how to make My Computer or Explorer show how much space the group had left when accessing a Samba share that either WAS the group directory or that was a User directory inside the Group directory. The answer, it turns out, was to use the force group = Group Name line in the share definition. We were relying on Linux to impose the group name on every file, which it was in fact doing perfectly. However, only the force group = Group Name line made Samba report to Windows that the amount of space left was what was left according to the quota. It would be nice to document this in The Official Samba-3 How-to -- under the force group listing in the smb.conf section, and in a separate place that was more about quotas (I don't know where). Unless this is the wrong way to get Windows to display this information. We certainly couldn't find much information on how to do this. Regards, Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba and Group Quotas
Question: Does Samba (3.0.11 and above) support the use of group quotas? I have set up quotas on my Linux box based on Linux groups. A given Linux group gets X GBs of space on a given volume V. Now, I want Windows XP users who map a share that a) belongs to their Linux group and b) that resides on volume V to see the reported total free space as being the number of GB allocated to the Linux group minus the total amount of space used by that group -- so that they can see when they (and other members of their group) about to hit their quota and run out of space. Important to note is that the files of a given Linux group will all reside within a single directory on the storage Volume. In other words, each high level directory on the storage volume belongs to a unique Linux group, and all the files inside that directory belong to the same Linux group. No files outside that high level directory, or inside any other high level directory, will belong to the same group. Right now, when a user maps a share that belongs to a Linux group with the quota, the user is seeing that the entire volume V is available. It is NOT an option to set quotas by individual users -- as individual users are members of more than one group. Any hints and suggestions would be appreciated. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] XP Pro and offline files
[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) writes: All: Not sure if this is an XP Pro issue or a samba issue. I am running v3.0.3 of the samba server acting as a Domain controller and file server. The problem that I run into is that every once in a while, while connected to the network the network shares go offline. I am running XP Pro SP2 and I am not really sure where to start to troubleshoot this. I wrote in about a similar thing just yesterday. We're using Samba 3.02 on about 40 Linux servers and our users are complaining about the same thing once in a while. Really only on a few machines. But the symptom is there. Seems to happen more with SP2 than it happened with SP1 -- but that's not a scientific observation. In a couple of cases, we could see in the /var/log/messages that the link beat was being lost continually. Replacing cables and switches between Server and Client got rid of that problem (we don't know which element was causing the problem, but making everything new fixed it). But a few other users are still complaining about these random disconnections and we are not sure either how to troubleshoot. We have asked users to carefully document exactly when the disconnections occur -- and on what machine and subnet -- so that we can look for clues in the logs. But so far, nothing in the logs is sticking out. Not all machines on a given pathway from Server to Client disconnect at the same time -- so unless it's a last cable problem it's not likely to be a hardware issue. BTW, we're running the 2.6.6 kernel on a mainly Mandrake distribution. Hopefully, somebody who reads these postings will have a clue or two. Regards, Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Shares Disconnecting
Hi Samba list We have about 40 Linux Servers in use at various locations. All are running Samba 3.02. On some of the servers, we seem to be experiencing periodic disconnection of Windows XP client machines to their Samba shares (BTW, some are Windows SP1 and some SP2). In a couple of cases, we were able to see many events in /var/log/messages stating link beat lost or link beat detected. Our assumption was that we had a bad cable or switch in the pathway between the Server and Client machines. Replacing all cables and switches in a particular path seemed to resolve the problem (we'll figure out later which component was the defective one. The important thing is that the client machines on that path are no longer disconnecting). But in some other cases, users seem to be experiencing continued random disconnections. By the way, we are using the Linux Servers to store files for video editing. Sometimes, an editor will go to lunch or take a phone call and leave the Windows editing machine just sitting idle -- and upon returning will discover that the machine has been disconnected from the Samba server. Most of the time, however, the disconnection does NOT occur, even after many hours of idleness. This is a very random thing. Does anybody have any clues what it could be other than defective hardware? Is there some timeout mechanism coming into play? We haven't specified any keep alive or dead time intervals in our smb.conf file, so I assume we're just getting the default values for those variables. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Roaming Profiles and Mapped Drives
Hi, I have a weird problem with a Linux Server acting as a PDC with Samba 3.02. If I map a particular Samba share as the Z drive -- and I use roaming profiles with a logon.bat script -- the share will NEVER automatically reconnect when logging on again. This happens 100 percent of the time. And now the same thing seems to be happening for any shared mapped as the M drive. Using any other letter for any share works fine -- the mapped share always comes back as the same drive letter with each subsequent logon. Any ideas what could be causing this? It was no big deal to tell my users to NOT use the letter Z -- that's an easy workaround. But now things are getting messy if there's another letter that can't be used. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Boston Job for Samba Person
Hi, We don't know the following is forbidden material on this list. We hope not. We're looking for a Samba/Linux Networking Consultant in the Boston area who can help us with a number of issues, among them: -- migration to Samba 3.11 -- cross subnet browsing -- adding router capabilities to a Linux server and making this work with other routers and firewalls -- PDC fine tuning -- Linux tuning to optimize network for 10 Gb Ethernet If you are interested and live in the Boston area (no long-distance folks on this job) -- or if you know somebody who fits the bill for us -- please contact: [EMAIL PROTECTED] Thanks. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] desktop.ini file appearing in folders.
In your smb.conf file, in the [profiles] share, add the line: hide files = /desktop.ini/ Regards, Andy Liebman In a message dated 2/15/2005 2:41:38 A.M. Eastern Standard Time, [EMAIL PROTECTED] writes: hi, i have the lastest stable samba running as a PDC in a home network environment. i get the file desktop.ini pop up, and in start menus, and in favourates as well. I can manually delete them. but when i log onto another machine, it reappears again. is there anything i can do to fix this as it is annoying to some of the users in the domain. Thanks. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Shares of Logged Out Users Still Visible By Next User
In a message dated 2/4/2005 12:14:15 AM Eastern Standard Time, [EMAIL PROTECTED] writes: Andy, Please show us how you have configured the [homes] stanza. Are you using valid users = %S in the stanza? - John T. Hi John, Actually I don't use HOMES directories. And I am not using the valid users line anywhere in my smb.conf files. Each user has many private shares that only HE/SHE is supposed to be able to access. Those shares are defined in individual smb.username.conf files. In the GLOBAL section of my smb.conf file, I have the statement: include = /etc/samba/smb.%u.conf The listings in the individual smb.username.conf files look like one of the two following models: [Private Projects] comment = Metadata No Media Here path = /home/andy/Projects write list = @editors read only = No guest okay = No create mask = 0775 directory mask = 0775 force directory mode = 2070 force group = editors [andy_TuesdayFiles] comment = Media Files path = /RAIDS/RAID_1/media/andy_TuesdayFiles write list = @editors read only = No guest okay = No create mask = 0775 directory mask = 0775 Note: The /RAIDS/RAID_1/media directory has the sticky bit set for the group , so the group is always editors inside the media folder. It's very important the the ownership and permissions of the files inside these shares be set broadly -- because they are often moved to other locations where other people need to access them. However, while they reside inside a particular user's share (and corresponding directory) they should only be accessible to that particular user. Andy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Shares of Logged Out Users Still Visible By Next User
Hi. I'm running Samba 3.0.2 (a?) on Linux. For the most part, it's working great. I have set up Samba as a PDC and also just as a workgroup server. However, under both scenarios I'm seeing a troublesome behavior with Windows XP machines that have many users who frequently log on and log off. If User A logs off Windows XP and User B logs on 30 or 40 seconds later, sometimes User B can see and access private shares that only User A is authorized to see or browse or read or write. It seems that User A's shares will disappear from the Samba Server after a few minutes -- but during those first minutes after logging on, User B can see both HIS shares and User A's shares. During the transition period, User B can actually copy or delete anything he wants from User A. Anybody have any clue what's going on and how to prevent it? Is the problem on the Samba side or on the Windows side. In my particular application, this is a very dangerous situation. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Any danger in having two shares with same name?
Hi, Don't ask why I'm posing this question -- actually, I WILL explain below -- but is there any danger in having two shares in Samba with the same name? Here's our situation. We have a bunch of production machines out in the field. On those machines, we are constantly setting up special project shares for each user (different from the user's Home directory) that refer to private directories only accessible by that user. We define those special project shares in a series of smb.username.conf files, where we also define which of hundreds of other shares are accessible to that user particular user. The whole process of setting up shares is highly automated from the point of view of the end user. By the way, we reference those smb.username.conf files in the general smb.conf file with the statement: include = smb.%U.conf ... so each user sees all the shares listed in their own smb.username.conf file as well as all the browseable shares listed in the general smb.conf file. This arrangement was working perfectly, until we were asked to turn some of the systems into Primary Domain Controllers and give hundreds of users roaming profiles. Our users now want the special project share for each user to be automatically mapped as the P Drive in Windows whenever a user logs on to a client system. However, we have found that Windows won't process any shares listed in the smb.username.conf directories while it executes the logon.bat script during log on. We know the logon.bat file IS being executed -- it syncs the client time with the server time, and it maps any shares we specify in the general smb.conf file. But it won't map any shares defined in those smb.username.conf files. Curiously, if we run the logon.bat file again about 10 seconds after log on has completed, it will map the shares listed in the smb.username.conf file!. As a workaround, we decided to take an alternate approach to defining the special project shares. For each of the special project shares (that all users have) we put a listing in the general smb.conf file as follows: [Special Project Share A] Comment = Special Folder A path = /home/theboss/%U/Special Folder A read only = No write list = %U guest ok = Yes create mask = 0775 directory mask = 0775 So now, we have two listings for Special Project Share A -- one in the user's smb.username.conf file, and one in the general smb.conf file. The question is, is there any danger of Samba or the Windows workstations getting confused? Each of these duplicate shares has the SAME NAME, and refers to the EXACT SAME DIRECTORY on the Linux box. And has the same access and read/write settings. It's probably the same as if you accidentally created the same share twice in your smb.conf file. I would love to hear from a knowledgeable authority on this. The best solution, of course, would be to stop defining the Special Project Shares in the user's smb.username.conf files. However, we would have to make many changes in the underlying program that is creating these shares and for the next few months it's not practical to update the programs on so many individual user's machines. It's much more practical to simply send out a new smb.conf file to every user. Regards, Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba PDC and Windows XP not executing logon.bat
The guest ok = Yes line proved to be the secret to getting Windows XP to execute the logon.bat file. Thanks for the suggestion! Nowhere in any Samba documentation have I found that mentioned. It should be in the book. Thanks again, Andy Liebman -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have my netlogon share defined as such: [netlogon] ~ comment = Netlogon ~ path = /var/lib/samba/netlogon ~ guest ok = Yes ~ locking = No I think the 'guest ok part' might help you... I'm not 100% sure... Regards, Pascal de Bruijn [EMAIL PROTECTED] wrote: | I have spent most of the past 24 hours reading various samba docs and | searching google for help -- but can't find a solution. Suggestions and solutions | would be appreciated. | | I have set up a Linux Box (Samba 3.02) as a PDC with roaming profiles. (I | haven't upgraded, because this box is a model for over 100 other boxes in the | field). I can add XP users to the domain and their roaming profiles work great. | However, I can't seem to get the logon.bat file to run when a user logs on. I | can run it from the windows command line (using the file stored the linux box | \\linuxbox\netlogon\logon.bat) -- and it does what it is supposed to do. But | this file will not run automatically when logging on. | | I created the logon.bat file on a Windows Box and copied it over to the Linux | Box (so the CR/LF thing should be fine). And of course the file runs from the | Windows command line, so there shouldn't be anything wrong with the file | itself. | | In the smb.conf file, relevant listings include: | | [global] | ... | security = user | domain master = Yes | preferred master = Yes | local master = Yes | domain logons = Yes | logon path = \\servername\Profiles\%U | encrypt passwords = Yes | logon script = logon.bat | time server = Yes | | [netlogon] | path = /etc/samba/netlogon | read only = Yes | browseable = No | | [profiles] | path = /etc/samba/profiles | browseable = No | writeable = Yes | create mask = 0600 | directory mask = 0700 | ;next line prevents desktop.ini from opening in Notepad upon logon | hide files = /desktop.ini/ | | | | A note on my smb.conf file. I originally set it up with the logon path = | \\servername\Profiles\%U with an uppercase P in Profiles. | | Then I noticed that the share name profiles had a lower case p. No I find | that if I change the logon path so that profiles has a lowercase p, logons | from all XP workstations fail. If I change it back to an uppercase P, all is | well. Seems strange to me -- but Samba is often a black box. | | Help would be appreciated. | | Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Roaming Profiles -- Problem Rapidly Switching Users
Does anybody have any insight into what could be causing this strange problem? I have Samba 3.02 (sorry, can't upgrade right now). My Linux box is running Mandrake 10 Official. I have Samba configured as a PDC. I can successfully add machines to my Domain -- and log on as ANY user from ANY machine. However on a SINGLE MACHINE, when I log on as USER_1 and access that user's roaming profile, if I then log off and immediately try to log on again (AS USER_1 or ANOTHER USER), Windows XP gives me a message saying that it can't access the user's roaming profile and that maybe there's a problem with permissions. If I just wait about 3 or 4 minutes, however, I can log on again as any user and access the roaming profile. Looking at the profile directory on my Linux Box, and can see that the roaming profile is updated when I succeed in accessing the roaming profile. When I get that message, Windows just uses the last information that was stored locally on the computer. The cause doesn' t seem to be a problem with permissions. As I log on and log off, I am watching the permissions on the profiles directory and they are not being altered. And I don't see anything in /var/log/samba/[machine_name].log that looks suspicious, except an occasional message: [machine_name] (192.168.1.101) couldn't find service [user who was trying to log on]. BTW, I have my profiles directory in the following path: /home/bigboss/profile/ The home directory on this machine is actually on its own very large partition -- so it's a good place to put the profiles. Whereas the root partition / has much less space -- certainly not adequate for 200 users with roaming profiles. I tried putting the profiles in /home/profile -- but every time I rebooted the permissions of the permissions of the profile directory would get changed to read-only for the group that needs to access the directory. Any ideas or solutions? Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Roaming Profiles -- Problem Rapidly Switching Users
Here is the log from /var/log/samba/[machine name].log. It seems to imply that it takes Samba about a minute to finish closing all the connections for the user who just logged out on a machine -- and therefore a new user can't log on and access his/her roaming profiles until the logging out/closing connections and services has been completed. This is when I am able to log on with a roaming profile: [2005/01/24 15:37:23, 1] smbd/service.c:make_connection_snum(705) gateway9500 (192.168.1.100) connect to service profiles initially as user jessica (uid=508, gid=500) (pid 3561) [2005/01/24 15:37:25, 1] smbd/service.c:close_cnum(887) gateway9500 (192.168.1.100) closed connection to service profiles [2005/01/24 15:37:25, 0] param/loadparm.c:lp_do_parameter(3066) Global parameter domain master found in service section! [2005/01/24 15:37:25, 0] param/loadparm.c:lp_do_parameter(3066) Global parameter preferred master found in service section! [2005/01/24 15:37:25, 0] param/loadparm.c:lp_do_parameter(3066) Global parameter local master found in service section! [2005/01/24 15:37:25, 0] param/loadparm.c:lp_do_parameter(3066) Global parameter domain logons found in service section! [2005/01/24 15:37:25, 0] param/loadparm.c:lp_do_parameter(3066) Global parameter logon path found in service section! [2005/01/24 15:37:25, 0] param/loadparm.c:lp_do_parameter(3066) Global parameter encrypt passwords found in service section! [2005/01/24 15:37:25, 0] param/loadparm.c:lp_do_parameter(3066) Global parameter add user script found in service section! [2005/01/24 15:37:25, 0] param/loadparm.c:lp_do_parameter(3066) Global parameter logon script found in service section! [2005/01/24 15:37:25, 0] param/loadparm.c:lp_do_parameter(3066) Global parameter time server found in service section! [2005/01/24 15:37:25, 0] param/loadparm.c:lp_do_parameter(3066) Global parameter logon script found in service section! [2005/01/24 15:37:25, 1] smbd/service.c:make_connection_snum(705) gateway9500 (192.168.1.100) connect to service netlogon initially as user jessica (uid=508, gid=500) (pid 3561) [2005/01/24 15:37:26, 0] smbd/service.c:make_connection(857) gateway9500 (192.168.1.100) couldn't find service jessica [2005/01/24 15:37:27, 0] smbd/service.c:make_connection(857) gateway9500 (192.168.1.100) couldn't find service jessica [2005/01/24 15:37:56, 1] smbd/service.c:make_connection_snum(705) gateway9500 (192.168.1.100) connect to service profiles initially as user jessica (uid=508, gid=500) (pid 3561) [2005/01/24 15:37:57, 1] smbd/service.c:make_connection_snum(705) gateway9500 (192.168.1.100) connect to service profiles initially as user jessica (uid=508, gid=500) (pid 3561) [2005/01/24 15:38:04, 1] smbd/service.c:close_cnum(887) gateway9500 (192.168.1.100) closed connection to service profiles [2005/01/24 15:38:26, 1] smbd/service.c:close_cnum(887) gateway9500 (192.168.1.100) closed connection to service netlogon Below is where I COULD NOT log on with roaming profiles. I'm not sure whether the last line above goes with logging off or logging on. [2005/01/24 15:38:28, 0] smbd/service.c:make_connection(857) gateway9500 (192.168.1.100) couldn't find service jessica [2005/01/24 15:38:33, 1] smbd/service.c:make_connection_snum(705) gateway9500 (192.168.1.100) connect to service netlogon initially as user jessica (uid=508, gid=500) (pid 3561) [2005/01/24 15:38:34, 0] smbd/service.c:make_connection(857) gateway9500 (192.168.1.100) couldn't find service jessica [2005/01/24 15:38:35, 0] smbd/service.c:make_connection(857) gateway9500 (192.168.1.100) couldn't find service jessica [2005/01/24 15:38:48, 0] smbd/service.c:make_connection(857) gateway9500 (192.168.1.100) couldn't find service jessica [2005/01/24 15:38:59, 1] smbd/service.c:close_cnum(887) gateway9500 (192.168.1.100) closed connection to service profiles Am I to conclude from these logs that it takes Samba about a minute or so to finish logging off the current user from a machine, and that you can't log on as the next user for about one or two minutes? That is my observation. If I wait for two minutes, no problem logging back on, or logging on as a different user. Wait only 30 seconds, it doesn't. Waiting some time between, I'm not sure what works and what doesn't. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba PDC and Windows XP not executing logon.bat
I have spent most of the past 24 hours reading various samba docs and searching google for help -- but can't find a solution. Suggestions and solutions would be appreciated. I have set up a Linux Box (Samba 3.02) as a PDC with roaming profiles. (I haven't upgraded, because this box is a model for over 100 other boxes in the field). I can add XP users to the domain and their roaming profiles work great. However, I can't seem to get the logon.bat file to run when a user logs on. I can run it from the windows command line (using the file stored the linux box \\linuxbox\netlogon\logon.bat) -- and it does what it is supposed to do. But this file will not run automatically when logging on. I created the logon.bat file on a Windows Box and copied it over to the Linux Box (so the CR/LF thing should be fine). And of course the file runs from the Windows command line, so there shouldn't be anything wrong with the file itself. In the smb.conf file, relevant listings include: [global] ... security = user domain master = Yes preferred master = Yes local master = Yes domain logons = Yes logon path = \\servername\Profiles\%U encrypt passwords = Yes logon script = logon.bat time server = Yes [netlogon] path = /etc/samba/netlogon read only = Yes browseable = No [profiles] path = /etc/samba/profiles browseable = No writeable = Yes create mask = 0600 directory mask = 0700 ;next line prevents desktop.ini from opening in Notepad upon logon hide files = /desktop.ini/ A note on my smb.conf file. I originally set it up with the logon path = \\servername\Profiles\%U with an uppercase P in Profiles. Then I noticed that the share name profiles had a lower case p. No I find that if I change the logon path so that profiles has a lowercase p, logons from all XP workstations fail. If I change it back to an uppercase P, all is well. Seems strange to me -- but Samba is often a black box. Help would be appreciated. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Stop users from connecting from two machines
Hi, Can anyone tell me if there is a relativelysimple way to prevent users from connecting to a Samba server from more than one machine? Do you have to use a preexec script? If so, could someone give me a complete example? I would appreciate it. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Why some WinXP machines won't reconnect on reboot
Hi Samba list. Here is my scenario. I have 10 Windows XP machines that use a Linux box as a file server. Running Mandrake 10 (more or less), 2.6, Samba 3.03. We have hundreds of individual shares defined -- but users only see their own shares (we use the include=smb.%U.conf setting in Global settings, and define the shares in individual conf files for each user.) When we use the map network drive function on our Windows XP clients, typically we select reconnect at logon. When we reboot the Windows machines, SOME of the machines will automatically reconnect on every reboot. In other words, we can open an application on the Windows machine that wants to read a file from one of the Linux shares, and we can instantly open the files. But on some of the Windows machines, when we try to do what I have just described above, the network drive can't be found. We have to actually click on the share a couple of times in Explore or My Computer to force the reconnection. On the first click, we will get a message that says Network resource can't be found. Maybe you don't have permission to access this resource (or something like that). Then, on the next click, we are logged on and we can access the share. Does anybody understand why we see this difference in behavior between the two Windows machines? Is there something I can configure on the Windows machines so this doesn't happen? Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Why some WinXP machines won't reconnect on reboot
The machines are pretty much identical. Most have XP SP1. One has SP2 (but it HAS the reconnecting problem like many of the SP1 machines, so it's not specific to either Service Pack). I get the same red X over the network drives on many of my Windows XP machines, and when I click I too get access. But there must be something configured differently on some of my XP machines that makes them NOT have this problem. Come on Samba gurus. Somebody must know what's going on here. Are these two computers identical with the others in regards to speed and size? Are the network settings identical as well. Did you install xp sp2 on them, I have heard some problems regarding this? I know on my machine (win xp), when I reboot, I will often get a red x over the network drives for samba, but once I click on them I can get access and the x goes away. Good luck. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Tuesday, November 16, 2004 9:39 AM To: [EMAIL PROTECTED] Subject: [Samba] Why some WinXP machines won't reconnect on reboot Hi Samba list. Here is my scenario. I have 10 Windows XP machines that use a Linux box as a file server. Running Mandrake 10 (more or less), 2.6, Samba 3.03. We have hundreds of individual shares defined -- but users only see their own shares (we use the include=smb.%U.conf setting in Global settings, and define the shares in individual conf files for each user.) When we use the map network drive function on our Windows XP clients, typically we select reconnect at logon. When we reboot the Windows machines, SOME of the machines will automatically reconnect on every reboot. In other words, we can open an application on the Windows machine that wants to read a file from one of the Linux shares, and we can instantly open the files. But on some of the Windows machines, when we try to do what I have just described above, the network drive can't be found. We have to actually click on the share a couple of times in Explore or My Computer to force the reconnection. On the first click, we will get a message that says Network resource can't be found. Maybe you don't have permission to access this resource (or something like that). Then, on the next click, we are logged on and we can access the share. Does anybody understand why we see this difference in behavior between the two Windows machines? Is there something I can configure on the Windows machines so this doesn't happen? Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Problem with include=smb.%U.conf
Hi, Does anybody know why Windows clients can see shares that are defined by the include=/etc/samba/smb.%U.conf option in but Mac OS X and Linux Samba clients cannot see those shares? In other words, I have a bunch of users. Each user has a set of his/her own unique shares on my Linux server that are defined in files called: /etc/samba/smb.User1.conf /etc/samba/smb.User2.conf /etc/samba/smb.User3.conf and so on. In Windows, User 1 will see the shares listed in /etc/samba/smb.User1.conf. User 2 will not see those shares (unless they are listed in User 2's directory file as well, which in my case never happens). In Mac OS X (10.3.4, 10.3.5, and 10.3.6) as well as in various Linux distributions like Mandrake 10 and 10.1 and the latest Debian, if I log in as User 1, I cannot see the shares that correspond to User 1. The only shares I can see through the Mac Finder or through the Mac Connect to Server or through the Linux Smb4k or LinNeighborhood are those defined in the general /etc/samba/smb.conf file. If there is no way around this situation, is there another way to define shares so that only specific users will see them when they browse for shares that are available? I have hundreds of shares each of which are restricted to individual users. Linux ownership and permissions are set on the directories that correspond to those shares such that User 2 can't enter User 1's directories. But I don't want User 2 to even see User 1's directories. Which is why I use the include=smb.%U.conf approach. It works great in Windows XP, but fails completely when connecting from Macs. Any solutions? Regards, Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] MAC OS X and Samba Shares 2 TB
Does somebody know if the Samba Client in MAC OS X (10.3.4 and 10.3.5) has problems looking at Linux-based Samba shares that are larger than 2 TB? I have Samba 3.0.2 running on my Linux box. I have never had any difficulty with the Mac seeing a 2 TB RAID array on the Linux box, but when the Mac looks at the 4 TB array, it can see all the contents and create folders but it can't create any new files. And in the Get Info for the 4 TB Samba share, the Mac tells me that there is zero K of space left on the drive. My Windows XP machines don't have a problem looking at the same share, or in creates files on the share. I don't think it's a permission thing because: a) I have made the share Read/Write for all users b) I am logging on with the same username and password from both the Windows and Mac machines Any ideas? Regards, Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Throughput to a single client
I have a Linux Server (3.06 Xeon) with a very fast RAID array -- reads at around 500 MB/sec as clocked by Bonnie++. I have 6 GigE nics on my machine -- on two 133Mhz PCI-x bus segments (not on the same bus as the RAID drives) I have noticed two puzzling things and I'm wondering if anybody has any ideas about why I'm seeing these: 1) transfer speeds over a single NIC from a single Windows XP workstation to the Server (host to host, no switch in between) starts out at around 43 MB/sec but then drops off to around 30 MB/sec. I don't think it's a disk speed issue on the Windows side, because data is coming from an 8 disk RAID-5 on the Windows side. 2) transfer speed from the Server to 3 windows workstations seems to max out at around 60 MB/sec total. One windows workstation can get around 40-45 MB/sec, but if I try to achieve maximum transfer speed with to 3 Windows machines each only gets about 20 MB/sec. Again, I don't think it's a disk speed thing on the Linux side -- and on the Windows side the data is not being stored on disk but rather it's being played out as video. So, the question is, does Samba have any configuration options that might limit the total throughput to the Network? And if it's not Samba that's causing the bottleneck, does anyone have any other ideas. Thanks in advance. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Puzzle -- Logon/Login from Windows XP
In a message dated 9/30/2004 1:55:16 AM Eastern Daylight Time, [EMAIL PROTECTED] writes: Long answer: a limitation of Windows is that when you connect via SMB to a remote server, all connections to that server must use the same credentials. If you are connected to \\sambaserver\datafiles as the user *nigel* and wish to connect to \\sambaserver\frederick (which is accessible only to the user *frederick*), the Windows workstation attempts to connect as *nigel*. In order to connect as *frederick* you must break all connections to that server. Simply put, you cannot make two connections to a server from one workstation with two different sets of credentials. Thanks Jon, To further clarify the situation, User 2 will only want to connect to User 2-specific shares after User 1 logs off the Windows workstation. So, in theory, logging off should close all network connections. After User 1 logs off, User 2 goes to Microsoft Windows Network in Explorer and sees the following: - Workgroup_Name + Samba Server + Workstation 1 + Workstation 2 + Etc... If User 2 clicks on Samba Server he sees: - Workgroup_Name - Samba Server [ ] Public Share [ ] Printers and Faxes + Workstation 1 + Workstation 2 + Etc... What user 2 doesn't see is his own private shares. If he clicks on Public Share, then when a few moments later he'll see this in Explorer: - Workgroup_Name - Samba Server [ ] Public Share available to Members of the Workgroup Only [ ] User 2 Private Share A [ ] User 2 Private Share B [ ] Printers and Faxes + Workstation 1 + Workstation 2 + Etc... I can create a similar effect if I am NOT logged on to the Windows workstation as a recognized Samba user by doing the following: So now, User 2 is logged on as Non Samba User and can see the following. - Workgroup_Name - Samba Server [ ] Public Share [ ] Printers and Faxes + Workstation 1 + Workstation 2 + Etc... If he clicks on Public Share, he gets an error message that the share is not accessible You might not havepermission to use this network resource. Contact the administrator... However, if he maps the Public Share as a network drive, and selects Connect using a different username and inputs his own username and password, when he comes back to Explorer he sees this: - Workgroup_Name - Samba Server [ ] Public Share available to Members of the Workgroup Only [ ] User 2 Private Share A [ ] User 2 Private Share B [ ] Printers and Faxes + Workstation 1 + Workstation 2 + Etc... Same as above, when User 2 logged on to the Windows machine as himself. So, the question is, why isn't Windows asking for a username and password when User 2 clicks on Public Share, and instead giving an error message. And why isn't Windows asking for a username and password when User 2 clicks on Samba Server. Why is it showing User 2 the Public Share available to Members of the Workgroup Only when it's not clear yet that User 2 is even a member of the workgroup? When I try to connect from one Windows workstation (# 2) to another (#1) , unless I'm logged on to workstation 2 as a user who has an account on workstation 1, I get a dialog box asking me for a username and password BEFORE I can see any shares on workstation 1. Do you think that with my Samba Server the fact that I'm SEEING that Public Share available only to members of the workgroup even though I can't access it is somehow related to why I'm not getting the username and password prompt? I really don't want to go down the Domain route. The servers I'm building need to be accessed by a large number of ever changing workstations ( including laptops that will come and go) and I don't want to create a nightmare for the person who has to administer the systems. If they have to constantly add computers to the domain, that will be a problem. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Puzzle -- More Logon/Login from Windows XP
In a message dated 9/30/2004 9:41:44 AM Eastern Daylight Time, AndyLiebman writes: In a message dated 9/30/2004 1:55:16 AM Eastern Daylight Time, [EMAIL PROTECTED] writes: Long answer: a limitation of Windows is that when you connect via SMB to a remote server, all connections to that server must use the same credentials. If you are connected to \\sambaserver\datafiles as the user *nigel* and wish to connect to \\sambaserver\frederick (which is accessible only to the user *frederick*), the Windows workstation attempts to connect as *nigel*. In order to connect as *frederick* you must break all connections to that server. Simply put, you cannot make two connections to a server from one workstation with two different sets of credentials. I think I solved the problem. By setting the Public Share only available to members of the Workgroup as not readable by guests, Windows will now prompt me for a username and password when I click on the share. The curious thing is, Windows still doesn't ask me for a username and password when I click on the Samba Server. It shows me the Public Share and I have to click on that to get the prompt. That's different behavior than when I click on another Windows XP workstation. I don't see any shares until I'm authenticated. The other curious thing is, before I made the share not readable by guests, I wasn't prompted for the password, but as a guest I couldn't open the folder anyway. I would get the Not authorized to access this resource message. Is there a problem with map to guest = bad user in global settings? BTW, I'm using Samba 3.0.2a, I believe. Came with Mandrake 10 Official. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Puzzle -- Logon/Login from Windows XP
In a message dated 9/30/2004 1:55:16 AM Eastern Daylight Time, [EMAIL PROTECTED] writes: Long answer: a limitation of Windows is that when you connect via SMB to a remote server, all connections to that server must use the same credentials. If you are connected to \\sambaserver\datafiles as the user *nigel* and wish to connect to \\sambaserver\frederick (which is accessible only to the user *frederick*), the Windows workstation attempts to connect as *nigel*. In order to connect as *frederick* you must break all connections to that server. Simply put, you cannot make two connections to a server from one workstation with two different sets of credentials. I think I solved the problem. By setting the Public Share only available to members of the Workgroup as not readable by guests, Windows will now prompt me for a username and password when I click on the share. The curious thing is, Windows still doesn't ask me for a username and password when I click on the Samba Server. It shows me the Public Share and I have to click on that to get the prompt. That's different behavior than when I click on another Windows XP workstation. I don't see any shares until I'm authenticated. The other curious thing is, before I made the share not readable by guests, I wasn't prompted for the password, but as a guest I couldn't open the folder anyway. I would get the Not authorized to access this resource message. Is there a problem with map to guest = bad user in global settings? BTW, I'm using Samba 3.0.2a, I believe. Came with Mandrake 10 Official. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Puzzle -- Logon/Login from Windows XP
I hope somebody can help me with this. I posed this question a week ago and got several well-meaning answers that were not very helpful. I have 10 Windows XP workstations and 100 users. Each of the 100 users has an account on my Samba server (running Samba 3.03 on Mandrake Linux 10). Each user has several shares on the Samba server which are unique to that user. In other words, only THAT user can access his/her shares, and THAT user has read/write priviledges for those shares. BTW, I define each user's shares by listings in smb.username.conf files and the include=smb.%U.conf option (I may have that backwards it may be username.smb.conf and include=%U.smb.conf, I have it right on my server.) The problem is, I need each of my 100 users to be able to logon to the Samba server (with READ/WRITE access to their own shares) from any of the 10 Windows XP workstations. It's not a problem if the user has an account on the XP machine that matches the username and password on the Linux Samba server. But users don't have their own machines and it's impractical to create 100 user accounts on EACH Windows XP workstation. Especially when the list of users changes every few months. So my question is, how can those 100 users logon to the Samba server from ANY workstation without having an account on the Windows XP workstation that matches their username/password on the Samba server? I have a clumsy workaround right now, but I need something better. This is what I can do now: -- I have a Samba share that is accessible to everyone. -- In Windows XP, if I map network drive on that share and select connect using different username, I get an opportunity to enter the username and password for the specific user. -- Once the Windows XP machine connects to the Samba server, the Samba server knows who the user is and displays a list of the user's own unique shares -- which can then be mapped as well. The thing that's awkward about this technique, however, is that I'm having to map a public share JUST to communicate to the Samba server the username and password. Isn't there a way to get the Samba server to ask for a username and password when the user clicks on the name of the Samba server in Explorer? That's what happens when I click on the name of a Windows XP machine (XP Machine 1) from another Windows XP machine (XP Machine 2) when I'm logged on to Machine 2 with a username and password that does not match an account on XP Machine 1. I get a dialog box asking for a username and password. If I enter a username that has an account on the first machine -- and the matching password -- I connect and get read/write access to all shared drives and folders. I want to get the same dialog box when I click on the Linux Samba server. But how? Thanks in advance for the help. Regards, Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Puzzle -- Logon/Login from Windows XP
In a message dated 9/29/2004 6:20:07 AM Eastern Daylight Time, [EMAIL PROTECTED] writes: Thanks for the reply So my question is, how can those 100 users logon to the Samba server from ANY workstation without having an account on the Windows XP workstation that matches their username/password on the Samba server? Why don't you want to creat a domain? How do you define and create a domain? And is it difficult to maintain a domain as the users change? And what if the Samba server is just one of many servers on a network that might have other domains and domain servers? And what if the workstations have to access other domains? This is the sort of environment where my system has to work. Isn't there a way to get the Samba server to ask for a username and password when the user clicks on the name of the Samba server in Explorer? The server can't ask the user for another username/password. It is a clients decision to ask the user for additional credentials. Unless you find out what specific setting triggers explorer to ask (null session, guest account settings or something, try ethereal) you are out of luck. Maybe you write a script that mounts the shares with net use and give the samba username with /user:name * to ask for the password. Any clues about how to write that script. I'm not a samba expert. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Weird thing with Samba and Final Cut Pro
Does anybody have a clue why, when I access my Linux Samba server from a Mac G5 (OS X 10.3.x) and try to capture digital video files, the Apple Final Cut application -- in allocating disk space for the file it's about to capture -- actually writes to the hard drive for a long time (presumably writing zeros) until it has created a file the very size of what it expects to store on the Samba server. This process basically occurs in real time. If I expect to capture a 30 minute file, the process takes about 30 minutes before capturing actually begins. When I access the same Linux server with Apple File Sharing/Netatalk, the disk space is allocated instantly and capturing begins right away. Could there be anything to configure in Samba that would make it behave more like Netatalk in this regard? Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Why this error? Unable to find Domain Master Browser
Hi. Can someone tell me why I'm getting this error (see below) in my daemon error log every hour? In my smb.conf section, I have my Linux box set to: wins support = yes os level = 65 This message occurs even when all Windows workstations are shut off, so it must be something with my samba configuration on the Linux box. Help appreciated. Regards, Andy Liebman Jul 21 06:54:34 localhost nmbd[1937]: [2004/07/21 06:54:34, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(350) Jul 21 06:54:34 localhost nmbd[1937]: find_domain_master_name_query_fail: Jul 21 06:54:34 localhost nmbd[1937]: Unable to find the Domain Master Browser name SALES_GROUP1b for the workgroup SALES_GROUP. Jul 21 06:54:34 localhost nmbd[1937]: Unable to sync browse lists in this workgroup. Jul 21 06:54:34 localhost nmbd[1937]: [2004/07/21 06:54:34, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(350) Jul 21 06:54:34 localhost nmbd[1937]: find_domain_master_name_query_fail: Jul 21 06:54:34 localhost nmbd[1937]: Unable to find the Domain Master Browser name SALES_GROUP1b for the workgroup SALES_GROUP. Jul 21 06:54:34 localhost nmbd[1937]: Unable to sync browse lists in this workgroup. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Why do windows users see (Samba 3.0) MyNetBiosName?
Can anybody tell me why most, but not ALL, Windows XP users on my network see my Linux server listed in the network browser as: (Samba 3.0) MyNetBiosName instead of just MyNetBiosName? And why, over the course of the day, the computers that see the extra (Samba 3.0) sometimes don't see it? What is the Global Settings listing that controls how the Linux server is named in user's browsers? Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Interaction between wins support = yes and os level = 65
I'm a little unclear about something. I want my Linux box to be the Local Browse Master -- so that the machine that's on all the time is the one that other computers look to. Is it correct that I want in my Global Settings: wins support = yes os level = 65 (or some higher number) And should my Windows XP workstations have the Linux box as the Wins Server? Or should I leave the Wins Server out of it? Thanks in advance for the help. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Capturing Quicktime Files into a Samba Share
I'm hoping somebody can explain why I'm having this peculiar problem capturing quicktime video files with Final Cut Pro (running on OS X 10.3.4) and storing them on my Linux server. The Linux server has both Samba 3 and Netatalk 1.6.4. I have the server set up so that I can connect from the Mac to various Linux directories using either Samba or Netatalk. When I connect with Netatalk, this is what happens. If I set the default Final Cut capture time to 30 minutes, just after I tell Final Cut to start capturing a DV video clip, the application will instantly create three 2GB empty files on the Linux box -- I guess the application is just grabbing space and saying it's mine -- and within seconds Final Cut starts capturing. About 30 minutes later, the capturing is done. However, when I connect to the Linux box through Samba, Final Cut (or the Mac) will actually write the three 2GB files (presumably with just zeros) before capturing. It takes almost 30 minutes to do that, almost real time. I can watch the files grow with Konqueror or Nautilus. Only after these empty files are completely written does the video capture process begin -- again taking 30 minutes, presumably overwriting all the zeros. Thus, if I connect to the Linux box with Samba, it takes twice as long to capture a given video clip compared to connecting through Netatalk. You might wonder, so why bother to use Samba?. The answers are many. Under Netatalk, if a user unplugs his network cable without shutting down his computer, the entire Netatalk network will crash -- disconnecting all Netatalk users and crashing their applications. I fear Netatalk is also doing all sorts of unpredictable things with directory ownership and permissions on the Linux server. When a Mac user accesses certain directories through Netatalk, I'm finding that the group permissions for that directory are instantly changing from read/write to read only. Kind of scary that a client machine can change directory permissions on a Linux server, but I've watched it happen five times today -- right before my eyes. And Samba is so much more tweakable. So, does anybody have a clue if there's a way to configure Samba on my Linux server, or the samba client in OS X 10.3.4, so that these huge pre-allocated spaces don't actually have to be written in real time before capturing can begin? Your help would be much appreciated. Regards, Andy Liebman Boston, MA P.S. Thanks John if you have any clue what might be going on here. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba on Mac doesn't see include shares
I'm having an annoying problem. On my Linux Server (with Samba 3.0.3) I am using the samba option of 'include = /etc/samba/smb.%U.conf' so that users mostly only see shares that specifically belong to them. This approach works perfectly on Windows XP workstations. After a user logs onto the Linux server -- by simply clicking on a share that's accessible to all users -- the user then can see the shares that are only supposed to be visible to him or her. But under Mac OS X 10.3.3, I'm not having any success with this strategy. Users can see the shares that are accessible to everyone. However, even after logging into the server and viewing one of those shares, the Mac users can never see the shares that specifically belong to THEM. Does the include option not work in Macs? In my samba logs, I can see that the Mac users are logging in. But they can never see their own shares listed in the dropdown box of available shares. And even if the Mac users try to log in manually to those shares after connecting to a generally-available share (e.g., by going to the Connect dialog box and typing smb://username:[EMAIL PROTECTED]/samba_share_name the private shares can't be accessed. Is there a way around this problem? I have no issues on the Mac when I try to access shares that are accessible to all users in a particular group, for instance. Only when I try to access individual shares that use this include option. Hope somebody knows the answer. It's very important to me that private shares not be visible by users other than those to whom they belong. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Reconnect to Shares not working
I've just reconfigured my Samba 3 setup so that Windows users basically only see shares they are supposed to see when they browse the Samba server through Explorer. At the suggestion of others on this list, I used the include = /etc/samba/smb.%U.conf feature and create a smb.username.conf file for each Linux user. To get Explorer to display the shares assigned to each user, I created a common share that everybody can access called log_on_here. When users click on that share, their Windows machine gets logged onto the Samba server. Then when users click on the BACK button in Explorer, their individual shares show up. Maybe has a better way of letting users log in to the Server. I couldn't think of one. Anyway, to make life easy for users, I suggested when they mapped their assigned shares, they checked the reconnect on logon box -- so their Windows machine would automatically reconnect to desired shares on the Samba server each time they booted up the client machine. However, I'm finding that the Windows machines aren't automatically reconnecting on each boot. The mapped share appears in Explorer with a red highlight (unconnected) until the user clicks on the share. The first click produces an error that the share is unavailable or you may not have permission to use it. Then the next click allows access to the share. Is there away to make this reconnecting of mapped (but private) shares less cumbersome? Your advice would be appreciated. Thanks in advance. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Making shares invisible to unauthorized users
Hi, Is there a simple way to set up Samba so that users ONLY see the shares that belong to them? I'm not talking about the user's HOME directory. But lets say I have 60 shares in my smb.conf file. To make it less confusing for users when they access the Samba server from Windows, I want the users to ONLY see the shares that belong to them. So, I want to set up each share so that it is only readable and writeable by a single user. And so that only that user can see the share. What are the key settings to achieve this kind of visibility and access control? I have figured out most of my Samba issues on my own, but I have a deadline today to get this issue resolved and I would appreciate hearing from someone who knows the solution. Thanks in advance. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba and Multiple NICs
In a message dated 4/4/2004 11:13:44 PM Eastern Daylight Time, [EMAIL PROTECTED] writes: Andy, I'd have to say you've got yourself a bit of a conundrum. Basically at this point, if you want to double the capacity your server can output, I would recommend segmenting your network into two VLANs (or separate switches if your switches aren't capable of doing VLANs, although any switch worth it's snuff is). However, before I go into more detail about how to actually accomplish that, what kind of hardware is this running on? I'd be seriously concerned that you'd be wasting a lot of time and effort if your hardware isn't capable of capping two GigE cards. I'd attach one machine with a GigE interface via a crossover cable to the second GigE interface on your Samba server and leave the other interface connected to the switch you have now. I'd then try to cap the interface from the side connected to the switch and from the side connected to another computer via the crossover and see if you can actually exceed greater than the speed one GigE is going to give you (or at least what you were getting previously). Also, some details on your hardware would be helpful. Clint Clint, Thanks for your reply. What I want to do is straightforward in concept (perhaps difficult in practice, though I doubt it). I want to put two Gigabit Ethernet Cards in one Linux server -- and have each card talk to half the Windows workstations in my place. In part, I'm looking for a way to get more data in and out of my server (the storage part can support it). Each workstation is running a video editing application and it's looking for about 4 to 4.5 MB/sec of data. The data is time critical. It HAS to arrive when needed, or the editing application stops. So far I'm doing okay with just one network segment, but I think I can add a few additional workstations if I split the network -- because my storage subsystem is capable of doing well over 100 MB/sec -- and that's a lot more than I'm going to push down one Gigabit Ethernet pipe. In part, I want to configure the two Ethernet cards differently so that one can talk to workstations that are optimized for Gigabit Ethernet and Jumbo Frames and the other can talk to workstations that only have normal Ethernet capabilities. I'm NOT looking to get more data to a single workstation. I'm looking to get the maximum number of workstations that can all receive the 4 to 4.5 MB/sec that they need. By the way, my Server hardware is: 3.06 Ghz single processor Xeon, 1 GB RAM, Intel Gigabit nics, fast RAID arrays, two switches capable of supporting Jumbo Frames. Andy -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba and Multiple NICs
Hi, I'm a happy Samba user. I've been working sucessfully in Linux for the past 6 months. I've built a Linux Server with very fast storage and I'm connecting it to many Windows XP video editing workstations via Gigabit Ethernet (all NICs using Jumbo Frames, by the way). Now I want to see if I can increase my data flow in and out of the Server so that more workstations to connect to it simultaneously. I'm pretty much maxing out on the amount of data that can flow through a single Gigabit Ethernet connection (from the Server to a single Gigabit Switch). So I'm wondering what's involved in adding a second NIC to my Server and dividing my workstations into two groups. Is this a difficult thing to configure? Would somebody be willing to tell me what are the crucial settings that need to be made (in smb.conf, for example, or in /etc/*.* stuff). Do I have to create subnets? I'm currently working on an internal network where all the workstations have 192.168.1.XXX static addresses. These workstations occasionally connect to the Internet through a Cable/DSL router that's also on the network and that serves as the gateway. Is it possible to give my server two fixed IP addresses (one corresponding to each NIC) and then connect each NIC to its own switch, which would then be connected to half of the workstations? I tried this today and had no luck. And how can I make it possible for each workstations to have access to the Internet. Presumably, only one switch can be connected to the cable/dsl router -- or else data traffic could go through the cable/dsl router to get from a workstation to the Server. But I suppose that's the least of my worries. I'm not looking for somebody else to do my homework. I've spent about 6 hours today googling around trying to figure out what's required and I'm coming up more confused with each article or discussion thread I read. I would sure appreciate it if somebody out there was willing to lend a hand. I'm sure this is basic stuff to an IT guy, but I'm just working on this networking stuff at a hobby level -- doing pretty well, but now a bit stumped. By the way, does anybody know if this scenario is covered in the new Samba cookbook? I'd be happy to purchase it tomorrow if I thought it would give me the recipe to do what I'm trying to accomplish. Regards, Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Access Suddenly Cut Off to Samba Shares
Hi. I'm hoping some samba genius has a clue about what's happening on my system. I am using Mandrake 10 Community Release. It comes with Samba 3.0.2. I have been using it without problems for two weeks, and before that I had Mandrake 10 betas and Release Candidates running on the same machine. Today, all of a sudden, I can't access any of my Samba shares over my network. I can see them listed in Windows Explorer -- but when I click on them, or try to map them, Explorer hangs for about 10 minutes. This happens on every computer connected to my network. I don't think I'm having a network problem. I can connect from every computer to the Linux Server via VNC. And my Mac OS X machines can all connect to the Linux Server via Appleshare File Protocol. But Samba seems to be dead. I tried a complete uninstall and reinstall of Samba to no avail. I did the following: Uninstalled the Samba rpms (server, client, common). Backed up and then Deleted the entire /etc/samba folder Rebooted the Server (for no particular reason) Reinstalled Samba 3.0.2 rpm Changed the smb.conf file to what I had been using on my network for 6 months -- and deleted all but one share. Added one user/smbpasswd (I had deleted all the old info) Started samba Same problem. I can see the one share, but when I click on it my Windows Explorer crashes. Other apps keep running on the Windows Boxes, but it takes about 10 minutes to be able to get the taskbar back. I even changed the permissions on all the underlying files that are accessed in the samba share to have the owner of the username trying to access the share through samba. Does anybody have a clue what the trouble could be? I would appreciate some good advice. Thanks in advance, Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Networking from Mac-to-Linux Linux-to-Linux
I have 10 machines in my office. A Linux server. Mostly Windows clients. And a couple of Mac G5s. Can anyone give me an informed opinion about the best way to access a Linux file server from the G5 Macs? They're running the latests OS X 10.3 (Panther). I'm using Mandrake 10 (based on the 2.6.3 kernel with Samba 3.0.2). So far I have only tried using smb/cifs from the Macs. I'm getting okay performance, but not as good as I get from my Windows PCs to the Linux machine. (using Gigabit in both cases.) I'm wondering if I should consider another networking protocol to run in addition to smb. On a related topic? Can anyone tell me why I'm only getting a maximum throughput of 12 MB/sec when I connect one Linux client machine to the Linux server via smb/cifs (again with gigabit nics) when I get nearly 4x that speed if I simply boot the the client machine into Windows XP? Seriously, I can write a 1 GB file to my Linux box about 22 seconds (46 MB/sec) if I boot up the client in Windows XP, whereas I only get 12 MB/sec if I boot the client in Linux. Is something wrong here? Is Linux samba better as a server than as a client? In Linux, I have used both LinNeighborhood and Smb4 something or other? Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Another Samba and Mac OS 10.3 Question
I have a different Samba and Mac OS 10.3 question. I have a small network in my office with a Linux box acting as a file server, mostly Windows XP clients, and a couple of Macs. When I create Samba shares on the Linux box, I have no problem getting my Windows XP users to be able to read and write to the shares. The login name and password on the XP boxes are the same as the corresponding Linux AND Samba usernames and passwords -- and all users are in the same common group called writers From the Mac, however, it's a different story. Mac users can mount the Samba shares and gain READ access, but they are UNABLE TO WRITE to the shares. Again, the Mac usernames and passwords are the SAME as the corresponding Linux and Samba usernames and passwords. Is there something that I have to do on the Mac to allow users to write to the common shares? By the way, I'm using Samba 3.0.0. I'll upgrade to 3.0.1 when there's a Mandrake rpm. Here's my smb.conf file: [global] workgroup = WRITERS netbios name = WRITERSPACE server string = WRITERSPACE %v map to gues = Bad User log file = /var/log/samba3/log.%m max log size = 50 printcap name = cups dns proxy = No wins support = Yes printer admin = @adm printing = cups [homes] comment = Home Directories read only = No browseable = No [printers] Not relevant here [print$] Not relevant here [pdf-generator] Not relevant here [InProgress] comment = Stories path = /home/raid/InProgress write list = @staffwriters read only = No guest ok = Yes # Option 1 Use the following line to make all new files editable by all users # inherit permissions = yes # Option 2 Use the following two lines to make all new files editable by all users create mask = 0775 directory mask = 0775 # Option 3 Use the following 2 lines to get Mac users to be able to write to directory as well as PC Users # force user = theboss # force group = staffwriters I would prefer to use Option 2 or maybe Option 1 but they don't seem to work with the Mac. Option 3 does give Mac Users read/write access, but there are reasons why I don't want to use it. Any ideas about getting the Macs to cooperate with Option 2 or 1? Thanks in advance Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Problem Restarting Samba3
I have Samba 3.0.0 installed on Mandrake 9.2. I also have Samba 2.8.8a installed per instructions from Mandrake -- but I do NOT start Samba 2.8.8a automatically. In fact, I don't use it at all. Maybe I should uninstall the Samba 2.8.8a rpm??? I will update to 3.0.1 as soon as an rpm is available from Mandrake. Anyway, I have a problem when I try to add a new share to my smb.conf file. I can't make it accessible to my Windows machines unless I reboot the Linux box. Simple restarting Samba3 doesn't do the trick (I think it's making Samba 2.2.8a START after shutting down Samba 3.0.0). Is there any trick to adding new shares and making them accessible to Windows without restarting either Samba3 or the whole server? And if I have to restart Samba3 -- and if I succeed in making it really restart -- won't that disconnect Windows users who are already connected to the server? Thanks for your advice. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Can some files be invisible to some users?
This may or may not be relevant to Samba -- hiding files, permissions, etc. I have half a dozen Windows XP video editing workstations all accessing the same data on my Linux Box. Each video editing worstation ideally would like to create it's own index of the video files in the shared directory. The video editing program stores the index data in a file that it HAS to write to the same directory where the media itself is. Does anybody know of a way to let each workstation write it's own index file (they all have to have the same name -- i.e., data.mdb) and put them in a common directory -- yet have each machine's file point to different data? Similarly, each machine needs a directory for temporary storage of captured video files (the directory is called creating) but the machines don't like to share the same directory. Again, this directory has to be a sub-directory of the one with the media files. Is there a solution to my problem? I have a workaround that keeps the machines from interfering with each other -- but it's a little clunky and I'm seeking a more elegant solution. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba Variables and TCP/IP Throughput
Thanks for the reply. Do you know (and if so, caan you tell me) what the relationship is between these Samba settings and Linux settings such as net.core.rmem_default (or _max), net.core.wmem_default (or _max), net.ipv4.tcp_rmem and net.ipv4.tcp_wmem. Do the Samba options override the Linux socket options, or do they act as another layer of limits and buffers? Perhaps your TCP window is too small You should try the following global settings: read size = 65535 max xmit = 65535 socket options = TCP_NODELAY SO_SNDBUF=65535 SO_RCVBUF=65535 Rgds Per [EMAIL PROTECTED] wrote: Hi, I am trying to optimize my gigabit network. I have two Intel 1000 MT Gigabit Server Adapters, which support Jumbo Frames -- as well as a Switch that supports Jumbo Frames. However, I am observing some strange behavior in my file transfers from Windows XP to Linux and I am wondering if it has anything to do with the way the Samba variables are set on my Linux box? The strange behavior is that when I set both NICs to use Jumbo Frames [MTU=9014 on the Windows side (includes IP headers) , 9000 on the Linux side (doesn't include the headers], I am getting about half the throughput that I get when I set both NICs to use the standard MTU of 1514/1500. I see the same behavior even if I take the switch out of the system and connect the Windows XP and Linux machines directly to each other (crossover cable not required for computer-to-computer connection with these NICs -- and by the way all of my cables are CAT6). On the Linux side, I am using Samba 3.0.0 on Mandrake Linux 9.2 with all of Mandrake's current updates -- kernel = 2.4.22-21enterprisemdk. The Linux machine is a P4-3.06 Ghz with 1 GB of RAM -- running in hyperthreading mode. I am wondering if any of the Samba socket options settings like tcp_nodelay, so_sndbuf=8192 or so_rcvbuf=8192 are affecting my throughput -- particularly when I am using Jumbo Frames? And are there any other Samba settings that might be interacting in a negative way with my TCP/IP and NIC driver settings that are causing me to get lower throughput with Jumbo Frames instead of higher throughput (which is what I am told I should be getting). Any guidance would be appreciated. I have purchased The Official Samba 3 HOW-TO and Reference Guide but it really isn't very helpful when it comes to understanding how to tune these options and how various socket options settings interact with other network settings and hardware. Andy Liebman Resolute Films 119 Braintree Street, Suite 410 Boston, MA 02134 Tel: 617-782-0479 Cell: 617-308-0488 Fax: 617-782-1071 -- 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
Re: [Samba] Samba Variables and TCP/IP Throughput
So, here's the answer to the puzzle... I did as Per suggested -- set the so_sndbuf and so_rcvbuf to 65535 each, as well as read size and max xmit to the same. And low and behold, the throughput between my Windows XP box and my Linux Box's Firewire RAID 5 arrays went from around 20 MB/sec to around 30 MB/sec. And when I raised all those values by another factor of 4 (up to 262140 for each one) my throughput increased to around 36-37 MB/sec. Raising those values further didn't seem to make any difference. And, and, and, ... at the 262140 level, now I was able to set the MTUs to 4088 on the Windows side and 4074 on the Linux side (4K Jumbo Frames). While throughput essentially remained the same as what I was getting with a standard 1514/1500 MTU, I was happy that it didn't DROP by 50 percent, as it did before when I was trying to use 4K and 9K Jumbo Frames with the buffers set to 8092. And although throughput didn't go UP with the 4K frames, the CPU usage in each machine was pretty much cut in half. That made my Windows XP video editing applications happy. Incidentally, I still get a serious DROP in throughput, about 50 percent, if I try to use 9K Jumbo Frames -- even with those big buffers (I even tried up to 1 MB buffers). Perhaps that could be due to the fact that both my Windows and Linux boxes only have 32-bit PCI slots. I should add a few other notes. First, I am using Intel Gigabit Server NICs because they seem to have good Linux drivers -- and the Intel Tech Support folks were totally blown away by the fact that a few variables in a Samba configuration file could affect network throughput so dramatically. Alas, Samba is a mystery to many folks in this world -- myself included. Second, after hours of playing with TCP/IP settings on both the Windows and Linux sides -- TcpWindowSize in Windows, and a bunch of wmem, rmem, and mem values in Linux -- I came to the conclusion that none of my changes gave me any improvement over the default configurations of both operating systems (at least the way Linux is configured in Mandrake 9.2). Before I started tweaking, I had tried all sorts of Window sizes using the program Iperf on both ends -- and found pretty much that I got to the maximum throughput (a pure bandwidth of about 780 Mbits) at about 64K TCPWindows. But both OS's must do that by default, so tweaking was a waste of time in my case, where I have a fast LAN with almost zero latency. Finally, I have to say that I am impressed with the Intel Gigabit Server Ethernet adapters. The Intel e1000 drivers (not the eepro1000 driver that came with my Mandrake 9.2 distribution) give you fantastic flexibility in both Linux and Windows. For instance, the driver has a number of methods to let you choose whether the NIC interrupts the CPU each time it receives or transmits a packet, or whether the NIC stores up lots of packets and interrupts less frequently. Playing around with that and other settings in the driver allowed me to trade a 15 percent reduction in maximum throughput (and a slight increase in latency) for a 75 percent reduction in CPU usage! Which let my Windows video editing application flawlessly playback uncompressed video through some hardware that's also vying for attention on the PCI bus. Without the ability to do this kind of tweaking, my video editing application was getting interrupted too often to work properly. Surely there are other real time applications that can benefit from such control. I certainly had a happier experience with the Intel NIC than with either Linksys or SysKonnect NICs -- although I hear the SysKonnect NICs are a little faster than most. Hope all this information is useful to somebody out there. As a last word, of course my switch supports Jumbo Frames. I'm trying out a fairly new SMC switch, the SMC8508T. It's fast, cheap and out of control... No just kidding. It's fast and cheap (around $ 140 US) and as far as I can see it's the only switch any where near that price that supports Jumbo Frames. Says so right on the box. It's an unmanaged switch. But I know it's not the switch that's caused my original problems with Jumbo Frames, because I had the same problems when I took the switch out of the system and connected the computers directly. And that's still the case with the 9K Jumbo Frames. Finally, I put use sendfile=yes in my samba configuration file. But what does it do??? I suppose I should at least try taking it out and seeing what it does. Thanks for your suggestions. It's because of people like you that Linux keeps getting better, and Linux users keep getting better results. Andy In a message dated 12/17/2003 10:10:10 AM Eastern Standard Time, [EMAIL PROTECTED] writes: I believe samba just does setsockopt or ioctl on the sockets. Do you get any errors on the interfaces in jumbo? Does your switch support jumbo? Setting use sendfile=yes will help alot on read speeds from samba. On the
[Samba] Samba Variables and TCP/IP Throughput
Hi, I am trying to optimize my gigabit network. I have two Intel 1000 MT Gigabit Server Adapters, which support Jumbo Frames -- as well as a Switch that supports Jumbo Frames. However, I am observing some strange behavior in my file transfers from Windows XP to Linux and I am wondering if it has anything to do with the way the Samba variables are set on my Linux box? The strange behavior is that when I set both NICs to use Jumbo Frames [MTU=9014 on the Windows side (includes IP headers) , 9000 on the Linux side (doesn't include the headers], I am getting about half the throughput that I get when I set both NICs to use the standard MTU of 1514/1500. I see the same behavior even if I take the switch out of the system and connect the Windows XP and Linux machines directly to each other (crossover cable not required for computer-to-computer connection with these NICs -- and by the way all of my cables are CAT6). On the Linux side, I am using Samba 3.0.0 on Mandrake Linux 9.2 with all of Mandrake's current updates -- kernel = 2.4.22-21enterprisemdk. The Linux machine is a P4-3.06 Ghz with 1 GB of RAM -- running in hyperthreading mode. I am wondering if any of the Samba socket options settings like tcp_nodelay, so_sndbuf=8192 or so_rcvbuf=8192 are affecting my throughput -- particularly when I am using Jumbo Frames? And are there any other Samba settings that might be interacting in a negative way with my TCP/IP and NIC driver settings that are causing me to get lower throughput with Jumbo Frames instead of higher throughput (which is what I am told I should be getting). Any guidance would be appreciated. I have purchased The Official Samba 3 HOW-TO and Reference Guide but it really isn't very helpful when it comes to understanding how to tune these options and how various socket options settings interact with other network settings and hardware. Andy Liebman Resolute Films 119 Braintree Street, Suite 410 Boston, MA 02134 Tel: 617-782-0479 Cell: 617-308-0488 Fax: 617-782-1071 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Variables and TCP/IP Throughput
Hi, Sorry if this is a duplicate message. I forgot whether or not this list accepts html posts so I am sending it again as a plain text message. I am trying to optimize my gigabit network. I have two Intel 1000 MT Gigabit Server Adapters, which support Jumbo Frames -- as well as a Switch that supports Jumbo Frames. However, I am observing some strange behavior in my file transfers from Windows XP to Linux and I am wondering if it has anything to do with the way the Samba variables are set on my Linux box? The strange behavior is that when I set both NICs to use Jumbo Frames [MTU=9014 on the Windows side (includes IP headers) , 9000 on the Linux side (doesn't include the headers], I am getting about half the throughput that I get when I set both NICs to use the standard MTU of 1514/1500. I see the same behavior even if I take the switch out of the system and connect the Windows XP and Linux machines directly to each other (crossover cable not required for computer-to-computer connection with these NICs -- and by the way all of my cables are CAT6). On the Linux side, I am using Samba 3.0.0 on Mandrake Linux 9.2 with all of Mandrake's current updates -- kernel = 2.4.22-21enterprisemdk. The Linux machine is a P4-3.06 Ghz with 1 GB of RAM -- running in hyperthreading mode. I am wondering if any of the Samba socket options settings like tcp_nodelay, so_sndbuf=8192 or so_rcvbuf=8192 are affecting my throughput -- particularly when I am using Jumbo Frames? And are there any other Samba settings that might be interacting in a negative way with my TCP/IP and NIC driver settings that are causing me to get lower throughput with Jumbo Frames instead of higher throughput (which is what I am told I should be getting). Any guidance would be appreciated. I have purchased The Official Samba 3 HOW-TO and Reference Guide but it really isn't very helpful when it comes to understanding how to tune these options and how various socket options settings interact with other network settings and hardware. Andy Liebman Resolute Films 119 Braintree Street, Suite 410 Boston, MA 02134 Tel: 617-782-0479 Cell: 617-308-0488 Fax: 617-782-1071 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [OT] Good Gigabit Ethernet Card ...
I'm doing well with the Linksys 32-bit instant gigabit card. .It's cheap -- like $ 70 US -- and based on a National Semiconductor Chip for which drivers are included in at least RedHat 9 and Mandrake 9.2. My only complaint is that the Linux drivers don't seem to support Jumbo Frames (although the card supports them under Windows). Linux support for Jumbo Frames was apparently turned off intentionally in the drivers due to stability problems. I have NOT had good luck with a SysKonnect 9821 64-bit card in a 32-bit slot -- although the card is supposed to be compatible with 32-bit PCI slots. Performance data that I've seen show the card achieving 80 MB+/sec on all Linux systems in a 64-bit slot and using Jumbo Frames. But I get segmentation faults when I'm using my firewire drives at the same time. Could be a motherboard issue and not an issue with the SysKonnect Gigabit card. I had switched to SysKonnect because the company claims to heavily support Linux, and its own Linux drivers support Jumbo Frames. When I put the Linksys card back into my Mandrake 9.2 system, all was well again. Andy Liebman In a message dated 11/28/2003 2:56:26 PM Eastern Standard Time, [EMAIL PROTECTED] writes: Greetings ... I hate to ask these questions, but I dought I will get a straight answer from an Salesmen ... I am looking at putting gigabit in as a back bone for a few Linux servers, but I have used an Accton Gigabit ethernet card with RedHat 8.0/9 and found it a little unstable ... do and RedHat users have a suggestion on a good, but not expensive Gigabit card, basicly for a Samba server(s). Thanks Mailed Lee -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Inherited Permissions vs Force/Create Mask
I have written to this list several times. I purchased the Officia SAMBA 3 How-To and Reference Guide (and read much of it). But I can't get a good answer to my question. I'm trying to figure out the difference between inherited permissions and force/create mask/directory, and other actions like force user and force group (it seems I don't want to use the latter). I have a very simple requirement. I have 6 users in a small network of Windows XP video editing workstations. All users must be able to read and write to the same shared directory (reading, modifying, and deleting each other's files). Plus, I want to know who wrote each file that's on the system (who is the true owner). Because I am doing video editing -- sometimes with uncompressed video over a gigabit network (18 MB/sec) -- I need the very highest efficiency. So, whatever solution I choose it can't have a negative impact on speed. So far I have been able to solve my problem more or less by using Inherited Permissions = yes in my smb.conf file under my shared directory name. Is this the best way to do it? Or are there better solutions? Here are the facts about my system. -- Each user has a username and password on my Linux system. -- Each user has the same username and password under Samba -- Each user logs onto his/her Windows machine with the same usernames and passwords that they have in Linux. -- The Shared Directory on my Linux machine is owned by the group to which all users belong, and the group has write permission (rwxrw-r--) -- The umask for the Linux user that created the directory is 0002 With the solution I have chosen (inherited permissions = yes), all files and folders that my 6 users create and write into the shared directory are listed as being owned by the person who created them (that's good) and by the group to which they all belong (that's good) and the group has read and write permissions. However, in Windows XP, group members who didn't originally create a file or directory are not listed as having FULL CONTROL. They have read and write permission, but not modify. I'm not sure it makes any difference in the end because all users seem to be able to change the names of files, read them and delete them. But maybe they solution I'm using isn't good or has a high impact on performance? It seems another approache could be to use force mask and create mask and force directory and create directory. And as I said above, another approach would be to force user and force group -- but that doesn't preserve the information about who actually created the file. And I want to keep that if possible. And maybe there's a solution that doesn't involve using any special smb.conf variables. Some guidance would be appreciated. Thanks. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Second Windows Computer Disconnects First
Hi, I'm setting up a Linux machine to use as a file server for a small group of windows machines. Like many of the folks who write to this list, I'm having all kinds of difficults getting the Windows machines to be able to access the Linux shares. In my case, the most frustrating thing is that all of my Windows machines and users can access the Linux shares SOMETIMES. But typically, if one computer accesses the shared folder, and then another one accesses it, the first computer gets disconnected. Does anybody have any insights into why this is happening? All of my windows computers have their own unique computer names. And the usernames that are set up for each machine are different (and match the Unix names and samba names and passwords that I have on the Linux machine). Does this have anything to do with the samba server being the preferred master? And why, when my Linux machine is running, do I so frequently see logged off windows machines in Network Neighborhood. This is something that I never see when the Linux machine is shut down. It's as if the Linux machine is taking control of keeping track of who is and who isn't on the network -- and it doesn't do as good a job of updating compared to the way windows stays current. Help would be appreciated. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Is there a buffer or cache setting in samba?
Hi. Can anyone tell me if samba has any settings that determine how much data gets cached or buffered in RAM before being written to the computer's hard drives? I'm having a strange problem and I suspect that the explanation has to do with that kind of setting. I am using a Linux system (P4-3.06 Ghz, 1 GB RAM, 2.4.22 kernel, samba 2.2.8a) to store video and audio files that can be accesssed by a group of Windows-based video editing systems. I got the whole system up and running a week ago and it was working perfectly (my storage devices, by the way, are a series of firewire drives arranged into a RAID 10 array) When I tested the system with disk testing program on the Windows side, I got a transfer rate of 22 MB/sec for a 1 GB test. And in real life, I could sustain a rate of at least 18 MB/second for 20 minutes over my gigabit network. That's what is required for my application -- digitizing uncompressed video. But now things have suddenly fallen apart. Yesterday I had to reinstall Mandrake 9.2 because I had been moving firewire and ethernet cards around to different PCI slots to optimize the system and I just messed things up too much. So I reinstalled and went back to the same card configuration I had when I got the 18 MB/second. And now it doesn't work. I know that I am using a DIFFERENT smb.conf file now compared to before. I don't think I have the old one that I had made with SWAT. The one I'm using right now is very simple and it forces a user and group name on all files written to the Linux share. Looking at a Linux monitoring program -- I believe it's called XOSVIEW -- I think I can see the problem. Yesterday when I tested the system I saw that all the RAM had to fill up completely (took about 40 seconds at 18 MB/sec) before Linux started writing to the hard drives. And shortly after that my Windows video program would abort, telling me the data wasn't getting transferred fast. Last week, when things were working -- and I was using the same monitoring program --Linux would start writing to the drives after about just a few seconds rather than buffering or caching so much data in RAM. And I could see in the monitoring program that there was more RAM free. There must be a setting in samba that determines how much data is cached or buffered in RAM before writing it to the drives. Do you know anything about this? Your advice would be very much appreciated. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Read Write Access to Linux Share
Hi, I need to allow all users on my small network (6 users) to be able to read and write on my Linux Share raid_A. So far, I have been partially successful. By forcing samba to use the same username regardless of who is actually logged on (see smb.conf file below), I can make the owner of all files written to the /home/avidserver/raid director be avidfiles and the group be avidusers. That way, anybody who has permission to access raid_A can read and write there. However, I prefer to keep a record of who wrote files to that folder but still allow anybody in the group to read and write the file. I have tried another approach that HAS NOT worked. Using chown and chmod, I have made avidfiles be the owner of the directory /home/avidserver/raid. And I have made avidusers the group (chown avidfiles:avidusers /home/avidserver/raid andchmod 2770 /home/avidserver/raid ) . My understanding is that what I did is supposed to set the sticky bit for the group avidusers so that any file or directory written within /home/avidserver/raid will give read/write/execute access to the owner avidfiles and any user who is in the group avidusers. However, when I comment out the two force lines in my smb.conf file, whoever acutally logs into samba gets listed as both the owner and the group of any file that gets written. Does anybody know how to solve my problem? I have 6 users. All of them are working on Windows computers. All have usernames and passwords on the Windows Computers that are identical to their usernames and passwords in my Linux machine. All have a smbpasswd that is the same as their Unix password. I want everybody to be able to read and write to/from some shared directories, but I would like to keep a record on the file to know who wrote it. Your solutions would be much appreciated. Here's my very simple smb.conf file: # Global parameters [global] workgroup = RESWORLD server string = Avidserver encrypt passwords = yes printcap name = cups printing = cups security=user [raid_A] path = /home/avidserver/raid guest account = avidfiles guest ok = yes write ok = yes host allow = ALL force user = avidfiles force group = avidusers -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Oplocks -- Simultaneously writing to same file
On my small network, I allow users on 6 Windows machines to read and write the same Linux Share. Can anyone tell me whether the smb.conf file listed below will get me into trouble with users opening -- and possibly writing -- the SAME FILE simultaneously? I have read the documentation on oplocks and I'm not sure I understand it sufficiently. I need a simple plain English explanation of how to use it (and whether I need to use it). What are the different settings and what effect do they have? Most of my files are primarily being read (they are video files for a networked video editing system). However, there is a database file -- more or less, and index of all the videofiles that is frequently changing -- that all Windows clients must be able to read and overwrite. Until this week, I was using Windows 2000 Server to provide access to all my video files -- as well as the database file. Over the course of a year, I never had any problems or conflicts with two machines trying to write the same database file at the same time. I want to be sure I continue without problems now that I have switched to Linux as my server. Is the default behavior of Samba on Linux the same as Windows 2000 with regards to simultaneously opening and possibly writing one file? Your advice would be appreciated. # Global parameters [global] workgroup = RESWORLD server string = Avidserver encrypt passwords = yes printcap name = cups printing = cups security=user [raid_A] path = /home/avidserver/raid guest account = avidfiles guest ok = yes write ok = yes host allow = ALL force user = avidfiles force group = avidusers Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Optimizations for Speed on Gigabit Network
Can anyone tell me if the default installation of samba 2.2.8a (on Mandrake 9.2) will give me the optimum throughput over my Gigabit Network? I realize that there are many things that affect throughput on a network (like the TCP/IP Receive Window, for instance -- or using a standard MTU of 1500 versus jumbo frames). But I also want to know if there is anything I can set in the smb.conf file that will help me get the best throughput possible. My scenario is as follows. I have 6 users on Windows XP machines all running a video editing program. All users need to access the same video files on my Linux Machine (the files are stored on a fast raid array). All users are connected to the Linux machine via Gigabit over copper network adapters. I have a gigabit switch that DOES NOT support jumbo frames, so I have the use the standard MTU of 1500. Most of the time, users are accessing very large files (200 MB to 2 GB in size) and opening hundreds of these files at a time to play bits and pieces of the video and audio from each file. Are there any buffer settings or other settings for SAMBA that will help me get the best throughput from the Linux box to the client side, as well as the reverse? Thanks in advance for the advice. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] File Permissions
I have set up Samba so that all users on my small network can read from my one of my Linux shares as well as write to that share. However, when user A saves a file to that share, user B can't open it -- and vice versa. How can I set up samba so that all files written to that share can be read, modified, and deleted by all users? Thanks in advance for an answer to this question. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Basic Setup Question
I have been struggling with SAMBA for about a month now. Wow, as a Windows user it's really infuriating trying to use SAMBA to put a Linux machine in my system. This is clearly the most frustrating aspect of Linux, in my opinion. All I want to do is make my Linux machine behave like any other Windows XP Professional machine in my office (I do confess, one of my employees brings in her own Windows XP Home machine. I hope that's not an issue.) I am not terribly concerned about security -- I have been using a Windows 2000 Server for about a year to let video editors in my office access 2 terabytes of video files on a series of RAIDS attached to the server. There are only 7 machines on my office network, and no real exposure to the outside. Now, I'm just trying to replace the Windows 2000 machine with a Linux machine. On the Linux Machine (running the new Mandrake 9.2 with Samba 2.2.8a I think) I have created user accounts and passwords for each XP user. I used the same names the editors use to log onto their XP machines as well as the same passwords. I did NOT use the names of the XP Computers. That's my understanding of which name to use.) I also created samba passwords for each of those users with smbpasswd. I made a very simple smb.conf file: But here's what happens. I can access the Linux shares from the Windows XP machines SOMETIMES. Usually the first time I click on the Linux computer (localhost) in Windows Explorer, I get an error. But the second time I click I can usually connect and see the Linux shares. But sometimes -- after being able to read and write to the Linux shares for hours -- I suddenly get back a message Localhost is not accessible. You might not have permission to use this network resource. Contact the administrator of this sever to find out if you have access permissions. You were not connected because a duplicate name exists on the network. Go to System in Control Panel to change the computer name and try again. The only way to gain access to the Linux shares again is to reboot the Windows XP machine. Does anybody know what's going on here? If I can get that issue straightened out, then I have another question. How do I set up SAMBA so that when a user writes a file to the shared folder, the file can be read AND ALTERED by anyone who can access the the share. It's crucial that users be able not only to read all files, but also modify and delete them. Finally, I would ALSO like to know how I can make it so that the files written to some Linux shares can be read by everybody but only modified or deleted by the computer (not the people, but the machine) that created the data. Appreciate your time. Thanks for reading this. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
