Hopefully someone can shed some light on this. Starting recently with 6.0 and also continuing with 6.1 upgrade, users sometimes have access OK through Wingate (with & without WGIC) then their access seems to block, i.e. sieze up. When I look at Gatekeeper I can see that they have a blocked DNS lookup pending on an internet name. All other access is then blocked for all users. If I terminate the session on that DNS lookup, all pending activity comes flooding through and then everything is OK. This happens a few times per week.
I've done 2 Windows updates on the Wingate server after which this problem started occuring, neither related to DNS. I've rolled both back but the problem still persists. Virus & malware scans reveal nothing untoward. Wingate std. runs on Windows 2000 with latest service pack and updates applied.
Any help or debug info would be much appreciated
cheers
B
DNS holdup
Moderator: Qbik Staff
4 posts
• Page 1 of 1
by Pascal » Nov 28 05 11:04 am
The first step would be to enable full debug logging for both the DNS Server and the DNS/WINS Resolver. This should allow us to begin tracing the problem.
How do you have DNS setup? Are you running a local DNS server as well?
How do you have DNS setup? Are you running a local DNS server as well?
- Pascal
- Qbik Staff
- Posts: 2623
- Joined: Sep 08 03 8:19 pm
- Location: Auckland, New Zealand
by daviesb7 » Nov 29 05 2:56 am
There is no local DNS server runnning. I'll try turning on full logging and get back to you with anything of interest in the log files as & when (if!) it happens again
cheers
B
cheers
B
Pascal wrote:The first step would be to enable full debug logging for both the DNS Server and the DNS/WINS Resolver. This should allow us to begin tracing the problem.
How do you have DNS setup? Are you running a local DNS server as well?
- daviesb7
- Posts: 10
- Joined: Apr 27 05 8:22 pm
Update
by daviesb7 » Jan 28 06 5:13 am
Don't know if this helps but the problem of the DNS requests queuing up seems to be triggered when the Intenet connection goes down.
Basically the ADSL signal goes away (perhaps only for a few seconds), then a Wingate user makes a request and instead of the DNS request comming back with some sort of timeout, it simply blocks, apparently waiting for the Internet to come back. unfortunatley, when the Internet connection does come back, the request neither completes or times out, thence blocking all subsequent requests/users.
If I terminate all sessions then all the subsequent requests which have stacked up go flying through and everything is OK.
I've tried adding the ISP DNS servers into the Wingate configuration, in case it was loosing this information when the Internet line dropped
Any ideas??
Basically the ADSL signal goes away (perhaps only for a few seconds), then a Wingate user makes a request and instead of the DNS request comming back with some sort of timeout, it simply blocks, apparently waiting for the Internet to come back. unfortunatley, when the Internet connection does come back, the request neither completes or times out, thence blocking all subsequent requests/users.
If I terminate all sessions then all the subsequent requests which have stacked up go flying through and everything is OK.
I've tried adding the ISP DNS servers into the Wingate configuration, in case it was loosing this information when the Internet line dropped
Any ideas??
- daviesb7
- Posts: 10
- Joined: Apr 27 05 8:22 pm
4 posts
• Page 1 of 1
Who is online
Users browsing this forum: Google [Bot] and 23 guests