Current System Configuration :

•       Asus P2L97S Motherboard with Adaptec SCSI3 onboard
•       Intel Pentium II 233Mhz processor
•       96 Mb 168Pin DIMM's
•       2.1 Gig Seagate 'cuda drive
•       Panasonic SCSI CDRom
•       Sony SDT7000-BM 4mm backup drive (4/8 Gig)
•       3com 3c905 10/100 BaseTX network card
•       ATI 4Mb RageII Video card
•       PS/2 Mouse

Special note : SCSI configured on IRQ 10 and 3com on IRQ 11

Server Side:

Installed Microsoft Proxy 2.0 :

I tend to install it into its own drive, of at least 500Mb size. Then I dedicate that drive just for the proxy. In my case I usually do an F:\ drive or G:\ drive. It must be NTFS. I usually allow for all but about 50 - 100Mb for the cache. I leave the rest in case I ever decide to turn on logging, then I dont get a problem with space. Good proactive thinking, no?

• Insert CD and it will autoplay.
• Key is : ***-*******
• Change folder to F:\MSProxy2.0\
• Click on install options
• Choose to select all components
• Continue
• For caching, remoeve all entries from c:

Add 400Mb for F:\


• Internal IP addresses are 192.168.1.1 thru 192.168.1.255
• Defaults for "Client Install" options
• DeSelect both access controls for both proxy services

Client Side:

• On the client machines, open up the "Network Neighborhood".
• Find the NTserver in the 'hood and open it.
• In that folder, should be a folder for "mspclnt".  Open that.
• That folder will contain a "setup.bat" file.   Run that.  That is the actual installation program.
• Choose continue.
• Change the folder if so desired.
• Click on Install icon.
• Click on OK when completed.
• Reboot the PC (This is undocumented, but there are setup files that need to be put in place.)

At this point, you can begin to test the install.  There is a new control panel applet, called "WSPClient".  You can double check it at this point, to make sure that the server name and options are correctly selected.

They claim (Microsoft) that this is all that is needed to make this work.  I am currently running on a client, thru a proxy, thru a parent proxy, to the web.  I seem to have a bit of difficulty, but that could be do to my special case of my parent proxy being WinProxy instead of Microsoft.  What I did find out, is that I can access an internal mail server, after the Microsoft Proxy server, but before the WinProxy server.  The mail server I can contact, is not "pingable" or accessible, so it would appear that in a single proxy setup, this may very well be sufficient.

More to follow .......