Version 6 (current) Version 5 Version 4 Version 3

Current version:

1. Fixes some problems with PPPOE connections.
2. Repairs StarBand 180 and 360 box connectivity issues.

1. 3.0R1q has an updated set of drivers (NAT version 1.15, DNE version 2.04). These drivers contain a fix for the Mini-Port problem. New users will not get the Mini-Port problem (multiple instances of 'mini-port' showing up in the network settings).
2. The new drivers should also repair an existing mini-port problem. A user who currently has the mini-port problem is encouraged to upgrade to this version.
3. Flash Acceleration settings have been moved from registry-based entry to a position in the GUI.

WinProxy version 3.0R1p addresses some earlier problems with connectivity through StarBand's satellite system and their acceleration software.

WinProxy 3.0R1o should always replace version 3.0n or 3.0m (version previous to M do not have this issue). It was changed to update web page handling and viewing in circumstances where web pages would not display properly.

WinProxy 3.0R1n is identical to 3.0R1m *except* that 'n' has newer DNE drivers. These DNE drivers (the low-level network drivers) have the same internal version numbers in WinProxy versions 'k', 'm', and 'n', and you will need to follow special procedures to ensure that you have the very latest drivers if that is important to your installation.

This version of WinProxy has a more recent set of DNE drivers than does WinProxy 3.0R1k (the previous release). This set of drivers fixes two problems:

1. K_Mode exception error on some NT machines, and
2. Failure to load Transparent Proxy on some Windows 2000 machines. The drivers in both 3.0R1k and 3.0R1m carry the same version number, so if you are upgrading from 'k' to 'm' specifically to fix one of these problems you'll need to take special care that you get the newer drivers. Upgrading to 'm' from an earlier version than 'k' will not require any special action to ensure that the drivers are updated.

1. Support for operation under Windows 2000 and Windows Millenium has been added.  WinProxy will work on Windows 95, 98, 98SE, NT4, 2000, and Me.
2. Feature names are now shortened in WinProxy's lower feature bar.  'BB' instead of BannerBlocker, for instance.  This is simply to make it easier to see all of the enabled features.  'Firewall' and 'Cache' are still spelled out in full.
3. Terminate ALL connections, as a right-click option.  Hi-lite a connection in ConnectionView, and right-click.  One option - 'Terminate' - has been there for a while, and allows you to immediately terminate that connection.  The new option 'Terminate ALL' will terminate all current connections immediately.  (WinProxy will not update settings while there is an active connection.  On a busy day, it can be impossible to 'terminate' the current connections fast enough to get a new setting to take.  This new option will do the trick.)
4. Routing table changes available for all connection types (not just for dialing).  WinProxy can make routing table additions for you, no matter what kind of Internet connection you have.  You can add these under File-Settings-General-DialUpSetup-RoutingScript, or under File-AdvancedSettings-ClientAccessMethod-ConfigureRoutes.
5. Updated route table algorithm for NAT.  The routing table and rules used in NAT only operations will match that used in Transparent and Classic Proxy to make IP trouble-shooting easier.
6. Updated External Gateway detection.  WinProxy will perform an automated test to find and use an external gateway address.
7. Cache search updated.  WinProxy employs a faster, more efficient method to find and return files from its cache of web documents.
8. Auto-updates virus scan engine.  WinProxy 3 has always updated virus data files on a daily basis for users who have subscribed to the Antivirus module.  Now, if a scan engine update is also required to catch that latest virus, it will be done automatically.
9. Checks more often for new anti-virus and smartfilter updates (every three hours instead of once a day).
10. Faster internal name resolution.  WinProxy has to know the names and addresses of the computers on your local network.  The method to find or confirm local names has been optimized to help make your connections as quickly as possible.
11. Supports AOL5 dialing.  Users who have AOL as their ISP are expected to use an AOL browser to connect.  WinProxy will use AOL's dial adapter to connect and disconnect for you; this release supports both AOL4 and AOL5.
12. Checks server for updated DNS default numbers on first connection.  WinProxy will use some default DNS numbers to help you get connected as quickly as possible even if you don't yet know what DNS means.  After initial installation and on your first connection to the Internet through WinProxy, WinProxy will check for a newer set of default DNS numbers and use them instead.  We still recommend that you configure WinProxy with your ISP's DNS addresses for best response, and to follow proper 'netiquette'.
13. DNE version displayed in About box.  We use Deterministic Network drivers to help provide Transparent Proxy and NAT; WinProxy will now display the version number in its About box.
14. NAT version displayed in About box even when it fails to load.  The NAT driver is another piece required for Transparent Proxy and NAT operation.  WinProxy has been displaying this number after the drivers load; starting in this release, it will report the version number whether the NAT driver has loaded or not.
15. 'Flush DNS Cache' now marks DNS entries as 'old' instead of removing them; marked entries are checked before use.  WinProxy maintains its own local cache of DNS lookups.  In 'the old days' we would allow the user to toss out the whole list; now as DNS and Transparent Proxy and maintaining a local network has become more complex a total flush can cause more problems than it solves.  This is a kinder, gentler way to have the DNS cache do your bidding.
16. When a DNS entry fails once, it is marked 'old'; entries older than 24 hours are also marked.  Any entry marked 'old' is checked before use.  More and more ISP's are playing fast and loose with mail and news server IP addresses; this helps ensure that the user won't even notice when the ISP changes those addresses.
17. FakeNameList file (the one that keeps track of those funny '1.0.0.x' IP addresses) now has an automatic entry for proxy.command.  Under certain circumstances, a user could lose access to administrative functions via http://proxy.command (it was an IP addressing issue).  This helps ensure that users won't lose that access.
18. RAS changes take effect within one minute, instead of several minutes later.  Changes to dialing, such as the allowed time period to dial, used to take effect only after several minutes.  These changes will now take effect within one minute of changing the setting.
19. 'Auto-user' feature that automatically added potential user groups has been removed (didn't work that well, and nobody much liked it when it did).  WinProxy 3 had been adding user groups (based upon dhcp) as a helpful little gesture to get folks started on filling out user groups.  No longer.
20. Changed IP survey to an ARP survey (WinProxy automatically checks all available internal addresses after every settings update to avoid DHCP surprises).  The ARP survey is less obtrusive and faster.  WinProxy will send out an ARP request to every possible address on the local network to keep straight what addresses are in use, and which are not.  WinProxy's DHCP - and this ARP survey - are limited to a class C address space.
21. Transparent Proxy port can be changed to a different port with a registry setting.  In rare cases, the default Tproxy port (29000) is needed by other programs that are not easily configured - in particular, client programs that *send* to that as a destination port.  Adding a registry key "TProxyPort" with the port number will change WinProxy's transparent proxy port.
22. Transparent Proxy port (29000) automatically changes to a new value when port 29000 is not available.  If port 29000 is already in use by another program, WinProxy will automatically change to another port, and then continue using the new port on subsequent use.
23. Namelist is checked much more often for changes  (within seconds, usually).  The file Namelist.pxy, accessed through File-Settings-Protocols-DNS-"edit namelist", is used by WinProxy's DNS and DHCP servers to preferentially assign addresses.  WinProxy will check this file every few seconds for changes, and implement them as soon as possible (implementation may not be immediate if there are conflicting DHCP leases, for instance).
24. About box has a button to initiate re-installation of Transparent Proxy if it has failed to load.  If you click on this box, WinProxy will begin a test and reinstallation of the Transparent Proxy drivers.  It will probably take two reboots to complete the sequence.  The box will not be visible if the drivers have successfully loaded.
25. Better reporting of connections blocked by restrictions (who made the request and why it was denied) in the Activity Log.  This includes connections blocked by user restrictions, site filter, blacklist, and whitelist.
26. New registry entry for 'service is started'; shows value of Windows time ticker when service was started.
27. Better enforcement of user restrictions.  We closed a couple more loopholes where client browsers using socks could evade restrictions.
28. Query parameters are suppressed in ConnectionView display.  In some circumstances, it was possible to view user's passwords on the WinProxy screen.  We now suppress all query parameters from the main WinProxy window.
29. 3.0k Installer finds existing 3.0 dat files, and copies them to the new directory.  If you install to a different directory, WinProxy will find and import the data files from your previous installation.  This will include dns, dhcp, user group, mapped port, filter, and restriction files.
30. Uninstaller removes itself and the 3.0 folder.  We didn't use to.
31. 3.0k Installer modifies the previous 3.0 Uninstaller if it is in a different directory.  (once 3.0k is running, correct way to remove previous 3.0 versions not overwritten by the subsequent 3.0k installation is to delete the other 3.0 directory).
32. Installer puts a shortcut to 'How to Set up a LAN' guide on the users desktop.
33. Browser 'refresh' has been updated to recognize the formatting change in newer browsers (means it works correctly now on newer browser versions as well as the older ones).
34. PPPoE.  This isn't a bug fix, but it deserves mention since its been a big problem.  Early problems with PPPoE have now largely disappeared.  No changes have been made in WinProxy; all changes have been a part of third-party PPPoE software upgrades and fixes.
35. W98 Sleep.  TCP/IP entries no longer vanish when W98 goes into sleep mode.
36. SMTP dial.  SMTP, POP, and telnet connections would fail when they were the connection initiating a dial-up (WinProxy would continue to dial, and the second cllient connection would succeed).  This has been fixed, and the first client connection attempt will now work.
37. Blank lines in site restrictions.  A blank line in any of the site restrictions (BannerBlocker, Blacklist, Whitelist) would be interpreted as an "all" with horrific results.  Most of these blank lines were inadvertant (caused by such things as abandoning an editing session).  Blank lines are now mercilessly removed and will not affect site restrictions.
38. First dial after hours no longer succeeds.  Used to be, with both dial and user time restrictions enabled, the very first dial attempt after user times passed would succeed.  No longer.
39. App Path entry in the registry is now updated all the time to avoid problems with multiple versions of WinProxy installed in multiple directories, and a problem that occurred in conjuntion with the 'run' problem (below) which could start the wrong, old copy of WinProxy when it was set to start automatically and App Path got out of kilter and still pointed to the old version.
40. 'Run' entry in the registry is now checked every time WinProxy runs, and removed if it doesn't apply.
41. Abandoned new filter edit no longer leaves a new filter with zero rules.
42. Deleted filters are now marked (they will no longer return, a previous problem in certain circumstances).
43. System clock set to a future date will not break the automatic update of  new anti-virus and smartfilter files.  Used to be, if your system clock showed a date in the future, it would decide that you didn't need the update yet.  Now you'll get it anyway.
44. New default DNS numbers have been incorporated in the install.  The previous default numbers were no longer 'pointing' to working DNS servers.

1. Specific to W2000 and Me:
   1. W2000 allows you to change IP addresses without a reboot.  WinProxy does not see these changes, and needs to be stopped and restarted to know about the change.
   2. W2000 has cute little taskbar icons to tell you when your NIC isn't connected to the network, and also makes some internal changes to disable the card....upshot is, when your W2000 NIC is unplugged, WinProxy can't find it.
   3. Windows Millenium has the potential for a similar problem.  If you check the option 'detect connection to network media' in the Me TCP properties dialog box, it will act pretty much like W2000, above. 

2. Other:
   1. client ftp / whitelist problem is still there.  (clients can't connect via ftp when whitelist is enabled, even if they are individually excluded from site restrictions).
   2. ftp from WinProxy machine will connect, but fail on ls or download (still).
   3. system date with year of 2038 or higher will crash WinProxy (still).
   4. Blabby incoming ports. Connection attempts to incoming mapped ports will reveal the customers port name (meaning, it will report the name of the port which has been put into the 'Mapped Port Name' field; this field is only for convenience and readability and does not affect the function), which may be a security