similar to: Troubles with NT domain logons ?

Could anyone tell me what I may be doing wrong here? I'm using samba-1.9.18p8 on a Linux 2.0.32 box, RedHat 5.0 install. I can descend into this share from a WinNT box just fine, but get the following error messages from a Win95 box. Thank you all in advance, -Jon Charette --------- Start log at debug level 4 ---------------------- 1998/07/08 13:20:22 Transaction 52 of length 47 switch

Greetings! We've got a neat little problem running Samba 1.9.18p8 on Solaris x86 2.5.1 and AFS on a dual-processor Dell PowerEdge 2200 w/ 128M RAM. The machine has 11M of free real memory and 417M of free swap according to "top". Every once in a while (there goes one now...) an "smbd" process will attempt to consume all available processing time it can. We recompiled

Hello all, I have a printing problem with NT, Samba 1.9.18p8 and Debian Linux 1.3 (Kernel 2.0.32). I defined a printer share, which works fine with Win95, but it does not print with NT 4.0 SP3 and NT 3.51. After installing the "EnablePlainTextPassword" registry entry NT4.0 is able to browse, connect and use a file system share on the printserver, but it can not print to the same

Hello, I try samba 3.0.2a with Mandrake 10 Official release. It works pretty well but one exception, "dotless i", a Turkish character. The other Turkish characters works. If any filename contains dotless i, this file/directory is inaccessible from win98 clients. I setup with Turkish locale. And i run samba with "export LC_ALL=C". Otherwise it runs, but doesn't share

I've searched around throught the documentation, but I can't find anything relating to the error message "Supplied buffer too small in API command". I have SAMBA installed on seven HP 9000 boxes running HP_UX 10.20, and they are working fine. I installed SAMBA on another box yesterday using a cloned smb.conf file, and now I can't connect from Windows 95 to the new box.

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

Hello Samba Users, I cannot change a user's Samba password from a Windoze client or from the Unix Samba server when "unix password sync = True". Any ideas what/where I screwed up? AtDhVaAnNkCsE - Samba version 1.9.18p10 on a Solaris 2.5 box. - compiled with the following flags: FLAGSM = -DSUNOS5 -DSHADOW_PWD -DNETGROUP -DFAST_SHARE_MODES -DALLOW_CHANGE_PASSWORD - global

Hello, A few months ago the distribution I use (Debian Testing) moved from Samba 3 to Samba 4 - I started seeing a lot of problems. Since then there are two bugs I find occurring on a regular basis: 1. Consistent dumping core on a regular basis (very rarely, if ever occurred with Samba 3) a. $ ls -ltr *core*smbd* |wc -l b. 1297 c. $ du -ach *core*smbd*|tail -n 1

Our computers in our office ceased being able to print to a shared cups printer today. Could not find the cause. Seems the smbd processes are dying. Below is the stack trace produced by gdb bt full. The Samba 'panic action' script, /usr/share/samba/panic-action, was called for pid 5839 (/usr/opt/samba-3.0.2rc2/sbin/smbd). 0x40150a59 in wait4 () from /lib/libc.so.6 #0 0x40150a59 in

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

Hi, I've a problem, with a cpu load (>66% while running a separate virusscanner with another 30%) of one of my smbd processes. It only happens occasionally (approx. 2 times in the last 4 weeks). The backtrace is attached. It seems to me, that smbd is looking for colorlaser5quota. This printer isn't attached anymore to the server and neither cups nor samba configuration files include a

Since upgrading to 3.6.1 in Debian testing, I receive a panic/segfault message with each print job. Printing succeeds and continues to work, but an email with the info below is sent each time. The system is standalone. Kernel is 3.1.0-1-686-pae, and the system is fully updated. testparm returns no errors. Does this mean anything to anyone? Dale [Thread debugging using libthread_db

Hello again, I would like to thank Giant Wang and Miquel Bonastre for their responses to my query in "Samba Digest 1734" regarding simultaneous passwd changing for users via Samba. Their comments were helpful, but have not solved the problem. For those who do not have a back log of the Digests, the problem is that with unix password sync=yes, users are not able to change their own

Unix solaris 10 samba 3.0.21b I am having a problem starting samba. I originally installed and started samba on a computer successfully, but realised I did not have the correct permissioning for the shared directory. I tried "chown" on the directory (in the path of the smb.conf file) whilst samba was still running. I then killed nmbd and smbd and tried re-starting everything.

Hi, I'm using latest Samba version 2.2.8a and are preparing a production server system, which was working fine recently in development stage. My system is basically a SuSE 8.2 Pro with some of the applications being installed manually from source. I'm using CUPS as printer backend and add printers to the system using lpadmin Afterwards I make a reload (or even a restart) of smbd and

Greetings, Similar to the other CUPS thread, but not the same. Samba 2.2.5 built on a Sparc Solaris 9 box with Cups 1.1.5. I've set up Samba to print with Cups as outlined in the docs. I am able to download the generic Adobe print driver to my Windows 2000 clients but the Windows 98 clients are asking for a local driver to be installed. Looking at verbose output from cupsaddsmb,

Hi, I saw your message on the SAMBA web site and thought you might have heard of this problem and a possible solution. I'm running Samba 1.9.17p5 on a SUN Ultra-1 and it appears that the lprm command is being completely ignored by the system, which seems to be inserting an lpstat -o command instead. I did a level 5 debug and have been looking over the C code pretty closely but can't see

hi, i wondered why i can still list my shares with "smbclient -NL localip", security = SHARE ....i just disable the user nobody? the log: [2005/11/27 12:05:48, 2] lib/interface.c:add_interface(81) added interface ip=192.168.10.66 bcast=192.168.10.255 nmask=255.255.255.0 [2005/11/27 12:05:48, 2] lib/interface.c:add_interface(81) added interface ip=127.0.0.1 bcast=127.255.255.255

I'd like to change Samba passwords from win95 and NT4 clients. I use security=user. I don't give shell access to every user, so they can't use smbpasswd. I've tested from a win95 client with the precompiled samba-2.0.4b.i386.rpm: net pass \\greg greg test1 test2 I'd used smbpasswd to change greg's password to test1 on host greg prior to this. Here's the smbpasswd

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