3 problems with Wingate

[guiem]

Hello,

we have 3 problems with the product:

1) We have deactivated the firewall because it blocked all the intern packages, and we have activated all lan and pcs ports to wingate.

2) In "History" we can't see anything, we can't see the activity.

3) Wingate become blocked sometimes, it doesn't accept any request, it doesn't allow to surf the net, we can't enter gatekeeper...

I can add the logs for the third question if you need.

Can anybody help me? Thanks! Thanks a lot!

[MattP]

Hi,

1. this sounds like it could be a problem with your internal IP addresses, if you're not using a private IP address range then WinGate will assume your connections are from the internet and block them. You can check by going to options>advanced and selecting the interfaces tab. Your internal NIC should be set to private yes trusted yes. Also, you can check in the Extended Networking menu that LAN connections to WinGate PC has the default action of allow.

2. this could be a problem with the history files, you can try deleting them. To delete the history files:
stop the WinGate engine
find and delete the files history.cdx and history.dbf
restart the WinGate engine
the files will be recreated on restart.

3. probably related to the corrupted history files, see above.

I hope this helps, please let us know how you get on,

Matt

[guiem]

Hello,

1) the configuration was like you said, and doesn't work.
2) We have deleted them and recreated, and we don't see anything. No changes have appeared.
3) Wingate stop almost everyday. The server is running 24h/day and almost all morning we need to stop wingate and re-start. It's curious that always stop in mornings at the hour to begin to work.

Wingate is Pro 5x for 25 users, i have licence id too if you need it.

I have logs copy too, if you want i send you, tell me where.

Thanks a lot!

[garydb4]

Its a memory leak. Go to task manager and you will notice when wingate stops your memory levels will be peaked out. Nobody has ever been able to explain this to me or help me with a solution. Every morning and sometimes twice per day I have to either reboot or stop wingate and restart the engine. Very annoying.

[paulocaceres]

Dear friend;

I have the same problem that you say in the point 3).-

Still I can't resolve it..............I dont know the causes of crash Wingate.....

Some people say that are the corrupt history files.......but I do all the step
(stop engine, delete file, start engine) but not resolve the problem.......

What Wingate version are you using ??

Paulo( )

Hello,

we have 3 problems with the product:

1) We have deactivated the firewall because it blocked all the intern packages, and we have activated all lan and pcs ports to wingate.

2) In "History" we can't see anything, we can't see the activity.

3) Wingate become blocked sometimes, it doesn't accept any request, it doesn't allow to surf the net, we can't enter gatekeeper...

I can add the logs for the third question if you need.

Can anybody help me? Thanks! Thanks a lot!

[adrien]

Its a memory leak. Go to task manager and you will notice when wingate stops your memory levels will be peaked out. Nobody has ever been able to explain this to me or help me with a solution. Every morning and sometimes twice per day I have to either reboot or stop wingate and restart the engine. Very annoying.

Hi Gary - which version is this - 5.2.3?

Adrien

[guiem]

Version is 5.2.3

[ingeltra]

Version is 5.2.3

face it since early wingate versions if you want gate keeper not to hang you need to disbale all logging delete history files disable history logging delete cache files from time to time..

as an overall view, let wingate use least memory and cpu usage.

[javila]

Version is 5.2.3

face it since early wingate versions if you want gate keeper not to hang you need to disbale all logging delete history files disable history logging delete cache files from time to time..

as an overall view, let wingate use least memory and cpu usage.

Wrong ingeltra.
I've been using wingate sin 3~4 years ago and the history problems only happened on the 5.0.x version, before and now I didn't have it any of those 3 problems.
The problem (on the majority of cases) (and in the majority of software) is the human factor, people do not configure well the hardware or just NOT configure it.