Wingate 6.0.1.995 server can't access to internet on XPPro.

[skfat]

Hi,
As mentioned in subject above, right after install wingate, Wingate Server can't surf the net. Uninstall it without changing anything solve the problem.

More info as below.
-Wingate server is connected directly to internet using ADSL.
-With Sygate Personal Firewall Pro set to allow all all the time. (Disabled the firewall)
-Using WinXP Pro SP1
-Get time out regardless of using IP or domain name in browser.
-Fail to resolve host with ping.

Please kindly advise.

Thank & Regards,
skfat.

[Pascal]

Under adapter settings, double check the properties of your adapters. If an adapter has a default gateway and a private IP, WinGate treats it as an external adapter. It could be that yours is simply detected incorrectly ?

Then, if WinGate is installed and you stop the WinGate engine, can you connect out to the Internet then ?

[skfat]

Really appreciate for your fast response.

I have only one adapter & didn't set gateway.
By the way, Wingate state that DHCP can't be use cause I am using non-private IP but I am using 192.168.0.1.

Still the same problem after I stop the service.

Any idea?

Thank you.

Regards,
skfat.

[Pascal]

So you have one NIC and one ADSL modem?

Other people have experienced problems with SyGate before. If you do a search for SyGate on the forums, you'll find a list of the topics.

http://forums.qbik.com/viewtopic.php?t= ... ght=sygate

Is there any way to temporarily disable the firewall and use the WinGate one instead?

[skfat]

Yap. I have only one NIC & ADSL modem.

I did search in forum & FAQ before posting.

I set firewall to allow all. I hope is the same?


Regards,
skfat.

[Pascal]

Don't think so. My only concern was for the interaction between the two low-level drivers. I'm going to refer this one to Genie, he is the driver guru.

[genie]

Pascal is right - there is a possibility that two drivers do not work together nicely. You can try stopping/uninstalling Sygate completely and see if it helps.

[allglass]

I've got the same problem....installed 6.0.1 as a trial version, got it to work for awhile. Then I installed ZoneAlarm. Everything stopped working (including my connection to the internet via the host.) I uninstalled ZA, no help, then I uninstalled WinGate. I was then able to access the internet. Reinstalled WinGate, not able to access the internet. Uninstalled WinGate....I can access internet. I guess I violated first rule...when things work, don't mess with them! Any help would be appreciated as when it was working, I really liked it and was all set with my AMEX card!

[Pascal]

Have you double checked the adapter useage when you re-installed WinGate?

[allglass]

Not sure what you mean by this Pascal.

[Pascal]

On the networking panel in GateKeeper there is a list of adapters. WinGate determines the useage of each adapter based on the ip address assigned to it. However, a private ip with a default gateway (common in DSL setups, like the one I have at home), is treated as an external adapter.

For everything to work 100%, WinGate needs to get the correct information about where which adapter will be used. So your public / external adapter must be marked as such (Firewall, NAT etc.) and your private / internal adapter must also be marked appropriately (Firewall, NAT, etc.)

You can double click each adapter in turn to override what WinGate has detected.

[allglass]

I checked each adapter and they were either set correctly or I changed them to the correct setting. Still no help. I'm getting no network traffic indication on the host server. This is getting to be a pain as I have to uninstall/reinstall/uninstall WinGate just to get here. Is there a step-by-step troubleshooter I can access somewhere that can walk me through various multiple fixes? Thanks for your help.

[genie]

Well, I would say that ZA caused pain for Wingate - it might leave its driver behind when you uninstalled it.

[Pascal]

Not really. The best options are either the forums or by posting support tickets, but, you do need the Internet available for either of those options to work. I'll post more than one question / possible area here, in case you want to go through that process again.

Can you at least access the Internet from the WinGate machine itself? (Without proxies set in the browser) If you can, that means that the Internet itself is working. (Assumed it would be, as you can get out with WinGate installed)

You say you don't see any activity on the server when a client tries to connect. How are the clients connecting? If they are using NAT or WGIC, try a direct proxy connection to see if a connection can at least be established to the WinGate Server. Also, try disabling intercepts (If you have them turned on) to see if that makes a difference. (Allowing the pure client connection to go through). You can disable intercepts by going into the appropriate WinGate Service (WWW is the easiest to test with) and unticking the "Use Intercepts" option on the "Sessions" page.

If you run a "netstat -an" on the host computer (WinGate Server), can you see WinGate listening on any ports? This will be from a command prompt, and should have output similar to:

TCP 0.0.0.0:809 0.0.0.0:0 LISTENING
TCP 127.0.0.1:808 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1027 0.0.0.0:0 LISTENING

If not, your WinGate server is not listening. This is probably a bindings problem - in which case you'd need to check each service to ensure that it is binding to your LAN adapter (Internal) so it knows about incoming connections.

If WinGate is listening, it's bound correctly and your client traffic is not reaching it - check (a) the port security actions under ENS and (b) the various firewall options you have turned on / off. Also, check the firewall hits you might be receiving. If any of them are for your internal adapters, you might have a configuration problem there. (WinGate blocking your client machines).

[allglass]

>>Can you at least access the Internet from the WinGate machine itself? (Without proxies set in the browser) If you can, that means that the Internet itself is working. (Assumed it would be, as you can get out with WinGate installed)<<

When WinGate is installed on the server machine, I cannot connect to the internet. I can dial-up but when I start either IE or Netscape (or any other internet dependent program for that matter) I get the standard timed-out message "Unable to find server, blah, blah blah."

>>You say you don't see any activity on the server when a client tries to connect. How are the clients connecting? If they are using NAT or WGIC, try a direct proxy connection to see if a connection can at least be established to the WinGate Server. Also, try disabling intercepts (If you have them turned on) to see if that makes a difference. (Allowing the pure client connection to go through). You can disable intercepts by going into the appropriate WinGate Service (WWW is the easiest to test with) and unticking the "Use Intercepts" option on the "Sessions" page.<<

Not only do I not see activity on the client, I don't see anything on the host either.

I'll reinstall WinGate, try the solutions you've posted and let you kow the results.

Again, thanks for the help.

[Pascal]

When WinGate is installed on the server machine, I cannot connect to the internet. I can dial-up but when I start either IE or Netscape (or any other internet dependent program for that matter) I get the standard timed-out message "Unable to find server, blah, blah blah."

Just to double triple check - that is on the actual server? You cannot connect out from the server when WinGate is installed?

If that's the case, can you email me a route table (Via route-print from the command line) when you have WinGate installed and when you have WinGate dialed up to the Internet, please?

Secondly, if that is the case - does stopping the WinGate Engine (Or disabling ENS and rebooting) affect the scenario at all? (Might help us narrow it down to a specific component, which means we might solve it easier)

When you had WinGate installed originally, did you make any modifications using "Advanced Options" on the start menu?

[allglass]

>>Just to double triple check - that is on the actual server? You cannot connect out from the server when WinGate is installed?<<

That's correct, I cannot connect to the internet via the server when WinGate is installed.

>>If that's the case, can you email me a route table (Via route-print from the command line) when you have WinGate installed and when you have WinGate dialed up to the Internet, please? <<

Will do, give me a couple of hours to do.

>>Secondly, if that is the case - does stopping the WinGate Engine (Or disabling ENS and rebooting) affect the scenario at all? (Might help us narrow it down to a specific component, which means we might solve it easier)<<

Stopping the engine hasn't worked. I'll try disabling ENS and rebooting.

Thanks again for all your help. Once we get this solved, I'm sure it will perform to my expectations.

When you had WinGate installed originally, did you make any modifications using "Advanced Options" on the start menu?[/quote]

[allglass]

Ok, I've narrowed the problem .... I use a dial-up adapter to access the internet. When I disble my wireless card I'm able to access the internet via my dial-up connection. When I enable my wireless card, internet connection kaput. I've modified the interface settings on the network tab to show my wireless card as an internal, trusted source....no help. I need the wireless card to access both home network and to allow my laptop to access my internet connection through the host server. Any ideas? I need an email addy in order to send you the routing table. Thanks again for the help.

[fcarbuc]

Hi all

I've got the same problem installing WinGate 6.0.1 on XPpro.
Impossible to get any reply after Internet connection.

Installing 5.2.3 all is OK

The difference I've noted when 6.0.1 is installed is that I don't get the default gateway from ADSL provider (I get only IP Address, default gateway is empty) while installing 5.2.3 I get both IP address and default gateway, and all is working.

I hope this can help to solve this problem.

Franco Carbucicchio
fcarbuc@tin.it

[Pascal]

What is the IP address on your ADSL interface? (Is it private or public) and what does WinGate detect it as? Also, do you have multiple default gateways? (Can check this doing a route -print)

[fcarbuc]

Ip address I get from Telcom company are always public and are changed each time I made a connection (ie 80.150.x.x or 80.113.x.x etc)

Default gateway is the same Ip address I've got, I see it launching ipconfig.

With 6.0.1 installed, after connection to ADSL, launching ipconfig, I see only Ip address assigned and not default gateway that is left blank.

This happens only with 6.0.1 and not with 5.2.3

Franco

[Pascal]

Do you see anything on WinGate's firewall when you connect the ADSL connection?

The two major differences between 5 and 6 is licensing and adapter useage (And everything else that flows from that). I doubt it's licensing.

Does it make a difference if you set your ADSL adapter explicitly to external? (Useage in the network pane)

[Tugsoo]

I was using Wingate 5.2.3. Everything was fine, but the trial version and trial period of time. Yesterday we've bought Wingate 6.0. Started to experience same problems as author of this topic:

1. After installing version 6 over version 5 no one on the network can't access internet. Even server machine on which Wingate 6 is installed. No any other software on server machine. Just Windows XP Professional and Wingate 6.0. Regarding hardware: two network adapters - one for Lan, another connected to ADSL modem.
2. Performed clean install of WinXP, than put Wingate 6. Results are same.
3. Uninstalled version 6 put version 5 back. Everything works with no problems.

What the matter with you, Qbik guys, huh? It's definitely your fault!!!
Solve my problem, otherwise give my money back!!!

[genie]

Can you send me the routing table (|route print| from the command line) from the server machine?

[Pascal]

Also, check that the adapter useage in GateKeeper is specified correctly. You can do this from the network panel. Make sure your ADSL interface is set to external, and your LAN to internal.

[Tugsoo]

to Genie: should I send you routing table with installed version 6 or version 5?

to Pascal: I've checked my settings. Network adapters were detected correctly, however I manually checked each - ADSL interface is set to external and LAN to internal.

where are else problems could be???

[Pascal]

Going through the same steps to try and isolate the component - when does networking + internet become available on the WinGate Server? (I'm assuming you cannot access the internet from the server as well, as other people in this post experienced)

Can you access the internet if the WinGate server is stopped?
Can you access the internet if the ENS is manually disabled?

Do you have the "protect my system before WinGate starts" or "Keep firewall enabled after WinGate stops" ticked?

[Tugsoo]

Going through the same steps to try and isolate the component - when does networking + internet become available on the WinGate Server? (I'm assuming you cannot access the internet from the server as well, as other people in this post experienced)

Can you access the internet if the WinGate server is stopped?
Can you access the internet if the ENS is manually disabled?

Do you have the "protect my system before WinGate starts" or "Keep firewall enabled after WinGate stops" ticked?

Internet is not available neither on server machine nor network client unless WinGate server is stopped and monitor in right-bottom corner closed.

I've tried many variations. With and without ENS. With and without "protect my system before WinGate starts". With and without "Keep firewall enabled after WinGate stops"

Nothing works.

[Pascal]

Gene is probably looking for the route table with 6.0 (As it's causing the problem) although both would be handy for comparison purposes.

Looking at the status of the different adapters as listed in GateKeeper, the routing table, anything that might help point us in the right direction here. Is there anything that seems out of the ordinary, like firewall hits for all interfaces, that kind of thing?

[skfat]

Just to let you guys know. As Pascal & Genie suggested, uninstalling Sygate Firewall solve my problem.

BTW, is there a more complete help file out there, the help file that come with wingate is very brief. I try to explore every features in wingate but many features are without any info. For example, I want to know more about 'Allow POP3 proxying' but can't find any info there.