IIS Configuration Problem and WCF Service

[wph101larrya]

I have a developed service and client application running on a Vista machine in IIS7 in the Visual Studio 2008 beta 2 with .NET 3.5 framework.
I am trying to deploy the service app to a test pre-deployment server that is on the Internet running Server 2003 sp2. I have had all kinds of issues trying to get what seems a simple thing to work, publish the service and connect.
In Visual Studio I should be able to type URL of the service into the "Add Service Referrence" where upon Visual Studio should interrogiate the service and create the "hook-up" proxies and classes.
At this moment, I have a site setup on the server with HTTP on port 80. I installed the server extensions so that Visual Studio could connect the service directly in the project solution (which it does). So now I have the target service and the client app in a Visual Studio solution together. I then attempt to add the service reference to the client and I get the following error:

There was an error downloading 'http://sys117.bizb.net/aService.svc'.
The request failed with HTTP status 403: Forbidden.
Metadata contains a reference that cannot be resolved: 'http://sys117.bizb.net/aService.svc'.
The HTTP request was forbidden with client authentication scheme 'Anonymous'.
The remote server returned an error: (403) Forbidden.
If the service is defined in the current solution, try building the solution and adding the service reference again.

Does anyone have a step by step method that works for deployment? I would like to know.

[wph101larrya]

In the continuing saga of the above post... I haven't been sussessful in getting Visual Studio to communicate with the site on IIS6 to use it for WCF service.
I have a working version on IIS7 local with Visual Studio.
I set up another machine remotely from the dev machine with Vista and IIS7. I have installed the frontpage server extensions (FPSE). Everything checks out with one major problem, I can't login to any FPSE extended site with the FPSE admin tool or Visual Studio. I gives the same symptom that you have on IIS6 when there is no metadata for NTLM. That is it will display the login screen and you can login until you die but no error and no login. In IIS6 to fix that problem you must use the metadata editor tool from the IIS resource tool kit (which I have always thought was a pain) and manually add metadata for the NTLM login support.

The question is: Do you have to have a similar tool in IIS7 for the FPSE to authenticate a connection? If so where do you get such a tool? Or what is the recommended workaround?

Stumped for days now!
Larry

Note the reason for all this fuss in the first place is that I can't get my WCF client application in Visual Studio to be able to add a WCF service reference that is running on an IIS installation. It all works just fine in the localhost. For you long time die-hard coders with an anger management problem, you will understand that this three day old issue has already cost me a new keyboard.

[kenobewan]

Here is an article that may help:
Deploying an IIS-Hosted WCF Service