a error when connect wingate server

[lfly]

when connected to the wingate server6.0 ,the gatekeeper report a protocol error, and the server log is:

Start time Computer User IP Application Action Duration Bytes in Bytes out
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
18-Nov 13:12:58 159.*.*.* 159.*.*.* N/A WinGate LoginNo response from client to challenge 5 0 13
18-Nov 13:12:40 159.*.*.* 159.*.*.* N/A WinGate LoginNo response from client to challenge 5 0 13
18-Nov 13:12:31 159.*.*.* 159.*.*.* N/A WinGate LoginNo response from client to challenge 5 0 13
18-Nov 13:08:32 159.*.*.* 159.*.*.* N/A WinGate LoginNo response from client to challenge 5 0 13

Can any one tell me why?

[MattP]

Wrong protocol version usually indicates that you're connecting to a WinGate server with a copy of GateKeeper from a different build/version.

Are you connecting from remote machine? Have you upgraded WinGate since you copied the exe file to the remote machine? If so then you'll need to copy a new executable to the new machine.

[lfly]

It still don't work after I matched the versions of server and gatekeeper!The error is the same as before!

The server computer and client computer are in the same building,one is 8F and one is 4F, each has a single net card. The server can access the internet by a way after login a diffrent internet client.

If the wingate can only work well in a LAN where one double net card is the one can access the internet? If the other computers' ip must be 192.*?

[MattP]

Have you bound the Remote Control Service to the LAN adapter? It needs to be listening on the LAN IP address (192.168.0.1, or whatever you're using) to be able to receive the login request from the remote machine.

[lfly]

Can the wingate server and clients be used in WAN network such as A class? My clients and server computer's IP are all the A class net adress.

[MattP]

WinGate doesn't care what IP addresses you use, but if you are using a public IP address range on your network (159.*.*.*) then the adapters will be detected incorrectly.

Please check the network tab in GateKeeper, make sure that your LAN adapter is set to "internal" and the internet adapter is set to "external". Only adapters that are set to "internal" will have services bound to them by default, and WinGate determines whether an adapter is internal or external based on the IP address; private IP addresses are "internal", public IP addresses are "external".