DNS nor NAT initiates Dialer

[Dennis]

Hi all. I have a problem with wingate 6.04. Even though "Connect as required" is checked and the connection profile is ok (manually hitting DIAL dials!) and DNS Service "allow request to initiate dialer" is checked, it won't dial if a DNS request is made.
I'm using the proxy settings in my client browser to connect to wingate but if I type "www.google.com" it doesn't dial. In the Activity log screen there is the DNS lookup for "google.com" but nothing happens, after some secs my browser tells me "unknown host". if I use the IP instead "http://66.102.7.147/" it says "Host unreachable".
All works fine if I hit the DIAL button manually everytime I want to connect to the internet - stop, no not quite: if the connection is made and I'm using just NAT then wingate hangs up after the "Disconnect after" seconds with cutting my NAT connection. If I'm using the web browser all is ok. This is no good. I have tried reinstalling Wingate - but same results.
Why does the Wingate dialer not work??

DNSResolver.log:

05/14/05 14:47:49 Request: request [0316d63c] A lookup "www.wingate.com."
05/14/05 14:47:49 Error: bounce request [0316d63c]<1> to try 3 (no specific and cannot select)


Regards,
dennis

[Nev]

Hi Dennis,

Probably no use but: http://forums.qbik.com/viewtopic.php?t=3434

Report back how it goes.

[Dennis]

Thanks for that response. But It didn't helped me - the dial profile is shown in my wingate. The user rights are "all unrestricted", the dial profile was on "auto(external)" so i set it to "external". nothing helped...

[Nev]

Ok Dennis, out of interest did you delete / re create the connectoid?

Which o/s is Wingate working under, AD by any chance?

[jamesc]

Some things to check.

1. On the WinGate server, check that the internal network card does not have its DNS and Gateway set as it self.
e.g. WinGates network card facing the LAN should not have a DNS and Gateway address specified.

2. As Nev said, do you have Active Directory, whats your O/S(s)?

3. What kind of Network Card is on the WinGate server?
(Windows) Start Menu --> cmd --> ipconfig /all --> look next to "Description" category of internal network card...

[Dennis]

Hello all,

thanks for your suggestions.

1. on the wingate server (windows 2000 server) no gateway is definied but DNS (on itself!), have deleted the dns entry, but windows now uses 127.0.0.1 as dns (because of AD - see 2.)

2. yes, AD is active. There is a DNS-Server running on IP .250 and WingateDNS on .251. The DNS is configured to forward all DNS queries that couldn't be resolved to the WingateDNS, so interal queries won't flood the wingate dns.

3. 3COM 10/100 PCI Ethernet Adapter

4. recreated the dialer account some time before

oh. it now works - first test showed on the client a "host not found" but I've noticed the dial up on the server. Hitting "refresh" on the client now shows the webpage. I'll try again. Ok it works. It was (1.) with setting the DNS on 127.0.0.1. Many thanks to all of you!

Regards,
Dennis

[MattP]

Hi Dennis,

Just further to this, have you added the AD DNS server to the advanced options applet in WinGate?

If you go to Start>Programs>WinGate>Advanced Options you'll open an applet, select DNS servers from the list and make sure that the AD DNS server is listed. This stops WinGate from referencing the AD DNS server when it receives a DNS request.

Also, if your AD DNS server is on .250, shouldn't your WinGate LAN NIC have that address listed as the DNS server so it can log on to the AD? Or did I misread your post?

[Dennis]

Hi MattP,

haven't added AD with adv options. Ok, now this is done.

>Also, if your AD DNS server is on .250, shouldn't your WinGate LAN NIC >have that address listed as the DNS server so it can log on to the AD?

I'm not sure what you mean. I have a single server with two IPs (.250 and .251). The AD DNS listens on 127.0.0.1 and .250, I have configured Wingate DNS to listen on .251. All the clients are set to DNS .250, AD DNS forwards all non resolvable (=non-internal) requests to .251 (Wingate) which initiates the dial up then. NAT works fine with that and Wingate DNS isn't flooded with MS internal DNS look ups.

I solved the the problem with deleting the DNS on the internal network card (was set to .250), but as it's an AD, windows set it internally to 127.0.0.1 (ipconfig tells me this).

regards,
dennis

[Dennis]

i have still a problem with the dialer. it now dials if a proxy request is made. but if i'm using only NAT connections it hangs up after the "disconnect timeout" time specified in the dialup profile, regardless of the still very active NAT connection...

[genie]

Hi, Dennis

This disconnecting problem is the bug we have fixed already - I can arrange the new driver and the new engine to be sent to you - just let me know what OS you are using.

[Dennis]

I'm using windows 2000 server, thanks for your effort.

[genie]

Hi, Dennis

I've just sent you the requested files (the driver and the engine).