WRP Control Session Shuts Down When Connecting to Internet

[Kong]

I have never had any major problems running wingate. Even with games.

I decided to install a game I haven't used in quite a while, Quake 3 Arena. I installed and updated it all and when I go to connect to a server (outside the local network) i can't make a connection.

I've checked with WinGate and for every program that uses Wingate a "WRP Control Session" starts up and remains running until I shut it down.

Well, with Quake 3... when I start up the game WinGate registers "WRP Control Session - QUAKE3.EXE" starts up but then the moment I try and connect to a server (outside local netowrk) it immediately shutsdown and the game is forced to use NAT.

I have not had this problem before with any software and could really use some help.

I was running Wingate 5.0.7 and decided a few mins ago to finally install 5.2.3, been meaning to do that for quite a long while. :P

Still having the same problem.

If you hve any ideas please let me know. Thanks in Advance.

[Kong]

I just installed WinGate 5.2.3 and still having the same problem.

And only with that one piece of software and only when trying to connect to server on the internet.

[Pascal]

In history, what application is shown for the WRP sessions? Could it be launching a DirectX / DirectPlay component to communicate with the game server which might be on the mixed mode list?

[Kong]

Thanks for the reply.

I dont' see anyinformation about DirectX or DirectPlay Components, although they maybe running.

All it says is running is QUAKE3.EXE.

The odd thing is, I've got other Quake3 Engine games that work fine.

[Pascal]

If you enable full debug logging (WRP), does it show anything out of the ordinary? (Might give us an idea of why the session closed, or from which side?)

I wonder what's different between this particular one and the other Quake3 Engine based games you're running.

[Kong]

I told WRS to log everything. I just found this in the log....

Code: Select all

Error:   Caught socket exception in CWRPSession::OnRead() Connection Reset by Remote Host - terminating

Here is, from what I can tell the section of hte log pertaining to that connection.

Code: Select all

09/09/04 19:11:59   192.168.0.2   Guest   0000000699   Created:   
09/09/04 19:11:59   192.168.0.2   Guest   0000000699   Debug:   Request 570 WRP_COMMAND_BIND UDP 192.168.0.2:27960 to 0.0.0.0:27960
09/09/04 19:11:59   192.168.0.2   Guest   0000000699   Debug:   Request 570 Created Socket 2672
09/09/04 19:11:59   192.168.0.2   Guest   0000000699   Debug:   Request 570 bound to 0.0.0.0:27960
09/09/04 19:11:59   192.168.0.2   Guest   0000000699   Debug:   Request 570 UDP Relay 192.168.0.1:2233 created socket #3100
09/09/04 19:11:59   192.168.0.2   Guest   0000000699   Debug:   Request 570 sending response packet
09/09/04 19:12:08   192.168.0.2   Guest   0000000699   Debug:   Receiving 125 bytes on UDP Relay socket #3100 from 192.168.0.2:27960
09/09/04 19:12:08   192.168.0.2   Guest   0000000699   Debug:   Sending 115 bytes to 192.246.40.56:27951 using socket #2672
09/09/04 19:12:08   192.168.0.2   Guest   0000000699   Debug:   Receiving 48 bytes on UDP Relay socket #3100 from 192.168.0.2:27960
09/09/04 19:12:08   192.168.0.2   Guest   0000000699   Debug:   Sending 38 bytes to 192.246.40.56:27952 using socket #2672
09/09/04 19:12:08   192.168.0.2   Guest   0000000699   Debug:   Receiving 26 bytes on UDP Relay socket #3100 from 192.168.0.2:27960
09/09/04 19:12:08   192.168.0.2   Guest   0000000699   Debug:   Sending 16 bytes to 212.85.0.79:27960 using socket #2672
09/09/04 19:12:08   192.168.0.2   Guest   0000000699   Debug:   Receiving 26 bytes on UDP Relay socket #3100 from 192.168.0.2:27960
09/09/04 19:12:08   192.168.0.2   Guest   0000000699   Debug:   Sending 16 bytes to 212.85.0.79:27960 using socket #2672
09/09/04 19:12:08   192.168.0.2   Guest   0000000699   Error:   Caught socket exception in CWRPSession::OnRead() Connection Reset by Remote Host - terminating
09/09/04 19:12:08   192.168.0.2   Guest   0000000699   Traffic    68   255   0   0   9s
09/09/04 19:12:08   192.168.0.2   Guest   0000000699   Terminated exit code 1

There are 2 lines I am not sure why they are listed or where this IP address is coming from.

Code: Select all

09/09/04 19:12:08   192.168.0.2   Guest   0000000699   Debug:   Sending 115 bytes to 192.246.40.56:27951 using socket #2672
09/09/04 19:12:08   192.168.0.2   Guest   0000000699   Debug:   Receiving 48 bytes on UDP Relay socket #3100 from 192.168.0.2:27960
09/09/04 19:12:08   192.168.0.2   Guest   0000000699   Debug:   Sending 38 bytes to 192.246.40.56:27952 using socket #2672

I've checked other q3 engine games, jedi academy, and it does not show that IP.

One thing I've noticed with some software is once an out going connection is created and then ended, i may not be able to make anohter connection. This means shutting down the application and then restarting to make new connection.

It almost seems like this is happening.

Does the above help at all or mean anything?

[Pascal]

That message might be a little misleading. If I'm not mistaken, that is WSAECONNRESET, which for a UDP socket indicates:

"The virtual circuit was reset by the remote side executing a hard or abortive close. The application should close the socket as it is no longer usable. On a UPD-datagram socket this error would indicate that a previous send operation resulted in an ICMP "Port Unreachable" message."

As it was just busy sending, getting a "Port Unreachable" ICMP error might indicate that the host is not available. I've tried to reach that site, but it is not available. (tracert to it fails, etc.)

I wonder if it's some special game server, etc. (Or maybe just something that Q3 does on it's own?)

[Kong]

tracert likely failed due to security.

The server it is on is running and we've never had a problem with hosting on it before. I have actually tried a number of game servers and so far had no luck connecting to any of them.

It seems to me that WRP is trying to connect to that 192.246.40.56:27951 which doesn't exist, is closing the connection real quick and then trying to connect to the proper server.

I'm just guessing though.

I'm really not sure how to fix or get around this.

[Pascal]

So is this [192.246.40.56] another Quake3 server? (Or used to be at some stage?)

The easiest fix I can think of would be to have that one NAT out - the driver has support for DirecPlay games so it should work correctly.

[Kong]

I am not typing that ip address at all but it seems to belong to idsoftware.

I just did some checking.

192.246.40.56 translates to monster.idsoftware.com

It must be something built into the game.

[Pascal]

Maybe an update check or something. Did switching to direct NAT help at all? (By adding Quake 3 to the list of ignored applications, or even temporarily disabling WGIC)

[Kong]

Okay I got it working.

I'm not exactly sure why but I have to put this to Local Network Access Only (Disable WGIC) but I have to select "Use non-standard connection sequence".

Once I do that it works.

I'm not entirely sure why but I have to assume it's because of that connection it makes before trying to connect to the game server.

Thanks for the help.

[Pascal]

Interesting. Non-standard connection sequence changes the response code from a "connect" call, for certain applications which operate properly when they get one response, not the other if the connect fails.

So it doesn't work if you don't have "Non-standard connection sequence" selected?

[Kong]

Well it did once, but every other time i tried it didn't work. I have to have it set for non-standard and it works everytime now.