Switch to full style
Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Post a reply

Wingate 5.2.3 NAT function not available on Win2003

May 17 04 1:15 am

Wingate 5.2.3 NAT function not available on Win2003 + Sygate personal firewall pro 5.5

The PC server installed Wingate 5.2.3, its local IP address is 192.168.0.1, subnet 255.255.255.0, all WinXP clients within this LAN.

Even I set High level firewall in Wingate 5.2.3, it still not available, seems no change at all. All WinXP clients still need to set apps' proxy to access the Internet.

Does anybody knows how to solve these problem? Thanks.

May 17 04 4:46 pm

Hi there

We have tested WinGate using NAT extensively on Win2003 with success.

NAT requires DNS and Gateway entries on client machines to be set to the Internal IP address of the WinGate server. (in your case 192.168.0.1)

The WinGate firewall does not block access to the server itself from LAN clients. Have you tried disabling the Sygate personal firewall on the WinGate server to see if this allows clients to use NAT through WinGate?
This could be restricting WinGates ability to access the Internet on behalf of the clients.

Just some things to check

Regards
Erwin

I tried allow all in Sygate firewall pro5.5

May 17 04 5:33 pm

I tried allow all in Sygate firewall pro5.5 setting. It should be access the Internet from the XP client end. But all clients still cannot visit Internet, even browse the website URL in IP address. I have already set the gateway IP to my Win2003 server IP.

Besides, I set the Wingate 5.2.3 firewall to High, denies all connection from outside. But anybody can access my Win2003 services as well, no attack logs in firewall tab.

Do you try a test with Sygate firewall pro5.5 environment? Is it really caused by Sygate incompatible or what?
Post a reply