Page 1 of 1

Portforwarding

Posted: Tue Feb 20, 2007 3:23 pm
by Spridis
I have tried the Search-button with no success so...

What do I have to do to get Scalix to work behind a firewall (IPCop) with portforwarding?
Is it even possible?
If possible, are there any more ports than 80 and 25 need to be forwarded from the evil internet to gain webaccess and to get emails flowing?

I have registered a FQHN (my Scalix-server hostname) at my ISPs DNS that is pointing to the external IP on my firewall.
What happends if I register the Scalix internal IP (192.168.x.x) in my local DNS-server (IPCop), does this mess something up?

The users need to have full access to the mailserver (outlook etc) when they are at work and only webaccess when they are out of office, no pop or imap to the outside.

Posted: Tue Feb 20, 2007 6:00 pm
by kanderson
Port 25 will allow inbound email.
Port 80 will allow webmail connections.

That should be all you need. We have a number of clients running IPcop in front of Scalix, and it's working quite well. What problems are you seeing?

Kev.

Posted: Wed Feb 21, 2007 6:30 am
by Spridis
No problems so far.

Posted: Tue Mar 20, 2007 10:45 am
by pharoh
what ports do I need to forward for remote scalix-connect users (outlook). These users are on a far end so I need to travese a nat to get to the scalix box.

Posted: Tue Mar 20, 2007 1:14 pm
by KevinAnderson
5729

Keep in mind that in a multi server environment, this will not work.

Kev.

Posted: Tue Mar 20, 2007 1:20 pm
by pharoh
would it work if I portforwarded the individual user/company each to their respective "home" server?

Posted: Tue Mar 20, 2007 2:14 pm
by KevinAnderson
Not really. Some parts will be fine, but things like delegation can be fairly complex and require DNS resolution between the servers and the desktops to all be correct.

Are you a multi server environment? If yes, I'd advise a VPN for now.

Kev.

Posted: Tue Mar 20, 2007 2:56 pm
by pharoh
no just asking in case it became that way :-)

Posted: Thu Jun 07, 2007 4:46 am
by pcrock
Just looking at this thread from a different perspective. We've got Outlook connecting OK via our vpn with 5729 being open, I've read that 5757 is UAL Free/Busy, but I can't find any documentation on this other than being referred to in a few posts. Is it vital to have this open, we've been running for a couple of months with it closed and had a few 'odd' issues with people connecting via our vpn so this may be the cause, but I don't want to open it if it's not actually required.

I've also been through the install and admin docs, but I can't see a list of required ports anywhere, I must be missing something.

Phill

Posted: Thu Jun 07, 2007 8:51 am
by pharoh
we have ~40 people on the outside with just 5729 all using group scheduling and only 5729 forwarded. no weirdness yet :-)