Avoiding AddressAccessDeniedException: Change WCF Binding To netTcpBinding

I was trying to deploy a nifty new ASP.NET and Windows service application pair, in which the ASP.NET application included a WCF client which accessed the Windows service which hosted a WCF server.  But I found when deploying it to a Windows 2003 server (instead of my XP development box) that when I tried to start the service, I got the following error in the event log:

Service cannot be started. System.ServiceModel.AddressAccessDeniedException: HTTP could not register URL http://+:50621/XX1TestSuiteService/RemoteInterface/. Your process does not have access rights to this namespace (see http://go.microsoft.com/fwlink/?LinkId=70353 for details).

A little googling turned up this page (among others):

http://blogs.msdn.com/b/paulwh/archive/2007/05/04/addressaccessdeniedexception-http-could-not-register-url-http-8080.aspx

Certainly trying to reconfigure the server to allow for the registration of the use of an HTTP listener might eventually have gotten me where I needed to go.  But I only used the HTTP binding because it was the default for WCF.  These applications were going to be on the same server.  So between the performance improvement I understood the netTcpBinding provided and my desire to eliminate this error, I reconfigured my two apps to use that binding, with the help of a very detailed and easy process described by Microsoft here:

http://msdn.microsoft.com/en-us/library/ff647180.aspx

After re-installing the Windows service, it started without any error.