 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / New Users / August 2005The underlying connection was closed: Unable to connect to the rem
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... Offhand, it sounds to me like you're scraping someone's site that doesn't want you to, and they've picked something about your connection to block based on, ip, user agent, etc. You'll have to provide more details about what you're connecting to and it might even get down to hardware load balancers and firewalls in between. This isn't something that's easily going to be solved in code most likely. Bruce Dunwiddie http://www.csvreader.com > 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 [quoted text clipped - 8 lines] > > Any ideas would be appreciated... The web site is one of my own. The problem is proxy server or AD policy related, I'm sure. The service is running on my machine on the internal network and attempting to access the web site on the dotcom web. I have had to authenticate with the proxy server to get access to the web. However, this has been working fine for a year. Any ideas on IE or Win2K patches that may modify local settings to make this happen would be appreciated. There are AD policies in play. However, I am not an admin and am not notified when policy changes are applied. If the problem is a policy change then I need to know which policy in question before I go to the "black hole people" to attempt to get a fix. (The network folks do not think it is their job to trouble-shoot other peoples's problems.) Thanks for any suggestions.... > Offhand, it sounds to me like you're scraping someone's site that > doesn't want you to, and they've picked something about your connection [quoted text clipped - 18 lines] > > > > Any ideas would be appreciated... 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". > 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 [quoted text clipped - 8 lines] > > Any ideas would be appreciated... Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.