![]() |
How the Automatic Web Proxy Setting Works |
||||||
Kenn's
19990615: How the Automatic Web Proxy Setting Works
June/1999
|
This note has been updated! See September/2000, Tech Note #3. For the latest information regarding WSD1IP, please see the WSD1 information document posted at the shop ftp site. The automatic web proxy updater relies on the Microsoft TCP/IP stack, and will not correctly update any browsers if used with a different version of TCP/IP, such as Trumpet Winsock, Netscape Dialer, or Microsoft's PPP Dialer. Also, the browser settings will not be updated for systems which are not connected to a network. If you are using a laptop to dial in to a school using Dial-Up Networking, either do the install at the school with the laptop on the network, or dial in to the school before beginning the install. Here's how the automatic web proxy update process works: Stage 1. The command WSD1IP /WEBPROXY is executed. (Wfwg 3.11 does this via a load= command in win.ini, Win 9x does this as a part of the Automatic Hard Disk Maintenance script which loads at startup, and Windows NT does this as a part of the WSD1Environment service which loads at startup.) WSD1IP /WEBPROXY looks for a file in the Windows (SYSTEM32 in NT) directory called WSD1IP.RPS. It then analyzes the local TCP/IP information. If it concludes that the workstation possesses a legal WSD#1 IP address, it then resolves the name and determines what the recommended proxy server should be (schps.wsd1.org). It then compares that name with the name in WSD1IP.RPS (Recommended Proxy Server). On systems where the routine does not confirm a valid WSD#1 IP address, or where the recommended proxy server matches the name stored in WSD1IP.RPS, no files are changed, and no further action occurs. If it determines the recommended proxy server is not the same as what is listed in WSD1IP.RPS, or if there is no WSD1IP.RPS file, it will (re)write the WSD1IP.RPS file and then search the hard drive(s) for files named NETSCAPE.INI, IEXPLORE.INI, and PREFS.JS. These are files which contain configuration information for certain versions of Netscape and Internet Explorer. For any such file it finds, it backs it up first to <filename>.00? and then rewrites it to the specifications noted in Tech Note #14. For Workgroups systems, there is no other component. Only browsers controlled by the above-noted text files are affected on Windows for Workgroups computers. Stage 2 (Windows 9x only). The file WSD1IP.REG is rewritten and silently merged into the registry. This file contains user information corresponding to the desired proxy configuration, and must be entered for every user that logs on to Windows 9x where user profiles are enabled. A registry key named WSD1AutoConfig causes this same file to be silently merged for all users when they log on, ensuring all users receive the same proxy configuration. This affects all 32-bit browsers which store setup information in the registry. Stage 2 (Windows NT only). The file WSD1IP.SCR is rewritten. This is a Kix32 script containing user information corresponding to the desired proxy configuration, and must be entered into the registry for every user that logs on to Windows NT. A shortcut called WSD1 Auto Config in the common Startup group causes the script to be executed for all users when they log on, ensuring all users receive the same proxy configuration. This affects all 32-bit browsers which store setup information in the registry. |
||||||
DISCLAIMER: This document is intended for the reference of computer support personnel within Winnipeg School Division No. 1. There is no warranty or liability if procedures recommended here have an adverse affect on any systems. Use them at your own risk. Any trademarks mentioned are the property of their owners, none of whom have certified any information provided here. Opinions expressed here are personal only and do not represent the policy of Winnipeg School Division No. 1 or any other organization anywhere.
|