Zentyal Forum, Linux Small Business Server

Zentyal Server => Installation and Upgrades => Topic started by: shocked on February 03, 2014, 07:55:04 pm

Title: OpenChange firewall ports
Post by: shocked on February 03, 2014, 07:55:04 pm
Hi All,

 We have installed Zentyal with OpenChange and it seems to be working fine. 

When I go to join a MS Outlook PC to Zentyal (this: http://labs.zentyal.org/part-ii-install-configure-zentyals-technology-preview-of-native-ms-exchange-replacement/)

It fails.  If I turn off the firewall, it syncs up great.  So, how can I find out exactly which firewall ports OpenChange needs to work with Outlook?  I would rather not just guess which ports it needs.

Thank you
Title: Re: OpenChange firewall ports
Post by: jkerihuel on February 04, 2014, 12:42:19 am
Good evening,

OpenChange is registered as an endpoint server for Samba4. When an RPC client like Outlook connects to Samba, it first queries the endpoint mapper to know where the service is located, then initiates a connection on the temporary port where the service is bind.

You therefore need to open:

* Samba4 sequentially assigns the tcp port depending on the port availability and order of the endpoint in the list.

If you intend to open these ports directly over the internet, I would strongly discourage you and instead advise to setup a VPN instead.

FYI, Zentyal 3.4 will be provided with Outlook Anywhere and your clients should therefore only have to open 80/tcp and 443/tcp.

Br,
Julien.
Title: Re: OpenChange firewall ports
Post by: Skymatix on June 07, 2014, 01:07:56 pm
Any updates on this?
Anybody actually got this to work??

I have tried everything possible... the moment I switch the fire-wall ON,  I cannot see the OpenChange server!
I have Zentyal V3.4.3
Title: Re: OpenChange firewall ports
Post by: BerT666 on August 18, 2014, 02:29:32 pm
I have the same Problem. (Zentyal 3.5 all Updates installed)
I added Rules for SMTP / IMAP => no connection possible (tested with Client & Telnet)
When I added the Rule "allow any TCP" it works...

But it is an unsecure workaround...

The Firewall Logs are emty, no hint why the connection doesn't work