Today I changed some ProgramAnd use the class that gets the webpage to capture the webpage. System. net. webexception: the basic connection has been closed: the remote server cannot be connected.
Connect to the target website. If you want to find out why, use Iris to sniff. There is no data in the output port. I think, will it be another network card? All other NICs, including wireless and virtual NICs, are disabled even if they are not connected. Check whether using this class VIa Asp.net is still useful, but the console program won't work, and it's almost desperate. Finally, I suddenly thought: I went somewhere else and set a proxy in IE. But it doesn't make sense. Now I am using ADSL. in Internet Explorer, the LAN proxy is invalid when dialing. In addition, we usually use various methods to access the Internet without passing through this nonexistent proxy.
No matter how many, the check box before enabling proxy is removed from the LAN Settings, and the program is easy to use immediately.
Conclusion: A small bug in. NET Framework 1.1 still uses the proxy information in LAN Settings during dial-up connections. This problem occurs in the console program, but Asp.net does not. It is also strange.
