[Samba] Failed to connect host on port 135 - NT_STATUS_CONNECTION_REFUSED

Marcel de Reuver marcel at de.reuver.org
Thu May 8 10:09:06 MDT 2014


2014-05-08 15:59 GMT+02:00 Jesper Koivumäki <jesper.koivumaki at kulturfonden.
fi>:

>
> 2014-05-07 12:53, Marcel de Reuver skrev:
>
>  The Samba4 box must be the DNS server for the Windows clients that join
>> the AD. The dns forwarder for your Samba box can be your external DNS
>> server.
>>
>> Check this Wiki <https://wiki.samba.org/index.
>> php/Samba4/HOWTO#Configure_DNS> on why DNS is important for Samba 4 to
>> work and for solving problems with the DNS server of Samba4
>>
>>  I couldn't get the internal DNS server to work, so I resorted to
> installing bind9, which is now up and running. Workstations and server
> alike can now resolve the domain.
>
> However, the actual problem still persists.
>
> [code]
>
>  $ sudo samba-tool dns zonelist 10.0.1.5
> GENSEC backend 'gssapi_spnego' registered
> GENSEC backend 'gssapi_krb5' registered
> GENSEC backend 'gssapi_krb5_sasl' registered
> GENSEC backend 'sasl-DIGEST-MD5' registered
> GENSEC backend 'schannel' registered
> GENSEC backend 'spnego' registered
> GENSEC backend 'ntlmssp' registered
> GENSEC backend 'krb5' registered
> GENSEC backend 'fake_gssapi_krb5' registered
> Using binding ncacn_ip_tcp:10.0.1.5[,sign]
>
> Failed to connect host 10.0.1.5 on port 135 - NT_STATUS_CONNECTION_REFUSED
> Failed to connect host 10.0.1.5 (10.0.1.5) on port 135 -
> NT_STATUS_CONNECTION_REFUSED.
> ERROR(runtime): uncaught exception - (-1073741258, 'The connection was
> refused')
>   File "/usr/local/samba/lib64/python2.6/site-packages/samba/netcmd/__init__.py",
> line 175, in _run
>     return self.run(*args, **kwargs)
>   File "/usr/local/samba/lib64/python2.6/site-packages/samba/netcmd/dns.py",
> line 806, in run
>     dns_conn = dns_connect(server, self.lp, self.creds)
>   File "/usr/local/samba/lib64/python2.6/site-packages/samba/netcmd/dns.py",
> line 37, in dns_connect
>     dns_conn = dnsserver.dnsserver(binding_str, lp, creds)
> [/code]
>
> Same errors appear if I try to do smbclient4 -L localhost or anything
> similar. I just can't seem to get this thing to work.
>
>
The Samba4 internal DNS server should run out of the box, why switch to the
more involved configuration of Bind?
I don't have any in dept knowledge of RHEL6, but maybe AppArmor or
SELinuxneed some attention, see
here<https://wiki.samba.org/index.php/DNS_Backend_BIND#Interaction_with_AppArmor_or_SELinux>
for
some pointers.

Best regards,
Marcel de Reuver


More information about the samba mailing list