similar to: Postoupit: Samba 3.3.x - "The system cannot log you in due to the following error: Procedure number is out of range"

Hi, I just upgraded from 3.0.32 to 3.3.4 on Aix 6.1, and noticed that a 'net view' command from a windows xp workstation fails with a system error 1745. The share works perfectly fine, just the net view command doesn't. This occurs when there is an umlaut in the comment line of the share. Is this WAD? here are the debug lines...from Samba 3.3.3, but it's the same error. Thanks,

Hi, I am trying to upgrade Samba from 3.3.2 to 3.3.9 for Win7 compatibility issue. It is running on Redhat 9.0 (I've planned to upgrade to Centos 5.5 in a second setp) and without any ldap backend (tdbsam actually). As I have already done in the past for upgrading, I have done the following procedure : 1) Compile 3.3.9 . My configure option are : ./configure --with-acl-support

Hi, I just updated my samba servers (debian wheezy, sernet samba4) from version 4.1.12-9 to 4.1.14-9 and suddenly all my hp printers produce errors instead of printing. Kyocera printers are still working. HP printers all use HP Universal drivers Version 5.9.0.18326 with snmp disabled. Errors occure from Windows Server 2003 32Bit and Windows 7 clients. Here's an level 1 log of what

Hi !!! I've Samba 3.3.12 running on AIX, I have a few windows 7 using a shared resource on that server. This is the shared resource definition: [shared_disk] comment = shared_disk path = /home2/nfs-chiappe/shared_disk valid users = user1,user2 write list = @staff read only = No create mask = 0764 This particular Windows 7 Computer is driving

Hello, All! I found that Samba checks description fields encoding at various tdb files to late. Case 1. FreeBSD with UTF-8 support. At some cases FreeBSD's adduser script can save incorrect UTF-8 sequence to GECOS /etc/passwd field. (Here is example http://www.acc.tula.ru/~acc107_3/samba/miscoding/gecos.txt) When user is added to Samba, Samba reads GECOS field "as is" without

Hello, All! I have domain network. But user managing via USRMGR.EXE is impossble. When I run USRMGR.EXE I get a window: The tag is invalid. Do you want to select another domain to administer? At this time at Samba's log: [2010/01/11 14:12:07, 1] librpc/ndr/ndr.c:ndr_push_error(493) ndr_push_error(5): Bad char conversion [2010/01/11 14:12:07, 0] rpc_server/srv_pipe.c:api_rpcTNP(2381)

look at this bug report https://bugzilla.samba.org/show_bug.cgi?id=10984 Louis >-----Oorspronkelijk bericht----- >Van: achim at ag-web.biz [mailto:samba-bounces at lists.samba.org] >Namens Achim Gottinger >Verzonden: dinsdag 6 januari 2015 9:56 >Aan: samba at lists.samba.org >Onderwerp: [Samba] Problem with HP printers after upgrade from >4.1.12-9 to 4.1.14-9 >

On Wed, 4 Jan 2017 15:58:39 -0300 Andres Tarallo via samba <samba at lists.samba.org> wrote: > Hi !!! > > I've Samba 3.3.12 running on AIX, I have a few windows 7 using a > shared resource on that server. > > This is the shared resource definition: > > [shared_disk] > comment = shared_disk > path = /home2/nfs-chiappe/shared_disk >

This samba is scheduled for upgrade. We've been testing samba 4.3.8 packages (from BULLFreeware) on other AIX. It was not easy the install, even with RPM packages. I hope to do the upgrade soon, but I need to have this particular user working now. What puzzles me is that I have other windows 7 PCs happily working on the same resource. 2017-01-04 16:21 GMT-03:00 Rowland Penny via samba

after update from samba 3.0.30 to 3.3.3. i can't login to windowsXP machines (SP2, SP3) with some user's accounts i got already these error message: "The system cannot log you in due to the following error: Procedure number is out of range" with some user's accounts all works right, but with some accounts is these error. My configuration is now same as before the update,

This problem shows up on both Linux and Solaris. I am going to show the logs from a Fedora 2.6.25-14.fc9.i686 machine. We are using 'security = domain' with a Windows 2000 domain controller. We are setting 'password server = starfish2' dispite the fact that the documentation says that this in not necessary as we have found it to be necessary. We are setting 'workgroup =

Hello all, I've set the log level of my DC to 3. I'm using it as a file server too although it is not recommended. I now have the following errors in log.samba: [2015/03/03 08:58:54.244106, 2] ../source4/dns_server/dns_query.c:629(dns_server_process_query_send) Not authoritative for 'versioncheck.addons.mozilla.org', forwarding [2015/03/03 08:58:54.266123, 1]

Adding a section of a debug level 5 log at the end that looks like it might have some usefull information. > This problem shows up on both Linux and Solaris. I am going to show > the logs from a Fedora 2.6.25-14.fc9.i686 machine. > > We are using 'security = domain' with a Windows 2000 domain controller. > We are setting 'password server = starfish2' dispite the

Hi, I have a strange problem with a Windows Server 2008 R2-System as a member of a samba domain (Samba-Version on PDC: 3.4.12). Join was successfully, but when I log on Windows I got an error "Unknown user name or bad password." (Event ID 4625). Here an abstract of logfile for Windows Server 2008 R2-System (log level 10). Maybe some of you has an idea:

Thats really annoying because the printing with samba is not possible, just printing directly to cups is possible. The clients are working with UTF-8, the server is working with UTF-8, don't know why character conversion should be a problem here. More details: [2011/09/14 13:55:24.173846, ?5] rpc_server/srv_pipe.c:2367(api_pipe_request) ? Requested \PIPE\\spoolss [2011/09/14 13:55:24.173878,

I'm sorry for the very long debug pasted below but I'm afraid lower debug levels would not give enough useful information about the problem. I've been investigating it for over two weeks with no result. Maybe developers can tell me where to search for the cause - browsing source code is very hard... I have a Samba PDC with LDAP backend. Configuration works fine on 3.0.x version but

Hello, after upgrading to samba 3.5.6 of Debian Squeeze some printouts will not printed. The same prinjob will printed after a couple of tries. I increased the loglevel and there are only a few messages which showing whtat could be the problem. The printjobs doesn't arrive at cups. [2011/08/10 11:32:12.700665,? 0] lib/charcnv.c:650(convert_string_talloc)? Conversion error: Illegal multibyte

I think bad breath... ;-) noo... just joking .. sorry , ... ;-) It is may be help full if you provide a bit more info. Like for example OS = Samba version = The smb.conf content. And what did you setup? AD DC server NT4 PDC server Standalone server? Member server? And based on what you already posted below. Im guessing an AD DC setup, but with the wrong backend setup. But you tell

"uname -a" gives Linux 4.9.0-1-amd64 #1 SMP Debian 4.9.2-2 (2017-01-12) x86_64 GNU/Linux "samba -V" : Version 4.5.6-Debian It is a standalone server with "security = user" and "passdb backend = ldapsam:ldap://localhost" The weirdness I described happens to any share, so I assume detailed share configuration is irrelevant. Apart from this weirdness all

I have been trying to setup a new print server on Fedora 12 based around samba-3.4.7-58.fc12.x86_64 and cups-1.4.2-28.fc12.x86_64. All looks good except for the ability for printer administrators to manage printers. Whether I specify users in a system group using the deprecated printer admin option, or specifically using net rpc rights and the SePrinterOperatorPrivilege, it does not matter.