Changes between Version 259 and Version 260 of TracOnWindows

Timestamp:

Dec 8, 2008, 5:16:36 AM (15 years ago)

Author:

goodeye <dev@…>

Comment:

Running tracd on port 80

TracOnWindows

@@ -347 +347 @@
 }}}
 
+=== Running port 80 on tracd on Windows (Standalone) ===
+
+This describes getting IIS out of the way, so you can run tracd on port 80. This assumes Windows Server 2003 SP1 (IIS 6); I just haven't tried it on other versions.
+
+IIS typically listens to port 80 on all IP addresses, whether or not a website is assigned to an IP. This prevents other services from using port 80, including tracd. To get IIS to stop listening to all IP addresses, use '''httpcfg''' to tell it specific IP addresses.
+
+Install the Windows Server 2003 SP1 Support Tools.
+  Normally found on the installation disk. Also found here:[[BR]]
+  [http://www.petri.co.il/download_windows_2003_sp1_support_tools.htm][[BR]]
+  [http://download.microsoft.com/download/3/e/4/3e438f5e-24ef-4637-abd1-981341d349c7/WindowsServer2003-KB892777-SupportTools-x86-ENU.exe]
+  
+  This basically just copies the tools, which are just executables. However, the installer does set Start menu links, which are handy for knowing what's there, so run it. The files end up in:
+
+{{{
+C:\Program Files\Support Tools\
+}}}
+
+List IP addresses currently listening: (this will be an empty list to start)
+{{{
+httpcfg query iplisten
+}}}
+
+Add IP address(es) to listen:
+{{{
+httpcfg set iplisten -i 127.0.0.1      (to keep it listening on localhost; seemed like a good idea)
+httpcfg set iplisten -i nnn.nn.n.nnn   (other IIS IP addresses as needed; NOT the one you want for tracd)
+}}}
+
+Stop and restart http service.[[BR]]
+Note the stop and start are different, to stop top-down, and start bottom-up. This is not simply restarting IIS. Sometimes this fails to restart; reboot the server.
+
+
+{{{ 
+net stop http /y
+net start w3svc
+}}}
+
+Run tracd
+  Include the hostname option, so tracd runs on a specific IP that isn't in the IIS listening list.
+  The IP address worked locally, but a host name seems required for remote access. IIS still seems to check it before passing on it.
+
+{{{
+tracd -b hostname.domain.com (and other options as needed)
+}}}
+
+'''Side notes:'''[[BR]]
+This specific listen list is also needed (and is how I discovered it) for installing different SSL certificates on multiple websites. This frees up the dialog boxes that allow entering a specific IP address for the SSL port 443.
+
+Later, if you add a new IP address and website to IIS, you must add it to this listen list. You'll forget. I don't remember the error message, but I'm sure it's vague, and it will drive you crazy.
+
+There are other toolkits (even though this task boiled down to the one above):
+  - Windows Server 2003 Resource Kit Tools[[BR]]
+  C:\Program Files\Windows Resource Kits\Tools\[[BR]]
+  [http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&DisplayLang=en][[BR]]
+  dnsdiag, tail, cmdhere, about 130 others.
+
+
+  - IIS 6 Resource Kit Tools[[BR]]
+  [http://support.microsoft.com/kb/840671][[BR]]
+  C:\Program Files\IIS Resources\[[BR]]
+  Metabase Explorer, SelfSSL, a dozen others.
+
+
+  - SSL Diagnostics[[BR]]
+  C:\Program Files\IIS Resources\[[BR]]
+  (has a separate installer and start menu entry, but ends up in this folder with the others.)[[BR]]
+  [http://www.microsoft.com/downloads/details.aspx?FamilyID=cabea1d0-5a10-41bc-83d4-06c814265282&DisplayLang=en][[BR]]
+  SSLDiag.exe
+
+
 
 === Using SSL with tracd on Windows (Standalone) ===