similar to: SAMBA digest 1524

I am getting the following level 5 logging for a Win95 PC under user-level sharing that is sharing to the user "backup" with "full-access". Can anyone help me get logged in via smbclient? shokk:/#> smbclient \\\\EOPORTO-DT\\DEPOT -U BACKUP doing parameter os level = 5 doing parameter domain controller = 137.202.xxx.xxx doing parameter wins proxy = yes doing parameter wins

My whole problem as far as samba was concerned was not compiling with DES support *and* that I did compile with FAST_SHARE_MODES. One clue was this in the samba.log. file. I then did a dejanews search for smb_shm_open and came up with that portion of the solution. ERROR smb_shm_open : mmap failed with code 11 The DES portion came from just reading the WinNT.txt file that came with Samba. I

One thing that needs to be mentioned is that for PC backups, the amanda patch that has to be applied to samba requires that you use level 3 logging to see the "Total" line. Also, does anyone know what this error means? smb: \> recurse directory recursion is now on smb: \> dir received 5 entries (eos=1 resume=0) . D 0 Thu Jun 5

I hate to suggest this, but we need to do what has been done on a few other lists that I'm on. We need to close the list off to only people that are members. It's a shame to see so much spam here after seeing it in my personal mailbox all day long. At 11:21 PM 7/24/97 +0000, you wrote: >Date: Thu, 24 Jul 1997 11:14:25 +0200 (MET) >From: Konstantin Eftaxias <kef@eeb.de>

Yes!!!! You just solved a problem I've been having since 1.9.17p1!!!! I didn't realize that CIFS was limited to passthrough authentication for only its domain, so that listing multiple password servers from different domains would not work...the following did. Yeeeehhaaa! Hurm...excuse me. I added to the following in my config to make this work: netbios aliases = unix1 unix2 (not

smbstatus reports the following...that my NT users on this one samba server are connected as the guest user "nobody". All Win95 users are connected under their proper name. Anything I need to change? Samba version 1.9.16p11 Service uid gid pid machine ---------------------------------------------- gdl nobody nogroup 1555 gdl-dt (137.202.211.8) Wed

Can anyone tell me what the error is with recursion here? It is keeping my smbclient from giving AMANDA a sice for the share. Without recursion, and stepping through the directories manually, I can do the dir and get no errors. smb: \> ls received 8 entries (eos=1 resume=0) . D 0 Thu Aug 15 09:19:58 1996 .. D

At the bottom is what I got returned from AMANDA 2.3.0.5 after patching Samba 1.9.16p11 to give estimates. Any idea what I might not have done yet? My disklist reads: shokk \\thor\depot nocomp-user-gnutar To connect successfully to that server with smbclient, I have to do this, giving the same password that I now have in /etc/amandapass: smbclient \\\\THOR\\DEPOT -U BACKUP Also, the

Ernie, Thanks for the great info.. Based on what you were seeing, would you suspect that part of the problem is with the combination of NT and the 3com card (3c595)? Currently, we are ONLY seeing this under NT Workstation (not server) and almost all of our machines have this same 3com 3c595 card (only if using 100BaseT).. -- Rick -----Original Message----- From: Ernie Oporto

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

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

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]

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

We are seeing erratic behaviour from Samba for connecting Unix drives to an NT terminal Server. Samba version 2.0.6 Solaris 2.6 NT Server 4.0 Terminal Server Edition with service pack 4 running WinCenter NIS Logon Utility. The NT server is not part of a domain and uses the WinCenter Logon Utility to authenticate username and passwords from my Unix NIS server. Samba is set up for server level

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.

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

I've had samba running cleanly on an HP-UX 11.0 system for many months, with "DOMAIN" security and one-to-one account name mapping. A few days ago I started getting password prompts on connection, and messages like this in the log files... [2003/01/02 15:46:36, 0] rpc_parse/parse_prs.c:(316) prs_mem_get: reading data of size 60 would overrun buffer. [2003/01/02 15:46:36, 0]

Hi, It's been a while since I created my smbpasswd file, and therefore it is no longer in synch with my Unix file. I've added and removed users over time, and now I need a way to update the 'smbpasswd' file without losing the encrypted passwords that are already in place (ie. I don't want to just run 'makesmbpasswd.sh' again). So, I've written the