Wingate not working after login on the server

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

Moderator: Qbik Staff

Wingate not working after login on the server

Postby JeF » Jun 07 04 8:06 pm

Hi,

I have a Web an e-mail server running Windows Server 2000 and MDaemon for mail and Wingate for Internet sharing.

Wingate seems to work correctly when I am not using the server. E-mail can be read an internet can be used without problem.

But I have a problem with wingate (I have tried V5.2.2, V5.2.3 and now 6.0.0 with the same problem) each time I am login on the server where it is installed. (directly or by Terminal Server).
The Wingate icon in the System Tray seems to be correct (blue for running) but if I want to connect to the server (open wingate), I receive the message from wingate "Unable to connect to the server...." and nothing displayed.
Since now (or even if I do not try to start wingate, just login onto the server) then if someone on the LAN try to check his e-mail, then I receive on the e-mail server a message from MDaemon indicating a wrong request (probably because Wingate is not working at this time correctly.

If a stop Wingate and restart it (I also have to restart the MDaemon service), then I can see the wingate configuration and all works good.(even If I stay logged and working on the server)
And this until I logout. Then if I login once again, it start to fail and display the same error messages again.

Thanks for your appreciate help.
JeF
 
Posts: 6
Joined: Jun 02 04 2:06 am
Location: Switzerland

Re: Wingate not working after login on the server

Postby Nev » Jun 08 04 12:55 am

JeF wrote:Hi,

I have a Web an e-mail server running Windows Server 2000 and MDaemon for mail and Wingate for Internet sharing.

Wingate seems to work correctly when I am not using the server. E-mail can be read an internet can be used without problem.

But I have a problem with wingate (I have tried V5.2.2, V5.2.3 and now 6.0.0 with the same problem) each time I am login on the server where it is installed. (directly or by Terminal Server).
The Wingate icon in the System Tray seems to be correct (blue for running) but if I want to connect to the server (open wingate), I receive the message from wingate "Unable to connect to the server...." and nothing displayed.
Since now (or even if I do not try to start wingate, just login onto the server) then if someone on the LAN try to check his e-mail, then I receive on the e-mail server a message from MDaemon indicating a wrong request (probably because Wingate is not working at this time correctly.

If a stop Wingate and restart it (I also have to restart the MDaemon service), then I can see the wingate configuration and all works good.(even If I stay logged and working on the server)
And this until I logout. Then if I login once again, it start to fail and display the same error messages again.

Thanks for your appreciate help.


Hi JeF,

Wonder if this could be history corruption, read the 'good oil' from Larry here http://forums.qbik.com/viewtopic.php?t=1859

Report back and someone will take it further either way....

Nev.
Nev
WinGate Guru
 
Posts: 861
Joined: Sep 22 03 11:35 pm
Location: Mudgee ~ NSW ~ Australia

Postby JeF » Jun 08 04 2:51 am

Thanks for the answer.

I have tried the process explained by Larry
(stop Wingate -> delete both files -> restart wingate).
Then I logout from the server and login again, but
unfortunately the problem is not resolved and it appears again.

If I tried to launch wingate I receive the following message (same as before) :
"There was a problem connecting to the server. No data was received from the server during authentification. Check the spelling of your username"
I have check the infos and they are correct because I can login with the same settings after I restart Wingate service.

Any another proposition ?
Thank's

JeF
JeF
 
Posts: 6
Joined: Jun 02 04 2:06 am
Location: Switzerland

Postby labull » Jun 08 04 4:28 am

A couple of things to check.

On Login to WinGate is the server set to "Local Host"?

Somewhere in this forum are instructions for deleting the Remote Control Service via the registry - but I can't find them.

Check both of these and let us know how it goes.

Larry
WinGate Lurker
labull
WinGate Guru
 
Posts: 710
Joined: Sep 06 03 1:03 am
Location: Washington, DC - USA

Postby JeF » Jun 08 04 9:36 pm

I will give some precision.

When I connect to my server where Wingate is installed and then I want to manage Wingate by double clicking on the comptuer in the System Tray, then I have the Wingate Windows which appaers but disabled. And after a few seconds, a message box appaers in the middle of my desktop with the message :" Unable to connect to the server.."
I DO NOT SEE THE LOGIN WINDOWS (with username, password. localhost.. and so one).

Then I close this windows, stop the Wingate (right click on the computer in the system tray) and restart it. Then I can open wingate and receive the login windows where the login is set to "Localhost" on port "808". And then it works.


I have check the following things :

- The login is set to "localhost"
- I have deleted the Remote Control Service by the registry but it did not solve the problem. Still the same.

I have checked in the log of the Remote Control Service and here is the line that is written after the login fails :

06/08/04 09:12:04 Remote Control Service Error: Caught X1SocketException in CTCPServiceSocketCallback()

I am not sure but I think that my problem appaers after I have installed some Windows patch on my server (patchs list:
KB329115, KB823182, KB823980,KB824105, KB825119, KB826232, KB828741, KB828749, KB830352, KB835732 and KB837001)

If I do not find a solution for my problem, I will try to remove these patch and see if it solve my problem.

Thank's in advance for your suggestions.

JeF
JeF
 
Posts: 6
Joined: Jun 02 04 2:06 am
Location: Switzerland


Return to WinGate

Who is online

Users browsing this forum: Google [Bot] and 4 guests

cron