similar to: Samba 1.9.16pl11: dropping connections between Solaris 2.5.1 and WinNT4SP3

We are having a problem with Microsoft visual C++ compiling source code maintained on a samba server. Occasionaly the compiler reports that it cant open the file vc50.pch. The samba server is running on a freebsd box. Taking a look at the log files it looks like when the operation fails the server is processing the command open (vc50.pch for exclusive use write setattrE write open (vc50.pch

Using Samba 1.9.18p10 I have found a difference between Win95 and WinNT: opening 'Lotus Freelance' files from Win95 is really slow (about 17 kB/s only) vs fast (~hundreds of kB/s) from WinNT. Looking into the log (with debug level=4) I see using Win95: switch message SMBopenX (pid 33994) Skipping become_user - already user unix_clean_name [./PRIVATE/Goyal_Sep98.PRZ] Got dir cache hit on

I just thought that I would put this out there and see if anyone else sees this problem with Samba 1.9.18p4 (under Solaris 2.6). It appears that after some reboots of Solaris, Samba printing is partly dead. What I see in the logs are below, and what happens is that the file to be printed is spooled to /var/spool/samba, like always, but when the lpr command is issued it croaks. I've been

I'm having lots of hassles and troubles since I moved to 1.18p10: 1\ Why do I need a smbpasswd and have to have a user equivalent on the unix machine when an NT user wants to print via an smb printer? My NT/Win users shouldn't need to know anything about unix and I don't want to tell them "you have to log into my unix machine and invoke

Sorry that I will ask a kind of a vague question, but I don't really know how to proceed at the moment: Some of our Samba (1.9.18p10) users experience the following problem: they map a drive to a Samba share (pointing into AFS, if that matters) and see all files/dirs correctly after the password dialog. 'Some time' later (for one user usually about one hour) they try to use the drive

I'm having a difficult time setting up printing from a remote client to a Linux server. Please email replies to mlepage@cgowave-16-35.cgocable.net as I am having difficulty subscribing to the mailing list. The print server is a Debian 2.1 Linux system with an HP LaserJet 5000 connected via parallel port. It prints correctly using lpr, even as user nobody. Also, remote Linux machines can

tl@fairplay.no wrote: > Hmm, I missed the original post, but this sounds like it could be the bug > I reported 15 days ago to samba-bugs (PR#8316) and still haven't got any > responses to. > Sorry, I'm still integrating incoming patches. > If it's the same bug it's mainly the write performance that's bad, and in > reality the performance is worse than

I posted a while back about getting very slow writes. People suggested modifying (increasing) SO_SNDBUF and SO_RCVBUF and this actually helps enormously. However, there is obviously something still not right. Writes are still about 1/2 the speed of reads. This only seems to affect Win95 clients (NT machines are fine). Doing a write of a 20mb file to the server generates the following message:

Hi, I'm having some problems with Samba 1.9.16p11 on a Sun3/60 running NetBSD 1.2. I have a Win95 client and a couple of DOS clients on a single ethernet segment (it's at home :-). I've set up a simple configuration, intention was just to serve files from the Sun to the PC's. Everything works perfectly except authentication from the Win95 client. I can connect to the Samba shares

----- Forwarded message from Brooklyn Linux Solutions CEO ----- >From ruben@www2.mrbrklyn.com Thu Mar 15 23:17:00 2001 From: Brooklyn Linux Solutions CEO <ruben@www2.mrbrklyn.com> Message-Id: <200103160417.f2G4H0O09806@www2.mrbrklyn.com> Subject: Some Users Work - Some don't In-Reply-To: <200103160226.f2G2Q1i09494@www2.mrbrklyn.com> from Brooklyn Linux Solutions CEO at

Hi there ! I just upgraded (last friday night) our main Samba host to Samba 2.0.0 from version 1.9.18p10. This host provides access to our own file based database system. The number of Samba clients is around 60 (nearly all NT4.0's and few NT3.51's). The Samba 2.0.0 host runs 'uname -a': HP-UX vertex A.09.05 A 9000/720 65914162 two-user license After the upgrade change I've

I have been trying to make password changing work with Samba from a Windows 95 clients. All the workstations use nonencrypted passwords. The server is SCO Open Server, Samba 1.9.18p10. The relevant lines of smb.conf are passwd chat = *Old*password* %o\n "1):" \n *New*password* %n\n *Re-enter*password* %n \n passwd chat debug = yes passwd program = /bin/passwd unix password sync = yes

Hi, I have been struggling with this OOM issue and so far nothing has helped. So we are running 10TB archive volume which stores bit more than 7M files. The problem is that due to the way we are managing this archive, we are forced to run daily "full scans" of file system to discover new uncompressed files. I know, i know, this is not optimal solution but it is as it is right now. So

Hi all, I'm extremely puzzled by the behaviour of one of my Samba servers. It's been working fine for yonks, and this morning (abuout 11:32) it just stopped. (mostly) Connecting to shares still works. Navigating the tree till works. Changing (DOS) attributes still works. But actually opening files and reading the contents doesn't work. The client just times out (Win 3.11, and

We are running Redhat 9, 2.4.20-30.9 kernel, Samba 3.0.0 and Winbind 3.0.0. Security is set to "Domain" and we are trying to set up shares which will be available to valid NT 4.0 users and groups. Winbind appears to be working, and you can use the commands "getent group" and "getend passwd" to see that it is communicating with the NT domain for user and group

I have samba-1.9.18p7-2 smb.conf says: # Configure smbpasswd passwd chat debug = yes # Default passwd chat = *old*password* %o\n *new*password* %n\n *new*password* %n\n *changed* passwd program = /usr/bin/yppasswd Using smbpasswd, my encrypted password is changed, but yppasswd is not even touched (as per ls -lu /usr/bin/yppasswd). Furthermore, running smbd with -d 100 didn't seem to show

Here's my setup: Caldera Open Linux Lite (kernel 2.0.29) Samba 2.0.4a Windows Domain (Two Windows NT 4.0 Servers -- one PDC, one BDC -- and numerous Windows NT 4.0 Workstations) I can see my Linux box in Network Neighborhood on my Windows NT boxes. I can open the Linux box and see the top level shares available. When I try to open a share I see one or two anonymous folders. Anyone

Hi all. When I try to mount a file system on a Mac running DAVE 2.1 as OS 8.5, the file system's mount fine, but shows up empty on the desktop. I've attached the log output (debug level 5). Any help is appreciated! Adam -- ---------------------------------------------------------------- Adam Weisser aweisser@kodak.com.au CI Digital Imaging Products

Howdy all: For those who are curious (eg, Peter de Groot <pdgtech@wantree.com.au>) here are the (I think) relevant posts from recent samba digests concerning win98 and or NT performance problems copying files between local drives and samba shares. It looks like there should be some new options to play with in the next samba release. Could Jeremy or Andrew confirm? (BTW, nice

I installed Samba on my Linux box, then I got next problems: 1. Printing from NT. When I try to connect a network printer to my Samba printer , NT report something like "invalid printer name" and in log writed by Samba appear: .............. smb_bcc=14 switch message SMBopenX become_user now uid=(0,507) gid=(100,100) 02/20/98 18:00:38 error packet at line 3677 cmd=45 (SMBopenX)