similar to: HELP -- upgrade to 1.9.18p8 causing print/disk trouble ..."

I recently upgraded all our site's samba servers to 1.9.18p8, and I seem to be having many strange problems where they didn't exist before. I haven't made any changes to smb.conf. The biggest trouble I seem to have is that people can no longer access printers ... NT/95 just gives a generic "path to server not available" message. Some nodes even have trouble connecting

I have a problem with new version (1.9.18p8) of SAMBA and username mapping. Configuration: WindowsNT 4.0 Workstation + SP1 WindowsNT domain - NTEP01 is PDC Digital UNIX 3.2C Username on NT: Babor Username on UNIX: baborl In SMB.CONF I have following lines: [global] security = server password server = NTEP01 username map = /usr/local/samba/lib/username.map username.map: baborl = babor

Hi All, Sorry to be posting this :-(, but if you're using the 'username map' parameter with Samba 1.9.18p8, here's a small patch you may need. Without it the username map will work once per smbd and then refuse to map subsequent names. This isn't a big problem as normally, on a single user NT or 95 system, username map will only be called once per session (in the

The Samba-Team is pleased to make known that binary packages for samba-1.9.18p8 are now available for: Red Hat Linux 4.2, 5.0 and 5.1 (Intel) Red Hat Linux 5.1 (alpha) Caldera Open Linux 1.2 (Intel) Sun Solaris x86 2.6 SCO Open Server 5.04 Slackware Linux 3.4 Digital Alpha Unix 4.0d (OSF1) We are hoping that others will contribute binary files for the remaining major platforms will be available

I've recently installed Version 1.9.18p8 on a V2.6 Solaris x86 box. This system has an 8GB disk that I'm sharing out using Samba. After I map this share to a drive letter on my V4 NTWS, the properties for this drive reports that it is only 4GB. Is this a known "bug"? Other than the bogus information, will it have any adverse affects after the disk fills up to exceed 4GB used?

I'm having problems with the username map feature of Samba. Everything was running fine in 1.9.18p7. After the upgrade to 1.9.18p8, the mapping no longer occurs, and I see errors in the log file: password server CSUNTS rejected the password get_smbpwd_entry: unable to open file /usr/local/samba/private/smbpasswd I tried going back to 1.9.18p7, and sure enough things work like a charm. I

Ronny Blomme <Ronny.Blomme@elis.rug.ac.be> writes: > The default configuration for smbclient in samba-1.9.18p8 is to send > verbose output to stdout. The output sent to tape is a mix of this > verbose output and the tar-file => corrupt tar file on tape The attached patch for SAMBA fixes this problem, preventing log messages from being printed to stdout if the tar-file is

I trying to compile samba-1.9.18p8 on a SunOS 5.5.1 machine using gcc 2.7.2. I setup the makefile to use the SunOS5 defines... # This is for SUNOS5.4 and later (also known as Solaris 2.4 and later) # contributed by Andrew.Tridgell@anu.edu.au FLAGSM = -DSUNOS5 -DSHADOW_PWD -DNETGROUP -DFAST_SHARE_MODES LIBSM = -lsocket -lnsl AWK = nawk I get the following compiler error... # make Using CFLAGS =

Hi all, Am I the only person to have fallen over the following 'gotcha' ? Upgraded to 1.9.18p8 from 19.9.17p5 on Friday. Came in this morning to discover all Printing had died. Eventually tracked this down to the 'printcap name' setting in Samba jad changed. It default was '/etc/printcap' (it must have been as printing was fine up 17p5 and all previous versions).

I installed samba-1.9.18p8 on our RS6000 running AIX: 4.2.1.0 with xlC: 3.1.4.0. There are 5 errors reported in "util.c" and 2 errors reported in "server.c", all about "Function argument assignment between types "unsigned long*" and "int*" is not allowed." I use encrypted passwords and have a smbpasswd password file in the ususal place. I can

I upgraded from Samba 1.9.18p2 to Samba 1.9.18p8 on Solaris 2.6 and now browsing does not work for WIN95 (haven't tried NT), nor does Network Neighborhood even show the server. The builds for p2 and p8 are standard, the only difference in the user changeable portion of the makefile being the location of the man page directory. I am using the same smb.conf file for both versions, and the

Hi there, I've just tripped over a problem I thought only existed in WfWg3.11. On Win95 clients connecting to a 1.9.18p8 Samba server (IRIX 5.3) the first logon dialog box seems to have a problem with mixed-case passwords. If I have a lower case password, then I can just enter it in the Win95 'Microsoft Network' logon dialog at startup, and all the shares are reconnected. If I

Having tried all the hints in DIAGNOSIS.txt, and having no success, and being unable to decrypt the error codes (does anyone have a list of these?) I send this to you all in the hope you can figure it out. FYI: I'm running 1.9.18p8, upgraded from 1.9.16p9. I got the exact same errors on both versions. I'm running debug level 5 to try and find some clue to the problem. I did have samba

Hello all, we're experiencing some problems with smbpasswd when using the latest samba version (1.9.18p8). When new people arrive, they are added to the smbpasswd file without a password and requested to change it asap. But unfortunately, it seems to be impossible to change a null password to something else :-( The last couple of releases have changed some things in this area. I went

Hi, I recently upgraded to 1.9.18p8 on Solaris 2.6 and am having a problem with writable services other than [homes]. [apps] is one that's causing the most difficulty. Users are being logged into writable shares as user 'nobody' and are not permitted write access. The shares are set as 'writable' and 'write ok'. host equiv does not have an effect either. All hosts

Hello all, after hacking around to get smbmount and smbmnt to get compiled on RedHat-5.1 I'm unable to use them. With the stock RedHat kernel and the old smbmount I used the following command line: smbmount //rho/homes /mnt/smb/homes -c pc-topaz -U pommnitz -u pommnitz -P mypassword Everything works fine this way (with 2.0.34). With 2.1.107 the new smbmount is required. As I said, after some

I get the following compile error when compiling p8 with p4 Makefile: Linking smbd util.o: In function `check_log_size': util.o(.text+0x2cc): undefined reference to `slprintf' util.o: In function `name_mangle': util.o(.text+0x94f): undefined reference to `slprintf' util.o: In function `standard_sub_basic': util.o(.text+0x4c9e): undefined reference to `slprintf' util.o: In

I recently installed samba 1.9.18p8. Since then, we get the following error: "No domain server was available to validate your password. You may not be able to gain access to some network resources." after the server has been running for >48 hours. If I stop and restart the server, everything is ok again. Our samba server is a Sun Ultra 2170 running Solaris 2.5.1. Any help will

Hi all, I'm extremely puzzled by the behaviour of one of my Samba servers. It's been working fine for yonks, and this morning (abuout 11:32) it just stopped. (mostly) Connecting to shares still works. Navigating the tree till works. Changing (DOS) attributes still works. But actually opening files and reading the contents doesn't work. The client just times out (Win 3.11, and

I'm running Samba 1.9.18p8 on a RedHat5.1 system. Shares are going cleanly, but domain logons are not. I have an NT box, but as it is for a dedicated app, not for servers, I simply shut it down while testing samba's PDC functionality. I'll turn PDC off on the NT box as soon as I get samba doing domain controlling. I recently posted this problem with subject line: Samba 1.9.18p7-2