Wingate Stopped responding all of a sudden.

[salimwng]

Hello,

I am a registered user of Wingate.

SITUATION:

Today morning, when we came to the office, nobody was having access to Internet and email. We phoned our service provider and they said that everything is working fine. We checked at the server and everything seems to run fine. We stopped the engine, deleted all the cache, and the history.cdx and history.dbf and restarted the engine. On the Control panel we can see the users trying to browse but they constantly get the error message "The page cannot be displayed...bla bla bla..."

When i try to make the server connect directly to Internet (through the router) without going through Wingate i can browse without any problem. When putting it back through wingate it cannot load again. We have two network cards installed. One that acts internally for our internal network and the other card is connected to the router.

I even tried to upgrade our Wingate from Version 6.0 to Version 6.14(Build 1099), without success. We even restarted the server. We checked at the space on the HD and it is Okay.

As at yesterday night everything was working fine. No changes were made to the Wingate neither. This happen all of a sudden.

What could be going wrong ? What test can i do to locate the problem ?

Thank you for your help and suggestions,

Kind regards.
Salim

[Microtech]

Hi,

We have been having the same problem with almost all our customers. As from this morning Wingate stopped responding to WWW resquests. We can still use NAT to go out but we don't have the same access control feature as WWW has. After 1 full day of troubleshooting, I have come up to the conclusion that our ISP has made some changes to its DNS servers, but these guys are so dumb that its helpless to discuss anything with them.

However, using Microsoft ICS in place of Wingate works fine. I have just made a fresh install on a freshly setup network for testing purposes and the result is the same.

I am very conversant with Wingate configuration, so be assured that I have tried all possible settings before turning back to this forum.

The WWW service log file indicates:

08/03/06 20:24:47 192.168.1.251 Guest 0000000009 Created:
08/03/06 20:24:54 192.168.1.251 Guest 0000000009 Requested: http://www.microtech.mu/
08/03/06 20:24:54 192.168.1.251 Guest 0000000009 Debug: [www.microtech.mu/] Copy to use: SERVER
08/03/06 20:24:54 192.168.1.251 Guest 0000000009 Debug: WWW Session sending server request in thread ea0
08/03/06 20:25:15 192.168.1.251 Guest 0000000009 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 3744} [socket #85C, 192.168.1.254:1074 to :0] - terminating
08/03/06 20:25:15 192.168.1.251 Guest 0000000009 Traffic 348 396 0 0 28s
08/03/06 20:25:15 192.168.1.251 Guest 0000000009 Terminated exit code 2
08/03/06 20:26:28 Configuration changed
08/03/06 20:26:32 192.168.1.251 Guest 0000000010 Created:
08/03/06 20:26:39 192.168.1.251 Guest 0000000010 Requested: http://www.google.com/
08/03/06 20:26:39 192.168.1.251 Guest 0000000010 Debug: [www.google.com/] Copy to use: SERVER
08/03/06 20:26:39 192.168.1.251 Guest 0000000010 Debug: WWW Session sending server request in thread 788
08/03/06 20:27:00 192.168.1.251 Guest 0000000010 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 1928} [socket #818, 192.168.1.254:1076 to :0] - terminating
08/03/06 20:27:00 192.168.1.251 Guest 0000000010 Traffic 348 473 0 0 28s
08/03/06 20:27:00 192.168.1.251 Guest 0000000010 Terminated exit code 2

BTW, Salim, we are the local representative of QBik. So you can contact us on info@microtech.mu if you need local support.

Regards

[salimwng]

Hello,

Many thanks for sharing this important information. I have been going crazy with this problem during the whole day and ..... till now.

Have you been able to get a work around for this ?

I hope QBik team will come up with some sort of solution.

Many thanks again,
Regards.
Salim

[salimwng]

Qbik Team,

Can we have a reply please. Business is down since yesterday !

Thanks
Salim

[genie]

Hi,
Sorry for the delay - we were checking the debug output. The trace indicated that the address resolved was incorrect - can you send us your Wingate configuration (in Options/Advanced options window click on Troubleshooting and then click on Save report and Save registry settings buttons) and send us the resulted files?

[Microtech]

Hi,

It seems that WWW service is back in operation since sometime around mid-day today. As I stated previously, I was sure that the ISP made some changes to their DNS servers that resulted in this problem. Some customers have called in to say that they system is back on road again.

I will however wait to get confirmation from them all.

I would advise Salim to forward his config data anyway, so that Qbik can locate the exact cause of the incompatibility of Wingate with the DNS.

Regards

[genie]

Thanks - it might be just the case of misconfigured or non-replying DNS server somewhere on the path.

[Microtech]

Could be as you said.

But the strange part in it was that all the services worked fine on the server where Wingate was installed. Also Microsoft ICS worked fine for sharing the internet connection to workstations.

All other services like mail server were operating fine as usual. Even Wingate worked when the workstations were configured to use the Wingate server as default gateway and NAT was enabled on Wingate.

Regards

[Microtech]

Dear genie,

I have still one installation experiencing the same problem. Part of their DNS Resolver log is as follows:

08/04/06 15:30:11 Request: request [0291eb74] A lookup "toolbar.msn.com."
08/04/06 15:30:11 Error: bounce request [0291eb74]<1> to try 3 (no specific and cannot select)
08/04/06 15:30:14 Request: request [02d3eb74] A lookup "www.yahoo.com."
08/04/06 15:30:14 Error: bounce request [02d3eb74]<1> to try 3 (no specific and cannot select)
08/04/06 15:30:20 Request: request [02d3e61c] A lookup "www.yahoo.com."
08/04/06 15:30:20 Error: bounce request [02d3e61c]<1> to try 3 (no specific and cannot select)

Please advise what to do.

Regards

[genie]

Can you send me config files for this machine?

[Microtech]

Dear genie,

I have sent you the files by e-mail.

Thanks & Regards

[salimwng]

Dear Genie and Microtech,

Please see below the configuration files. (Save Report on Advanced Configuration). However, i dont think it is going to be a good idea to paste the registry file here, as it is around 69 Pages long (A4 size). Genie, please kindly let me have your email address and i will mail it to you.

Here's the situation:

As metioned by Microtech, the situation got almost okay around 13:00. I had to shout almost at the tech guys of our service provider, but still they maintain that they did nothing on their server....which is totally bulls**t to me. After 1 hour it got down again, and few mins after it was back to normal. Microtech findings are ok, as i noticed same through logs. However, even though i think Wingate should have function.

I hope the configuration i am submitting below will help all of us here to get a solution.

Keep us informed,

Many thanks
Regards.
Salim
===== START OF ADVANCED CONFIGURATION REPORT =====

1.01 WINGATE CONFIGURATION REPORT

1.02 Friday, August 04, 2006, 17:13

1.03

1.04 ---------------------------------------------

1.05 WinGate Engine

1.06 ---------------------------------------------

1.07 WinGate 6.1.4 (Build 1099)

1.08 Operating System: Windows NT 4.0

1.09 Language: ENU

1.10 User database: WinGate

1.11 Num. users: 3

1.12

1.13

2.01 ---------------------------------------------

2.02 License keys

2.03 ---------------------------------------------

2.04 License Key 1: { INFORMATION NOT BEING DISPLAYED }

2.05

3.01 ---------------------------------------------

3.02 License details

3.03 ---------------------------------------------

3.04 License Key 1

3.05 Version: WinGate 5 Professional 50 concurrent users

3.06 Expiry: None

3.07

4.01 ---------------------------------------------

4.02 Dialer information

4.03 ---------------------------------------------

4.04 Dialer is disabled

4.05

5.01 ---------------------------------------------

5.02 Network Interfaces

5.03 ---------------------------------------------

5.04 Telecom Plus (Dialup) external

5.05 MS TCP Loopback interface (Loopback)

5.06 Compaq Ethernet/Fast Ethernet Adapter/Module (Ethernet) internal

5.07 Compaq Ethernet/Fast Ethernet Adapter/Module (Ethernet) external

5.08

6.01 ---------------------------------------------

6.02 Services

6.03 ---------------------------------------------

6.04

6.05 System Policies

6.06 ---------------------------------------------

6.07 Default System Access Rights:

6.08 Everyone - Restricted by ban list

6.09 Default Start/Stop Rights:

6.10 Administrators - Unrestricted rights

6.11 Default Edit Rights:

6.12 Administrators - Unrestricted rights

6.13

6.14 POP3 Proxy server (POP3 Proxy server)

6.15 ---------------------------------------------

6.16 Session Timeout: 120

6.17 Port: 8110

6.18 Startup: Automatic start/stop

6.19 Access Rights: Defaults: may be used instead

6.20 Start/Stop Rights: Defaults: may be used instead

6.21 Edit Rights: Defaults: may be used instead

6.22

6.23 Telnet Proxy server (Telnet Proxy server)

6.24 ---------------------------------------------

6.25 Session Timeout: 60

6.26 Port: 23

6.27 Startup: Automatic start/stop

6.28 Access Rights: Defaults: may be used instead

6.29 Start/Stop Rights: Defaults: may be used instead

6.30 Edit Rights: Defaults: may be used instead

6.31

6.32 WWW Proxy server (WWW Proxy server)

6.33 ---------------------------------------------

6.34 Session Timeout: 60

6.35 Port: 80

6.36 Startup: Automatic start/stop

6.37 Access Rights: Defaults: may be used instead

6.38 Everyone - Unrestricted rights

6.39 Start/Stop Rights: Defaults: may be used instead

6.40 Edit Rights: Defaults: may be used instead

6.41

6.42 DHCP Service (DHCP Service)

6.43 ---------------------------------------------

6.44 Session Timeout: 60

6.45 Port: 67

6.46 Startup: Automatic start/stop

6.47 Access Rights: Defaults: may be used instead

6.48 Everyone - Unrestricted rights

6.49 Start/Stop Rights: Defaults: may be used instead

6.50 Edit Rights: Defaults: may be used instead

6.51

6.52 Winsock Redirector Service (Winsock Redirector Service)

6.53 ---------------------------------------------

6.54 Session Timeout: 600

6.55 Port: 2080

6.56 Startup: Automatic start/stop

6.57 Access Rights: Defaults: may be used instead

6.58 Start/Stop Rights: Defaults: may be used instead

6.59 Edit Rights: Defaults: may be used instead

6.60

6.61 FTP Proxy server (FTP Proxy server)

6.62 ---------------------------------------------

6.63 Session Timeout: 60

6.64 Port: 21

6.65 Startup: Automatic start/stop

6.66 Access Rights: Defaults: may be used instead

6.67 Start/Stop Rights: Defaults: may be used instead

6.68 Edit Rights: Defaults: may be used instead

6.69

6.70 RTSP Streaming Media Proxy (RTSP Streaming Media Proxy)

6.71 ---------------------------------------------

6.72 Session Timeout: 60

6.73 Port: 554

6.74 Startup: Automatic start/stop

6.75 Access Rights: Defaults: may be used instead

6.76 Start/Stop Rights: Defaults: may be used instead

6.77 Edit Rights: Defaults: may be used instead

6.78

6.79 SOCKS Proxy server (SOCKS Proxy server)

6.80 ---------------------------------------------

6.81 Session Timeout: 60

6.82 Port: 1080

6.83 Startup: Automatic start/stop

6.84 Access Rights: Defaults: may be used instead

6.85 Start/Stop Rights: Defaults: may be used instead

6.86 Edit Rights: Defaults: may be used instead

6.87

6.88 VDOLive Proxy server (VDOLive Proxy server)

6.89 ---------------------------------------------

6.90 Session Timeout: 60

6.91 Port: 7000

6.92 Startup: Automatic start/stop

6.93 Access Rights: Defaults: may be used instead

6.94 Start/Stop Rights: Defaults: may be used instead

6.95 Edit Rights: Defaults: may be used instead

6.96

6.97 POP3 Server (POP3 Server)

6.98 ---------------------------------------------

6.99 Session Timeout: 120

6.100 Port: 110

6.101 Startup: Automatic start/stop

6.102 Access Rights: Defaults: may be used instead

6.103 Start/Stop Rights: Defaults: may be used instead

6.104 Edit Rights: Defaults: may be used instead

6.105

6.106 SMTP Server (SMTP Server)

6.107 ---------------------------------------------

6.108 Session Timeout: 300

6.109 Port: 25

6.110 Startup: Automatic start/stop

6.111 Access Rights: Defaults: may be used instead

6.112 Start/Stop Rights: Defaults: may be used instead

6.113 Edit Rights: Defaults: may be used instead

6.114

6.115 GDP Service (GDP Service)

6.116 ---------------------------------------------

6.117 Session Timeout: 60

6.118 Port: 368

6.119 Startup: Automatic start/stop

6.120 Access Rights: Defaults: may be used instead

6.121 Start/Stop Rights: Defaults: may be used instead

6.122 Edit Rights: Defaults: may be used instead

6.123

6.124 XDMA Proxy service (XDMA Proxy service)

6.125 ---------------------------------------------

6.126 Session Timeout: 20

6.127 Port: 8000

6.128 Startup: Automatic start/stop

6.129 Access Rights: Defaults: may be used instead

6.130 Start/Stop Rights: Defaults: may be used instead

6.131 Edit Rights: Defaults: may be used instead

6.132

6.133 SMTP Proxy server (SMTP Proxy server)

6.134 ---------------------------------------------

6.135 Session Timeout: 180

6.136 Port: 25

6.137 Startup: Automatic start/stop

6.138 Access Rights: Defaults: may be used instead

6.139 Start/Stop Rights: Defaults: may be used instead

6.140 Edit Rights: Defaults: may be used instead

6.141

6.142 DNS Service (DNS Service)

6.143 ---------------------------------------------

6.144 Session Timeout: 60

6.145 Port: 53

6.146 Startup: Automatic start/stop

6.147 Access Rights: Defaults: may be used instead

6.148 Start/Stop Rights: Defaults: may be used instead

6.149 Edit Rights: Defaults: may be used instead

6.150

6.151 WWW Server for viewing log files (Logfile Server)

6.152 ---------------------------------------------

6.153 Session Timeout: 60

6.154 Port: 8010

6.155 Startup: Automatic start/stop

6.156 Access Rights: Defaults: may be used instead

6.157 Start/Stop Rights: Defaults: may be used instead

6.158 Edit Rights: Defaults: may be used instead

6.159

6.160 Remote Control Service (Remote Control Service)

6.161 ---------------------------------------------

6.162 Session Timeout: 60

6.163 Port: 808

6.164 Startup: Automatic start/stop

6.165 Access Rights: Defaults: may be used instead

6.166 Start/Stop Rights: Defaults: may be used instead

6.167 Edit Rights: Defaults: may be used instead

6.168

7.01 ---------------------------------------------

7.02 System Route Table

7.03 ---------------------------------------------

7.04 Current Route Table:

7.05 ---------------------------------------------

7.06 Network Mask Gateway Interface Metric

7.07 0.0.0.0 0.0.0.0 100.0.0.143 100.0.0.1 1

7.08 10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1 1

7.09 10.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1 1

7.10 10.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1 1

7.11 100.0.0.0 255.255.255.0 100.0.0.1 100.0.0.1 1

7.12 100.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1 1

7.13 100.255.255.255 255.255.255.255 100.0.0.1 100.0.0.1 1

7.14 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1

7.15 224.0.0.0 224.0.0.0 10.0.0.1 10.0.0.1 1

7.16 224.0.0.0 224.0.0.0 100.0.0.1 100.0.0.1 1

7.17 255.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1 1

7.18

8.01 ---------------------------------------------

8.02 Enhanced Network Support

8.03 ---------------------------------------------

8.04 Enhanced Network Support: Qbik NDIS Hook 6.0 - Installed and active

8.05 Driver: Enabled

8.06 NAT: Enabled

8.07 Router: Enabled

8.08 Firewall level: Custom

8.09

8.10 Firewall

8.11 ---------------------------------------------

8.12 Disable network name broadcasts to the Internet: Enabled

8.13 Allow users to ping this machine locally: Enabled

8.14 Allow users to ping this machine from the Internet: Disabled

8.15 Discard spoofed packets: Enabled

8.16

8.17 Routing

8.18 ---------------------------------------------

8.19 Multiple default routes: Enabled

8.20 Relay UDP broadcast packets: Enabled

8.100

8.101 Port Security

8.102 ---------------------------------------------

8.103

8.104 Security for: External TCP

8.105 Action: Allow Port: 113 - AUTH

8.106 Action: Allow Port: 1024 - 4096 - External

8.107

8.108 Security for: External UDP

8.109 Action: Allow Port: 1024 - 4096 - External

8.110

8.111 Security for: Internal TCP

8.112 Action: Allow Port: 21 - Hole for FTP Proxy server (Auto)

8.113 Action: Allow Port: 23 - Hole for Telnet Proxy server (Auto)

8.114 Action: Allow Port: 25 - Hole for SMTP Proxy server (Auto)

8.115 Action: Allow Port: 80 - Hole for WWW Proxy server (Auto)

8.116 Action: Allow Port: 110 - Hole for POP3 Server (Auto)

8.117 Action: Allow Port: 554 - Hole for RTSP Streaming Media Proxy (Auto)

8.118 Action: Allow Port: 808 - Hole for Remote Control Service (Auto)

8.119 Action: Allow Port: 1080 - Hole for SOCKS Proxy server (Auto)

8.120 Action: Allow Port: 2080 - Hole for Winsock Redirector Service (Auto)

8.121 Action: Allow Port: 7000 - Hole for VDOLive Proxy server (Auto)

8.122 Action: Allow Port: 8010 - Hole for Logfile Server (Auto)

8.123 Action: Allow Port: 8110 - Hole for POP3 Proxy server (Auto)

8.124

8.125 Security for: Internal UDP

8.126 Action: Allow Port: 0 - Hole for Dialer Monitor (Auto)

8.127 Action: Allow Port: 53 - Hole for DNS Service (Auto)

8.128 Action: Allow Port: 67 - Hole for DHCP Service (Auto)

8.129 Action: Allow Port: 368 - Hole for GDP Service (Auto)

8.130 Action: Allow Port: 8000 - Hole for XDMA Proxy service (Auto)

8.131

8.132 Security for: NAT TCP

8.133 Action: Redirect Port: 21 - Intercepted by FTP Proxy server

8.134 Action: Redirect Port: 25 - Intercepted by SMTP Server

8.135 Action: Redirect Port: 8010 - Intercepted by Logfile Server

8.136 Action: Redirect Port: 8110 - Intercepted by POP3 Proxy server

8.137

8.138 Security for: NAT UDP

8.139

8.140 Security for: DMZ TCP

8.141

8.142 Security for: DMZ UDP

8.143

8.144 Security for: (unknown)

8.145

8.146 Security for: (unknown)

8.500

9.01 ---------------------------------------------

9.02 END OF CONFIGURATION REPORT


===== END OF ADVANCED CONFIGURATION REPORT =====

[Deju]

As for me...I also support
salimwng
Microtech

the problem was detected on the 3d of aug. All users are working by WWW Proxy caouldn't using IE. It seems that Proxy Server stopped working correctly. NAT, and other services were working good. Browsing by NAT works good. In www log:

08/04/06 11:00:37 192.168.1.5 kravtsova 0000004374 Requested: http://www.yandex.ru/
08/04/06 11:01:09 192.168.1.5 kravtsova 0000004371 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 952} [socket #13F4, 0.0.0.0:1445 to :0] - terminating
08/04/06 11:01:09 192.168.1.5 kravtsova 0000004371 Traffic 0 304 0 0 55s
08/04/06 11:01:10 192.168.1.5 kravtsova 0000004372 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 276} [socket #1494, 0.0.0.0:1446 to :0] - terminating
08/04/06 11:01:10 192.168.1.5 kravtsova 0000004372 Traffic 342 350 0 0 55s
08/04/06 11:01:19 192.168.1.5 kravtsova 0000004374 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 1624} [socket #1498, 0.0.0.0:1449 to :0] - terminating
08/04/06 11:01:19 192.168.1.5 kravtsova 0000004374 Traffic 343 724 0 0 55s

W2K3 Server SP1 + WG 6.1.4 ( 2 NIC: Internal+External), DNS local in LAN, forward to DNS service of WG and then to ISP DNS.

Any comments?

[adrien]

HI All

THe documentation for socket error 10049 indicates that Wingate tried to bind to an invalid address. It's not clear whether it tried to connect to an invalid address (i.e. DNS failed resolution), or whether it tried to bind to an invalid local address before it even tried connecting.

I'm pretty sure that if the DNS lookup fails, you'll get a different error.

So, I would check are you using specified local interfaces to connect out on? If so, a change of IP allocated to you by your ISP could get you trying to bind to the wrong local IP.

Check the gateways policies in the proxy servers.

Regards

Adrien

[adrien]

Also check if any MS automatic updates were downloaded and installed that day - you never know - it wouldn't be the first time MS has released a troublesome update.

[Deju]

adrien, thanx for answer
....but no..no...no!
I was at holidays about a week. Six days everything was working good, at the end of the week -> problem appeared!!!
Autoupdate disabled! Nobody has access to server!
Windows 2003 Server +SP1+hotfixes.
2 Static NIC (Int- 192.168.1.1 ; Ext - 193.30.x.x)

1. NAT works well. (WEB, SMTP, FTP and other protocols)
2. DNS server 192.168.1.100 (cashing DNS, forward all requests to WG or ISP DNS) works good, no problems!!
3. On WG machine DNS service enable, DNS/WINS resolver, FTP proxy, WWW Proxy, ENS, Remote Control, LogFile Server

On clients machines WG machine - default GW, DNS server (192.168.1.100), static ip adress. No DHCP servers!

When I change in IE Connection to proxy: port, web pages don't open!
I can't resolve this problem, it's out of my mind! (((

[adrien]

Hi

Your ISP may then have installed a transparent proxy that doesn't like something about the requests coming through from WinGate.

go to www.whatismyip.com to see if your IP is what you expect.

What happens if you have your clients use NAT and then intercept the connections in WinGate?

Adrien

[Deju]

My ISP didn't do any changes, no proxies my ip shows realy.
But when I setup to intercept connections WEB still working good and
trafic goes through Proxy!!!!! Why it is working in such way?

[Deju]

Anybody has ideas????
Adrien, I hope you....will tell something interesting))))

[adrien]

Hi

There are several things that happen differently when you go through the proxy vs being intercepted by the proxy.

In the first case, the client makes the connection to the proxy and sends the request. The proxy makes a DNS lookup for the name in the request and makes the connection and sends the request.

In the second case, the client makes the DNS lookup, then tries to connect to the end server. The proxy intercepts the connection, but knows already the destination of the request so does not make another DNS lookup. It connects to this destination and sends the request.

So, the differences are that the client makes the DNS lookup not the proxy.

Also some tags may be changed in the request.

If you enable debug logging in the DNS resolver, when it's not working do you see any errors posted in there about being unable to lookup names? Do your LAN clients use WinGate as their DNS server?

Adrien

[Deju]

adrien, I understand about DNS lookup.

No, DNS server local on another machine in LAN and clients usining it.
About debuging mode...later...

[Deju]

It'a strange, but when i activate proxy in IE, it bigin working.
in logs DNS resolver:/08/06 19:20:58

Debug: completed [02d5eb78]<0> (cache hit) (0.00s)
08/08/06 19:20:58 Request: request [02e5eb78] A lookup "www.wingate.com."
08/08/06 19:20:58 Debug: completed [02e5eb78]<0> (cache hit) (0.00s)
08/08/06 19:20:58 Request: request [02c5eb78] A lookup "www.wingate.com."
08/08/06 19:20:58 Debug: completed [02c5eb78]<0> (cache hit) (0.00s)
08/08/06 19:21:01 Request: request [02c5eb78] A lookup "www.google-analytics.com."
08/08/06 19:21:01 Debug: completed [02c5eb78]<0> (cache hit) (0.00s)
08/08/06 19:21:01 Request: request [02d5eb78] A lookup "www.wingate.com."
08/08/06 19:21:01 Debug: completed [02d5eb78]<0> (cache hit) (0.00s)
08/08/06 19:21:01 Request: request [02e5eb78] A lookup "www.wingate.com."
08/08/06 19:21:01 Debug: completed [02e5eb78]<0> (cache hit) (0.00s)
08/08/06 19:21:02 Request: request [0245eb78] A lookup "www.wingate.com."
08/08/06 19:21:02 Debug: completed [0245eb78]<0> (cache hit) (0.00s)
08/08/06 19:21:02 Request: request [02c5eb78] A lookup "www.wingate.com."
08/08/06 19:21:02 Debug: completed [02c5eb78]<0> (cache hit) (0.00s)
08/08/06 19:21:08 Request: request [02c5eb78] A lookup "forums.qbik.com."
08/08/06 19:21:08 Debug: bounce request [02c5eb78]<0> to try 1 (nothing useful in cache)
08/08/06 19:21:08 Debug: selected 217.23.130.1 <IP helper> for request [02c5eb78]<1> (best looking)
08/08/06 19:21:08 Debug: request [02c5eb78](ID 964) sent to 217.23.130.1 <IP helper> (33 bytes)
08/08/06 19:21:09 Debug: received block [105] (server 217.23.130.1, port 53)
08/08/06 19:21:09 Debug: useful response [02c5eb78](ID 964) (1.09s)
08/08/06 19:21:10 Request: request [02d5eb78] A lookup "forums.qbik.com."
08/08/06 19:21:10 Debug: completed [02d5eb78]<0> (cache hit) (0.00s)
08/08/06 19:21:10 Request: request [02e5eb78] A lookup "forums.qbik.com."
08/08/06 19:21:10 Debug: completed [02e5eb78]<0> (cache hit) (0.00s)
08/08/06 19:21:10 Request: request [0245eb78] A lookup "forums.qbik.com."
08/08/06 19:21:10 Debug: completed [0245eb78]<0> (cache hit) (0.00s)
08/08/06 19:21:10 Request: request [02c5eb78] A lookup "forums.qbik.com."
08/08/06 19:21:10 Debug: completed [02c5eb78]<0> (cache hit) (0.00s)
08/08/06 19:21:16 Debug: DNS registry entry scan (0 total entries)
08/08/06 19:21:33 Request: request [02e5eb78] A lookup "forums.qbik.com."
08/08/06 19:21:33 Debug: completed [02e5eb78]<0> (cache hit) (0.00s)
08/08/06 19:21:34 Request: request [02c5eb78] A lookup "web.icq.com."
08/08/06 19:21:34 Debug: bounce request [02c5eb78]<0> to try 1 (nothing useful in cache)
08/08/06 19:21:34 Debug: selected 217.23.130.1 <IP helper> for request [02c5eb78]<1> (best looking)
08/08/06 19:21:34 Debug: request [02c5eb78](ID 965) sent to 217.23.130.1 <IP helper> (29 bytes)
08/08/06 19:21:35 Debug: received block [196] (server 217.23.130.1, port 53)
08/08/06 19:21:35 Debug: useful response [02c5eb78](ID 965) (0.03s)
08/08/06 19:21:36 Request: request [02e5eb78] A lookup "status.icq.com."
08/08/06 19:21:36 Debug: bounce request [02e5eb78]<0> to try 1 (nothing useful in cache)
08/08/06 19:21:36 Debug: selected 217.23.130.1 <IP helper> for request [02e5eb78]<1> (best looking)
08/08/06 19:21:36 Debug: request [02e5eb78](ID 966) sent to 217.23.130.1 <IP helper> (32 bytes)
08/08/06 19:21:36 Debug: received block [177] (server 217.23.130.1, port 53)
08/08/06 19:21:36 Debug: useful response [02e5eb78](ID 966) (0.03s)
08/08/06 19:21:36 Request: request [0245eb78] A lookup "status.icq.com."
08/08/06 19:21:36 Debug: completed [0245eb78]<0> (cache hit) (0.00s)
08/08/06 19:21:40 Request: request [0245eb78] A lookup "forums.qbik.com."
08/08/06 19:21:40 Debug: completed [0245eb78]<0> (cache hit) (0.00s)
08/08/06 19:21:40 Request: request [0245eb78] A lookup "forums.qbik.com."
08/08/06 19:21:40 Debug: completed [0245eb78]<0> (cache hit) (0.00s)
08/08/06 19:21:55 Request: request [0245eb78] A lookup "forums.qbik.com."
08/08/06 19:21:55 Debug: completed [0245eb78]<0> (cache hit) (0.00s)
08/08/06 19:21:57 Request: request [0245eb78] A lookup "forums.qbik.com."
08/08/06 19:21:57 Debug: completed [0245eb78]<0> (cache hit) (0.00s)
08/08/06 19:22:01 Request: request [0245eb78] A lookup "forums.qbik.com."
08/08/06 19:22:01 Debug: completed [0245eb78]<0> (cache hit) (0.00s)
08/08/06 19:22:16 Debug: DNS registry entry scan (0 total entries)
08/08/06 19:23:16 Debug: DNS registry entry scan (0 total entries)
08/08/06 19:24:16 Debug: DNS registry entry scan (0 total entries)

[Deju]

Before debugging mode and activating proxy connection in clients IE
the situation was like this one:

08/08/06 00:44:17 Error: bounce request [022a1538]<1> to try 3 (no specific and cannot select)
08/08/06 03:21:52 Request: request [022a1538] PTR lookup "116.37.242.72.in-addr.arpa."
08/08/06 03:21:52 Error: bounce request [022a1538]<1> to try 3 (no specific and cannot select)
08/08/06 07:59:49 Request: request [022a1538] PTR lookup "68.148.85.194.in-addr.arpa."
08/08/06 07:59:49 Error: bounce request [022a1538]<1> to try 3 (no specific and cannot select)
08/08/06 10:12:11 Request: request [022a1538] A lookup "attcanada.net."
08/08/06 10:12:41 Request: request [022a1538] MX lookup "attcanada.net."
08/08/06 10:12:41 Error: bounce request [022a1538]<1> to try 3 (no specific and cannot select)
08/08/06 12:17:48 Request: request [022a1538] A lookup "hcsds.ru."
08/08/06 12:17:48 Error: bounce request [022a1538]<1> to try 3 (no specific and cannot select)
08/08/06 12:18:06 Request: request [022a1538] A lookup "hcsds.ru."
08/08/06 12:18:06 Error: bounce request [022a1538]<1> to try 3 (no specific and cannot select)
08/08/06 12:20:49 Request: request [022a1538] A lookup "hcsds.ru."
08/08/06 12:20:49 Error: bounce request [022a1538]<1> to try 3 (no specific and cannot select)
08/08/06 12:21:07 Request: request [022a1538] A lookup "hcsds.ru."
08/08/06 12:21:07 Error: bounce request [022a1538]<1> to try 3 (no specific and cannot select)
08/08/06 12:25:54 Request: request [022a1538] A lookup "hcsds.ru."
08/08/06 12:25:54 Error: bounce request [022a1538]<1> to try 3 (no specific and cannot select)
08/08/06 12:26:08 Request: request [022a1538] A lookup "hcsds.ru."
08/08/06 12:26:08 Error: bounce request [022a1538]<1> to try 3 (no specific and cannot select)
08/08/06 12:30:59 Request: request [022a1538] A lookup "hcsds.ru."
08/08/06 12:30:59 Error: bounce request [022a1538]<1> to try 3 (no specific and cannot select)
08/08/06 12:31:17 Request: request [022a1538] A lookup "hcsds.ru."
08/08/06 12:31:17 Error: bounce request [022a1538]<1> to try 3 (no specific and cannot select)
08/08/06 12:36:04 Request: request [022a1538] A lookup "hcsds.ru."
08/08/06 12:36:04 Error: bounce request [022a1538]<1> to try 3 (no specific and cannot select)
08/08/06 12:36:22 Request: request [022a1538] A lookup "hcsds.ru."
08/08/06 12:36:22 Error: bounce request [022a1538]<1> to try 3 (no specific and cannot select)
08/08/06 12:41:09 Request: request [022a1538] A lookup "hcsds.ru."

[adrien]

Hi

That indicates that WinGate doesn't have any DNS servers defined.

It's possible that changes at your ISP could have affected the way they assign a DNS server to you.

Are you able to manually enter into the WinGate DNS resolver the IP address of a DNS server to use at your ISP?

Adrien

[Deju]

Again this situation repeated:]

In IE window:

Socket EROR
Socket Error 10049 {Thd 3336} [socket #1160, 0.0.0.0:1252 to :0]

In debug mode in DNS resolver log:

8/09/06 19:15:26 Debug: request [0245dcbc] "www.wingate.com." (no response on try 3)
08/09/06 19:15:26 Debug: multicast request [0245dcbc]<4> (2 known servers)
08/09/06 19:15:26 Debug: request [0245dcbc](ID 39) sent to 217.23.130.1 <IP helper> (33 bytes)
08/09/06 19:15:26 Debug: request [0245dcbc](ID 40) sent to 217.23.142.1 <IP helper> (33 bytes)
08/09/06 19:15:26 Debug: request [02c5eb78] "wingate.com." (no response on try 3)
08/09/06 19:15:26 Debug: multicast request [02c5eb78]<4> (2 known servers)
08/09/06 19:15:26 Debug: request [02c5eb78](ID 41) sent to 217.23.130.1 <IP helper> (29 bytes)
08/09/06 19:15:26 Debug: request [02c5eb78](ID 42) sent to 217.23.142.1 <IP helper> (29 bytes)
08/09/06 19:15:26 Debug: received block [33] (server 217.23.142.1, port 53)
08/09/06 19:15:26 Debug: useful response [0245dcbc](ID 40) (0.03s)
08/09/06 19:15:26 Debug: received block [33] (server 217.23.130.1, port 53)
08/09/06 19:15:26 Debug: useful response [0245dcbc](ID 39) (0.03s)
08/09/06 19:15:26 Debug: received block [29] (server 217.23.130.1, port 53)
08/09/06 19:15:26 Debug: useful response [02c5eb78](ID 41) (0.03s)
08/09/06 19:15:26 Debug: received block [29] (server 217.23.142.1, port 53)
08/09/06 19:15:26 Debug: useful response [02c5eb78](ID 42) (0.03s)
08/09/06 19:15:31 Debug: request [0245dcbc] "www.wingate.com." (retry termination)
08/09/06 19:15:31 Debug: request [02c5eb78] "wingate.com." (retry termination)
08/09/06 19:15:31 Request: request [02c5e620] A lookup "wingate.com."
08/09/06 19:15:31 Debug: bounce request [02c5e620]<0> to try 1 (nothing useful in cache)
08/09/06 19:15:31 Debug: selected 217.23.130.1 <IP helper> for request [02c5e620]<1> (best looking)
08/09/06 19:15:31 Debug: request [02c5e620](ID 43) sent to 217.23.130.1 <IP helper> (29 bytes)
08/09/06 19:15:31 Debug: received block [29] (server 217.23.130.1, port 53)
08/09/06 19:15:31 Debug: useful response [02c5e620](ID 43) (0.03s)
08/09/06 19:15:33 Debug: request [02c5e620] "wingate.com." (no response on try 1)
08/09/06 19:15:33 Debug: multicast request [02c5e620]<2> (2 good servers)
08/09/06 19:15:33 Debug: request [02c5e620](ID 44) sent to 217.23.130.1 <IP helper> (29 bytes)
08/09/06 19:15:33 Debug: request [02c5e620](ID 45) sent to 217.23.142.1 <IP helper> (29 bytes)
08/09/06 19:15:33 Debug: received block [29] (server 217.23.142.1, port 53)
08/09/06 19:15:33 Debug: useful response [02c5e620](ID 45) (0.03s)
08/09/06 19:15:33 Debug: received block [29] (server 217.23.130.1, port 53)
08/09/06 19:15:33 Debug: useful response [02c5e620](ID 44) (0.03s)
08/09/06 19:15:36 Debug: request [02c5e620] "wingate.com." (no response on try 2)
08/09/06 19:15:36 Debug: multicast request [02c5e620]<3> (2 known servers)
08/09/06 19:15:36 Debug: request [02c5e620](ID 46) sent to 217.23.130.1 <IP helper> (29 bytes)
08/09/06 19:15:36 Debug: request [02c5e620](ID 47) sent to 217.23.142.1 <IP helper> (29 bytes)
08/09/06 19:15:36 Debug: received block [29] (server 217.23.130.1, port 53)
08/09/06 19:15:36 Debug: useful response [02c5e620](ID 46) (0.03s)
08/09/06 19:15:36 Debug: received block [29] (server 217.23.142.1, port 53)
08/09/06 19:15:36 Debug: useful response [02c5e620](ID 47) (0.03s)
08/09/06 19:15:40 Debug: request [02c5e620] "wingate.com." (no response on try 3)
08/09/06 19:15:40 Debug: multicast request [02c5e620]<4> (2 known servers)
08/09/06 19:15:40 Debug: request [02c5e620](ID 48) sent to 217.23.130.1 <IP helper> (29 bytes)
08/09/06 19:15:40 Debug: request [02c5e620](ID 49) sent to 217.23.142.1 <IP helper> (29 bytes)
08/09/06 19:15:40 Debug: received block [29] (server 217.23.130.1, port 53)
08/09/06 19:15:40 Debug: useful response [02c5e620](ID 48) (0.01s)
08/09/06 19:15:40 Debug: received block [29] (server 217.23.142.1, port 53)
08/09/06 19:15:40 Debug: useful response [02c5e620](ID 49) (0.01s)
08/09/06 19:15:45 Debug: request [02c5e620] "wingate.com." (retry termination)
08/09/06 19:15:45 Request: request [02c5e620] A lookup "wingate.com."
08/09/06 19:15:45 Debug: bounce request [02c5e620]<0> to try 1 (nothing useful in cache)
08/09/06 19:15:45 Debug: selected 217.23.130.1 <IP helper> for request [02c5e620]<1> (best looking)
08/09/06 19:15:45 Debug: request [02c5e620](ID 50) sent to 217.23.130.1 <IP helper> (29 bytes)
08/09/06 19:15:45 Debug: received block [29] (server 217.23.130.1, port 53)
08/09/06 19:15:45 Debug: useful response [02c5e620](ID 50) (0.03s)
08/09/06 19:15:47 Debug: request [02c5e620] "wingate.com." (no response on try 1)
08/09/06 19:15:47 Debug: multicast request [02c5e620]<2> (2 good servers)
08/09/06 19:15:47 Debug: request [02c5e620](ID 51) sent to 217.23.130.1 <IP helper> (29 bytes)
08/09/06 19:15:47 Debug: request [02c5e620](ID 52) sent to 217.23.142.1 <IP helper> (29 bytes)
08/09/06 19:15:47 Debug: received block [29] (server 217.23.130.1, port 53)
08/09/06 19:15:47 Debug: useful response [02c5e620](ID 51) (0.03s)
08/09/06 19:15:47 Debug: received block [29] (server 217.23.142.1, port 53)
08/09/06 19:15:47 Debug: useful response [02c5e620](ID 52) (0.03s)
08/09/06 19:15:50 Debug: request [02c5e620] "wingate.com." (no response on try 2)
08/09/06 19:15:50 Debug: multicast request [02c5e620]<3> (2 known servers)
08/09/06 19:15:50 Debug: request [02c5e620](ID 53) sent to 217.23.130.1 <IP helper> (29 bytes)
08/09/06 19:15:50 Debug: request [02c5e620](ID 54) sent to 217.23.142.1 <IP helper> (29 bytes)
08/09/06 19:15:50 Debug: received block [29] (server 217.23.130.1, port 53)
08/09/06 19:15:50 Debug: useful response [02c5e620](ID 53) (0.01s)
08/09/06 19:15:50 Debug: received block [29] (server 217.23.142.1, port 53)
08/09/06 19:15:50 Debug: useful response [02c5e620](ID 54) (0.01s)
08/09/06 19:15:52 Debug: DNS registry entry scan (0 total entries)
08/09/06 19:15:54 Debug: request [02c5e620] "wingate.com." (no response on try 3)
08/09/06 19:15:54 Debug: multicast request [02c5e620]<4> (2 known servers)
08/09/06 19:15:54 Debug: request [02c5e620](ID 55) sent to 217.23.130.1 <IP helper> (29 bytes)
08/09/06 19:15:54 Debug: request [02c5e620](ID 56) sent to 217.23.142.1 <IP helper> (29 bytes)
08/09/06 19:15:54 Debug: received block [29] (server 217.23.130.1, port 53)
08/09/06 19:15:54 Debug: useful response [02c5e620](ID 55) (0.01s)
08/09/06 19:15:54 Debug: received block [29] (server 217.23.142.1, port 53)
08/09/06 19:15:54 Debug: useful response [02c5e620](ID 56) (0.01s)
08/09/06 19:15:58 Debug: request [02c5e620] "wingate.com." (retry termination)
08/09/06 19:15:58 Request: request [02c5dcbc] A lookup "wingate.com."
08/09/06 19:15:58 Debug: bounce request [02c5dcbc]<0> to try 1 (nothing useful in cache)
08/09/06 19:15:58 Debug: selected 217.23.130.1 <IP helper> for request [02c5dcbc]<1> (best looking)
08/09/06 19:15:58 Debug: request [02c5dcbc](ID 57) sent to 217.23.130.1 <IP helper> (29 bytes)
08/09/06 19:15:58 Debug: received block [29] (server 217.23.130.1, port 53)
08/09/06 19:15:58 Debug: useful response [02c5dcbc](ID 57) (0.01s)
08/09/06 19:16:00 Debug: request [02c5dcbc] "wingate.com." (no response on try 1)
08/09/06 19:16:00 Debug: multicast request [02c5dcbc]<2> (2 good servers)
08/09/06 19:16:00 Debug: request [02c5dcbc](ID 58) sent to 217.23.130.1 <IP helper> (29 bytes)
08/09/06 19:16:00 Debug: request [02c5dcbc](ID 59) sent to 217.23.142.1 <IP helper> (29 bytes)
08/09/06 19:16:00 Debug: received block [29] (server 217.23.130.1, port 53)
08/09/06 19:16:00 Debug: useful response [02c5dcbc](ID 58) (0.03s)
08/09/06 19:16:00 Debug: received block [29] (server 217.23.142.1, port 53)
08/09/06 19:16:00 Debug: useful response [02c5dcbc](ID 59) (0.03s)
08/09/06 19:16:03 Debug: request [02c5dcbc] "wingate.com." (no response on try 2)
08/09/06 19:16:03 Debug: multicast request [02c5dcbc]<3> (2 known servers)
08/09/06 19:16:03 Debug: request [02c5dcbc](ID 60) sent to 217.23.130.1 <IP helper> (29 bytes)
08/09/06 19:16:03 Debug: request [02c5dcbc](ID 61) sent to 217.23.142.1 <IP helper> (29 bytes)
08/09/06 19:16:03 Debug: received block [29] (server 217.23.130.1, port 53)
08/09/06 19:16:03 Debug: useful response [02c5dcbc](ID 60) (0.01s)
08/09/06 19:16:03 Debug: received block [29] (server 217.23.142.1, port 53)
08/09/06 19:16:03 Debug: useful response [02c5dcbc](ID 61) (0.01s)

217.23.130.1 and 217.23.142.1 - ISP DNS !!!!

What's up?????

[adrien]

Looks like the ISP DNS servers aren't very responsive - there are a lot of timeouts where there is no reply from those servers.

Are there any other DNS servers you know of you can use? Often a local university, or other ISPs etc will let you use them for DNS.

Adrien

[Deju]

But when clients are working by NAT, DNS working good!!!!

[adrien]

Yes, but when the clients use NAT, they are using your local DNS server, which may be doing full recursive name lookups from the root servers, whereas when using proxy, WinGate's DNS resolver is used, which relies on the ISP DNS servers.

Adrien

[Dr_Cancel]

Same problem...

As for me...I also support
the problem was detected on the 3d of aug. All users are working by WWW Proxy caouldn't using IE. It seems that Proxy Server stopped working correctly. NAT, and other services were working good. Browsing by NAT works good.
W2K3 Server SP1 + WG 6.1.4 ( 2 NIC: Internal+External), DNS local in LAN, forward to ISP DNS.

[Dr_Cancel]

What cure?