basti.mueller31 at web.de
2017-Jun-09 20:30 UTC
[Samba] smbclient ends in NT_STATUS_CONNECTION_REFUSED error
Hi, After a few years I wanted to migrate my Samba 4(as a PDC,version 4.2 from debian package) to a Samba4 in AD-Mode (with classic upgrade). The PDC is running on an OpenLDAP and his own DNS Server(bind). As I was upgrading I was following the Samba-Wiki instruction and had no error message during this. Now I have the issue, that I’m getting error messages when I’m executing the command „smbclient –d10 –L 192.168.15.2 –U%“. INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10 rpc_cli: 10 passdb: 10 sam: 10 auth: 10 winbind: 10 vfs: 10 idmap: 10 quota: 10 acls: 10 locking: 10 msdfs: 10 dmapi: 10 registry: 10 scavenger: 10 dns: 10 ldb: 10 lp_load_ex: refreshing parameters Initialising global parameters INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10 rpc_cli: 10 passdb: 10 sam: 10 auth: 10 winbind: 10 vfs: 10 idmap: 10 quota: 10 acls: 10 locking: 10 msdfs: 10 dmapi: 10 registry: 10 scavenger: 10 dns: 10 ldb: 10 Processing section "[global]" doing parameter workgroup = EXAMPLE doing parameter realm = example.com doing parameter netbios name = PDC doing parameter server role = active directory domain controller doing parameter server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate doing parameter idmap_ldb:use rfc2307 = yes pm_process() returned Yes lp_servicenumber: couldn't find homes added interface br0 ip=192.168.15.2 bcast=192.168.15.255 netmask=255.255.255.0 Netbios name list:- my_netbios_names[0]="PDC" Client started (version 4.2.14-Debian). Connecting to 192.168.15.2 at port 445 Connecting to 192.168.15.2 at port 139 Connection to 192.168.15.2 failed (Error NT_STATUS_CONNECTION_REFUSED) Nslookup shows me this: root at server:/# nslookup localhost Server: 192.168.15.2 Address: 192.168.15.2#53 Name: localhost Address: 127.0.0.1 # Global parameters [global] workgroup = EXAMPLE realm = example.com netbios name = PDC server role = active directory domain controller server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate idmap_ldb:use rfc2307 = yes [netlogon] path = /var/lib/samba/sysvol/example.com/scripts read only = No [sysvol] path = /var/lib/samba/sysvol read only = No My resolv.conf: domain example.com search example.com nameserver 192.168.15.2 What could be the reason that no connection can be developed?
Rowland Penny
2017-Jun-09 21:04 UTC
[Samba] smbclient ends in NT_STATUS_CONNECTION_REFUSED error
On Fri, 9 Jun 2017 22:30:48 +0200 "basti.mueller31--- via samba" <samba at lists.samba.org> wrote:> Hi, > > After a few years I wanted to migrate my Samba 4(as a PDC,version 4.2 > from debian package) to a Samba4 in AD-Mode (with classic upgrade). > The PDC is running on an OpenLDAP and his own DNS Server(bind).This is confusing, you have upgraded from a PDC and you have called your new DC 'PDC', so I hope you mean the old PDC was running openldap.> As I > was upgrading I was following the Samba-Wiki instruction and had no > error message during this. Now I have the issue, that I’m getting > error messages when I’m executing the command „smbclient –d10 –L > 192.168.15.2 –U%“. >Try it like this: smbclient -L localhost> My resolv.conf: > domain example.com > search example.com > nameserver 192.168.15.2'domain' and 'search' are mutually exclusive in /etc/resolv.conf, or to put it another way, you cannot have both, the last one wins, so I suggest you remove the 'domain' line ;-)> What could be the reason that no connection can be developed?Don't really know (yet), can you post: /etc/krb5.conf /etc/hosts /etc/hostname your bind conf files Rowland
basti.mueller31 at web.de
2017-Jun-12 12:01 UTC
[Samba] smbclient ends in NT_STATUS_CONNECTION_REFUSED error
>> Hi, >> >> After a few years I wanted to migrate my Samba 4(as a PDC,version 4.2 >> from debian package) to a Samba4 in AD-Mode (with classic upgrade). >> The PDC is running on an OpenLDAP and his own DNS Server(bind).>This is confusing, you have upgraded from a PDC and you have called >your new DC 'PDC', so I hope you mean the old PDC was running openldap.Sorry... Yes the old PDC was running OpenLDAP.>> As I >> was upgrading I was following the Samba-Wiki instruction and had no >> error message during this. Now I have the issue, that I’m getting >> error messages when I’m executing the command „smbclient –d10 –L >> 192.168.15.2 –U%“.>Try it like this: smbclient -L localhostI get: root at server:~# smbclient -L localhost Enter root's password: Connection to localhost failed (Error NT_STATUS_CONNECTION_REFUSED)>> My resolv.conf: >> domain example.com >> search example.com >> nameserver 192.168.15.2>'domain' and 'search' are mutually exclusive in /etc/resolv.conf, or to >put it another way, you cannot have both, the last one wins, so I >suggest you remove the 'domain' line ;-)Fixed - thanks! :)>> What could be the reason that no connection can be developed?>Don't really know (yet), can you post:>/etc/krb5.conf[libdefaults] default_realm = HIPERSCAN.COM dns_lookup_realm = false dns_lookup_kdc = true>/etc/hosts127.0.0.1 localhost server.example.com server>/etc/hostnameserver>your bind conf filesnamed.conf: include "/etc/bind/named.conf.options"; include "/etc/bind/named.conf.local"; include "/etc/bind/named.conf.default-zones"; --- named.conf.default zone "." { type hint; file "/etc/bind/db.root"; }; zone "localhost" { type master; file "/etc/bind/db.local"; }; zone "127.in-addr.arpa" { type master; file "/etc/bind/db.127"; }; zone "0.in-addr.arpa" { type master; file "/etc/bind/db.0"; }; zone "255.in-addr.arpa" { type master; file "/etc/bind/db.255"; }; zones: --- named.conf.local zone "hiperscan.com" { type master; file "/etc/bind/hiperscan.com.db"; notify no; allow-update { localhost; }; }; zone "15.168.192.in-addr.arpa" { type master; file "/etc/bind/192.168.15.db"; allow-update { localhost; }; }; --- named.conf.options: options { directory "/var/cache/bind"; forwarders { 193.189.250.99; 192.168.15.1; }; auth-nxdomain no; # conform to RFC1035 listen-on-v6 { any; }; };
Possibly Parallel Threads
- smbclient ends in NT_STATUS_CONNECTION_REFUSED error
- smbclient ends in NT_STATUS_CONNECTION_REFUSED error
- smbclient ends in NT_STATUS_CONNECTION_REFUSED error
- smbclient ends in NT_STATUS_CONNECTION_REFUSED error
- smbclient ends in NT_STATUS_CONNECTION_REFUSED error