similar to: BUG: Re: Cannot use smbpasswd for new user (1.9.18p7)

I get these messages when compiling on a Sun Sparc 5 running Solaris 2.6: Compiling ipc.c ipc.c: In fonction `api_RNetServerEnum': ipc.c:1194: warning: passing arg 4 of `qsort' from incompatible pointer type Compiling nmbd_incomingrequests.c nmbd_incomingrequests.c: In function `process_node_status_request': nmbd_incomingrequests.c:380: warning: passing arg 4 of `qsort' from

More information on the problem. A couple of days ago I posted a request for help for this error msg terre{testgb}73: smbpasswd Old SMB password: New SMB password: Retype new SMB password: /opt/samba/bin/smbpasswd: machine 127.0.0.1 rejected the session setup. Error was : ERRSRV - ERRbadpw (Bad password - name/password pair in a Tree Connect or Session Setup are invalid.). This happens only

Hi Samba admins, I was wondering if any of you had problems with your automounter with Samba ? My environment is: Samba 1.9.17p4 on a Sparc20 running Solaris 2.5.1 with the home directories defined in the NIS+ tables. The client are all Win95 PC. Lately, we lose the automounter on the Sun host. Even logged in as root on the console I cannot 'cd' to the /home directory. We have

Since I upgraded from 1.9.18p3 to p4 (Friday May 8) the users cannot execute the smbpasswd command. I would appreciate any help as soon as possible plase. Thank you. Here is the output we get: terre{testgb}65: smbpasswd Old SMB password: New SMB password: Retype new SMB password: smbpasswd: machine 127.0.0.1 rejected the session request. Error was : code 131. --

Hi Samba admins, I have a mysterious problems with printers. When you are in a Windows application and you click on the icon to print, you get no error messages anywhere but no paper output. You just click again (sometime you have to repeat twice) and finally it prints (one copy). It happens to everyone on all PC on all printers. PC are Windows 95, printers are network HP Laserjets setup

Recently (after updating from 1.9.18p3 to p4) I couldn't use smbpasswd. After adding the address 127.0.0.1 in the 'allow hosts' it was OK. Now some users (on the same machine) can use it, others not. Thet get this: terre{vendetm}82: smbpasswd Old SMB password: New SMB password: Retype new SMB password: /opt/samba/bin/smbpasswd: machine 127.0.0.1 rejected the session setup. Error

JdL> I've always been afraid to ask, but here goes... JdL> What's the advantage of GUEST_SESSSETUP being a compile time parameter, JdL> instead of having it as an smb.conf parameter? I'd like to second this question! Also, just in case that it will not become an smb.conf parameter: can't it be added as a comment to the Makefile (probably near the comments to

Pishotta.Fred@Mayo.Edu wrote: > > Yes, I got those too, on an identical platform, but with p6. Things seem > to work, but it would be comforting to know if this is a non-issue. > > -- Fred P. > > On Wed, 13 May 1998, SI-Gaetan Boudreau wrote: > > > I get these messages when compiling on a Sun Sparc 5 running Solaris 2.6: > > > > Compiling ipc.c >

I've got a user here that is unable to connect to any of the Samba shares that are available -- in fact, she doesn't even get past the username / password validation step. The message that Samba puts into the logs is as follows : NT Password did not match ! Defaulting to Lanman To narrow down the problem, I logged onto her machine as myself (from the same domain also) and then got onto

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

Andrej Borsenkow wrote: > Current aside, the February2000 was last modified on February, 2nd. Last > message there is http://us1.samba.org/listproc/samba/February2000/0042.html > The same is true for samba-technical, samba-cvs (did not check others) > Or is it a problem of my proxy? I don't think so, I see the same thing. Samba web-folks, could you check this out, please?

I just test samba 2.0.3 on Solaris 2.6/Sparc no NIS+. I just do an smbpasswd -a frank it woked, but it is not possible to change the password except i'm root. The only thing i get is: [1999/03/30 11:37:38, 1] smbd/server.c:(614) smbd version 2.0.3 started. Copyright Andrew Tridgell 1992-1998 [1999/03/30 11:37:38, 1] smbd/files.c:(219) file_init: Information only: requested 10000 open

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)

I am using a syntax like coxph(Surv(start, stop, event) ~ X, data) to estimate the effect of X, which may change at each measurement (every 6 months). Is there anyone who knows a way to test the proportional hazard assumption in that case? Thank you in advance Jean-François Boudreau Sherbrooke University [[alternative HTML version deleted]]

Hello, I finally switched to the samba-1.9.18p4, and got all my files on this server. But now I have a big problem, all our NT machines can't access the server. They tell wrong user or password. In the debugging mode I see, that the NT machines come to the server and find the right user, then they tell me: lp_file_list_changed() file /usr/local/samba/lib/smb.conf ->

Hi all, I'am trying to set up my Samba server to use DOMAIN auth. I followed the instructions in the "security = domain in Samba 2.x" and had good results. Used this command to join the domain "smbpasswd -j DOM -r DOMPDC -UAdministrator%password" and I got the result "smbpasswd: Joined domain DOM." I added the entries into the configuration file to complete

Hello, I want to set up my Samba-servers to use encrypted passwords (smbpasswd). First I enabled "Update Encrypted" to set the correct password and then I disabled "Update encrypted" and enabled "encrypted passwords". When I map up a share from the client everything is working ok, but in the log I have the following: [1999/11/09 21:37:10, 1] smbd/password.c:(532)

Hello from a neophyte! Is there a diagnostic programme which can be run to determine if there are any faults in Samba 2.2.3a? I cannot connect from Win XP to my rev/b iMac (suddenly, maybe 'upgrade' to 10.3.4 had some effect) and the smb crashlog (shown below) has a pile of stuff which is incomprehensible to me. Secondly, how does one upgrade to another version of Samba and is this

Hi all.. Happy holidays! I am having trouble all of the sudden with samba. I was running an older version and I suddenly couldn't connect the mapped drives this morning (yesterday it worked fine) so I downloaded the lastest samba and compiled and installed it. Now when I try to connect to a public share windows keeps asking me for a password. Also, if I use "smbclient -L

Hi, I''ve got a weird 500 error that I can''t fix. I''m using scgi with Apache2 on Fedora core 2. Status: 500 Internal Server Error Even when I launch dispatch.cgi from the command line, I get the 500 error. I don''t have any log entry written so I''m completely blind. I know that the app is fine because I can run it in the console and get my records from