text/microsoft-resx 2.0 System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 Version 3.x of TI Pro should automatically detect and use the correct HTTP settings. However, some customers are having trouble. This will help you track down any problems. This will let you test several different URLs using several different proxy settings. The test will generally stop after the first failure. That's why the proxy settings are all checkboxes. As soon as you find a failure, you probably want to skip that test and try the other settings. The first proxy option is the default. This should be read from the operating system. If MSIE works, this should work. The second option is no proxy. We do this only to see if it's different from the default. The logs show what server the software selects for the proxy. The third option is a custom proxy. The information will come from your system administrator. We test three different URLs. The first two should return the current time. One uses a host name and the other uses an IP address. This will help us see if the DNS is the problem. The third test should display the date 10 times. There should be a 1 second pause between each row. This checks to see if the proxy is affecting the timing of the results. Our server requires realtime streaming HTTP data. You can add a fourth URL. This can be almost anything. Some proxies treat different URLs different ways. Maybe it's blocking our web site, but allowing wikipedia.