Hi,
While deploying a Webservice in Windows 2003, you can use either application
pool or provide the default credentials.
We face issues many times while deploying a webservice, if we miss a single
step.
Below are the steps that we follow for deploying a webservice without
Application Pool:
1. Install the WEbservice.
2.if it is a new Virtual folder or a website, open the properties dialog
box.
3. Under Directory Security Tab, select Anonymous Access editing option.
4. Under Anonymous Authentication, select the IUSR_<MachineNameas the
default user
5. LEt the IIS maintain the password.
TRy running the webservices now.
If any other user is selected for providing the credentials, then, the user
should have integrated access to the database which the webservice accesses.
The user should also be given permissions for Temp folder, and other
processes involved.
Application pool to would follow the same steps except that an Application
pool can be reused for multiple websites or virtual folders.
"MACH II" <ma***********@hotmail.comwrote in message
news:47**********************************@microsof t.com...
You need to set the credentials for accessing the web service.
wsWebService.Credentials = New System.Net.NetworkCredential(lswsUser,
lswsPassword, lswsIP)
Note these might be the same user credentials under which the asp.net site
is running.
You might also need to check that the web service uses integrated windows
authentication, set fro IIS.
"hulinning" wrote:
>Hi,
I create my Webservice in 2003 VS and test in Windows 2000 and Windows
XP
Pro without any problem. When I deploy it over Windows 2003 server, It
fails
to connect to the WS. I got Anonymous access check, and integerated
Windows
authentication check.
My client, WinCE 4.2 device, still cannot access the web service. I got
a
WebException return to WinCE.
The same setting is always work in Windows 2000/XP Pro.
What else I have to do to make it pass the secruity checking ?
Thanks for any comment
