similar to: RPC Error with PC Netlink - additional info

Some additional info: The solaris server is Solaris 10 (sparc.) According to man smb.conf, "enable asu support = yes" creates an IPC only "ADMIN$" share. Using the computer management tool from a Windows machine I could verify this was the case. However, the "ADMIN$" share on the PC Netlink server is actually a data share. I did try "enable asu support =

I have setup a Samba 3.024 server on Solaris. I have successfully enabled two-way trusts between my samba domain and my legacy PC Netlink domain. (PC Netlink is the solaris port of NT4 aka Advanced Server for Unix.) My Samba domain includes 2 Windows 2003 Servers (One is Windows 2003 SP1, the other is Windows 2003 R2 SP2.) The PCNL server supports Windows 2000 Servers and XP Pro clients.

I recently brought up our fifth Samba domain member server with 3.0.26a-0.9-1787-SUSE-SLES9 against an NT4 domain on a new subnet. The subnet also has an NT4 BDC that is working correctly. Wbinfo and getent both work properly but users can not get to the [homes] service but can get to another share that is on the same system. If I setup a share definition in smb.conf for myself as a home

I only have limited Samba experience, and expect this is a silly mistake, but have been unable to find a solution I have installed Samba and Winbind on my desktop Linux (Debian) machine (SPARKSTONELX), aiming to unify logins with other windows machines accessing the PDC, again samba/Debian, with tdbsam password backend. All is well, joining the domain, and getting account details using wbinfo -u,

Thanks for the advice. I had played with NT4 a little bit to see if I could use it for setting up a resource domain for windows 2003 machines- since it looks like you can join Windows 2003 machines to an NT4 domain (so why PCNL can't I don't know), and then establish trusts between NT4 and PCNL. I didn't really want to have NT4 machines in my enviroment any longer than necessary so

I portupgraded my samba domain server and domain member to 3.0.23b from 3.0.23 and found that the domain member was not accessible from workstations. The error message: \\HOSTNAME is not accessible. There are currently no logon servers available to service the logon request. In the log.winbindd of the domain member, I found: [2006/08/23 22:52:00, 0] nsswitch/winbindd.c:request_len_recv(517)

Hello All, I am having two problems. I am running Samba on Solaris 10 as a member server to a NT 4.0 domain with a PC NetLink 2.0 PDC. The first problem: Running Samba 3.0.10 I am able to get the server to join the domain just fine with authentication and acls working correctly but if the shares aren't accessed for a little while winbind seems to halt and I have to start and stop

dear samba community, we have a big problem on joining a Samba 3.5.6 PDC. Hopefully anyone has an idea/suggestion. When trying to join with a Samba 4.2.10 or 4.3.9 we got the following error on client site: Failed to pull dcerpc auth: NT_STATUS_RPC_PROTOCOL_ERROR. cli_rpc_pipe_open_schannel_with_key: rpc_pipe_bind failed with error NT_STATUS_RPC_PROTOCOL_ERROR libnet_join_ok: failed to open

We recently upgraded our PDC from Debian 4 to Debian 5. That entailed an upgrade of Samba from 3.0.24 to 3.2.5. Since the upgrade we've had a very specific problem connecting to shares on a commercial NAS running Samba 3.0.34. The problem happens when users try to connect to shares from standalone servers--e.g., Windows XP Pro boxes that we use for testing. From those boxes users should be

Hello all, Relevant info up front: Gentoo PC, using 2.6.38 kernel and Samba 3.4.12. I'm trying to get a FreeRadius instance working for our Windows network. To do so, I need a Linux box running Samba. I've installed and configured Kerberos, Samba and FreeRadius, and can get most things to work. I can get a Kerberos key using kinit, and "sudo net ads keytab list" shows me

Hi, we have a problem with your Samba4 Domain Member as with Shares. when i would connect i got an Error. In Samba Logs it tells me ==> /var/log/samba/computerid349.log <== [2016/02/10 14:39:50.313835, 1] ../source3/printing/printer_list.c:226(printer_list_get_last_refresh) Failed to fetch record! [2016/02/10 14:39:50.313949, 1]

I'm running Samba v4.4.4 as a domain member server in security=domain mode. Our 3 domain controllers are Server 2012r2. Every 3-4 days, I see log messages from winbind saying "winbind_samlogon_retry_loop: sam_logon returned ACCESS_DENIED". Sometimes this corresponds to a trust password change, but not always. Today, new connections to Samba were failing with the error

I now have one PDC (Samba 3.026a on Solaris 10) and several member servers (including Samba 3.026a on Solaris 9 and 10, and Samba 3.024 on Fedora core 6.) Each machine uses NIS for unix accounts. If I start smbd and nmbd on a member server, I can connect to a share from a windows 2000 or XP client. If I look at the permissions on a folder, if shows "Unix Account/someuser" or

Hello, I saw on my member servers in winbindd.log sometimes the following message appearing: [2009/05/29 21:51:53, 1] rpc_client/cli_pipe.c:cli_pipe_validate_current_pdu(755) cli_pipe_validate_current_pdu: RPC fault code DCERPC_FAULT_OP_RNG_ERROR received from host GENOME, pipe \lsarpc, fnum 0x7101! What does this error mean and how can I fix it? PDC and meber server are running 3.3.4.

I thought I had setup winbind correctly as I can login to my ubuntu 9.04 machine with domain users, but I am trying to get ntlm working with squid, and while testing winbind I get the following error. sudo wbinfo -a MBAG\\user%passwd plaintext password authentication failed Could not authenticate user MBAG\user%passwd with plaintext password challenge/response password authentication failed error

I'm testing out a new Samba setup to hopefully replace my aging Win2k domain. I've got some of it working: - My PDC (shadow) seems to be working on the CASA domain with an LDAP backend. - nss_ldap and pam_ldap are working on shadow - I can run wbinfo -u and get the user info from LDAP on shadow. - I can run wbinfo -a username%password and authenticate a user on shadow. I can run

Hey List- I've got 2 samba servers. PDC: FreeBSD 5.4; samba: 3.0.23 ? name: bugs member server: FreeBSD 6-stable; samba: 3.0.23 ? name: daffy note: config files are at the bottom of the email The PDC was running an older version, but I just upgraded and it didn't fix the below issue. The member server was running fine with the old smb.conf file, but I rebuilt the server and now it

Hello, when i send the SIGHUP signal to Samba, then Samba won't load the printers from CUPS. I need to shutdown Samba and start it again. Now when i'am running cupsaddsmb i got the following errors(this error occours in 3.5.x but not in 3.2.x): server-p:/# cupsaddsmb -H server-p -v edv01 edv02 edv03 Kennwort f?r root erforderlich, um ?ber SAMBA auf server-p zugreifen zu k?nnen:

Hi. We add a new virtual machine with vmware server 1.0.4, centos 5.x client, we update the server with yum and receive samba 3.0.25b-1.el5_1.4, we have a PDC running Gentoo with Samba 3.0.24+ldap, all the windows clients and other Linux boxes(.3.0.10 + 3.0.23 + 3.0.24) are working very good and stable. The only problem is this new server, i read about some changes with samba 3.0.25b and

Hi, We recently upgraded some AD member file servers from 4.6.7 to 4.6.11. Since then, "getent group" has been failing to return groups properly after winbind's been running for a couple of days. We have a lot of entries in log.wb-<DOMAIN> like this: [2017/12/15 11:39:47.959368,  1] ../source3/winbindd/winbindd_ads.c:1236(lookup_groupmem)   lsa_lookupsids call failed