Reading the Diagnostic log

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

Moderator: Qbik Staff

Reading the Diagnostic log

Postby kranitzw » Feb 01 12 12:08 pm

Hi all,

I'm Using Wingate 7. Where do I find information on the various error codes that appear in the Global Diagnostic Log. I'm seeting thousands of errors a day posted. Below are 4 of them:

78 36584 1/31/2012 0:33:18.368 192.168.1.202 Unknown DNS Service 3776 353906 Error 0 Unsupported DNS opcode (WINS_REGISTRATION)

122 36628 1/31/2012 0:55:59.764 DNS Client 2632 Warning 106 Error 10054 receiving from 205.128.79.45

176 36682 1/31/2012 1:14:10.610 192.168.1.204 Unknown DNS Service 3776 354386 Error 0 unknown exception in ProcessRequest

1506 38012 1/31/2012 10:28:25.832 192.168.1.200 Wingate Admin RTSP Proxy Service 2176 359827 Error 0 Caught client socket exception in CRTSPSession::OnRead() Connection to Remote Host timed out {Thd 2176} [socket #3DE4, 0.0.0.0:62835 to :0] - terminating

I'm particularly interested in the line 78 and 176. SO, where can I find information on troubleshooting this stuff.

Thanks,

Wes
kranitzw
 
Posts: 14
Joined: Jan 20 12 8:27 pm

Re: Reading the Diagnostic log

Postby adrien » Feb 01 12 2:37 pm

Hi

line 78, unsupported DNS opcode means the client sent a request type that's not supported. WINS_REGISTRATION means the client tried to register itself with WinGate's DNS server, which isn't supported. This error can be safely ignored.

line 122. Error 10054 is a windows sockets error code. It implies (I think) that WinGate tried to send a packet to a ip:port that had been closed. E.g. the server WinGate sent the request to wasn't running a DNS service. The particular IP can be the result of a previous lookup (in which case it's not serious), or one of the DNS servers specified in WinGate DNS client, in which case its severity depends on whether it's a permanent state or transient (e.g. your ISP DNS server rebooted, or you have an invalid DNS server specified).

line 176. This is more serious. does it happen often? Which version of WinGate 7 is this?

line 1506: this implies a requested server in the RTSP proxy wasn't available, it's not an error in WinGate per se.

Regards

Adrien de Croy
adrien
Qbik Staff
 
Posts: 5448
Joined: Sep 03 03 2:54 pm
Location: Auckland

Re: Reading the Diagnostic log

Postby kranitzw » Feb 01 12 8:47 pm

Adrien,

Thanks for the analysis.

With respect to line 176, I see at least 10 of them a day in the logs. I am running WinGate 7.0.8 (Build 3364). The IP addresses shown are from different machines on our network so it doesn't appear to be isolated to one machine.

Any ideas as to where I could find information about these errors so I don't have to bother you to tell me what they are.

Thanks again,

Wes
kranitzw
 
Posts: 14
Joined: Jan 20 12 8:27 pm

Re: Reading the Diagnostic log

Postby adrien » Feb 02 12 9:08 am

Hi

Short answer is we haven't got a definitive list yet for WinGate 7

There are a lot of new log entries compared to WinGate 6. Some of them we will likely re-assign, e.g. error->warn or similar.

Also it's quite useful for us to see what issues customers are seeing, so we don't mind you posting.

We had a list for WinGate 6, I'll see if our support guys can update it a bit as well.

Adrien
adrien
Qbik Staff
 
Posts: 5448
Joined: Sep 03 03 2:54 pm
Location: Auckland

Re: Reading the Diagnostic log

Postby kranitzw » Feb 02 12 11:25 am

Adrien,

Thanks for the response.

For those interested, I found a list of socket errors with explainations on Microsofts Website. They are in Knowledgebase article 819124.

Wes
kranitzw
 
Posts: 14
Joined: Jan 20 12 8:27 pm


Return to WinGate

Who is online

Users browsing this forum: No registered users and 81 guests

cron