Parker Software Ltd Homepage
Forum Home Forum Home > WhosOn Live Chat > FAQ's > Advanced FAQ's
  New Posts New Posts RSS Feed - Making The WhosOn Gateway Use Port 80
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

Making The WhosOn Gateway Use Port 80 - Event Date: 23 Nov 2006 - 26 Jul 2007

 Post Reply Post Reply
Author
Message
Stephen View Drop Down
Admin Group
Admin Group
Avatar

Joined: 21 Oct 2005
Location: Stoke on Trent
Points: 1454
Post Options Post Options   Thanks (0) Thanks(0)   Quote Stephen Quote  Post ReplyReply Direct Link To This Post Calendar Event: Making The WhosOn Gateway Use Port 80
    Posted: 23 Nov 2006 at 9:49am
The WhosOn gateway is used when visitors are tracked using embedded code in your pages instead of log files. It also handles the chat 'invites'.

By default the WhosOn Gateway 'listens' on port 8080 for the page tagging requests. This port can be changed to any unused port. The best port to use to avoid any firewall issues both at the visitors end and at the WhosOn end is port 80.

You can only use port 80 for the Gateway if your WhosOn PC has at least 2 external IP addresses. This is because IIS also needs to use port 80 and IIS is required to serve the WhosOn chat (and your web site if WhosOn is running on your web server). You must configure IIS to only use 1 of your IP addresses (using the Windows HTTPCFG utility) so that the Gateway can use the other.

The procedure for setting up the Gateway to use port 80 is as follows:

- Install the HTTPCFG.exe utility from the Windows 2003 utility disk.. or download it from here: http://downloads.whoson.com/httpcfg.exe - save it to C:\Windows
- Open a command prompt and enter: HTTPCFG SET IPLISTEN -i {ipaddress1}
- This will make IIS listen only on the IP address specified.
- Stop and Start IIS
- Stop the WhosOn Gateway if it is running.
- Open the WhosOn Service Manager - select File - Server Options - Remote Access - WhosOn Gateway
- In the 'Listen On IP Address' drop down, select the 'other' IP address.
- Change the 'Listen For Page Tagging Requests On Port' entry to 80
- Change the 'SSL Port' to 443.
- Change the 'External Domain Name Or IP Address' entry to the selected IP address (you could assign a DNS name to this eg 'gateway.mysite.com' and use the DNS also).
- Click OK to save the settings
- Restart the WhosOn gateway
- Now restart the WhosOn Client, and re-generate the embedded code to upload to your site.

The page tagging tracking will now be using port 80 (and 443 for SSL pages). This is how we do it for the WhosOn 'Hosted' service. When we get a new hosted server we give it 2 external IP address. We register 2 DNS names 'hostedx.whoson.com' and 'gatewayx.whoson.com'. We then configure WhosOn as above using the external DNS 'gatewayx.whoson.com' as the external gateway address. We also obtain an SSL certificate for both DNS's. We assign 1 to the IIS default web site 'hostedx.whoson.com' and the other to the gateway. Thus we can have secure chat and the tracking code can be used on SSL pages without security warnings.

Steve

Edited by Daniel - 29 Dec 2009 at 11:03am
Stephen Parker
Back to Top
Daniel View Drop Down
Admin Group
Admin Group
Avatar
Technical Director

Joined: 19 Dec 2006
Location: Stoke-on-Trent
Points: 881
Post Options Post Options   Thanks (0) Thanks(0)   Quote Daniel Quote  Post ReplyReply Direct Link To This Post Posted: 25 Apr 2007 at 12:15pm
Sometimes the machine needs to rebooted for the changes to IIS to take effect. + After stopping & starting IIS, you need to check what ports it is listening on; open a command prompt, and type (| is the pipe character, shift and \ on a UK keyboard):
netstat -aon | find ":80"
This will display the proc ids that are running on port 80. If anything is listening on 80 on 0.0.0.0 then you will probably need to restart the machine at this point.
Back to Top
Daniel View Drop Down
Admin Group
Admin Group
Avatar
Technical Director

Joined: 19 Dec 2006
Location: Stoke-on-Trent
Points: 881
Post Options Post Options   Thanks (0) Thanks(0)   Quote Daniel Quote  Post ReplyReply Direct Link To This Post Posted: 26 Jul 2007 at 11:08pm
Sometimes even doing this won't work - you may need to use this method:
1. httpcfg delete iplisten -i 0.0.0.0
 
This removes IIS from listening on all available IPs 0.0.0.0
 
2. httpcfg delete iplisten -i <second ip address>
 
Removes IIS from listening on the second IP
 
3. 2. httpcfg set iplisten -i <first ip address>
 
Expliclitly configure IIS to be listening on the first IP
 
4. httpcfg query iplisten Check the HTTP.sys IP listening list, you should only see the first IP in it.
 
After this above, please run:
 net stop http
net start http
 iisreset
 
 to restart HTTP service before restarting IIS.
 
 Restart IIS services will not make the changes of HTTP.sys take effect.
 
 


Edited by Daniel - 04 Aug 2008 at 4:48pm
Daniel Tallentire
Support
Parker Software
Back to Top
Daniel Horton View Drop Down
Admin Group
Admin Group
Avatar
Technical Support

Joined: 01 Jun 2009
Location: Stoke-on-Trent
Points: 347
Post Options Post Options   Thanks (0) Thanks(0)   Quote Daniel Horton Quote  Post ReplyReply Direct Link To This Post Posted: 23 Aug 2011 at 3:15pm
Windows Server 2008 (or above)

Within Windows 2008 you can use the Net Shell HTTP command to populate the available IP addresses for your Network Card to use within IIS.

To use Netsh, open CMD with Run As Administrator and type Netsh. This will open Net Shell and from here you can drop into the HTTP level by typing in HTTP and hitting enter. need to use a Net Shell command to manually populate the IIS MetaBase list of available IP addresses for HTTP. The command will require Netsh -> HTTP (http://msdn.microsoft.com/en-us/library/cc307236(v=vs.85).aspx)


Once inside the HTTP level you can now use the command Add IPListen to populate your IP addresses for the Network Card that you wish IIS to be able to access (note that the gateway's chosen IP address needs to be excluded from your additions). Type add iplisten {NIC ip address} then enter.

Now exit the Netsh command level and use Net Stop HTTP to stop the World Wide Web Service. Then IISReset to reset IIS and the World Wide Web Service and restore IIS to only use your specified IP address via HTTP.

The gateway and IIS elements will now be able to co-exist on the same machine via TCP 80 and two different IP addresses.



Edited by James Horton - 11 Apr 2012 at 4:02pm
Best Regards,

Daniel James Horton
Technical Manager
Parker Software
Back to Top
Daniel Horton View Drop Down
Admin Group
Admin Group
Avatar
Technical Support

Joined: 01 Jun 2009
Location: Stoke-on-Trent
Points: 347
Post Options Post Options   Thanks (0) Thanks(0)   Quote Daniel Horton Quote  Post ReplyReply Direct Link To This Post Posted: 23 Aug 2011 at 3:19pm
We now also support the use of IIS for the gateway via ARR.

This offers many benefits such as the fact that WhosOn can operate from a single IP address via TCP 80 (HTTP) and 443 (HTTPS).

For further information consult the help -  http://www.whoson.com/help/index.html?arr_and_the_whoson_gateway.htm



Edited by James Horton - 04 Jun 2013 at 3:35pm
Best Regards,

Daniel James Horton
Technical Manager
Parker Software
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 11.05
Copyright ©2001-2016 Web Wiz Ltd.

This page was generated in 0.078 seconds.