similar to: RPC Error with PC Netlink

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 =

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 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

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

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

Hi all, I'm having some problems getting a fedora core 4 box to work as file server into a windows domain. pdc is a hp unix with asu installed. i managed to get the linux box to join the domain, and i can see the box when i browse the network from a windows machine. but, i cannot map any shares... wbinfo -g is telling me it got an "error looking up domain groups", wbinfo -u shows

Users are having trouble accessing Samba shares via winbindd in a NT domain. If the 'valid users' parameter for a share contained the user name for example as follows: valid users = DSP-John Then John who is a member of the DSP domain can access the share. If John is a member of a domain group called DSP-production, and the 'valid users' parameter is as follows: valid

I have set up a system to be a member server and installed the samba rpms. I then copied over the samba config file and changed it to reflect the new shares and name change. I ran 'net rpc join - UAdministrator%'secret' and I was able to join the domain. Started up smb and then winbind wbinfo -u and I can see the users in the domain getent passwd shows nothing but the users in

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

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)

I am using the following in my smb.conf on samba-3.0.28-0.el5.8 idmap domains = MYDOMAIN idmap config MYDOMAIN:backend = rid idmap config MYDOMAIN:base_rid = 998 idmap config MYDOMAIN:range = 998 - 49999 idmap uid = 998-20000 idmap gid = 998-20000 template homedir = /home/users/%U # template primary group =

Hi, I am not sure it's the same issue, but I had a similar problem when upgrading from DSM 5.x to 6.0 : error after domain join : "Connection failed. Please check your network settings" . With the help of the (very efficient) Synology support, we solved the problem by uninstalling an old Cluster HA DSM package that was installed on the NAS but not used. Just in case it could help.

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

On both the synology (samba 4.1.20) and PDC (samba 3.6.25) testparm showed client schannel = Auto server schannel = Auto I don't know if the server even supports schannel. Maybe it doesn't any all the clients successfully negotiated not to use it. On the synology, I set client schannel = no This fixed my domain membership issue. Although

Hi folks, sorry for the re-post, I need some help to solve this problem. Since my previous e-mail, we made a set-up: there is a Clear Pass device (Aruba), which controlls the network access for users. Between the CP and these two DC's there is a load balancer. But, when we stopped the DC1, which was set up first, and the DC2 works continously, then the authentication of users is stopped

I have a Synology NAS array appliance. It is linux based and uses samba for file sharing. Normally the config is done via a gui interface but you can ssh to the array. The domain controllers are running Samba 3.6.x in classic domain mode. I have member servers running 3.6.x and 4.3.8. no problem. I recently updated the Synology "OS." The current version of samba is

It looks as if 2-way trusts are working between Samba and PCNL and between Samba/NT4. The one exception seems to be logging in as Samba/myname on the ENT4 PDC. I had created a ENT4/myname account. I had forgotten to add SAMBA/myname to the local users group on the ENT4 PDC before trying to the ENT4 PDC as SAMBA/myname. If I log in as SAMBA/anothername it is OK. This isn't real show

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

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