similar to: smbclient -t flag doesn't seem to work

Hi, If this has been answered already please point me to the right place. The thing is I am having problems getting smbclient from samba-2.2.8a package to work properly. I have used Red Hat 9, Suse 8 and Gentoo before migrating to LFS 5.0. In all earlier distributions it worked fine so I think the problem might be LFS specific though my mind refuses to believe this. Synopsis of the problem:

I am running smbclient: Version 3.0.6-SUSE (SLES 8.0) I am still unable to see any printer shares with names longer than 12 characters. Does anyone have an idea how to resolve this? [Please cc: me with any replies] -Nathan On Fri, 22 Nov 2002, Diana McKenna wrote: > If no one has any further information on this, I'll submit this as a bug. This is a known limitation of the

Hi All, I've run into a strange problem, which so far I haven't seen reported by anyone else recently. A while back I set up a Linux box (SUSE 9.2) to authenticate (using kerberos) against a w2k3 AD domain. A nice side effect of this was that I could use "smbclient -k" and save typing in my password again. I didn't have cause to use smbclient for some time, until the other

I cannot get smbclient (or smbmount) to display iso8859-1 characters (umlauts) correctly... I'm trying to access an NT 4.0 service from a Linux client using smbclient 2.0.6 My settings in /etc/smb.conf are client codepage = 850 character set = ISO8859-1 valid chars = ?:? ?:? ?:? ? But all codepage characters get messed up, e.g. ? (udiaeresis) -> ? (threesuperior). Looking at

When I made the move to 3.0, I noticed that smbclient no longer works with null passwords. Am I missing something? I read the FAQ, which suggests that the server is rejecting the null password. But I know that null passwords work fine for the 2.2.8a client, so the server is not the issue. The FAQ recommends "smbclient -L host -U%", but I don't want to set the username to null. I

Hi I have a problem with subject. I have a samba 3.0.1 server to which both windows and linux (using smbclient version 3) users can connect perfectly. But smbclient version 2.2.8a or earlier users cannot connect to this server. I have searched release notes, changelogs, the linux.samba newsgroup and found no indication of others having the same problem. Most likely it is something I have

after compile (gcc 3.0.2) install and configure (SWAT) on tcpps02 the following test failed # /usr/local/samba/bin/smbclient -L TCPPS02 added interface ip=172.16.207.7 bcast=172.16.255.255 nmask=255.255.0.0 session request to TCPPS02 failed (Call timed out: server did not respond after 20000 milliseconds) session request to *SMBSERVER failed (Call timed out: server did not respond after

Hello, please excuse if this question was asked before, but I wasn't able to find an answer for my problem in the list archive nor (with google) on a website. Here is my problem: I use Samba 3 from Debian/unstable together with ldap. The ldap-server is a NDS Server (Novell directory service/eDirectory). Authentication works well - with the smbclient of samba 3.x - from Windows2000 with

Resending for assistance on this issue. Thank you in advance, - Mike ? -----Original Message----- From: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org] On Behalf Of Tompkins, Michael Sent: Thursday, January 29, 2015 7:48 AM To: Jeremy Allison Cc: samba at lists.samba.org; USA Xerox Samba Subject: Re: [Samba] Samba 4.0.7 doesn't work with Russian credentials Sorry

Great spot, thanks Mark. This really ought to appear somewhere in the ?Quotes help page. Having a warning under Windows might be nicer behaviour than silently returning the wrong value too. On 4 December 2014 at 22:24, Mark van der Loo <mark.vanderloo at gmail.com> wrote: > Richie, > > The R language definition [1] says (10.3.1): > > \Unnnnnnnn \U{nnnnnnnn} > (where

Sorry about the lack of info. So in the wireshark trace, our printer smbclient 4.0.7 sends a Unicode value in Russian of ???? with a password of ????123. The server rejects the login attempt with STATUS_LOGON_FAILURE. The second attempt is with the linux version smbclient 4.0.7, and the same credentials to the same server work. The only thing I see different in the requests are the flags sent:

Richie, The R language definition [1] says (10.3.1): \Unnnnnnnn \U{nnnnnnnn} (where multibyte locales are supported and not on Windows, otherwise an error). Unicode character with given hex code ? sequences of up to eight hex digits. Best, Mark [1] http://cran.r-project.org/doc/manuals/r-release/R-lang.html http://www.markvanderloo.eu

On Thu, 2015-01-29 at 12:47 +0000, Tompkins, Michael wrote: > Sorry about the lack of info. So in the wireshark trace, our printer smbclient 4.0.7 sends a Unicode value in Russian of ???? with a password of ????123. The server rejects the login attempt with STATUS_LOGON_FAILURE. The second attempt is with the linux version smbclient 4.0.7, and the same credentials to the same server work. The

Hi, the problem is that when doing smbclient -L user I'm getting NT_STATUS_ACCESS_DENIED. ,,user'' is using win xp and I can view his shares from other _windows_ computer but not with smbclient. Any ideas why? [misiek@arm ~]$ smbclient -L lookas -d4 Serverzone is -3600 Initialising global parameters params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf"

In both R and JSON (and many other languages), unicode characters can be escaped using a backslash followed by a lowercase "u" and a 4 digit hex code. However when deparsing a character vector in R on Windows, the non-latin characters get escaped as "<U+" followed by their 4 digit hex code and ">": > x <- "I like \u5BFF\u53F8" > cat(x) I like

Just the beginning of a question to anyone who might have experienced the following issue with Samba 3.0.2[5-6] series. We currently have service accounts accessing Samba shares on AIX 5.3 servers ( from TL04 - TL06 ). Most of the processes access the shares via UNC rather than mapped drives. After completing the upgrade to Samba 3.0.26a on the production side, the service accounts started

Hello, I am investigating some strange authentication problems with our network. I am attempting to access a share on a DC with smbclient. If I authenticate with kerberos (kinit, then smbclient -k) then everything works fine. If, instead I use -U administrator -W DOMAIN, or just -U administrator, I get session setup failed: NT_STATUS_LOGON_FAILURE This is samba 3.3.2. Here is the d5 output

I've just spent a happy couple of days writing a text file for formatting with Markdown. The results are phenomenal! It's easy to write, and attractive to read. I'll try to send a Christmas present to the writer :-) But when I looked at the perl source, I also found that it was small and well-structured. Of course, I couldn't resist adding a few things that appealled to me.

Hi All, Here's an interesting one... I need to be able to connect smbclient on a linux machine to a dos based machine, which is running MSCLIENT and the WG1049 patch. I can browse to the machine and see all the files from Network Neighbourhood in Windows, but if I try and go in with: smbclient \\GAUGE1\C, or even just smbclient -L GAUGE1 all I get is: Added interface ip=10.0.1.1

On Mon, Aug 24, 2020 at 09:15:48PM +0200, LPC DPG via samba wrote: > Dear fellows. > > Another piece of information. The issue reprduces on RHEL 7.7, Samba 4.9.1 > > [root at vnhprerhds01 ~]# cat /etc/redhat-release > Red Hat Enterprise Linux Server release 7.7 (Maipo) > [root at vnhprerhds01 ~]# smbclient -V > Version 4.9.1 > > [root at vnhprerhds01 ~]# smbclient