RE: The underlying connection was closed: Unable to connect to the rem

Resolved. I saw another posting regarding this problem but the guy who posted
it found out his problem was related to something else. However, he posted
his code. In his code I saw he was setting the HTTP UserAgent property on the
HTTPRequest, something I wasn't doing. I set the property to the name of my
app and it worked! I didn't know the proxy server was now requiring it. It is
not something that would normally get desiminated by the "black hole".

"Brad Roberts" wrote:

> I have a VB.NET application running on Win2K in an AD Domain. My App runs
> locally as a service, using a Domain Account, and runs a web page on the
> internet. The request is initiated by
> System.Net.HttpWebRequest.Create(CurrentURL) and the getResponse() on the
> request. It uses SSL with a Proxy Server in play. Everything has been working
> fine for a long time until recently when I consistently get the above error
> message.
>
> I have checked the "effective" local security policies and see nothing that
> stands out. The account is an admin on the local box.
>
> Any ideas would be appreciated...
>
.

Relevant Pages