WinGate 5.2.3 DNS issue on WinNT4Serv

[Mickey]

Hello

I just installed WinGate v5.2.3 on a test machine (WinNT4 SP6a, hotfixes etc...).
After WinGate Engine starts DNS don't work, even on SERVER ping any site by domain name is blocked (unable to resolve host IP)
When I disable Engine I can ping by domain name on Server.
I uninstall v5.2.3 and install 5.2.2 and everything work OK !!!
I test new NAT driver from v5.2.3 on installed WinGate 5.2.2 and DNS stop work (after change to oryginal v5.2.2. nat file "qbikhknt.sys" DNS start to work)

And another thing I notice that when users use NAT the WG Traffic Monitor don't show their traffic. Du Meter also don't show this traffic, only Proxy and WGIC trafic is monitored. It is so annoying that I unable to check trafic on NIC interface.

[genie]

The reason WG Traffic monitor does not see NAT traffic is that NAT traffic is not visible to the system (since WG monitor uses system facade to get traffic info). This drawback will be fixed in one of the upcoming versions.

As of the DNS issue - our test lab is on it.

[genie]

What kind of networking do you have on this test machine? Like, what network cards are installed, dialing if any, etc.?

[Mickey]

No dialing, only 2 network cards:
First to LAN => RealTek 8139 driver v6.11
Second to Router => Katron Computers ET-16TB driver v3.51.1057.1

Server IP for LAN:
192.168.0.1

Server IP for internet:
5x public IPs bind to this NIC
3x DNS IPs (from my ISP)
defined gateway IP (ISP)

[genie]

Well, my immediate advise would be to update network card drivers :)
Seriously, though, can you run Commview or any other network sniffer and see if there is any outbound traffic generated by the DNS server and/or inbound replies traffic?

[Mickey]

Realtek driver is the latest available on the net.
Katron Computers ET-16TB don't publish any newer driver, the NIC is build on RealTeh 8029 chip but drivers from realtek site don't work.

I say that on older version everything work OK, only on newer qbikhknt.sys file the DNS stop to work when WinGate Engine is started

Ping by IP address always work, only resolving DNS name won't work
Ping from server by DNS name work only when WinGate Engine is STOPED

[genie]

Can you see the actual traffic going out from your machine? I mean we tried reproducing it here, in the lab, but did not succeed. I'd suggest we send you our debug kit so you can generate a debug log for us to analyse. To do that we need your IP address - just drop me a message and I'll forward this kit to you.

[simoko]

[quote="Mickey"]Hello

I just installed WinGate v5.2.3 on a test machine (WinNT4 SP6a, hotfixes etc...).
After WinGate Engine starts DNS don't work, even on SERVER ping any site by domain name is blocked (unable to resolve host IP)
When I disable Engine I can ping by domain name on Server.
I uninstall v5.2.3 and install 5.2.2 and everything work OK !!!


==========================

I have a similar problem witn Wingate Pro:
5.2.2 works fine;
after the upgrade to 5.2.3. [901] serious problems [dns];
after uninstall 5.2.3. and re-install 5.2.2.: no problem

We use W-XP-pro.

[Remco79]

Hi all,

I have a similar troubles on a W2K pro SP4 machine.

outgoing NIC: SMC 1208 (using Realtek 5.08 drivers)
NIC for lan: Sitecom rtl8139-based NIC (using Realtek 6.11 drivers)

If wingate 5.2.3 is running, no DNS lookups are possible on this system.
(ping to IP is still possible.)

Could this be the same problem?

[Mickey]

I send debug files, and just found that when this issue presents there is a line in log file like that:

D:\Programming\@WGDEV.523\common\CDNSSession.cpp(206): error response from resolver

[ulenius]

Hi!
In Wingate 5.2.2 and older versions I have noted that Seti@home now and than hangs when it tries to send work packags to server through Wingate. The client problem is probably related to Windows XP?!?!+
I have not noticed the problem on W2K or W98. If I use proxy or not on the client does no difference?!?!
After refresh of client or restart of Seti application the SW runs nicely again. (Until one or 2 workpackages later). It might be in connection to DNS or client dropout??? and than when Seti tries to access it's server it just hangs....

Can Wingate client refresh itself? Can the Seti problem be resolved?? and is it a Seti or Wingate problem??

/Anders