DNS: A lookup"embproxy.embserverx1.local."

[keeper30]

Guys,

I'm running with Windows Server 2003 and Wingate 5.1. At the activity section console, in the realtime tree activities have so many DNS: A lookup"embproxy.embserverx1.local." horizontally which is cause out of resource in my server. And after a few minutes wingate gatekeeper is terminated. Why is that? Would tell me pls what is going on?

Please help me about this...

Thanks and more power.

keeper30

[adrien]

any time you get heaps of DNS lookups in WinGate I am suspicious you have a DNS configuration loop... i.e if you have configured the WinGate machines OS networking properties DNS settings to use the IP address of the WinGate machine as a DNS server, you will get a loop whenever WinGate uses that DNS server.

With the DNS lookups in the activity window, do the lookups show as coming from the WinGate machine itself?

Adrien

[keeper30]

Adrien,

Thanks for the reply...

Yup, do you mean that i have remove or change the 192.168.0.1 in the DNS server address of local area connection properties?

Thanks again.

keeper30

[adrien]

yep, you'll need to set it to an internet-based DNS server...

WinGate's DNS resolver uses the same value, so if you tell your OS to use WinGate, you are telling WinGate to use itself, hence the loop.

Adrien

[jeds]

you'll need to set it to an internet-based DNS server

Can you explain this further?

I understand how to do it, but not what IP to use, or how to determine what the IP should be.

Thanks

[logan]

Your ISP will be providing at least two Internet DNS servers that you can use in your network configuration. You should contact your ISP and request the IP addresses for these servers.

[jeds]

My ISP states that their DNS servers may change, and to set the adapter to "obtain address automatically", which is how it is set now on the server. It also obtains the DNS server address automatically.

My LAN card is set to use 192.168.0.1 for IP address and DNS server.

Some of the clients are set to automatically connect to the LAN, others work better to use a specified IP in the 192.168.0.1-255 range with gateway set to 192.168.0.1

1st thing in the morning is when I find the server looping through tons of lookups, causing connection problems for the clients.
If I reboot the server it takes care of it, but it keeps re-occuring.

I rarely use the server for anything other than the gateway.

[Nev]

My LAN card is set to use 192.168.0.1 for IP address and DNS server.

Hi,

This will cause a loop, where the Internal NIC you mention [if it's in the Wingate server] will cause a loop as Adrien explained above.

This NIC should only have an IP address which you mentioned and a suitable subnet mask.

The external NIC should have the Gateway and DNS Servers required for your connection, or supplied by DHCP is quite ok too, if the servers change.

[jeds]

This NIC should only have an IP address which you mentioned

So the internal LAN card should have an IP address in the 192.168.0.1-255 range, but not 192.168.0.1 or any that is being used by one of the clients?

I guess that is confusing because the clients use 192.168.0.1 for the gateway, as they are all connected to the server via the LAN card. If I change the IP for the LAN card on the server, they are still going to be able to connect?

Subnet mask is set to 255.255.255.0, preferred DNS server is 192.168.0.1 (the problem?), and no default gateway is set in advanced TCP/IP on the server LAN card

Thanks much

[logan]

Nev was pointing out that the Default Gateway and DNS settings of the Internal NIC, should not point to the NIC's own IP address.

If your internal NIC is assigned 192.168.0.1, then ensure that neither the Default Gateway or DNS settings on that NIC are set to 192.168.0.1.

[jeds]

Thanks, that seems to have fixed it.

JEDs