Wingate 6.5.1 dialer bug

[pino]

When I upgrade from 6.2.2 to 6.5.1, wingate's dialer does not work on my adsl modem any more
as I get back to 6.2.2, dialer working well
ps. my os is win2003 sp2

[logan]

We have a new WinGate.exe here which might fix the problem. We still have to test and confirm it, but if you would like give the new exe a try, drop an email by the support desk. support at qbik dot com. I will send the exe and instructions on how to use it in a reply.

[pino]

I tried 6.5.2, but the bug is still live :-(

[adrien]

Hi

Does your ADSL modem use PPPoE or PPPoA or something else - do you know?

Regards

Adrien

[pino]

PPPoE

[adrien]

OK.

When you say it doesn't work, what doesn't work? e.g

a) WinGate has trouble initiating the connection
b) WinGate can't use the connection once it is connected

Regards

Adrien

[pino]

a) WinGate has trouble initiating the connection
but WinGate can work when I have manual dialed

[genie]

Do you dial from Gatekeeper or initiate dialing from the system panel?

[pino]

in fact, dialer can not be initiating from gatekeeper
unless I dialing from OS before starting Wingate

[genie]

Do you have user name and password configured in Wingate for the dialer?

[pino]

of course :-(
with same config, 6.2.2 works well, but 6.5.1 and 6.5.2 can not work

[genie]

Hi, Pino

We've identified the cause of the dialer problem - if you drop me a message (genie@qbik.com) I will give you a reference for a fixed engine to try.

[genie]

Hi, Pino

I have sent you an email in regard to the fixed engine.

Gene

[Diego]

Hi, I have the same problem.
After upgrading to 6.5.2 the dialer has trouble initiating the connection.

Thanks
Diego

[pino]

New engine works well, thx

[genie]

Hi, Diego

Can you, please, drop me an email genie at qbik.com?

Gene

[fionik]

I have a similar problem. I configured WinGate to dial via existing PPTP connection. If I establish a connection manually through Windows it works. If I establish a connection manually through GateKeeper by pressing the Dial button it works. A user from another machine can access web pages.

But if the user from another machine attempts to look at a Web-page when connection is not established manually then it doesn't work. GateKeeper even doesn't try to connect. The Client Activity window and the History window don't contain a record about dial attempt. Dialer.log doesn't contain any appropriate records (though it contains them when I dial manually) about the dial process. Is it a bug or a feature?

Version of WinGate is 6.6.4.

[adrien]

Hi

do you know which is the first request - the one that should trigger the dial... is it a client DNS lookup, or a proxy web request or something else? If you can manually dial from GateKeeper, then it may be that some code changed which would normally have called into our dialing code, and it's just a matter of tracking that down.

What do you see first in history when this happens?

Regards

Adrien

[fionik]

Honestly, I don't know which request is first. A browser on a remote machine is configured to use HTTP proxy and SOCKS5 proxy, that's all. A user enters an address of a site. For example it is the address of google. I've downloaded WinGate today from your site to look if it suits my needs. Currently I see that it doesn't.

[adrien]

Hi

If you look on the history tab in GateKeeper, you should be able to tell from the timestamp which is happening first.

Is the browser firefox? If it's configured to use SOCKS, I think it may still do a DNS lookup first.

Check in the DNS service in WinGate, and make sure that the option "Allow request to initiate dialer" is enabled.

Depending on your setup, do the clients even end up using the WinGate DNS server? e.g. if you're on an active directory, do your AD DNS servers forward to WinGate?

Regards

Adrien

[fionik]

If you look on the history tab in GateKeeper, you should be able to tell from the timestamp which is happening first.

I looked on the history tab. The history is in the attached file.

192.168.65.2 - is the remote computer (a netbook connected via a wireless connection)
192.168.65.1 - is the local computer which has access to the Internet and runs WinGate

I see that FireFox doesn't do a DNS lookup. An update service for another program attempts to do a DNS lookup.

Check in the DNS service in WinGate, and make sure that the option "Allow request to initiate dialer" is enabled.

Yes, this option is enabled.

Depending on your setup, do the clients even end up using the WinGate DNS server? e.g. if you're on an active directory, do your AD DNS servers forward to WinGate?

No. I'm not on an active directory. My network is very simple. I have a stationary PC with two network cards. The card one is plugged into a local city network through Ethernet cable. The card two is a wireless network card. Both machines are inter-connected by the wireless ad-hoc connection. Both have static IP addresses for the wireless connection and they see each other. In order to reach the Internet I have to establish a VPN (PPTP) connection by providing user name and password otherwise I can use only local city network. I want WinGate to dial this connection when the remote computer asks for a web page.

Please notice everything works if I dial this connection manually either by Windows GUI or by GateKeeper.