search for: samba_port_usag

...FUSED > > >I don't know this script. But if it says connection refused, I'm sure, >that >a) there's a firewall preventing connection >b) the service you try to connect to, isn't listening on localhost > > >To check b): >https://wiki.samba.org/index.php/Samba_port_usage#Identify_on_which_ports_and_interfaces_Samba_is_listening > > > >Regards, >Marc >-- >To unsubscribe from this list go to the following URL and read the >instructions: https://lists.samba.org/mailman/options/samba

....1 Connection failed: NT_STATUS_CONNECTION_REFUSED I don't know this script. But if it says connection refused, I'm sure, that a) there's a firewall preventing connection b) the service you try to connect to, isn't listening on localhost To check b): https://wiki.samba.org/index.php/Samba_port_usage#Identify_on_which_ports_and_interfaces_Samba_is_listening [1] Regards, Marc -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba [2] Links: ------ [1] https://wiki.samba.org/index.php/Samba_port_usage#Identify_on_which...

...te_Network ) : "Plese note that the Domain Controller (Samba4) can also be configure on the Firewall itself, but this is strongly not recommended due to a security issues." Are these security issues still there when Samba is listening only on LAN port ( https://wiki.samba.org/index.php/Samba_port_usage ) like : bind interfaces only = yes interfaces = lo eth0 Of course server is well firewalled and remote users are connecting through VPN. Thanks in advance for your time. Nicolas

Louis, I ran your "1-setup-sernet-samba4-ADDC-wheezy.sh" script and noticed this (during install:) ==========SE Privileges =============================== Enter administrator's password: Could not connect to server 127.0.0.1 Connection failed: NT_STATUS_CONNECTION_REFUSED This is my /etc/resolv.conf: root at dc01:~# cat /etc/resolv.conf search dts***m.dt nameserver

I tried to promote another server as a domain controller so I can get my machines upgraded to Debian 8 Conveniently the samba versions are the same dictator at drakeburner:~$ sudo samba -V Version 4.1.17-Debian root at soothsayer:/etc/samba# samba -V Version 4.1.17-Debian root at soothsayer:/etc/samba# samba-tool drs showrepl Failed to connect host 127.0.0.1 on port 135 -

...nnection failed: NT_STATUS_CONNECTION_REFUSED I don't know this script. But if it says connection refused, I'm sure, that a) there's a firewall preventing connection b) the service you try to connect to, isn't listening on localhost To check b): https://wiki.samba.org/index.php/Samba_port_usage#Identify_on_which_ports_and_interfaces_Samba_is_listening Regards, Marc

Hi, I installed a samba 4 DC. It works fine, however it autoregisters all IPs in DNS (Dynmaic Update). This bears the problem that when a client wants to connect to the DC it connects using a wrong ip. I tried to remove the IP using dnsmgmt.msc, this works for around an hour than the "wrong" address is back again. Is there a way to limit dynamic updates to a specific interface or can

After researching win7 and samba issues we upgraded to 3.5.22. We still can not connect to shares on the RHEL 5.9 box. Odd thing is, when attempting to connect we never see anything in the logs, which makes me think its a networking issue. We've turned off the firewall on the win 7 box, but still nothing. We can ping the RHEL server from the Win 7 box. Any insights or suggestions would

How can I configure samba4 to be protected against DNS amplification attacks? Is there a way to set the network I want it to be recursive, like in bind9? My samba4 is receiving attacks and googling I found this: http://dnsamplificationattacks.blogspot.com.br/2014/02/domain-gerdar3ru.html -- --------------------------------------- Bruno Vane S.O. do Brasil Telecomunica??es +55 24 99306-8618 |

Hi, i have a samba 4.0 server with bind DNS. I has two configured interfaces 192.168.1.1 and 192.168.2.1. The second nic is just for backup purposes i don't want it to be accessed by clients. At the moment samba dnsupdate push the .1.1 and the .2.1 address as server addresses. Windows clients in the 1.0/24 try to access 2.1 which does not work. How can i tell samba not to puch the second

Hallo, I've just updated my slackware samba packet from 3.6.17 to 4.1.6. My start script is not changed, it still calls "nmbd -D" and "smbd -D". Seems to run as expected. But now I get strange messages like [2014/04/15 10:36:05.535423, 0] ../source3/lib/ util_sock.c:423(open_socket_in) open_socket_in(): socket() call failed: Die Adressfamilie wird von der

I have followed the Samba AD DC HOWTO wiki and after everything looks proper, I can't get samba to properly start. I'm using Samba 4.1.7 on Arch Linux. Running samba -d3 -i -M single I get the following error: service_setup_stream_socket(address=::,port=0) failed - NT_STATUS_INVALID_PARAMETER_MIX task_server_terminate: [Failed to startup dcerpc server task] samba_terminate: Failed to

Hello, Outside of running 'samba-tool drs showrepl' and examining 'log.samba'. How does one monitor the overall health of Active Directory or the Samba4 daemons? I currently have Nagios configured to monitor the servers themselves(ie. ping,ssh,swap etc). Thanks for any input. -- -James

I have a Samba 4.1.6 up and running(?) When I try to join the AD, I get 'RPC server is unabailable.' This also happens when I try the Microsoft Remote Administration tools, I get the same issue. The samba, smbd, and auth logs don't seem to provide the answer I need, but that may only mean I can't see it. The workgroup server works fine. I have spent hours online and in the samba

I am installing a new Samba 4.2 Active Directory server on CentOS 7. I followed the Wiki instructions on how to create the server. I am using sernet-samba 4.2 binaries. Everything seems to be OK on the Linux side but I cannot get any windows client to successfully join the domain. Each attempt returns the following error message "RPC Server in not available". Below are the config file

Hi, Me again, still trying to migrate my samba3-server. Using the script op L.P.H. van Belle, there is one failure : net rpc rights grant ${SETNTDOM}\\"Domain Admins" SeDiskOperatorPrivilege -U${SETNTUSER} This is the result : ==========SE Privileges =============================== Giving group Domain Admins the SeDiskOperatorPrivilege rights. Enter Admikoen's password: Could not

Hello, I'm trying to install samba 4 as a DC following this tutorial https://wiki.samba.org/index.php/Samba_AD_DC_HOWTO. Ihave reached the step of testing the connectivity to the DC with smbclient [root at DC-TEST ~]# /usr/local/samba/bin/smbclient -L localhost -U% session setup failed: NT_STATUS_CONNECTION_REFUSED Samba 4 has started successfully [root at DC-TEST ~]# netstat -lntp

Ubuntu 14.04, Samba 4.1.6 I'm having trouble connecting Windows clients to the domain. "The following error occurred attempting to join the domain "smbdomain": The RPC server is unavailable." When you attempt to join the domain, it finds it by name immediately and asks for username/password, after which it gives the error above. I haven't found documentation on