similar to: Difficulty w/Offline Files and Samba 3.0.25

I've recently attempted to convert from the Adobe PostScript drivers for my Canon BJC=2110 printer over to the native CUPS Windows PS drivers and can't quite get things to work correctly. After deleting the printer on my WinXP SP1 clients, verifying under "Server Properties" that the Adobe driver was removed, then reconnecting to my Samba printer, I connect fine but receive

I'm having a problem wtih 2.2.6pre2 that I seem unable to resolve. When logging out of my Win2K SP3 machine, I receive the error "Windows cannot update the roaming profile. The system cannot find the file specified." Checking the archives and google brings up several references to errors around the copying of ntuser.dat from the local machine, to a temporary file on the

Hi. I have problems, when upgraded from samba sernet 3.0.24 to 3.0.25 (too early ?): 1) always must change password, when log in to windows XP professonall - samba 3.0.25 PDC - password expired 2) I can't browse widnows network on client machine - network broswer in WinXP don't respond - just hangs 3) I cann't priny any more to printers attached to another widnows machines

People who have reported this bug (Endless Password Expiration in 3.0.25, bugzilla id #4630) can you please let me know if you're working on 64-bit machines please ? I'm trying to track this down for 3.0.25a and am working on a theory.... Jeremy.

Hi, I'm currently using v3.0.24 in production and all works well. I'm testing 3.0.25 to see if I'm going to have any problems with it if I have to upgrade. I have a problem with the "force group" setting if it is set to a local Unix group. This same setting works fine in 3.0.24 but I'm denied access to the same share in 3.0.25. If I comment off the "force

I use the sernet samba packages on debian sarge and have problems after upgrading to 3.0.25 with rid mappings. My rid configuration for 3.0.24 looks like this idmap backend = rid:ISC=500-100000000 idmap uid = 500-100000000 idmap gid = 500-100000000 after updating to 3.0.25 I get a core dump of winbind (log at the end of the post) with these settings. I tried to use the new configuration

Hello Recently I migrated from samba 3.0.24 to samba 3.2.5 on Debian etch amd64. In old system I have working samba-vscan used with ClamAV 0.91. Now I have ClamAV 0.94.2. I compiled vscan-clamav successfully, but when I try to connect to the share, it fails and I get some strange messages in the samba logs: "Error trying to resolve symbol 'init_samba_module' in

Hello all, I've tried everything I can think of, I've gone through Google and the Samba website and I can't come up with a fix for this problem. I've been running Samba 3 for at least the past year with no problems. I run a small FreeBSD 6.2 box that I use as a storage area for the windows XP systems on my network. Things have been fine up until 3.0.25 and 3.0.25a. Now,

Dear all, Hi. This is imacat from Taiwan. We have just upgraded from Samba 3.0.24 to Samba 3.0.25, as the samba-announce suggeseted ("... is the version that servers should be run for ..."). We are running Samba as our PDC and only server in our domain. My environment is: x86_64, Debian 4.0 r0 Etch, kernel 2.6.18, gcc 4.1.2, glibc 2.3.6. Before upgrade I have read the

Hello, I'm trying to use rpcclient to add a driver to a Samba 3.0.25 running on Gentoo. When I run the script below, rpcclient prints out the same message as if "--help" was submitted as the only switch. #!/bin/bash -x RPC="/usr/local/samba/bin/rpcclient" ARCH='Windows NT R4000' #ARCH='Windows NT x86' DRIVER='HP LaserJet 4Si/4Si MX

I have compiled both samba-3.0.25a and samba-3.0.25b and with both I have problems setting user password longer than 8 chars with smbpasswd. I get no errors, but if I try to set a password with more than 8 chars the password will only be generated using the first 8 chars. This is on Solaris-10 update 3 on amd64 and I have compiled samba using Sun Studio 11 compiler suite and no other options to

I updated all my servers to 3.0.25 early this morning. Everything seems 100% A-OK except for the most surprising thing, all my Windows and Macintosh clients, no problems. But I'm having severe difficulty with the 3.0.25 smbclient. If I use smbclient from 3.0.24 it too can connect to my 3.0.25 servers without issue. Its bizarre. Before I go into it let me say, I've got some 3.0.25

We've updated from 3.0.24 to 3.0.25 and we've noticed some minor problems such as some clients had to reboot in order to mount the share. And the log is now showing this warning all the time: WARNING: Winbindd not running, mapping ids with legacy code [2007/05/17 08:57:37, 2] passdb/lookup_sid.c:sid_to_gid(1435) We are thinking to revert to the previous version 3.0.24 which works

Hi all, sorry for the long posting. Samba 2.2.x is outdated. Trying to switch to 3.0.7 with no success. The vfs layer is one of my current problems. Googled some time for an solution for this: [2004/10/21 20:04:00, 0] smbd/server.c:main(760) smbd version 3.0.7 started. Copyright Andrew Tridgell and the Samba Team 1992-2004 [2004/10/21 22:12:07, 0] smbd/server.c:main(760) smbd version

Gerry, It looks like 3.0.25 breaks "stand alone/no winbind/no domain" servers. This is remeniscent of the 3.0.23b SID/GID problem. The only thing that jumps out at me is that you can't access your home share and other shares just quit working. Looking at the log files, I see this: [2007/05/14 15:24:55, 10] smbd/open.c:share_conflict(389) share_conflict:

I'm trying to configure Samba's vscan on-access VFS module on a box with a working CLAM installation. [CLAM is merrily scanning mail on this box via clamav-milter]. I've set this up before, but this time it seems to be giving me grief. If I remove the vscan-clamav module then everything works, and I can open files. When I try to open a file with the module enable I just get a file

Hi Mariusz, I found this thread at SAMBA.ORG: snip... I can't remember for certain, but try using a relative path. > (e.g. vscan-mksd.so). I tried relative and non-relative path, with this same effect but you've right because in manual for samba-vscan we can read that in samba 3.0 we should use relative path. I had increase debug level of samba daemon and in my log I have found

Hi All, I've got some performance issues with Samba and Vista that I just can't seem to figure out. Googling and fiddling has all been in vain up until now, so I'm not sure what I can do other than wait for Samba 4, but maybe someone here can find something I've missed. First off, the server is an Athlon 64 1.8GHz running Gentoo 2006.1, tested with both Samba 3.0.24 and

Hello, I've been testing out 3.0.25 before putting it into production and came across an issue. As a simple example.. in a share definition root preexec = echo "hey there, hi there, hello" > /tmp/hiya.txt works fine under 3.0.24 not so under 3.0.25, /tmp/hiya.txt isn't created. Cranking up the debugging and using some other similiar tests it seems to me that Samba is in

Hello First I prepared mks_vir Daemon, necessary libraries and modules, everything work fine (I can scan files for vireses from the command line) after that I had install samba from source next I copies and modyfying necessary mks configuration file like /etc/samba/vscan-mks32.conf and add to /usr/local/samba/lib/smb.conf following lines in global section: vfs object =