similar to: SUMMARY: Bad Password

Hello all, I have asked this before but I have not found a solution. I have one Dec Alpha running Tru-64-UNIX, formerly DecUNIX, v4.0d. I am running 2.0.2 and have run 2.0.0 with no problems. SWAT works fine on it also. I have 2 other systems, one running v4.0d and the other running v4.0b. On those systems I can connect to guest volumes just fine but anything that requires a password fails

Hello all, In addition to what I wrote this morning I just ran Test 8 from DIAGNOSIS.txt and it worked but Test 9 didn't. I got invalid password error. I am not running shadow passwords and passwords are not encrypted. Please HELP!!!! I have asked this before but I have not found a solution. I have one Dec Alpha running Tru-64-UNIX, formerly DecUNIX, v4.0d. I am running 2.0.2 and have run

I have gotten Samba to work but them came up with a problem. It is working on a mchine with the class C address 198.xxx.xxx.xxx. Any PC's with that on that IP address can see the server just fine. However, we also have another class C 207.xxx.xxx.xxx and folks on that one cannot see the server. We have seen this problem before and NetBeui solved that one. Any ideas? Thanks in advance.

Samba Gurus: I just upgraded from samba-1.9.15p8 to samba-1.9.18p8 on one of our Sun boxes (Solaris 2.5.1). When I try to connect to the samba server from another machine with smbclient I get the following error message: smbclient -L odin Added interface ip=192.10.11.32 bcast=192.10.11.255 nmask=255.255.255.0 Server time is Wed Oct 28 15:17:47 1998 Timezone is UTC-5.0 Password: Session setup

I would like to see those of us who send an inquiry to this list also send a summary of what fixed the problem so that someone in the future could find the answer. I searched archives for an answer and only found questions. Since a lot of folks reply ot individuals then even the replies don't end up in the archives and so it would be nice if summaries were sent to the list. Anyway, enough

We are going to install a new remote access device for students to dial into our network. We are trying to decide what type of authentication to use and how it will impact Samba and out current NT stuff we have going. I know little to nothing about NT. We are running Samba on a Compaq Alpha running Tru64-UNIX. Currently Samba is set up to authenticate against the passwd file of our Alpha. We

This isn't strictly a Samba question but I'll ask it anyway. If someone can point me in a better direction I would appreciate it. We are going to install a new remote access device for students to dial into our network. We are trying to decide what type of authentication to use and how it will impact Samba and out current NT stuff we have going. I know little to nothing about NT. We

Running Samba 2.0.3 on a Digital Unix 4.0D system. All functions of the new Samba version appear to run properly (previously ran 1.9.15) with exception of users being able to change their own Samba password (root is only able to change password on behalf of users). Following is permissions assigned to smbpasswd: -rwxr-xr-x 1 root system 901120 Mar 31 16:06 smbpasswd Following is

Hi, I have four computers on a home network: A) A 2004-era debian machine B) A 2005-era debian machine C) A 2007 xandros machine D) A 2007 kubuntu machine The problem: Machines B and C allow users to mount samba shares, but machines A and D don't. I get: smbmount //spk/homes ~/mnt Password: 3573: tree connect failed: ERRSRV - ERRbadpw (Bad password - name/password pair in a Tree Connect

Hello! Really, this problem exists since v 3.0. smbtar can't connect to win98 password protected share: server is korotkova share is SBRF\\ tar args is tape is tar.out blocksize is [2004/01/09 14:17:54, 0] param/loadparm.c:map_parameter(2423) Unknown parameter encountered: "client code page" [2004/01/09 14:17:54, 0] param/loadparm.c:lp_do_parameter(3151) Ignoring

I'm having a problem with samba validating against the /etc/password file with Digital Unix. We have 2 Alpha systems, one running unix 4.0d, the other running 4.0e. The 4.0d system is using enhanced security, the 4.0e system is not (the major application for that machine won't run with enhanced security). I have samba 2.0.2 installed on both machines. There are no problems with the

Well I figured it out.. did not know that I could make a host file on the winblows client. I knew about the lmhosts file however.. this is a great list.. thanks to all.. *++++++++++++++++++++++++++++++++++++++* * Les Higger ITAF , * Local Area Network Coord. * lhigger@lausd.k12.ca.us * Francisco Bravo Medical Magnet High School * Los Angeles

Jens Rieck wrote: >>Can anyone help me? >> >>I have Samba 2.0.5a running on SuSE Linux 6.0 (2.0.36) and >>Windows NT Server 4.0 SP4 (PDC). >> >>When I try to do a "smbclient -L MYUNIX" (according to the trouble >>shooting guide) I get the following message: >> >>Addes interface ip=195.90.254.xxx bcast=195.90.254.255

> Hi, > I'm trying to setup Samba 2.0.2 in security=domain mode. My machine name > (softy) has been added as a member of the domain (waterloo). The > smbpasswd -J option keeps giving me an error: > > /usr/local/samba/var# ../bin/smbpasswd -D 3 -j WATERLOO > resolve_name: Attempting lmhosts lookup for name 53SVR1<0x20> > resolve_name: Attempting host lookup for

G'Day everyone, We are new to SAMBA and are having problems with initial configuration of SAMBA Version 1.9.18 on DigitalUnix 4.0B on a Digital AlphaServer 4100. If anyone can help us, we would be greatly appreciative. The installation and compilation all went OK. Following the points in DIAGNOSIS.TXT. Steps 1 to 6 all go OK. Step 7 says... TEST 7: -------

Hi all together, all answers to my first posting didn't help to solve my problem. Maybe this can help you. When I'm doing: smbclient -L MYLINUX -U MYUSER I get the following message: Added interface ip=195.90.254.xxx broadcast=295.90.254.255 nmask=255.255.255.0 Password: <enter password for myuser> Domain=[MYDOMAIN] OS=[Unix] Server=[Samba 2.0.5a] Tree connect failed: ERRSRV -

Can anyone help me? I have Samba 2.0.5a running on SuSE Linux 6.0 (2.0.36) and Windows NT Server 4.0 SP4 (PDC). When I try to do a "smbclient -L MYUNIX" (according to the trouble shooting guide) I get the following message: Addes interface ip=195.90.254.xxx bcast=195.90.254.255 nmask=255.255.255.0 Password: Domain=[MYDOMAIN] OS=[Unix] Server=[Samba 2.0.5a] tree connect failed: ERRSRV

Dear Ladies and Gentlemen, I would dearly like to access CIFs directories on a NetApp filer (850) with Linux/*ix SMB clients. Unfortunately, smbclient from Samba 2.2.7 fails with a session setup request tsitc> /usr/local/samba/bin/smbclient //cbrnas01/Stan3$ -U stan3%PPPP added interface ip=10.0.100.252 bcast=10.255.255.255 nmask=255.0.0.0 session setup failed: ERRSRV - ERRbadpw (Bad

Hello All, I have two computers. I want the Linux box to act as an SMB server for the NT box. I only need plain text passwords right now. I modified the NT Registry to support this. But I can't even do a loopback on the Linux box with smbclient. See below: [gsw@pagestreet ~]$ smbclient -L pagestreet Added interface ip=192.168.0.1 bcast=192.168.0.255 nmask=255.255.255.0 Password:

Hello everybody, I'm using Samba Version 1.9.17p3 on an IRIX 6.2-based workstation and because I still have the same problem with the shares on the PC-box (I'll send my report to samba-bugs too), I need workaround in order to get the smbtar process running. Here's my problem (I hope it's not too long): I can see what's being shared by the Win95 box where I want to make the