Different behaviour when adding the same WSDL from the local development server or from a remote machine

Hi,

we're developing some web services and use the local development server of
Visual Studio 2005 to create, run and debug the project. The web service
methods connect to a database hosted on a dedicated server and the Microsoft
CRM 3.0 server, also on a separate machine. As the CRM server installation
makes changes to the Active Directory, they are located in a separate
domain, while the development machines are member of the companies domain.
There's no trust relationship between these domains. However, authentication
works fine with one problem:

Scenario 1:
The web service is hosted on a remote machine and in VS 2005 we add a web
reference to it, say http://remoteMachine:4444/webservice/service.asmx. When
creating a new instance of the generated web service proxy class, we set the
URL to the location of the web service (which is the same as the web
reference location, thus the default) and the Credentials property to a
valid NetworkCredential. Beside authenticating the user, the web service
further uses this credential to connect to the web services offered by the
CRM server. All of this works fine.

Scenario 2:
The exactly same web service is hosted on the local development machine and
in VS 2005 we add a web reference to it, say
http://localhost:2142/webservice/service.asmx. Beside that reference,
everything else is the same, so we create a new instance of the generated
web service proxy class, set the URL to the location of the web service
(which is http://remoteMachine:4444/webservice/service.asmx, thus different
from the default) and the Credentials property to a valid NetworkCredential.
So our request still goes to the remote machine, but this time each request
fails with 401 Forbidden/Access denied.

This is reproducable. If I change the web service reference back to the
remote machine, the application will work without problems. If I use the
local address, authentication errors will occur in each call to a web
service, though the remote address and network credential do not change.

Any suggestions?

Thanks
Michael


.

Relevant Pages

  • RE: Web Service Implementation Security Question
    ... Server was unable to process ... CompilerParameters parameters, Assembly assembly, Hashtable assemblies) at ... > As for the security problems regarding on using TypedDAtaset in asp.net ... Web Service Implementation Security Question ...
    (microsoft.public.inetserver.iis.security)
  • Re: Permission Errors
    ... >a domain account so that it can be validated on the win2k server machine. ... However I have discovered that I can deploy the web service to the W2K ... domain server and there it runs with no problems, ... for me to decide that the new XP dev machine is up and usable. ...
    (microsoft.public.dotnet.general)
  • Re: Permission Errors
    ... I built the TempConvert3 sample web service on the XP work ... Next I looked at the 2003 server and saw that the local path was ... XP work station. ... >>local workstation, not the server. ...
    (microsoft.public.dotnet.general)
  • Re: Permission Errors
    ... So when we move a webproject to a new server (creating the new virtual ... I built the TempConvert3 sample web service on the XP work ... |>>local workstation, not the server. ... visual studio automatically selected my work station as the ...
    (microsoft.public.dotnet.general)
  • RE: Asynchronous Web Service Method Failure
    ... this is an ASP page calling the ... >that pops up if the proxy can't reconcile the web method parameters. ... I cannot return a .pdf document object from a web service method ... >> On the server side, it's not a background thread any more than any other ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
Loading