similar to: a bug in smbmount

Hello all This patch tries to remove a few bugs from smbmount. It would be nice to get some testing+feedback on this from others using smbmount and possibly get these things fixed for the next release of samba. It does the following: * Change lib/debug.c to allow changing your mind on being interactive. A second call to setup_logging should now replace the effects of a previous call. (hmm,

(using samba-2.0.7 on Debian Linux 2.2.15) Hi, I'm wondering how do I get around the problem when you smbmount a share on a win32 machine and that machine reboots, the mount becomes a blackhole. If you attempt an 'ls', 'df' or anything that would access that mount point the program then goes into a state of void and cannot be killed, leaving the proc open until reboot

Hi Everyone. I'm still having that problem that my samba cannot backup more than 2 GB onto a Windows share (on a Win2K box) (see messages earlier in this forum - I have to backup a 66 GB file out of database). Setting loglevel of SAMBA to "2" I received the following (for the time running the backup up to the broken connection): ...... [2003/11/18 11:39:47, 3]

RH6.0. I downloaded: samba-2.0.4b-19990527.src.rpm Follwing the instrucions in README.smbmount, I edited samba2.spec to add 1) --with-smbmount to configure 2) the smbmount related files and man pages to the install and files sections. rpm -ba samba2.spec stops with: ..... Compiling smbd/ssl.c with -fpic Linking shared library bin/smbwrapper.so Compiling client/smbmount.c client/smbmount.c: In

Hi all, I'm trying to build 2.0.3 and make gives me the following error: Compiling client/smbmount.c client/smbmount.c: In function `close_our_files': client/smbmount.c:242: `NR_OPEN' undeclared (first use in this function) client/smbmount.c:242: (Each undeclared identifier is reported only once client/smbmount.c:242: for each function it appears in.) make: ***

Warning this will be a lengthy post. I?ve been beating my head on my desk for days now. I have a Samba PDC in an NT4 domain. I have several domain member servers and a non domain member server. Versions really don?t matter but for the sake of argument the systems that are ?working? are all CENTOS 4.7 systems using 3.0.28 Samba. My procedure is this: I mount a Domain member share on the non

It appears that openssh has inherited the dos attack that ssh is susceptible to. This has been discussed on Bugtraq (see http://securityportal.com/list-archive/bugtraq/1999/Sep/0124.html for the thread). There does not appear to be an official for ssh. Attached below is a simple, proof of concept, patch that adds a MaxConnections to sshd_config that sets the maximum number of simultaneous

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am on FreeBSD 8-current (AMD64) and am attempting to get wine compiled and installed... several issues: 1. Due to item 2 I can't build wine but I have vista64 installed on a mounted partition can I just tell wine to use it's dll's... if so how? 2. When I do a make (I am not installing as a port) I get: actxprxy_servprov_p.c:272:2:

Changes: * Removed utimes() posix hack since scp.c moved to utimes() * Fixed waitpid() to be more proper. It was driving me nuts. * Made setsid() a #define in next-posix.h * Removed WCOREDUMP() from next-posix.h since we really don't support it and now #ifdef .. #else .. #endif around the single place it was used. * Fixed typecasting issue in sshd.c with sizeof() returning "long

Hi, Has anybody produced diffs for openssh-2.3.0p1 for the rsa keyexchange problem that Core-SDI described ? ( I noticed that fix is already in openbsd tree ). -Jarno -- Jarno Huuskonen - System Administrator | Jarno.Huuskonen at uku.fi University of Kuopio - Computer Center | Work: +358 17 162822 PO BOX 1627, 70211 Kuopio, Finland | Mobile: +358 40 5388169

Hello all, I'm having a problem with smbclient after an upgrade from 3.0.37 to 3.5.3 (I also tested 3.5.11 and 3.6.0). The client uses a command similar to: tar -cz /some/directory | smbclient '\\server_ip\share' -N -c 'put - "\directory\filename"' After that the client checks the exit status to determine if the transfer succeeded or failed. The server

Patch against samba 3.0.0 client/client.c Mainly for -L parameter options 1.) Add a configurable connection delay. The default is too long. Add items to long_options of poptOption for help message, however I just put something "i.e. CONNSETUP" to the last parameter of long_options. It seems for use of documentation ???? 2.) Remark the code that require list_servers must using port

Fellow Samba-ists, I read about smbmount But I cannot find it in 2.04b Where and how do I use it ? Regards Terence

Hi all, Sorry for this question which has certainely already been answered, but I could not find info in the list nor in the wiki. From my Debian laptop running testing (samba 4.9.5) and with an empty smb.conf (I wanted to be sure that only default values are used), I can not browse shares of a Windows 10 machine (sorry, Thunderbird splits some lines): smbclient -L 192.168.122.200 Unable to

Shanks for the hint! Very strange that the default is only to use a deprecated protocol… Anyway, this option has no effect on this issue… Yvan Le 31/05/2019 à 18:53, Kris Lou via samba a écrit : > Most likely, your Windows 10 (file server) is disallowing SMB1 connections, > which is the default for smbclient. > > You can force smbclient to use a higher protocol with "smbclient

Hi All, First time poster. Not a unix pro. We had samba client installed (v. 3.6) and working to run a single file print command. smbclient --debuglevel=1 --log-basename=/mnt/autofs/logs/print/ -U bbldtl\\adminuser //$3/$2 'obscured-password' --command "print $1" | tee -a /mnt/autofs/logs/print/print.log It would output [2019/07/04 04:27:36, 0]

Hi everyone: I'll try to be both succinct and accurate here: Attempting to get a directory listing from a DFS export fails using "Samba 3.0", but works fine on windows (XP, 2K, NT4). This happens via smbclient and via "smbmount"ed directories. I had no problem joining this domain, and the user that I am connecting as has permissions to open these folders (I checked

Hi everyone: I'd appreciate any help here... Using smbclient I can change into a directory within a DFS share, but when I attempt to list it's contents, I receive the subject error. I can view the directory (folder) from a win client using the same credentials. I already posted much of my configuration, sans the "smb.conf", although if anyone suspects that there are

Most likely, your Windows 10 (file server) is disallowing SMB1 connections, which is the default for smbclient. You can force smbclient to use a higher protocol with "smbclient -m SMB2" https://www.samba.org/samba/docs/current/man-html/smbclient.1.html Kris Lou klou at themusiclink.net On Fri, May 31, 2019 at 9:45 AM Yvan Masson via samba <samba at lists.samba.org> wrote:

Hi, I am very new to mailing lists so please excuse any mistakes I make regarding ettiquete etc. On a home network (Windows/Apple/Lunux) everybody has co-operated happily. I recently swapped my Linux system from Mint (Mate) to Debian (KDE) Buster. I can no longer access the Windows machine's printer form Debian. I have tried many things and done a great deal of googling but cannot seem to