Winproxy to Wingate

[alyork]

Hi.

For the past 12 years we have been installing Winproxy in numerous networks. Now we are converting them to Wingate as Winproxy is a discontinued product. Here is an exert from the Winproxy installation guide. As a result every server we installed has an internal network card addressed at 90.0.0.1. This has worked fine if we are using either the server DNS and DHCP or the Winproxy DNS and DHCP or a combination of.

-------

WinProxy Host Computer Windows 2000 Configuration
1. Right mouse click on "My Network Places" on your desktop and select "Properties"
2. Right mouse click on the “Local Area Network Connection” icon (the one that goes to the
internal network) and select “Properties”
3. On the General screen highlight “Internet Protocol (TCP/IP)” and click "Properties"
4. Click on the “Use the following IP address” button and enter a non-routable IP addresses
(examples 90.0.0.1, 172.16-31.0.1, or 192.168.0.1)
5. Enter a “Subnet Mask” of 255.255.255.0
6. Gateway should be left blank
7. Click on the “Use the following DNS server addresses” button and insert your ISP’s DNS
server addresses
8. Click “OK” through all open menus, close the network and dial-up connections box (DO NOT
click cancel, if you do all your new settings will be lost)
9. Your PC should does not need to be restarted for the settings to take effect

-------

(All the Winproxy examples use 90.0.0.1.)

We have now converted several networks from Winproxy to Wingate. If we use the server DNS, DCHP and DNS work fine and send out all the info to the client. It doesn't seem to matter if we use the server or Wingate's DHCP.

However, if we use the Wingate DNS, the DNS info is NOT being sent to the client.

Some of the servers are running as workgroup severs and do not have DNS server installed.

There have been suggestions that its the 90.0.0.x address range that is causing the problems. However I don't see why Wingate would or should care what we us as an internal IP address range.

Am I missing something?

It would be a horrendous job to convert all the networks from 90.0.0.1 to another address range.

- Al

[rboynton]

I used to use Winproxy as well, and also installed it onto lots of customers' sites. When Winproxy was brought out, the 90.x subnet was considered internal like 10.x and 192.168.x. The specification changed and the 90.x subnet is no longer considered internal.

Since that is the case, you might want to change one setup to a true internal IP range and see how that goes. Sorry, I know it is a pain... If you still are having probs, at least that will rule out an incorrect internal IP range. Do let us know how things went, please. This board is a great source of help from folks who have a lot more experience with WG than I do.

[jasona]

WinGate will assume that any network adapter with a IP that is not from the following ranges, Is an external network:

10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255

It is highly recommended you use a range from the above list. As you are using 90.x you should see that network adapter has been allocated as external by WinGate. You can change this manually by double clicking on the network adapter in WinGate and changing it from "auto detect" to "internal trusted".

[alyork]

Thanks rboynton. That explains the 90.0.0.1 and Winproxy.

And thanks jasona for explaining default settings.

I had already figured out the network adapter settings.

However I still don't understand why Wingate's DNS doesn't work and Windows server DNS does work with 90.0.0.1 as the internal address. If it becomes a major issue I will consider changing the LAN address range.

- Al