Wingate Causes Dialing error - TCP/IP CP reported error 31

[AL C]

I have a System with Wingate on Windows 2000 Server with AD and Win DNS and DHCP .
The System was working okay until last week .
Since last week the problem is that the dialer can't connect to the Internet . If you try dialing the internet manually the following error appears

TCP/IP CP reported error 31: A device attached to the system is not functioning.

Initially I thought - windows error disable and re-enable network .....
that didn't work .
So I tried a reset and everything worked fine for an hour or so . Then I decided to try creating a new dial up connection to a different ISP but the same thing occured ..

I then Disabled the wingate service from auto-starting and restarted the server . That was friday morning I left the system over the weekend and the dialer worked fine all weekend and through until monday .
I then put on the lates version of Wingate version 5.0.10 ( previously had version 5.0.08 ) . And restarted the system ( you need to restart after and install ) . Initailly the system seemed fine but eventually back to the same problem ...

TCP/IP reported error 31: Adevice attached to the system is not functioning ..

Has wingate been fully tested on Windows 2000 Server ( active Directory domain controller) with the latest service packs and ecurity patches ...?


Can I revert back to an earlier version of Wingate without losing my installtion settings ...?

Update 15-10-2003
I have included some of the dialog of the dialer log

10/14/03 15:20:52 Debug: Refreshing OS phonebook entries
10/14/03 15:21:28 Debug: Eircom: Off line.
10/14/03 15:21:28 Debug: Using WINVER-401 RAS support
10/14/03 15:21:28 Debug: Multilink dial mode == 1
10/14/03 15:21:28 Debug: Eircom: Dialing: Eircom
10/14/03 15:21:28 Eircom: Dialing...(requested by )
10/14/03 15:21:28 Debug: Eircom: Opening Port
10/14/03 15:21:28 Debug: Eircom: Port Opened
10/14/03 15:21:28 Debug: Eircom: Connecting (ISDN) to PCI ISDN Card
10/14/03 15:21:29 Debug: Eircom: Connected
10/14/03 15:21:29 Debug: Eircom: All devices connected
10/14/03 15:21:29 Debug: Eircom: Verifying username and password
10/14/03 15:21:31 Debug: Eircom: Registering your computer on the network
10/14/03 15:21:32 Debug: Eircom: On line to Eircom
10/14/03 15:21:32 Debug: Eircom: Connected
10/14/03 15:21:32 Debug: Eircom: Dial succeeded
10/14/03 15:21:32 Debug: Profile Eircom managed connection
10/14/03 15:21:32 Debug: Profile Eircom on line and grants access for
10/14/03 15:21:32 Debug: Profile Eircom on line and grants access for
10/14/03 15:21:32 Debug: Profile Eircom on line and grants access for


Connection remains up until ......


10/14/03 16:37:49 Debug: Profile Eircom on line and grants access for http://www.fxcentre.com/breakingnewsiframe.asp
10/14/03 16:37:50 Debug: Profile Eircom on line and grants access for http://www.fxcentre.com/images/sp.gif
10/14/03 16:41:10 Debug: Eircom: Timing out connection
10/14/03 16:41:10 Eircom: Resetting Eircom
10/14/03 16:41:10 Debug: Eircom: Resetting Eircom
10/14/03 16:41:10 Debug: Eircom: Disconnecting from: Eircom
10/14/03 16:41:15 Debug: Eircom: Could not find connection to reset
10/14/03 16:41:15 Debug: Dialer took 4485 milliseconds to process OnTimer
10/14/03 16:41:18 Debug: Eircom: Off line.
10/14/03 16:41:18 Debug: Using WINVER-401 RAS support
10/14/03 16:41:18 Debug: Multilink dial mode == 1
10/14/03 16:41:18 Debug: Eircom: Dialing: Eircom
10/14/03 16:41:18 Eircom: Dialing...(requested by http://www.fxcentre.com/table1iframe.asp)
10/14/03 16:41:18 Debug: Eircom: Opening Port
10/14/03 16:41:18 Debug: Eircom: Port Opened
10/14/03 16:41:18 Debug: Eircom: Connecting (ISDN) to PCI ISDN Card
10/14/03 16:41:20 Debug: Eircom: Connected
10/14/03 16:41:20 Debug: Eircom: All devices connected
10/14/03 16:41:20 Debug: Eircom: Verifying username and password
10/14/03 16:41:21 Debug: Eircom: Registering your computer on the network
10/14/03 16:41:21 Debug: Eircom: The connection attempt failed because your computer and the remote computer could not agree on PPP control protocols.
10/14/03 16:41:21 Debug: Eircom: Dial unsuccessful - resetting
10/14/03 16:41:21 Eircom: Resetting Eircom

[semihbattal]

I have exactly the same problem.
Reverted back to version 5.0.7 but the problem continues...
Please see also http://forums.enterpriseitplanet.com/sh ... readid=829
Semih[/url]

[nathanrjung]

Same Problem.. Windows 2000 Professional, with all the latest greatest updates from MS, as the Wingate server.

[semihbattal]

QBIK Software, will you please do something about this problem urgently... I am having to reset the PC every few hours. Everything was almost perfect until version 5.0.10. I repeat, reverting back to previous versions only make the problem occur less frequently... Please UNDO whatever you have done in 5.0.10... We are a "gateless" company at the moment...
Thank you,
Semih

[adrien]

Hi

i would recommend you try the latest version 5.1... we made some changes in relation to the dialup handling in the driver to combat problems that people had been seeing with 5.0.10

Adrien

[semihbattal]

Hi Adrien,
I noticed the new version after posting my last mesage. I installed it and it works ! It has been 20 hours and it did not need a reset. I also notice that the installation process keeps the bindings information intact, previous versions used to reset service bindings to the local interface and I had to bind them all again to correct interfaces. Thanks for the fixes.

A few months ago I had posted a message about a deadlock situation when shutting down wingate ( when registering a new licence key ), but I can't find this post anymore. I had also included the deadlock analyzer log files. With the new 5.1.0, unfortunately, this problem is still there...
Thanks.
Semih