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

Wingate doen't dial in any more

Aug 24 06 7:11 am

I have a big problem: I use WinGate Standard to connect my network with the internet by using an ISDN-dialin-connection.

Everything worked fine, but now WinGate doesn't dial in any more - not automatically if a website is requested and not manually by clicking "Dial". But directly under windows I can dial in without problems.


This is WinGate's dialer-logfile from my last try to dial in manually:

Code:
08/23/06 18:57:05 Debug: Freenet: Dialing: Freenet
08/23/06 18:57:05 Freenet: Dialing...(requested by )
08/23/06 18:57:05 Debug: Freenet: Synchronous Dial with RasDialDlg()
08/23/06 18:57:35 Debug: Freenet: RasDialDlg() timed-out (unknown reason) - closing it
08/23/06 18:57:35 Debug: Freenet: completed with error code 0)
08/23/06 18:57:35 Debug: Freenet: RasPhone dial attempt failed (unknown reason)
08/23/06 18:57:35 Debug: Freenet: Off line.
08/23/06 18:57:35 Debug: Freenet: Dial unsuccessful - resetting
08/23/06 18:57:35 Freenet: Resetting
08/23/06 18:57:35 Debug: Freenet: Resetting
08/23/06 18:57:35 Debug: Freenet: Disconnecting trom: Freenet
08/23/06 18:57:35 Debug: RasHangUp returned error code 6
08/23/06 18:57:35 Debug: Freenet: No connection
08/23/06 18:57:35 Debug: Freenet: Could not find connection to reset
08/23/06 18:57:35 Debug: Freenet: Disconnecting from: Freenet
08/23/06 18:57:36 Debug: Freenet: Dialing: Freenet
08/23/06 18:57:36 Freenet: Dialing...(requested by )
08/23/06 18:57:36 Debug: Freenet: Synchronous Dial with RasDialDlg()
08/23/06 18:58:06 Debug: Freenet: RasDialDlg() timed-out (unknown reason) - closing it
08/23/06 18:58:07 Debug: Freenet: completed with error code 0)
08/23/06 18:58:07 Debug: Freenet: RasPhone dial attempt failed (unknown reason)
08/23/06 18:58:07 Debug: Freenet: Off line.
08/23/06 18:58:07 Debug: Freenet: Dial unsuccessful - resetting
08/23/06 18:58:07 Freenet: Resetting
08/23/06 18:58:07 Debug: Freenet: Resetting
08/23/06 18:58:07 Debug: Freenet: Disconnecting from: Freenet
08/23/06 18:58:07 Debug: RasHangUp returned error code 6
08/23/06 18:58:07 Debug: Freenet: No connection
08/23/06 18:58:07 Debug: Freenet: Could not find connection to reset
08/23/06 18:58:07 Debug: Freenet: Disconnecting from: Freenet
08/23/06 18:58:08 Debug: Freenet: Dialing: Freenet
08/23/06 18:58:08 Freenet: Dialing...(requested by )
08/23/06 18:58:08 Debug: Freenet: Synchronous Dial with RasDialDlg()
08/23/06 18:58:38 Debug: Freenet: RasDialDlg() timed-out (unknown reason) - closing it


What's wrong?

Aug 24 06 7:54 pm

So all of a sudden WinGate stopped dialing your ISDN account called FreeNet. Can you confirm to the forum that you have:

1. Checked the Windows Event Viewer.
2. Not installed any new software since this problem began.
3. Checked the Logs and Alerts of any security suite you have installed.
4. Have tried creating a second dialup in Windows for the ISDN, and then configure it in WinGate.
5. Has any software updated since this problem began?
6. Have you upgraded or installed WinGate to a different drive?

Aug 25 06 6:26 pm

ImmediateAction wrote:1. Checked the Windows Event Viewer.


There is nothing suspicious ....


ImmediateAction wrote:2. Not installed any new software since this problem began.


None. I finished the Installation of the Gateway-Server on 17th of August, made a final test an shutted the system down. On the 23rd I turned it on and had the described problem. In the meantime, according to the eventlog nobody used it ...


ImmediateAction wrote:3. Checked the Logs and Alerts of any security suite you have installed.


I have installed Kaspersky Business Optimal for Fileservers, but there are no suspicious entries in the logfile. Yesterday I shutted Kaspersky down and tried again to dial in ... it didn't work without Kaspersky too.


ImmediateAction wrote:4. Have tried creating a second dialup in Windows for the ISDN, and then configure it in WinGate.


Yes, the Freenet-Connection for which I posted the log is this second dialup. Primary I use a connection via T-Online. I created the Freenet-Connection BECAUSE the T-Online didn't dial in.


ImmediateAction wrote:5. Has any software updated since this problem began?


No, same as answer 2


ImmediateAction wrote:6. Have you upgraded or installed WinGate to a different drive?


Different to what? Sorry, my english is not the best, so perhaps I don't get the meaning of your question correctly ...

Aug 28 06 9:58 pm

Hi,

From memory this post here could be the answer where faulty dialing is concerned.

Aug 29 06 11:55 pm

Hi

That's a really weird log entry about RasDialDlg. I can't see how this would work in a non-interactive service (i.e. service doesn't normally have a desktop to display dialogs with).

The presence of that line indicates that either there's a registry setting to force use of the RasDial dialog which is in

HKLM\Software\Qbik Software\WinGate\Dialer\ called "ForceUseRasDlg". THis would be unusual.

Otherwise it means that the dialer profile you are using is multi-link - has more than one sub-entry in it.

You could try resetting the "use synchronous rasdial" setting to off.

Adrien

Aug 30 06 12:12 am

If it still shows it's doing a synchronous dial, try creating a reg value called

DisableNonRAS

in that registry key (the dialer one), and setting it to 1.
Post a reply