Upgrade Problem

[rwgroot60]

I was running Wingate 4.5.1 and was finding there were memory problems on the machine.

The ENS and NAT services worked when the wingate service was running


During the upgrade I installed the latest version with the 4.* license and copied the registry settings

The install was successful , I stopped the service from running and I updated the registry with the old settings.

When I rebooted the system the wingate server turned on and I was able to access the internet from the server

At the clients I was not able to connect to the internet or start the internet applications


The ip settings for the server is 192.168.0.1 255.255.255.0 mask

the clients have static ip addresses in the range 192.168.0.2 -192.168.0.7
mask of 255.255.255.0 and gateway of 192.168.0.1

When i tried pinging the server from the client i recieved

Request timed out

I went to the wingate server and turned of the firewall
The firewall says allow local to Ping but it wasn't working

At the client i tried to ping and it responded
when i put firewall back on it stopped

I think there is a NAT problem, possibly confusion on what is the local and which is remote interface.

Would the registry entries not included that?

how would i fix

i can't get out to the internet obviously

rwgroot60

[erwin]

Hi there

Are you able to reach the Server normally from the client (i.e. across the LAN accessing files etc) ?

The reason why I ask is because if you cant ping the server normally there may be something wrong with the TCP/IP setup. WinGate has been designed to recognise the difference between private and public IP addresses (interfaces) so for it to block the ping from a 192.168.*.* seems strange.

Have you checked the system services in GateKeeper to make sure the interfaces are bound correctly (under bindings tab). WinGate will not affect you reaching the Internet from the server itself so access from here should be allowed.

On the client machines do they also have their DNS entries set to point at the WinGate's internal IP (192.168.0.1), although you havent mentioned it this is also required for them to use WinGate/NAT.

And finally is the dialup or Internet connection configured and ready to be used in WinGate?

Just some things to check.

Regards
Erwin

[rwgroot60]

Erwin

Thanks for your reply

The client settings all include the !92.168.0.1 address as there DNS server

When the servewr was 4.5.1 they were allowed to connect instantly using NAT and not WGIC. Thet were also able to connect to the server without a problem at all

After the upgrade to 5.2.3 and registry export/import it did not work properly at all. no connections to the wingate server until I shut firewall off. But even after firewall was turned off i could not get to internet

The bindings showthe card with the private address as internal
and the card that gets the DHCP from ISP as external.

The reason i mentioned we were able to get to the internet from server was to let you know that the connection to the internet was operational