Am 07.04.2012 19:39, schrieb Romain LE DISEZ: > Hi Tim, > > a better description of the problem than "it does not work" could help. > > But, here is my idea. When configuring a SOGo server, you configure Apache to > set some headers that indicate to SOGo the URL/port used for the connection. > > If it work internally, you probably set those headers: > RequestHeader set "x-webobjects-server-port" "80" > RequestHeader set "x-webobjects-server-name" "192.168.1.3" > RequestHeader set "x-webobjects-server-url" "http://192.168.1.3"; > > But these values are incorrects when accessing from the outside. Try to > change these values with the "outside" URL / port: > RequestHeader set "x-webobjects-server-port" "665" > RequestHeader set "x-webobjects-server-name" "140.134.120.134" > RequestHeader set "x-webobjects-server-url" "http://140.134.120.134:675"; > > If it works, you found the problem. The fix is to create two vhosts in Apache. > > You can also use a generic configuration (but for the port forwarding, you > must have inside port = outside port). See the diff attached for a generic > Apache configuration (generated on a CentOS, can't guarantee it is applicable > on a Debian). It's better to work with (dynamic) DNS names. For this you need an internal DNS server which resolves the internal IP address for the (dynamic) name you use external and you get everytime the right IP address. If you have no DNS server in your local network you can use an entry at the local host table on each PC or on the firewall/router (if this is supported).
Stefan -- *CaC, Computer and Communication* Inhaber Stefan Klatt End-2-End Senior Network Consultant Triftstrasse 9 60528 Frankfurt Germany USt-IdNr.: DE260461592 Tel.: +49-(0)172-6807809 Tel.: +49-(0)69-67808-900 Fax: +49-(0)69-67808-837 Email: [email protected]
<<attachment: stefan_klatt.vcf>>
signature.asc
Description: OpenPGP digital signature
