scalix natted behind linksys OK?

[jefe7777]

Just installed scalix/centos to test. The server is sitting behind a typical linksys firewall, as are all the workstations.

Everything seems to work: webmail, sac, outlook

Everything except the sharing of stuff in outlook.

I suspect the problem to be the in the way that I setup the hostname, etc.

For example, I used:

-foo1.realdomain.tld as hostname of server.
-foo1.realdomain.tld resolves forward/backwards properly to a public ip.
-the actual IP address of the server is not the public IP in question though, as it's natted.(with all the mail related ports forwarded to the scalix server)

This caused an initial problem of setting up Outlook clients as they had to connect to "foo1.realdomain.tld", which resolves to a public ip, so they end up going outside the nat, and when they try and get back in, they hit the firewall.

So I setup a second DNS entry "foo2.realdomain.tld" that points to servers private/nat ip address (i.e. 192.168.0.220). This allowed the Outlook clients to connect, and they work, except for sharing calendars, contacts etc.

Thoughts?

[mephisto]

I'm using the same setup here, i.e. an internal dns that resolves my server's hostname to its internal IP. This is working fine even with roaming clients if I set scalix connect to use the fqhn and not the scalix-default-mail alias.
Nevertheless, I also suspect you have a dns issue.

[jefe7777]

Thanks for the response.

I made the configuration more straight forward.

Gave the scalix server a static public ip. Put it out in front of the linksys, directly on the dsl modem. So now hostname via DNS (a & ptr records) and the server's actual IP/hostname all match.

Reinstalled Scalix, and everythings happy.

[burhankhalid]

I had a similar setup to yours, except I did it a bit differently. Posting it here in case you can find some ideas or suggest improvements.

We have an external server that does our preset email routing and runs our web server.

Internally, we have 6 servers, one of which is scalix, the other is webmail, and the rest are for various other tasks. All connected via a Linksys router to the internet using one static IP.

The majority of the system users are all on the internal network, we have some roaming users.

I setup a mirror DNS locally so that mail.mydomain.com points to the internal scalix server's private IP address. I also setup webmail.mydomain.com the same way.

Then, on our public DNS servers, I pointed mail.mydomain.com to our static IP address. I created a subdomain on our public web server for webmail.mydomain.com, and just installed SWA on that box (pointing it to mail.mydomain.com).

Now what happens is that internally, people connect to our scalix server without having to jump on the internet. This was a big concern of mine because access here is not very reliable (a recent fire knocked out three of the four ISP in the country).

Outside users will automatically connect to the 'outside' server when they type webmail.mydomain.com, and then SWA will connect to the internal server.

Works great for us because even if the internet is down, the majority of the users are able to send mail to each other (which is the current email use profile).