Port Mismatch

[ChrisH]

Occasionally this message pops up when remoting into another WG machine. Even though port 808 is selected. Both machines have 6.1 GateKeeper Why would this happen? And WGLite - bit of a throwback, eh? Thanks.

[Pascal]

Hi Chris,

I just went through the source code and that message should be an impossibility. Firstly - can you double check the GateKeeper version, please? Secondly, are there any particular circumstances that lead to this or is it entirely random?

[ChrisH]

Hi Pascal,

Seems to me to be a random occurence. I should change my story slightly. I am remotely authenticating using GateKeeper 6.1 to a machine running WG 6.1. Then I am using WinXP Remote Desktop software to control that machine using WG to forward port 3389. I have seen this error box pop up before with other 6.x versions. Here is log file snippet from Remote Control Log of remote machine where 216.46.x.x is the machine I am connecting from;

12/01/05 09:31:48 216.46.x.x 0000020548 Error: Caught socket exception in CRemoteControlSession::InitInstance() Port mismatch disallowed - direct connection required - terminating
12/01/05 09:31:48 216.46.x.x 0000020548 Traffic 21 67 0 0 3s
12/01/05 09:32:24 216.46.x.x 0000020549 Error: Caught socket exception in CRemoteControlSession::InitInstance() Port mismatch disallowed - direct connection required - terminating
12/01/05 09:32:24 216.46.x.x 0000020549 Traffic 21 65 0 0 1s
12/01/05 09:32:33 216.46.x.x 0000020550 Error: Caught socket exception in CRemoteControlSession::InitInstance() Port mismatch disallowed - direct connection required - terminating
12/01/05 09:32:33 216.46.x.x 0000020550 Traffic 21 59 0 0 0s
12/01/05 09:35:18 216.46.x.x 0000020551 Error: Caught socket exception in CRemoteControlSession::InitInstance() Port mismatch disallowed - direct connection required - terminating
12/01/05 09:35:18 216.46.x.x 0000020551 Traffic 21 66 0 0 1s
12/01/05 09:35:22 216.46.x.x 0000020552 Error: Caught socket exception in CRemoteControlSession::InitInstance() Port mismatch disallowed - direct connection required - terminating
12/01/05 09:35:22 216.46.x.x 0000020552 Traffic 21 67 0 0 0s
12/01/05 09:39:29 216.46.x.x 0000020576 Error: Caught socket exception in CRemoteControlSession::InitInstance() Port mismatch disallowed - direct connection required - terminating

The remote machine is running WG 6.1 Standard. At one time this machine had WG Ver 3.x on it but I'm sure I did a clean install of 6.0. Does any of this help? Need more info? Thanks

[adrien]

Hi Chris

It's from Standard not allowing remote access to GateKeeper - that is a pro only feature, so we disallowed connection via a mapping in case someone just set up a mapping pointing to localhost to get around this restriction. It checks port numbers to do this.

Adrien

[ChrisH]

Thanks for the reply Adrien.

Does that mean one shouldn't be able to remotely authenticate using Standard? When I do this no remote control of GateKeeeper is possible, as expected with Standard license, but I have authenticated which is all I want to do. So, I guess I am then wondering why I can authenticate at all. It only appears to be random occurences that I am not able to. Is this a violation of the license? Thanks.

[adrien]

Hi Chris

in the early days (which is where this code comes from), there was not even remote authentication with GateKeeper available for non-Pro licenses.

When we allowed remote auth only in I think WinGate 5.something, it allowed you to connect and auth, but not control WinGate. At this stage the port-checking should have been removed but wasn't. We just removed it in the code here so it will be in the next release. we can send you a new engine if it's causing you trouble. It's odd that it only works sometimes in your case - I guess that depends on whether the connection translates the client's source port or not (some mappings / NAT devices don't) as to whether it works or not.

Cheers

Adrien

[ChrisH]

we can send you a new engine if it's causing you trouble.

Not necessary. This isn't a big issue for me. Thanks for clearing it up.