Well Sumaira,
That’s what the firewall is intended for. You should open port 80 (or someone else if accessing the service by soap.tcp) to allow incoming requests to your machine.
HTH,
Martin Kulov
www.codeattest.com
Hi Sumaria,
I agree with the earlier response. Your firewall is doing it's job. You
can open Port 80 if you want wide open access to your service on your
computer. You may want to do this with some caution, as this will be one
of the first ports hackers start to ping. If you want to limit what
machines can call your service, you can open the port, and then add port
filtering security to the web service itself. Also be sure to add port
filtering to the default web site, and take precautionary measures such as
disabling/deleting the IIS web based admin page.
Regards,
Dan Rogers
Microsoft Corporation
--------------------
>From: sumaira.ahmad@gmail.com (Sumaira Ahmad)
>Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
[quoted text clipped - 7 lines]
>Content-Transfer-Encoding: 8bit
>X-Trace: posting.google.com 1099600534 30780 127.0.0.1 (4 Nov 2004
20:35:34 GMT)
>X-Complaints-To: groups-abuse@google.com
>NNTP-Posting-Date: Thu, 4 Nov 2004 20:35:34 +0000 (UTC)
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!tornado.fastwebnet.it!tiscali!new
sfeed1.ip.tiscali.net!news.glorb.com!postnews1.google.com!not-for-mail
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.aspnet.webservices:26382
>X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
>
[quoted text clipped - 8 lines]
>Thanks,
>Sumaira