A Forum reader recently asked:
"Is there any way to have the secure gateway on the same machine as IIS, other than loading one of them into a VM (take that, wise guys)? When I tried it, one won't start if the other is running.
It seems like a great expense to put a server online for a small site with few mobile users that is also security-aware."
And here's the response from Doyle Collings ...
I was able to get Secure Gateway and IIS on the same box by doing the following:
1. In the securegateway.properties file, unremark the HttpPort=80 line and change the value to 82:
2. Add HttpSSLPort=442 (The default is 443, which conflicts with the IIS default.)
3. Save the file.
4. Restart the Secure Gateway Service.
5. Follow the instructions on page 16 of the Intellisync Mobile Suite Secure Gateway Administrator's Guide and specify http port 82 as part of the Secure Gateway Server Name. I actually used the IP address (e.g., http://220.127.116.11:82).
I did not want to require clients to remember port 82, so I made a name-based virtual host in IIS that pointed to the http address and port. For example, the host header is sync.domain.com, and the home directory is http://18.104.22.168.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.