Web Host Ports
Posted by Linda on 09 February 2007 12:08 AM
The Web Host should be just fine on any computer that has ports 80 and 443 available. Most sites have their Web Host running on the computer that is acting as their Collect! server. If your Collect! server is also running many CPU intensive tasks, then using another computer to run the Web Host is an option, but that should not be necessary. If disk access is your bottleneck, no matter which computer runs the Web Host, it will be the disk on the server that is being read and written to, so moving Collect! to a dedicated computer will not increase speed. Any server that meets the hardware requirements outlined in the following page will do the job as your Collect! server:


If you choose to run the Web Host on your 2003 Server, you can either disable the services that are already using those ports, or configure the Web Host to use different ports. Either way will work just as well. The port that the Web Host listens on is configured in the shortcut target that you are using to start it. For example, the default configuration has command line parameters including "/w1ss /s80 /y443" which puts it in secure mode, listens on port 80 for connections and forwards those connections to the secured port 443. To change this, simply modify your shortcut to use, for example, "/w1ss /s81 /y444."

If you wonder whether you should use a DMZ, or port forwarding, we suggest port forwarding and that is what we use. Just ensure that if you use nonstandard ports for the Web Host, you forward back to those nonstandard ports. If you only allow access to ports 80 and 443 on the Web Host, then both setups should have the same security.
(5 vote(s))
Not helpful

Comments (0)