similar to: [homes] not usable in 18p4?

All, Please help me defend Samba. We are having major performance problems when using VisualStudio to build projects. The source lives on the server, and the intermediate files are dumped locally to try to speed things up. One of the engineers downloaded a demo of NetManage/Chameleon NFS and it was significantly faster. Here are some numbers: samba-1.9.18p8 samba-1.9.18p8

Has anyone seen file-corruption by Samba when files are copied to an NT 4.0 machine? We've been getting quite a few of those lately with larger (>5MB) binary files. It seems like only the last few bytes (50 or so?) are corrupted. (The file size seem OK.) Samba Host: IRIX64 version 6.2 Samba Version: 1.9.17p2 Clients: NT 4.0 (with or without SP/3) P266 and P333 Seems to happen only on

In our environment, we would like to map two drives to a Samba server, each as a different user. For instance, I'm user "vince", but many of us also work as user "developer" in a special directory. Thus we would like to make the following connections: F: maps to \\sambaServer\\homes user: vince G: maps to \\sambaServer\\developer user: developer I can do

If I do a 'smbclient -L <sambasever>', I do not see a list of workgroups or masters. That's because we didn't set Samba up to be master. If I do a 'smbclient -L <ntserver>', I see: This machine has a workgroup list: Workgroup Master --------- ------- NTDOMAIN <ntserver> WORKGROUP

Hello everyone. I have a question concerning the [homes] directive. I've set it up and everything's working fine but there's just a slight little detail that bothers me, and that is that when I browse my samba server off a w2k/wXP client I have two shares (I only have [homes] in my config file as far as shares are concerned) in the root view. That is \\sambaserver\homes and

Hello, I found another strange problem while migrating from 3.0.22 to 3.0.23x (with 'x' eq 'd' now): I can't access my [homes]-share anymore - if i try, the samba-server prompts me for a password. What *is* working is accessing the same directory as [<username>]... E.g.: \\Sambaserver\matthias works whereas \\Sambaserver\homes works *not* Unfortunaely it

I run a pretty large network, we have plenty of users. Most of our users have their windows home directories on Samba servers. One of these many users has the username "homes". This user is unable to map their home directory (\\sambaserver\homes). It seems that this could be a conflict between the "homes" share definition and his username and samba getting confused.

Howdy All, I have read with interest the problems that some people have with profiles and XP ( service pack 2 included ) in getting them to work. I, however, have not had any such trauma's ( thank goodness) and the smb.conf file listed below works a treat. The problem I have is people using profiles over several vpn connections ( just to slow ). So now I am in the situation of wanting to turn

First, my installation is samba 2.2.8 running as a daemon (not inetd) on Solaris 8 configured to use a WINS server and provide authentication via a PDC (same host as WINS server). I do have an lmhosts file in the samba /lib directory with the PDC/WINS server address in it. My globals section; [global] workgroup = WORKGROUP netbios name = SAMBASERVER security =

I am not sure if your problem is similar to what we have just experienced. we are using samba 2.2.3a-12.3 on debian with winxp sp1 clients we are using roaming profiles first logon after reboot fails sortof Windows cannot find a server copy of roaming profile will logon with local profile funny thing we never saw any activity in hostname.log (seperate smb.log for each machine) smbstatus showed

On 10/7/16 3:30 PM, Rowland Penny via samba wrote: > idmap.ldb is very easy to repair, just open it in ldbedit, find the sid > and delete the entire object, close and save. > > If the user/group does exist in sam.ldb, it will be recreated in > idmap.ldb, but with a different ID number. > Ok, I fixed the issue with the SID ending in 1111, but this one remains (and the

Hi all Follow up to this post, as it didn't seem to go through the first time. We have a common problem occurring with our Samba setups. We run 3 (identical) processing environments that each contain a Samba host sharing approx .5TB of data to 6 Wintel machines. Normally these hosts operate fine, though we intermittently experience a Samba panic (intermittent = every 2-3 days) as per below.

Hello, I have problems setting up a canon multifunction ir7200. When I print the windows test page, I have something like "smiley" "arrow" "arow" "smiley" "arrow" name_of_the_samba_spool "smileys" driver.dll etc,etc,etc, on a single line. Did somebody used such a multifunction with Samba ? Below is a (long) description of what I did. I

Hi, I'm having an issue trying to make a Windows machine sambaserveroin a Samba domain. Samba is running with LDAP backend (OpenLDAP). When I try to join the domain, Windows says that the machine account does not exist. The machine account, however, is successfully created in the LDAP directory after the join fails. When I try to join again, Windows says that the account already exists.

Everyone, I am hoping that someone can help me. I have been trying for several weeks to get Samba working to no avail. I have consulted many online help files including the ones located at http://us1.samba.org/samba/docs/DIAGNOSIS.html, browsing.txt that comes with samba, http://us2.samba.org/samba/ftp/docs/Samba24Hc13.pdf, and a few others. I have even posted a previous message, which

On 10/7/16 10:39 AM, Ron García-Vidal via samba wrote: > I've restored the original DBs as it seems the dbcheck error I was > focusing on was a red herring. I'm now trying to look at the "Unable > to convert SID" messages, as these are the only other errors I've > seen. A reminder that this started after I ran "samba-tool dbcheck > --cross-ncs --fix

vince@rti.com (Vince Chen) write: >We upgraded from samba 1.9.17 to 1.9.18 (now running p7) in hopes of >solving file-corruption problems when large files are copied to >NT from our IRIX 6.2 samba server. > >Has anyone see any file corruption? This won't solve your problem, but I just ran some tests copying a large file from NT to FreeBSD2.2.6 and back, w/o any sign of

Hi, my dovecot installation dovecot-2.0.9-19.el6_7.2.x86_64 can't authenticate using winbind from 4.4.3, but it can with winbind from 4.4.2. 4.4.3: May 5 22:11:07 sambaserver auth: pam_winbind(dovecot:auth): getting password (0x00000010) May 5 22:11:07 sambaserver auth: pam_winbind(dovecot:auth): pam_get_item returned a password May 5 22:11:07 sambaserver auth: pam_winbind(dovecot:auth):

I am having issues getting my Windows clients (all WinXP) in a 2003 AD domain to transparently authenticate to my Samba (version 3.0.10-1.4E.2) server. I had this previously working before I changed the name of the server. After changing the name of the server in smb.conf, I ran the same init commands such as kinit, net ads join, and so on. I had also deleted the previous computer object in AD,

But the win wks on the other subnet is configured to use my SAMBASERVER as its WINS SERVER, and it is configured using the IP Adress of the SAMBASERVER and not the name. Shouldn't this do the trick? win wks is on a wireless subnet and hence runs at 11 MBPS, while the SAMBASERVER is on a wired subnet. I read somewhere that windows does some kind of "optimization" with slow networks.