similar to: Failed to connect host on port 135 - NT_STATUS_CONNECTION_REFUSED

Displaying 20 results from an estimated 700 matches similar to: "Failed to connect host on port 135 - NT_STATUS_CONNECTION_REFUSED"

2017 Mar 28
1
Failed to connect host xx on port 135 - NT_STATUS_CONNECTION_REFUSED
Hello Rowland, >> --- >> # Global parameters >> [global] >> >> username map = /etc/samba/user.map >> > > I am sure this has nothing to do with your problem, but you should > remove the 'username map' line, it has no place on a DC. > ok, did so. >> >> It really does not listen: >> >> root at dc2:~# netstat
2015 Jan 30
2
Winbindd dies instantly
Hi, I'm trying to set up a Samba 4.1.16 file server for our (Samba 4) domain. But for some reason I can't seem to be able to get it to work. Even worse, I have run out of ideas on how to debug this. I've been tampering with this for quite some time now, but I've come to realize I can't figure this out on my own. Can someone give me some pointers on where to look in order
2017 Mar 28
4
Failed to connect host xx on port 135 - NT_STATUS_CONNECTION_REFUSED
Hello there, I installed a dc1 using debian jessie-packages strictly following the samba-manual "Setting up Samba as an Active Directory Domain Controller". I installed a dc2 using debian jessie-packages, also strictly following the manual for "Joining a Samba DC to an Existing Active Directory". It worked for a few weeks but then it quit working without having changed the
2013 Dec 14
2
Problem with Mail Server CentOS 6.5 (Postfix, Dovecot)
I flow the tutorials... But, I can't success.. :( Please check this links: http://www.unixmen.com/install-postfix-mail-server-with-dovecot-and-squirrelmail-on-centos-6-4/ http://www.krizna.com/centos/setup-mail-server-in-centos-6/#postfix http://linuxdrops.com/install-postfix-with-cyrus-on-centos-rhel-fedora/ Please tell me which is good ? & Do I need to change any command or step? I
2016 Dec 04
0
port 135 - NT_STATUS_CONNECTION_REFUSED
On Sun, 04 Dec 2016 08:01:09 -0600 Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > I have two DC's running Samba 4.5.0 and the "dtdc03" log.samba is > showing the following: > > root at dtdc03:~# tail -f /usr/local/samba/var/log.samba > [2016/12/01 10:14:39.167794, 0] > ../source4/librpc/rpc/dcerpc_sock.c:245(continue_ip_open_socket)
2016 Dec 04
0
port 135 - NT_STATUS_CONNECTION_REFUSED
On Sun, 04 Dec 2016 09:43:25 -0600 Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > On 2016-12-04 09:11, Rowland Penny via samba wrote: > > > On Sun, 04 Dec 2016 08:01:09 -0600 > > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > > >> I have two DC's running Samba 4.5.0 and the "dtdc03"
2015 Mar 19
2
The RPC server is unavailable
>On 18/03/15 17:56, Jesper Koivum?ki wrote: >>/ Hi, />>/ />>/ I'm running a samba 4.2 server on RedHat5 and for some reason I can't />>/ seem to logon using the AD Users and Computers -tool. />>/ />>/ Whenever I try to connect to the PDC I get the following error: />>/ />>/ "The following Domain Controller could not be contacted:
2015 Mar 19
1
The RPC server is unavailable
Hi, Thank you for your reply! I don't have any openchange services included in my installation. Nor am I using sogo. I changed the DNS settings on the DHCP server now, to only include the PDC. Any idea if I can still have the PDC forward the DNS calls with "dns forwarder" in smb.conf? Can I still use a secondary DNS server in resolv.conf on the PDC? It feels a bit risky,
2016 Dec 04
2
port 135 - NT_STATUS_CONNECTION_REFUSED
I have two DC's running Samba 4.5.0 and the "dtdc03" log.samba is showing the following: root at dtdc03:~# tail -f /usr/local/samba/var/log.samba [2016/12/01 10:14:39.167794, 0] ../source4/librpc/rpc/dcerpc_sock.c:245(continue_ip_open_socket) Failed to connect host 192.168.16.50 (aa03011a-94c2-4c52-bc60-6fd2f75d35e5._msdcs.dtshrm.dt) on port 135 - NT_STATUS_CONNECTION_REFUSED.
2016 Dec 04
1
port 135 - NT_STATUS_CONNECTION_REFUSED
On 2016-12-04 10:25, Rowland Penny via samba wrote: > On Sun, 04 Dec 2016 09:43:25 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > On 2016-12-04 09:11, Rowland Penny via samba wrote: > > On Sun, 04 Dec 2016 08:01:09 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > I have two DC's running
2015 Jan 31
0
Winbindd dies instantly
You didn't send your mail to the list. ;-) As you said, you have samba-ad packages installed. Uninstall samba-ad, because you only need samba. Samba-ad is for DCs. I would try this to avoid errors to winbind by this package. Am 31. Januar 2015 00:32:30 MEZ, schrieb "Jesper Koivum?ki" <jesper.koivumaki at kulturfonden.fi>: > >I realize now I should have been more
2016 Dec 04
2
port 135 - NT_STATUS_CONNECTION_REFUSED
On 2016-12-04 09:11, Rowland Penny via samba wrote: > On Sun, 04 Dec 2016 08:01:09 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > >> I have two DC's running Samba 4.5.0 and the "dtdc03" log.samba is >> showing the following: >> >> root at dtdc03:~# tail -f /usr/local/samba/var/log.samba >> [2016/12/01
2019 Mar 17
1
Accidental samba_dnsupdate success after NT_STATUS_CONNECTION_REFUSED
Greetings, The process to join a new samba 4.6 DC to an existing samba 4.1 DC repeatedly caused: samba_dnsupdate --verbose --all-names to fail on the new DC with: Failed to connect host x.x.x.x on port 49152 - NT_STATUS_CONNECTION_REFUSED Noted: both samba versions are obsolete and will be updated post haste. Regardless, samba_dnsupdate was accidentally invoked on the new DC while the
2017 Mar 22
2
net rpc info throwing NT_STATUS_CONNECTION_REFUSED
Hi Team, When i am accessing folders through cifs it always saying Username could not be found. In log i could see, [2017/03/22 10:03:50.184453, 0] ../source3/libsmb/cliconnect.c:1918(cli_session_setup_spnego_send) Kinit for DHANRAJ$@DHAN.LOCAL to access cifs/WIN-R2345ED.DHAN.LOCAL at DHAN.LOCAL failed: Preauthentication failed When i am running below command, I am getting
2015 Feb 26
0
SOLVED Re: NT_STATUS_CONNECTION_REFUSED
aha ... ;-) netstat --numeric-hosts --numeric-ports --programs -u -t -l i didnt see samba running.. ;-) >I removed the "service bind9 stop &&" from line 449 (as bind9 was >already stopped, why stop it again) and ran the script on my >VM. All the "NT_STATUS_CONNECTION_REFUSED" warnings were gone. but.. the NT_STATUS_CONNECTION_REFUSED is a samba
2015 Feb 26
1
SOLVED Re: NT_STATUS_CONNECTION_REFUSED
On 26/02/15 08:15, L.P.H. van Belle wrote: > aha ... > > ;-) > > netstat --numeric-hosts --numeric-ports --programs -u -t -l > i didnt see samba running.. ;-) > > >> I removed the "service bind9 stop &&" from line 449 (as bind9 was >> already stopped, why stop it again) and ran the script on my >> VM. All the
2015 Feb 27
0
NT_STATUS_CONNECTION_REFUSED, again!!!
On 27/02/15 17:28, Bob of Donelson Trophy wrote: > > > I thought I was over this the other day when I got it to work properly > on my VM. > > Now, on an actual PC I am getting: > > ==========Test kerberos =============================== > > Lets test some things > > Testing : kerberos > > Password for Administrator at DTSHRM.DT: > > Warning: Your
2014 Jan 22
1
Error when adding user NT_STATUS_CONNECTION_REFUSED
Any idea what the following error message is describing and how to troubleshoot? Newly joined DC. Using Ubuntu 12.04 and Samba 4.1.4 from a tarball. Used samba-tool. Windows Users & Computers app gives error as well. ERROR(ldb): Failed to add user 'usertest': - ../source4/dsdb/samdb/ldb_modules/ridalloc.c:547: No RID Set DN - Request for remote creation of RID Set for this DC
2016 Jan 27
0
NT_STATUS_CONNECTION_REFUSED
And please also do check hostname -s hostname -d hostname -f if you see somewhere 127.0.0.1 or incorrect hostname. Check /etc/hosts Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens mathias dufresne > Verzonden: woensdag 27 januari 2016 7:40 > Aan: Henry McLaughlin > CC: samba > Onderwerp: Re: [Samba]
2019 Mar 18
0
Accidental samba_dnsupdate success after NT_STATUS_CONNECTION_REFUSED
im betting here on a smb.conf that was not 4.6 compliant. port 49152 is not related i my opinion. is there a firewall running? the dynamic port range changed from a low range to high. Greetz Louis Op 17 mrt. 2019, om 22:36, Rowland Penny via samba <samba at lists.samba.org> schreef: On 17 Mar 2019 20:44:12 UTC Don Kuenz via samba <samba at lists.samba.org> wrote: