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

NAT problem: log message "Terminated exit code 42"

Mar 07 06 10:26 am

Hello.

I've installed WinGate 6.0.4 on my "server" computer (the one with internet access) a couple of weeks ago and everything worked just fine. The second computer (connected via a crossed-over cable) had full internet access without any other software installation.

The problem occurred a couple of days ago, when suddenly the client computer wasn't able to connect to the internet. The Wingate NAT.log file shows the client connection, but after a while the connection is dropped and the following message is logged: "Terminated exit code 42".

The only software recently installed on my server was:
- Borland Delphi 7
- .NET 1.1 SDK
Nothing installed on my client computer.

I also have "Automatic updates" turned ON on both computers.

Could someone help me out on this?

P.S.: I can post more technical information, just tell me what do you need.

Mar 07 06 11:27 am

Code 42 means that the NAT connection was terminated - meaning that either a client or a server closed the connection. Do you have other firewalls installed?

No firewalls

Mar 07 06 7:45 pm

I have Windows Firewall disabled (i disabled the service) on both computers. No other firewall or security application is installed.

Mar 07 06 10:12 pm

Have you noticed the interval the connection stayed alive? Was it close to 2 minutes? Was the connection active (that is was there any data pumped through) or inactive (no data after connecting)?

A snippet from the log file

Mar 08 06 12:07 am

My external IP is 85.204.48.208. My client ip address is 192.168.0.142 (assigned by wingate DHCP).

As you can see the connections stay alive for about 1 minute.

I noticed that the error code i was talking about appears only when the windows.time server is accesed (probably due to the way windows is dropping the connection).

I'm not sure what is the log file column showing the total amount of bytes received, but the history window in wingate GUI shows two columns: "bytes in" and "bytes out". The "in" column has some values, the "out" is always set to 0 (zero).

Here is a snippet from my Wingate NAT.log file.

Code:
03/05/06 23:00:35   192.168.0.142   Guest   0000000031   Requested:   NAT: TCP Connection to 216.155.193.179:80
03/05/06 23:00:49   192.168.0.142   Guest   0000000029   Traffic    0   144   144   0   56s
03/05/06 23:00:56   192.168.0.142   Guest   0000000032   Requested:   NAT: TCP Connection to 216.155.193.179:21
03/05/06 23:01:14   192.168.0.142   Guest   0000000030   Traffic    0   144   144   0   60s
03/05/06 23:01:17   192.168.0.142   Guest   0000000033   Requested:   NAT: TCP Connection to 216.155.193.179:25
03/05/06 23:01:34   192.168.0.142   Guest   0000000031   Traffic    0   144   144   0   59s
03/05/06 23:01:38   192.168.0.142   Guest   0000000034   Requested:   NAT: TCP Connection to 216.155.193.179:119
03/05/06 23:01:54   192.168.0.142   Guest   0000000032   Traffic    0   144   144   0   58s
03/05/06 23:02:00   192.168.0.142   Guest   0000000035   Requested:   NAT: TCP Connection to 216.155.193.179:20
03/05/06 23:02:14   192.168.0.142   Guest   0000000033   Traffic    0   144   144   0   57s


The "Terminated exit code 42" error:
Code:
03/06/06 22:54:27   192.168.0.142   Guest   0000000000   Created:   
03/06/06 22:54:27   192.168.0.142   Guest   0000000093   Requested:   NAT: UDP 192.168.0.142:123 <-> 207.46.232.189:123
03/06/06 22:54:27   192.168.0.142   Guest   0000000000   Created:   
03/06/06 22:54:27   192.168.0.142   Guest   0000000094   Requested:   NAT: UDP 192.168.0.142:123 <-> 207.46.130.100:123
03/06/06 22:54:51   Authorisation failure:   NAT STATUS: firewall block: TCP src 193.27.70.30:36504 dst 85.204.48.208:80
03/06/06 22:55:00   192.168.0.142   Guest   0000000094   Traffic    0   76   76   0   33s
03/06/06 22:55:00   192.168.0.142   Guest   0000000094   Terminated exit code 42
03/06/06 22:55:05   192.168.0.142   Guest   0000000093   Traffic    0   76   76   0   38s
03/06/06 22:55:05   192.168.0.142   Guest   0000000093   Terminated exit code 42

Mar 08 06 12:17 am

Can you connect and communicate normally from the Wingate machine itself?

Server works just fine, client can't connect

Mar 08 06 1:48 am

Yes, the wingate server machine has no problem accessing the internet (i'm posting these messages from it).
As i wrote in my first post, everything worked just fine until a couple of days ago. But i didn't install any system updates or anything similiar.

Mar 08 06 9:38 am

Has anything new been installed on the client machine lately?

Mar 08 06 10:42 am

No. Nothing has been installed on the client machine either.

Mar 09 06 7:16 pm

Isn't there anything i can do to make it work? Maybe some additional debug info could help?

Mar 09 06 7:18 pm

Hi, sorry for the delay - I was about to ask you whether you could run some traffic capturing software and capture one session from start to finish?

Ethereal or something else?

Mar 09 06 10:14 pm

Yes, i could. Didn't think about this earlier.
I will try to run Ethereal and see what's happening? Do you think this will do the job or do you recommend a different application to use for traffic capture?

Mar 09 06 10:27 pm

Ethereal is fine - just send me the trace after that. The reason I am asking about this being if the disconnection is initiated by the QBIK driver, these packets will have specific Wingate trace, which we can then analyze.

Ethereal logs

Mar 10 06 10:23 am

I sent you the log files by email.

Mar 10 06 10:25 am

Aye, got them and have sent you a reply.
Post a reply