dotnet web services: We were calling out to a web service just fine before we put our server
behind a firewall. Now we can't call out. Port 80 is open in the firewall.
What ports need to be open?

--
Regards,
Gary

"GaryDean" <GaryDean@newsgroups.nospam> wrote in
news:eb61ytCRIHA.6036@TK2MSFTNGP03.phx.gbl:

[quoted text, click to view]

TCP Port 80... or whatever port your server is running.


--

Hi Gary,

Regarding on this issue, I think we'd better first verify that the service
is listening on the 80 port and the client proxy does send the message to
the 80 port as well. Then, since the problem may be specific to firewall, I
suggest you also perform some network trace to see what's the exact error.
Is there any particular port mapping for your intermediate firewall or
proxy? Or whether the intermedate proxy require additional authentication?

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
From: "GaryDean" <GaryDean@newsgroups.nospam>
Subject: Web Services & firewalls
Date: Fri, 21 Dec 2007 16:44:36 -0700
Lines: 9
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Message-ID: <eb61ytCRIHA.6036@TK2MSFTNGP03.phx.gbl>
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: ip24-255-56-160.tc.ph.cox.net 24.255.56.160
Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.dotnet.framework.webservices:2674
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

We were calling out to a web service just fine before we put our server
behind a firewall. Now we can't call out. Port 80 is open in the
firewall.
What ports need to be open?

--
Regards,