PROBLEM DESCRIPTION =================== The outcome of the execution of PAC file seems to change when called from IE or from a .Net 2.0 client. The internal URL we want to call is http://webapps.custname.com and the IP address of the web apps server is 141.122.180.192. For example, here is a sample PAC file function FindProxyForURL(url, host) { if (isInNet(host, "141.122.0.0", "255.255.0.0")) { return "DIRECT" } else { return "PROXY 169.12.232.25:8080" } } When called from IE, the internal url http://webapps.custname.com is directly connected to the web server without using a proxy. So the PAC file returns “DIRECT”. When called from a .Net 2.0 application, the same url (http://webapps.custname.com) is redirected to the internal proxy 169.12.232.25:8080. If he uses the IP address of the web Server ( http://141.122.180.192 ), the isInNet function seems to work as the request is not redirected to the proxy anymore. I used the code below to test the differences between .Net 1.1, .Net 2.0 and IE (taken from http://msdn.microsoft.com/msdnmag/issues/05/08/AutomaticProxyDetection/default.aspx ). using System; using System.Net; public class Test { public static void Main(string[] args) { IWebProxy iwp11 = GlobalProxySelection.Select; Console.WriteLine(iwp11.GetProxy(new Uri(args[0])).ToString()); //comment the following 2 lines when compiling on 1.1 IWebProxy iwp20 = WebRequest.DefaultWebProxy; Console.WriteLine(iwp20.GetProxy(new Uri(args[0])).ToString()); }  …

PROBLEM DESCRIPTION===================You are using Site Manager from MCMS 2002.Site Manager is partly build on C# and is using the HttpWebRequest class in .NET framework to connect to the MCMS server.In the customers environment SiteManager wrongly tries to connect through a proxy server rather than directly connecting to the MCMS server. SUMMARY of TROUBLESHOOTING==========================Using a configuration file to instruct your application to use the right parameters:. Set the GlobalProxySelection option in the application config file (NRClient.exe.config) and copy the file into “C:\Program Files\Microsoft Content Management Server\Client” (see below for file content) <configuration>    <system.net>        <defaultProxy>            <proxy                proxyaddress = “http://proxyaddress:port” bypassonlocal = “true” />        </defaultProxy>    </system.net></configuration>   CheersCarlo

As my colleague Tess told a while ago, sometimes the problems seems to come in bunches; so it happened that I saw the following error message from two different customers in less than a week… Server Error in ‘/’ Application. Configuration Error Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. Parser Error Message: This config section already contains an identical line, which is not allowed.Source Error: Line 350:   extension=".js" Line 351:      type="Microsoft.JScript.JScriptCodeProvider, Microsoft.JScript,    Version=7.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> Line 352:   </compilers> Line 353: Line 354:   <assemblies> Source File: c:\windows\microsoft.net\framework\v1.1.4322\Config\machine.config    Line: 352 Unfortunately this error message is a bit misleading, and you get this problem if you run multiple installations of a Device Update for Outlook Mobile Access (OMA), without have first uninstalled previous versions of this update. To resolve the problem, open your machine.config file and check line #359 and #367 (please note that the line numbers may vary a bit, depending if you have installed other components which have changed your machine.config):– line 359: assembly=”System.Web.UI.MobileControls.Adapters,Version=1.0.0.0,Culture=neu­tral,PublicKeyToken=b03f5f7f11d50a3a” /> – line 367: assembly=”System.Web.UI.MobileControls.Adapters,Version=1.0.0.0,Culture=neu­tral,PublicKeyToken=b03f5f7f11d50a3a” /> Both lines should be the same. Next, remove the section that…