Re: [Samba] Re: Samba 3.0.25b on centos 5.1 a lot of signal 11 very unstable!!!
I've found that if I delete anything from a roaming profile on the client-side, I need to delete the server-side copy entirely, then log out to save a new roaming profile. On Tue, 27 May 2008 18:29:34 + (UTC), Avery Payne wrote: On Tue, 26 Feb 2008 22:12:53 -0800, Alberto Moreno wrote: The only problem is this new server, i read about some changes with samba 3.0.25b and oldest version, since we add this server to the domain we had been having problems, we enable the roaming profile to our windows clients, but some times the server doesn't update the user profile, on other situations we lost the profile, example firefox settings, or if the user update some excel file next day appear with no changes. Roaming profiles are just problematic, even on native Windows servers. I have seen several roaming profiles implode on WinXP client boxes. I've also seen bad behavior with Win2k client/server setups as well. Symptoms include the client creating new profiles, ignoring existing profiles, or dialogs indicating profile corruption. We have almost 3GB of core dumps since we setup samba inside winbind folder, look this is my smb.conf file: [ lots of stuff snipped out ] lib/fault.c:dump_core(181) dumping core in /var/log/samba/cores/ winbindd [ even more stuff snipped out] [0x645c97] #19 winbindd [0x6443f2] #20 winbindd [0x615368] #21 winbindd(main+0x94d) [0x615dbd] #22 /lib/libc.so.6(__ libc_start_main+0xdc) [0x21fdec] #23 winbindd [0x614061] : 13 Time(s) -- Hope this info give some point to start debugging this problem, does someone see what is causing the problem? Thanks all for your time, if u need more info please let me know, thanks!!! I'm no Samba or programming expert, but that last line looks like a libc segfault. Sig 11 errors a long time ago used to implicate RAM issues, usually due to bad contacts or faulty RAM chips.This may sound silly but try powering down the machine, unseating and reseating all of your RAM. If it continues, try reducing the RAM and see if the issue goes away (due to a bad RAM stick). Just my .02 cents. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- 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 /etc/passwd
This sounds like a situation just crying out for Winbind authentication. I'd say set the boxes up for that rather than messing around with the /etc/passwd files. With Winbind, you don't need local accounts. On Tue, 2008-03-04 at 08:17 +0900, Michael Heydon wrote: Shain Miley wrote: Hello all, I was wondering if anyone knew a way to configure samba so that it does not use /etc/passwd for a list of users,group id's,etc. I am currently setting up a server to authenticate against AD. I have that configured fine. The overall goal here is to provide a samba backup to our existing fileserverserver. Here is the problem: we need a way to sync the info in /etc/passwd between servers, these two serves will have a different list of users,groups,etc. So instead of writing a script that will compare the two and add the ones as needed (as well as do a bunch of other cleanup work) I thought maybe I could have samba point to /home/user_name/passwd instead...samba has what it needs..and the accounts on the server itself (/etc/passwd) can be left untouched. Thanks in advance, Shain Samba doesn't look at /etc/password directly, however it does require that any user who connects must have a valid uid on the server. I can suggest a couple of ways you could hack something together to make it easy to sync parts of /etc/password between machines but I would suggest checking out ldap first. *Michael Heydon - IT Administrator * [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Mixing share and user?
Bob, Try to do a chmod -R 777 /home/public -- it's possible that filesystem permissions are not right. Also try adding these lines to the definition for the public share as well. force group = public read only = No create mask = 0777 directory mask = 0777 Hope this helps you out!! On Tue, 11 Oct 2005 19:40:46 -0400, Bob Cohen wrote: Hi, My goal is to set up the server so that one directory acts like a windows share that (1) does not require any log in information to gain access (2) Can be viewed from a windows box and selected using map network drive. At the the same time, I also want to set up private space on the disk that does require an authorized user, username and password for access. My set up (see smb.conf below), as currently written, helps me accomplish the second goal. But not the first. As I'm looking at this, it occurs to me that the problem is that the open to all director is within the /home directory tree. Is there a way to make an exception to the security = users directive specified in [global]? Or should I place it in another directory altogether. The open to all directory will contain two things: files shared by everyone on the network and data for a custom database which is accessed by client-type applications distributed across the network. Thanks in advance for the help! Bob smb.conf. [global] workgroup = home_office netbios name = DEXTERLAKE server string = NBTAFileServer security = user encrypt passwords = yes guest account = public username map = /etc/samba/smbusers guest ok = yes [public] comment = For Lighthouse and general NBTA User data guest ok = yes force user = public path = /home/public/public writeable = yes browseable = yes [homes] comment = User Space path = /home/%U writeable = yes browseable = yes -- Bob Cohen Principal MojoTools and b.p.e.Creative http://www.mojotools.com bob -at- mojotools.com 508.384.0405 Yahoo IM bob_j_cohen -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Office (2003) saving excel sheet takes VERY long..
Max, I'd try working on the TCP Socket options. Adjust the SO_RCVBUF and SO_SNDBUF values up in steps of 1024, restarting Samba after each change. You can then time the transfers. That should help! On Wed, 07 Sep 2005 19:22:58 +0200, Max Riedel wrote: Hi! Maybe you can help me, would be very nice! I'm new to the list and I'm very glad that it exists... A week ago we migrated to samba and since then it's taking very long to save a 1,8MB excel document. On fast ethernet it takes us about 10 seconds, on wireless lan it can take up to a minute, although transferring the same amount of data from the very same machine, that is connected via 802.11g, to samba (by copying a file) takes only about 3-4seconds over the wireless connection. We use Excel in Office 2003 with SP1. Machine is a WinXP Pro SP2. It looks as if it was Excel's fault, but it also seems to be much slower now since the files are stored on the samba server. Is there any way to enhance Excel's writing or maybe the caching on the server?Most of the files are smaller than 300kbytes, but this particular one is ~1,8MB and used VERY frequently. Samba version is 3.0.20 System's running on an Athlon XP 2.400+, 512MB ram, Redhat Enterprise WS 4 The smb.conf looks like: [global] netbios name = smb workgroup = WORKGROUP server string = Samba Server hosts allow = 192.168.0. guest account = guest log file = /var/log/samba/%m.log max log size = 500 security = user ;oplocks = no ;level2 oplocks = no encrypt passwords = yes smb passwd file = /etc/samba/smbpasswd socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 IPTOS_LOWDELAY ;getwd cache = yes ;dead time = 15 ;read raw = yes ;write raw = yes interfaces = 192.168.0.102/24 remote announce = 192.168.0.255 local master = yes os level = 200 preferred master = yes name resolve order = wins lmhosts bcast wins support = yes dns proxy = no preserve case = no default case = lower case sensitive = no idmap uid = 16777216-33554431 idmap gid = 16777216-33554431 template shell = /bin/false winbind use default domain = no [shared] comment = Temporary file space path = /smb/shared public = yes writeable = yes create mask = 0640 directory mask = 750 force create mode = 020 force directory mode = 020 guest ok = yes force group = users [daten] comment = Root path = /smb/daten valid users = @verwaltung write list = @verwaltung force group = users create mask = 0640 directory mask = 750 force create mode = 020 force directory mode = 020 [folder1] path = /smb/daten/folder1 valid users = @users writeable = yes public = yes force group = users create mask = 0640 directory mask = 750 force create mode = 020 force directory mode = 020 [folder2] path = /smb/daten/folder2/ valid users = @users writeable = no write list = silvia, @verwaltung force group = users create mask = 0640 directory mask = 750 force create mode = 020 force directory mode = 020 Thanks alot for any help! -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Help...!
Anri, The clock skew issue means that your machine's time is set incorrectly. This issue is easily corrected by running Network Time Protocol (ntpd). Edit your /etc/ntpd.conf file, and set the time server to be your existing Win2K box's IP address. See man ntpd.conf for info on the syntax of the file. A quick fix that you can try is run the ntptime command to do a one-shot time synchronization. Use ntptime [Win2K IP]. Note that any clock drift on the two hosts will eventually cause the time to get out of sync, so you will be better served using a normal NTP daemon instead over the long term. I would further tweak the ISA server and create a rule allowing unauthenticated transparent access for the SAMBA machine's IP address to the outside for the protocols of interest to you. This may not be required once the clock skew issue is resolved. On Mon, 5 Sep 2005 11:25:44 +0700, Anri wrote: Dear All, I'm a new member of this listing. And also a new user of LINUX, I tried the SuSe Linux and wanted to do a simple task of joining my existing Windows 2000 Domain. I've tried to change the SMB.conf file, also do some changes to use winbind etc, but even though I have retrieved all my AD Users, I cant get my machine to login using any of my AD account. Every time I tried to logon it keeps telling me that xsession: login for DOMAIN\User is disable. When I tried to test the KBS system, and type Kinit [EMAIL PROTECTED] I received an error msg Clock skew too big. Another problem is I'm trying to use my proxy for internet using my ISA Server proxy but keep on getting error to initialize since none of the password is accepted. I'm just trying to connect a client to be able to do some of the most basic task, like typing document, making spreadsheet, printing, internet connecting and email retrieving, but still to no avail. I hope somebody out there can help me!! Thanks in advanced guys. Sincerely, ANRI JONG -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Help - Serious samba problem with Excel
Jamie, Try adding a force user = some_unix_user line to the share. Also try a force group = some_unix_group as well. I've had to do this with MS Office apps before... they try to take ownership and mess things up pretty badly. Also try turning off oplocks as well. Once you add those lines, also make sure to chown all the affected files to the appropriate Unix user/group as well. Hope it helps!!! On Mon, 05 Sep 2005 19:49:10 +0100, Jamie Heckford wrote: Hi, Damn I hate upgrades. After updating at the weekend to FreeBSD 5.4-R in a fresh install our samba server just doesn't want to play ball. I have managed to get Samba3 working ok apart from when it comes to using Excel documents. If a user has an excel document open and another user tries to open it, Excel 2003 will fail with 'Unable to open the file, it may be read-only or encrypted' It worked perfectly before, I have driven myself mad trying to get it to work all day :( If anyone could lend a hand it would be very much appreciated.. relevant config, details etc. below: --- FreeBSD 5.4-RELEASE-p6 #1: Sun Sep 4 16:37:13 BST 2005 samba-3.0.12_1,1 from FreeBSD ports (I have tried 3.0.20 as well, no luck) [global] workgroup = TRIDENT server string = SERV01 security = domain socket options = TCP_NODELAY netbios name = SERV01 log file = /var/log/samba/log.%m dns proxy = no wins support = no interfaces = 192.168.120.6/24 encrypt passwords = yes enhanced browsing = yes [stats] comment = Operations - Stats Area path = /u/stats force user = root guest ok = no writeable = yes valid users = user1, user2, user3, user4, user5 I have taken everything else out to try and solve this problem. /u is mounted from another FreeBSD 5 box over NFS, I have tried all the various oplock settings as well and this didn't make any difference. Thanks, -- Jamie Heckford Network Manager Trident Microsystems Ltd. t: +44(0)1737-780790 f: +44(0)1737-771908 w: http://www.trident-uk.co.uk/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: Connection reset by peer
I agree. This indicates a packet loss on the LAN. I would check the cables and switches. If you can, try using a 10,000 packet flood ping from the server to a suspect host, with a 1500=byte packet size. This is a nice quick test of network health. Oh - a bad NIC at either end can also do this. On Fri, 24 Dec 2004 07:15:52 -0500, Michael Lueck wrote: I had some of those showing up on a test network with home-made LAN cables. I switched it to pre-fab tested onces and the errors went away. So, one vote for LAN cable issues. Connection resets are a TCP/IP stack condition you could pick up the existance of with a sniffer, Samba in my opinion is being nice and logging that it detected it happening. -- Michael Lueck Lueck Data Systems Remove the upper case letters NOSPAM to contact me directly. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba + MS Access
Try putting a force user = line into the share. I've had to do that a time or two when sharing databases -- it seems that each user tries to chown the file. Force User prevents this by having all accesses at the filesystem level appear to come from the same Unix user (doesn't affect permissions of Samba users). It may be a good idea to create a special Unix account for this purpose... # useradd database Set the database user's login to /sbin/nologin as it doesn't need shell access. Then do # chown -R /shared/Access database --- I believe MS Jet specifies the permissions of LDB files and overrides the server's defaults when it does so. This is the only way I was able to make Act! databases play nicely over Samba 3.x shares, and suspect that MS Access is behaving in a similar fashion. Please let me know how it works. I added a force user line into the configuration you posted below. Change the username entry to a valid user on your system and life should be good. On Thu, 17 Jun 2004 08:36:35 -0700, Dan Weisenstein wrote: Well, so far I'm not having much success. The weird thing is that no matter what settings I put into smb.conf, the lock file gets created with permissions of 644. Here is the section in question: [access] force create mode = 0777 force user = username create mask = 0777 directory mask = 0777 force directory mode = 0777 available = yes browseable = yes read only = yes write list = dan,tesoro,heidi,sue,inventory locking = yes strict locking = no level2 oplocks = no oplocks = no comment = Access guest ok = no path = /shared/Access/ veto oplock files = /*.mdb/*.xls/*.ldb/*.LDB/ dos filetimes = yes As you can see, new files should be created with perms of 777. I do a /etc/init.d/smb stop and then start and new files still get created (from the XP client) with perms of 644. Even after a reboot of the server. What am I doing wrong?? Dan [EMAIL PROTECTED] wrote: From: Dan Weisenstein [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [Samba] Samba + MS Access Date: Tue, 15 Jun 2004 11:42:50 -0700 - Original Message Follows - I have a single Linux server running SuSE 9.1 and Samba 3.04. I have one share that has several MS Access tables on it. One user can operate just fine, however when a second+ user tries to access the same database tables, one of several things happens depending on what I have in the smb.conf file. It's usually a permission denied, or a can't lock type of error. When the first user opens a table, a file called xxx.ldb gets created, where xxx is the name of the table. The lock file is owned by the user and has permissions of 644. When a second user tries to open the same table, the error occurs. In my smb.conf file, I have tried almost every option I can find that would apply to file locking, including turning on and off kernel oplocks, level2 oplocks, oplocks, and setting veto oplock files to /.ldb/.mdb/ and all possible permutations of all of them. Nothing really changes with any of them. If I force the lock file to 666, Access hangs. I saw this in a Samba book by Gary Wilson. Maybe it will help (p83): To configure a share for [Access] database that is readable by all users but can be modified by a few users ... [share] path = /path/to/share read only = yes write list = user1, user2, @sales create mask = 0666 directory mask = 0777 force create mode = 0666 force directory mode = 0777 oplocks = no veto oplock files = /*.mdb/*.MDB/*.ldb/*.LDB/ dos filetimes = yes It was for Samba 2.2 but maybe it will help. -- Dan Weisenstein General Manager Tesoro Electronics 715 White Spar Road Prescott, AZ 86303 928-771-2646 -- 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 just Slow with AutoCad?
I would try turning off the Strict sync option. I would also test it with the oplock options disabled as well. On Mon, 7 Jun 2004 08:59:34 -0600, Brian Merrell wrote: This is from 1998: We've had serious performance problems loading AutoCAD R14 .dwg files from a VAResearch VArServer 3000 (dual 400MHz PII, Red Hat 5.0, SAMBA 1.9.17p4, 256MB RAM, 36GB RAID5). The problem is that on first access, trying to read the .dwg file is very, very slow This is from 1999: A friend of mine just had a big problem with Samba, which we eventually solved. The problem was that NT clients did well on a copy in a command prompt, but were terribly slow when opening the same file in Autocad. (Compared to serving the file from an NT server). The solution was well hidden in dejanews and the Samba documentation somewhere; we had to set socket options = SO_SNDBUF=4096 SO_RCVBUF=4096 I have found a couple of other people complaining about performance with AutoCad. I have tried the above fix, and I did not notice any difference whatsoever. I have also tried generic speed fixes like this: http://www.dd.iij4u.or.jp/~okuyamak/Documents/tuning.english.html to no avail. This is very important to our company, and I may be forced to use a windows server if I cannot resolve this problem. We had our files on a Windows XP machine (with worse hardware than we are using now) and it was running quite a bit faster than the Samba server we have now. The speed problem, however, only seems to be with AutoCad. Here are some smb.conf's I have tried: (I have tried SO_SNDBUF=8192, and 4096) [global] workgroup = TRISTATE security = USER netbios name = SERVER encrypt passwords = Yes smb passwd file = /etc/samba/private/smbpasswd oplocks = true ole locking compatibility = no read prediction = true strict sync = yes socket options = IPTOS_LOWDELAY TCP_NODELAY SO_SNDBUF=2920 hosts allow = 127.0.0.1 10.0.0.0/24 hosts deny = 0.0.0.0/0 [Drawings] path = /fileservice/drawings writeable = Yes browseable = Yes read only = No guest ok = No comment = autocad related files and misc files valid users = drafter [Topowork] path = /fileservice/topowork writeable = Yes browseable = Yes read only = No guest ok = No comment = adobe related files valid users = drafter AND: [global] workgroup = TRISTATE security = USER netbios name = SERVER encrypt passwords = Yes smb passwd file = /etc/samba/private/smbpasswd [Drawings] path = /fileservice/drawings writeable = Yes browseable = Yes read only = No guest ok = No comment = autocad related files and misc files valid users = drafter [Topowork] path = /fileservice/topowork writeable = Yes browseable = Yes read only = No guest ok = No comment = adobe related files valid users = drafter Any help would be greatly appreciated. Brian Merrell -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Connection To Server Dropping Intermittantly
I am troubleshooting a strange issue... Current setup is 12 PCs accessing a Samba box. Network was recently changed to security=DOMAIN to authenticate to a Windows 2000 PDC via a VPN tunnel. Users can login fine, but intermittently we are getting a Network path not found message at the clients, especially when they attempt to write. When connecting to the server by servername\share, we see the server go offline and online constantly, and see these same issues when connecting via ip address\share, but to a somewhat lesser extent. This is a pretty critical problem for the office that this is installed in, as they share an Act! database and mount their my documents folders from the server. Even momentary glitches in connectivity result in corrupted databases. My guess is that we are dropping packets on the VPN link back to the DC, and that is causing Samba to deny access from time to time, then later it comes back when a successful authentication request happens. Does this sound reasonable, or is there something else we need to look at here? Has anyone seen this issue before? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
