I can't get smbclient connecting to old samba server (unknown version inside a sagecom NAS): smbclient -L gateway -N -I 192.168.25.1 -d10 INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10 rpc_cli: 10 passdb: 10 sam: 10 auth: 10 winbind: 10 vfs: 10 idmap: 10 quota: 10 acls: 10 locking: 10 msdfs: 10 dmapi: 10 registry: 10 scavenger: 10 dns: 10 ldb: 10 lp_load_ex: refreshing parameters Initialising global parameters rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10 rpc_cli: 10 passdb: 10 sam: 10 auth: 10 winbind: 10 vfs: 10 idmap: 10 quota: 10 acls: 10 locking: 10 msdfs: 10 dmapi: 10 registry: 10 scavenger: 10 dns: 10 ldb: 10 params.c:OpenConfFile() - Unable to open configuration file "/etc/samba/smb.conf": Arquivo ou diretório não encontrado pm_process() returned No lp_servicenumber: couldn't find homes smbclient: Can't load /etc/samba/smb.conf - run testparm to debug it added interface wlan0 ip=192.168.25.3 bcast=192.168.25.255 netmask=255.255.255.0 added interface virbr0 ip=192.168.122.1 bcast=192.168.122.255 netmask=255.255.255.0 Netbios name list:- my_netbios_names[0]="POLESBOOK" Client started (version 4.1.7-Debian). Connecting to 192.168.25.1 at port 445 Connecting to 192.168.25.1 at port 139 Socket options: SO_KEEPALIVE = 0 SO_REUSEADDR = 0 SO_BROADCAST = 0 TCP_NODELAY = 1 TCP_KEEPCNT = 9 TCP_KEEPIDLE = 7200 TCP_KEEPINTVL = 75 IPTOS_LOWDELAY = 0 IPTOS_THROUGHPUT = 0 SO_REUSEPORT = 0 SO_SNDBUF = 87040 SO_RCVBUF = 372480 SO_SNDLOWAT = 1 SO_RCVLOWAT = 1 SO_SNDTIMEO = 0 SO_RCVTIMEO = 0 TCP_QUICKACK = 1 TCP_DEFER_ACCEPT = 0 session request ok convert_string_talloc: Conversion error: Incomplete multibyte sequence() Conversion error: Incomplete multibyte sequence() protocol negotiation failed: NT_STATUS_INVALID_PARAMETER
this works for me, there might be some protocol settings that you have to tune to make you error do away but this is most likely not a bug. Please consult the mailing list for further help if you don't get this to work.