[Samba] Error NT_STATUS_CONNECTION_REFUSED (was :Classicupgrade loses shares ?)

Rowland Penny rowlandpenny at googlemail.com
Tue Feb 25 06:53:47 MST 2014


On 25/02/14 09:26, Koenraad Lelong wrote:
> op 25-02-14 09:49, L.P.H. van Belle schreef:
>> Hai, just a question.. but,
>>
>> when i look at this.
>>
>> #What does /etc/resolv.conf contain ?
>>> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by
>>> resolvconf(8)
>>> #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
>
> I think this is something left from the installation.
>
>> Did you remove the resolvconf packages.
>> Or did you set the interfaces file "correcty"
>>
> cat /etc/network/interfaces
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> auto eth0
> iface eth0 inet static
>     address     192.168.200.10
>     netmask     255.255.240.0
>     gateway     192.168.200.199
>     dns-search  ad01.ace-electronics.be
>     dns-nameservers     192.168.200.10
>
>
>> I guest not because of the following.
>>
>> this line is incorrect, or is your subdomain : "ad01.ace-electronics.be"
>
> Reading samba4 information I came to the conclusion that using 
> ace-electronics.be as domainname/realm is not done with samba4, so I 
> made a subdomain ad01.ace-electronics.be. The host is 
> samba1.ad01.ace-electronics.be.
>
>
>>
>> you can try to :
>> remove the resolvconf package.
>>
> I now did, although I don't think that's my problem. I tested this 
> (adresses modified of course) :
> $ host -t SRV _ldap._tcp.samdom.example.com.
> _ldap._tcp.samdom.example.com has SRV record 0 100 389 
> samba.samdom.example.com.
>
> $ host -t SRV _kerberos._udp.samdom.example.com.
> _kerberos._udp.samdom.example.com has SRV record 0 100 88 
> samba.samdom.example.com.
>
> $ host -t A samba.samdom.example.com.
> samba.samdom.example.com has address 192.168.1.1

If samba.samdom.example.com is actually samba1.ad01.ace-electronics.be 
(your server) and 192.168.1.1 is the actual ipaddress returned, then you 
have a problem, it should be 192.168.200.10 (your servers ip)

Rowland

>
> All had the expected results.
> But, although this is OK :
> host -t A samba1 localhost
> Using domain server:
> Name: localhost
> Address: 127.0.0.1#53
> Aliases:
>
> samba1.ad01.ace-electronics.be has address 192.168.200.10
>
> This is not :
> host samba1 localhost
> Using domain server:
> Name: localhost
> Address: 127.0.0.1#53
> Aliases:
>
> samba1.ad01.ace-electronics.be has address 192.168.200.10
> Host samba1.ad01.ace-electronics.be not found: 3(NXDOMAIN)
> Host samba1.ad01.ace-electronics.be not found: 3(NXDOMAIN)
>
> Seems something *is* there something with my dns. Maybe this :
> cat /etc/nsswitch.conf
> # /etc/nsswitch.conf
> #
> ...
> hosts:          files mdns4_minimal [NOTFOUND=return] dns mdns4
> networks:       files
> ...
>
> Think not, I modified
> hosts:          files mdns4_minimal [NOTFOUND=return] dns mdns4
> to
> hosts:          files dns
>
> results remains the same (also after reboot).
>
>> and i suggest,
>> [libdefaults]
>>           dns_lookup_realm = true
>
> I modified this, but it did not help.
>
>> but this is based on the asumption that this :
>> AD01.ACE-ELECTRONICS.BE  is your hostname.domain.tld.
>>
>> so if this asumption is correct, you did something wrong in the setup.
>>
> Your assumption was not correct, but you gave thing to try, so thanks.
>
> Koenraad
>



More information about the samba mailing list