similar to: 2.0.4b: "null passwords = yes" -> confusing LOG

This is the list of problems I had with samba-2.0.6 so far. Can anyone tell me if he can reproduce them and if he considers them as problems? 2.0.6 on linux 2.2.13 or 2.0.33 1) sighup/log reopening doesn't always work: connections that are already active keep logging to the old logs; logrotate rotates/zip the logs and samba stops logging completely till restart. 2) Localized chars. I have

I have a similar problem to Giulio Orsero. I have failure messages in the log files, but I actually have samba mapping failures. A PC will map every day for two weeks properly and then not connect. Fifteen minutes later, it will connect. Any suggestions? Alvin ---------- Giulio Orsero <giulioo@tiscalinet.it> 7) I have 2.0.6-PDC and a 2.0.6-domain-member of the 1st pdc.

Hi! Just today, I managed to attach my Win98 client at home to my remote network which is controlled by a Linux samba 2.0.5a server. The TCP/IP connection is working just fine, I'm able to access all services like ftp, telnet, ... The Win98 client is connected to the network using the DialUp-Network. The option "log on to remote network" is activated and as far as I can conclude

Using Samba v2.0.10 on a RedHat v7.1 box, I see that the Win98 clients on our network are making sporatic requests for user "nobody" (as shown below). Anyone know what's going on here? My network has both Linux and Win98 clients, but only the Win98 clients are showing this behavior. Both the Linux and Win98 clients access the same shared drives, but only the Win98 clients use

Hello everyone, we try to use a server running linux in an NT-domain and get the error message given in the subject-line. More details from the logfile and smb.conf are given below. Can anyone give us a hint what the problem is? (Of course...) The problem is very urgent for us. Thanks a lot in advance. Helmut Rickel ================= smb.conf ======================== [global]

Running Samba v2.0.4b on a RedHat v6.0 system, I find that when I log onto the server running Samba my authentication fails twice before succeeding. I get these messages in the Samba log file: [1999/06/16 11:45:11, 1] smbd/password.c:pass_check_smb(532) smb_password_check failed. Invalid password given for user 'steve' [1999/06/16 11:45:13, 1] smbd/password.c:pass_check_smb(532)

The problem: Strangely, the PDC rejects user password challenges from Samba. The user account gets locked. After unlocking the account, everything is back to normal. This happens several times a day to different users and from different Samba servers. All Samba servers have the same [global] configuration. Is this a Samba problem? Is samba perhaps not passing along the correct password? If I add

Hi, Recently i moved from samba 2.0.5a to Samba 2.0.6 on 4 machines. Samba 2.0.5a ran quite smooth except for oplocking problems, so i decided to upgrade. I compiled both releases myself and used the same ./configure options both times (but i compiled on different machines: v 2.0.5a was compiled on a HP 9000/715/50, 2.0.6 was compiled on a HP 9000/800/K360) I used binutils 2.9.1 and gcc 2.8.1 on

I have been running RedHat 5.2 and Samba 2.0.3 for the past week or so. My network is made up of NT servers and 95/98 clients. So far Samba has been running beautifully - I can use my Samba shares just like they are NT shares. My only problem is from time to time my Win98 machine "goes to sleep" and asks me for either a password or an IPC$ password. Generally this happens after a

Hello, I'm having a problem configuring samba (2.0.5a) on a Linux system using NIS+ as the password system. Samba complains that it cannot find the smbpasswd file, which is not surprising as I'm not using one. I tried 'smb password file = passwd.org_dir' that sort of worked, except that it creates a directory called passwd.org_dir from whatever directory I ran the smbd from.

I'm trying to get win9x clients to connect to a Samba 2.0.4b server on FreeBSD 3.2-STABLE. Some of these machines have Windows logins different from the Unix user on the server, and the smb.conf manpage suggests that the "share%username" hack should be used in this case. This seems to work fine on my old 1.9.18p8 server, but not on any of the newer ones. With debug level 5 I see

Item Subject: cc:Mail Text Hi Mike, I got almost the same problem as you when I was using 2.04b on HP-UX 10.20 machine. I can not map to \\servername\sharename to my hpux machine from Win95 successfully when the sharename is different from the client login name. But it's successful on my WinNT. I can not resolve this problem but have a

My systems: rh61, 2.2.14 + smbfs-nls.patch. === 1) Samba seems to override unix permissions in a particular case. I get the very same behavior of: http://us1.samba.org/listproc/samba-technical/February2000/0476.html === 2) browsing behavior: anonymous login There is a different behavior doing smbclient -L -U% if the server is samba or nt/w2k nt wants a correct user/pass pair if guest account

Hi folks, I'am using Samba 2.0.0 on a Linux and a Sun box and i have the following problem: I can log in from a smbclient but not from an NT Client using Security=Domain. 1.) Doubleclick on the machine opens the password dialouge (which should'n appear, beacuse i'am already logged in the domain) Enter my domainusername and password. Window dissapears and appears again and forces me

Greetings: I'm having a couple of problems that I can't seem to resolve (even after searching the Samba archives). 1) When selecting "Shared Directories" from within NT Server Manager, I get the following error: "The Remote Procedure Call Failed" 2) When setting the scope to \\servername with "User Manager for Domains," the scope gets set to domain (the

Every once in a while a user cannot connect to one of two samba servers. Most of the time (but not always), if he waits 15 minutes to an hour, he can connect successfully. Sometimes he can connect to one server, but not the other, which have the same configuration. We are using authentication from the NT server. Samba version 2.0.3 The messages in the log file are are shown below. In this

Hi, I?ve setup a Samba 2.0.5a on a SuSe 6.2 based Linux 2.2.10. I?m trying to integrate the server into our NT domain SF-DOM as described in samba/textdocs/DOMAIN_MEMBER.txt . The described procedures work, but access as domain user is impossible. In the logfile I get: [1999/09/14 11:18:31, 2] smbd/server.c:main(716) Changed root to / [1999/09/14 11:18:31, 2] smbd/reply.c:reply_special(96)

Samba 2.0.3-8 installed via rpm RH5.2 I've set up security = domain. I have 2 errors: 1. I cannot map to a share on the linux PC via name. 2. When I use IP address to map a share, I get the following errors in the log.<machine> [1999/05/14 14:44:24, 0] smbd/uid.c:become_gid(105) Couldn't set effective gid to 99 currently set to (real=0,eff=0) [1999/05/14 14:44:24, 0]

Hello I have this problem with printing to a HP Laser Jet 4L set up on my linux box which is the local samba server for the intranet. I can only print as root or as a user admin user = thatuser. I need to be able to set a password for the printer and only those users to use the printer who know the password. Or a similar solution. As ordinary user Windows98 says:

Hello, I have a fairly large problem mounting a samba share from within linux. The samba server, running Solaris 7 with Samba pre-2.0.7, has a bunch of shares on it, one of which I can mount from Windows, while logged into the ACADIA domain, but I cannot mount that share using smbmount in linux. When I log into windows, I log in with the username 033197m and my password. In smb.conf I have my