similar to: AW: AW: Windows Profiles not being placed in defined logon path

Rudolf Kollien email: Rudolf.Kollien@medas.de Rudolf.Kollien@kollien.de *************************************************************************** Never trust a operating system you have no sources for *************************************************************************** Buying an operating system without source is like buying a self-assembly Space Shuttle with no instructions.

Hi there everyone, I recently upgraded to 2.0.6 from 2.0.5a in a hope to improve data integrity (I was having oplock_break problems that would affect the integrity of a lot of Excel files). So far so good with the oplock_breaks (even with oplocks reenabled). :-) However, I've started having problems with the clients' Windows profiles not being placed in my defined logon path.

I think, it's a good idea to control the binds of the smbclient as it's possible on smbd. Rudolf Kollien email: Rudolf.Kollien@medas.de Rudolf.Kollien@kollien.de *************************************************************************** Never trust a operating system you have no sources for *************************************************************************** Buying an

Hello everybody, I use 2 samba servers. Server A (SA) is connected to networks n1 and n2. It is the wins server and the domain controller with domain logons and used as password server. Server B (SB) is connected to networks n2 and n3. As diagram it looks like this: +---n2-----(SA)----n1--+ | (SB) | +-------n3---+ Server B's smb.conf has: ... time server = yes domain master = no local

I encountered an bug in samba 2.0.7. With the config option "logon home = \\%N\%U\profile" in smb.conf and roaming profiles, smbd panics when the share "%U" is not listed in smb.conf. I had some users for which i forgot to enter the accompanying share in smb.conf. When such a user logged in or logged off, smbd paniced with signal 11. While on logging off the profiles where

Hi James, we use some NFS mounted shares on our Linux-SCO-network. Samba runs on the linux box. The linux server mounts some NFS shares from the SCO server. The access error should not be a samba failure. Make sure that the directory above the mountpoint is accessable for user nobody (chmod o+x , if you upgrade to samba > 1.9.18p7 make sure that there is read permission on the directories too:

Hi everyone, Just today one of our users informed me that a file she was working on in Microsoft Excel 97 got corrupted. She was working on the file directly on our server, which is running Samba 2.2.3a compiled using gcc-3.0.4 on Linux kernel 2.4.17-xfs and XFS-based filesystems. I checked the Samba logs for her machine and found the following in a search for the filename of the Excel file she

too. However, when I mount the share via smbfs (on a Linux box, of course), the same file is 2.0T as reported by du (ie: du -csh), 18446744072754680087 bytes as reported by ls, but is only 3340095767 bytes as reported by stat. Further comparison of stat results of the same file via smbfs and directly are intriguing. directly (ie: on the server): Size: 3340095767 Blocks: 6523640 IO Block: 4096

Hi everyone, Our system is a Debian GNU/Linux box running Linux kernel 2.4.17-xfs and Samba 2.2.3 (from the 2.2.3-5 package from Sid), built using gcc-3.0.3. With Samba 2.2.2 we hit certain tdb errors where make_connection would reject connections arbitrarily. Supposedly this was fixed using 2.2.3 so we upgraded right away (thankfully we do only have Windows 95, 98 and ME clients so we

Olaf, (cc XFS and Samba lists) On Mon, 4 Mar 2002 at 15:50, Olaf Fr?czyk wrote: > I have similar problems, (with doc and xls) but I don't have file > corruption (I hope :) We hope. I've turned off oplocks with my Samba completely just to be sure. Things haven't slowed down that drastically, but perhaps it's because the load isn't as high as with some other much larger

Hi there everyone! One of the users complained to me that yesterday, he suddenly couldn't access the network. He was online the whole day, then suddenly at around 6:45pm he couldn't write. A restart of his workstation rendered him completely disconnected from the Samba domain. Server is running Samba 2.0.6 on a RedHat 6.0 machine with Linux kernel 2.2.13. Client is running Windows95 OSR2

Wolfgang, (cc Linux XFS list) (cc Samba list) Quoting wolfgang.glas@ev-i.at: > I just found you message in the samba mailing list archives and foiund > out, that we have a very similar problem. We are using samba-2.2.1a on a > kerenl-2.4.16 and we use reiserfs. > We also experience data corruption with messages like: > > [2002/03/14 15:15:26, 0] >

Suddenly, today, my wife's Windows 95 machine can't print to the network printer on my Linux machine. It complains that "there was an error printing to \\posh\lp ... There was a problem printing to the port." The error 1st occurred (coincidentally?) after I had upgraded the kernel from 2.4.18 to 2.4.19. But rebooting to 2.4.18 has made no difference. We're running smbd

samba does the SMB(!) authentication against machine "a" but you MUST have equal users on ALL machines. How else should samba create files on the unix file system if there is no UNIX user to deal with? It is not a problem of samba, it's a "problem" of unix. The only trick to do this would be to create a dummy unix user and do a "force user" to this dummy on every

If you don't want to type the ip adress of your samba server every time you connect, add a entry to your local hosts file and lmhosts file. You will find this files (and sample files with extension ".sam") in the windows main directory of Win95 and under "system32/drivers/etc" on WinNT 4.0. Regards, System-Consulting Kollien Rudolf Kollien Email: kollien@kollien.de Our

I've exactly the same problem. My config looks similar to yours: 1 samba as wins server (wins support=yes" on one segment, 1 samba as "wins server client" (wins server = xxx). The "wins server client" never discards machines from segment 1. I looked at the browse.dat and the wins.dat on the server on segment 1. There are no entries of the shutdowned maschines. Only in

Hi there everyone, Again another slight thing I noticed since I upgraded to Samba 2.0.6 from 2.0.5a. I'm using RedHat Linux on a Celeron 400 with kernel 2.2.13. My socket options in smb.conf is set to "TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_SNDBUF=8192 SO_RCVBUF=8192". However I've started getting the following everytime I SIGHUP to reload the configs and stop-start:

Hi to all, i've got same problems with "hanging" sessions. I use samba 2.0.4a on a S.u.S.E. Linux with kernel 2.2.5. After a client (win95) shuts down sometimes a session still locks the files on the samba server. I tried to use the socket option "S0_KEEPALIVE" and the global option "keepalive=600". During the day i see many log entries like this: [1999/07/29

You must create a output filter. Edit /etc/printcap and add your client printer like this: ... PC-PRINTER:\ :sd=/var/spool/lpd/PP01:\ :mx#0:\ :lp=/dev/null:\ :if=/var/spool/lpd/Filter/PP01:\ :sh: ... Adjust the printcap parameters as needed (spool directory, directory to find the filter script). Make sure the lpd can access the directory. Consult your manual. Now create the filter

Hi there everyone! I'm using Samba 2.0.5a-19990721 on a RedHat 6.0 machine with Linux kernel 2.2.12. My system generally works fine, however recently I've had some complaints about some files being corrupted. The latest and best-handled to enable a debugging happened at around the same time. Both clients were using Windows95 OSR2 machines with Excel 97 SP-2. Two users reported the problem