[Samba] CTDB Error / tcp port 445 not repsonding

Vogel, Sven Sven.Vogel at kupper-computer.com
Fri Apr 4 02:25:41 MDT 2014


Hi Gaiseric,

yes i have these setting. Testparm -v

smb ports = 445 139

i mean with ad (active directory). I know that ctdb not uses 445 but ctdb starts samba and wait for startup from samba. Maybe ctdb check some responses from samba and wait for startup from samba. If there is not correct response it send these error message.

I think ctdb is correct configured. is there any way to debug the samba connection problem? I can set the debug level ... 

Thanks

Sven


-----Ursprüngliche Nachricht-----
Von: Gaiseric Vandal [mailto:gaiseric.vandal at gmail.com] 
Gesendet: Freitag, 4. April 2014 00:59
An: Vogel, Sven
Betreff: Re: [Samba] CTDB Error / tcp port 445 not repsonding

You stated "ctdb cluster uses winbind for connection to the ad."   When 
you say "ad" do you mean active directory or something else?     I don't 
use CTDB so I was trying to figure out if you had some network issue that was not specifically related to CTDB.


On my samba servers

#testparm -v

         smb ports = 445 139


This is the default.   I had tried setting "smb ports" to only use 139 
-  since supposedly  clients in a Samba 3.x domain don't use it.     
Port 139 is for CIFS (windows file services) over Nettbios-over-tcp.   
Port 445 is for CIFS-over-IP.           It turns out displaying 445 
actually caused problems.       Windows 7 machines can use 445 for file 
access (not for authentication though)   so disabling 445 caused 
problems if a router was involved.


It doesn't look like CTDB uses 445-   which is why I think there may be 
some other issue.

https://ctdb.samba.org/configuring.html



Are you using a VPN tunnel between sites?



On 04/03/14 18:38, Vogel, Sven wrote:
> Thanks for reply.
>
> Yes all the ctdb servers and domain controllers are in the single domain. I know that samba 3 can not be a activie directory controller. I mean the ctdb cluster uses winbind for connection to the ad.
>
> I will run testparm -v and send tomorrow the output. Which ports will ctdb check?
>
> Thanks
>
> Sven
>
> -----Ursprüngliche Nachricht-----
> Von: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org] Im Auftrag von Gaiseric Vandal
> Gesendet: Donnerstag, 3. April 2014 23:36
> An: samba at lists.samba.org
> Betreff: Re: [Samba] CTDB Error / tcp port 445 not repsonding
>
> Are the the servers in a single domain?    Which is the primary domain
> controller?    Samba 3.x cannot be a domain controller for active
> directory.
>
> It seems like your CTDB machines are unable to connect to the domain controllers on the other side of the firewall. You may want to use a
> tool like nmap to verify that all the appropriate ports are open.   I
> have been running into similar issue with a router that will not let
> UDP 137 traffic pass.    It will let TCP 445 traffic pass.
>
>
>
> When you run "testparm -v" -  which ports are enabled on the samba servers?
>
>
>
>
>
> On 04/03/14 17:10, Vogel, Sven wrote:
>> Hi,
>>
>> i need some help. We have two Networks. A CTDB Cluster and one domain controller in the same network. All other domain controller are outside this network. They are both connected with a firewall / router.
>>
>> We activated netbios over tcp on the other domain controllers outside but it seems that when we remove the single internal domain controller ctdb will not start with the following error. "tcp port 445 not responding"
>>
>> Winbind and ad is working we checked it with e.g.  wbinfo -u.
>>
>> We use: CentOS 6.3 / Samba from Sernet Repo 3.6.9-44 / CTDB version: 2.1.0.95.gb5a8791.devel
>>
>>
>> 1.       What exactly ctdb checks during samba startup? (445?)
>>
>>
>>
>> 2.       What exactly is wrong or missing ctdb?
>>
>>
>>
>> 3.       Do we need update to a newer Version?
>>
>>
>> Thanks for help...
>>
>> Sven Vogel
>>
>> ---------------------------------------------
>> Sven Vogel
>> Systemingenieur / Consultant
>> Kupper Computer GmbH
>>
>>



More information about the samba mailing list