STRANGE DNS PROBLEM...

[mcit]

I don't think that this is directly wingate related, however I was hoping that someone here may have come across something similar.

Have 2 servers, both Windows 2000 Server.
Server1:
Windows 2000 Advanced Server
256Mb DDR
MS DNS server
Used for file and print sharing and personal directories for all users. Also runs domain [thus the need for DNS] through Active Directory.

Server2:
Windows 2000 Std Server
256Mb DDR
Extra Tools ExtraDNS Server [I'll explain this further down]
Winagte 5.2.3
ATGuard 3.22 Firewalll

Server 2 does all the internet sharing, and is NOT a domain controller on the network, it is simply a member of the domain.
The need for the third party DNS server is because I cannot run MS DNS server with Winagte NAT [don't understand why, it does work with proxies specified in clients though, this is also the reason that this server is NOT a domain controller] and the DNS resolver in wingate I have never been able to make work [right back since version 3]

The problem I have is that I have just installed a new server which has been set up from scratch. I have specified the ExtraDNS server on server2 to forward packets to MS DNS on server1, and then set the wingate DHCP to point client DNS towards server2 [wingate machine], however this leaves me with internet access and no access to the fileserver. When I specify the wingate DHCP to hand out both DNS servers to clients it works for around 2 weeks [I have done this before] and then it stops working. When I then change the DHCP to only give out the DNS of the wingate machine [Server2] it continues to work perfectly. I thought originally that this may be due to the clients learning the DNS adresses and storing them in the route tables. However, when I then connect a completely new machine to the network, it also has no problems connecting to both the file server and the wingate machine.

You may ask why I am using the Wingate DHCP when I can use the MS DHCP [as it specifies in the white papaers], however I assume these papers are referring to a scenario where there is only one server and that configuration does not work in this case [I have tried many times over the last couple of years]

I hope this is not too hard for you to understand. If you are unclear of any details, please post a reply and I will do my best to explain.

Thankyou in advnace.

[Pascal]

http://support.qbik.com/index.php?_a=kn ... ails&_i=82

That might be of some help.

[mcit]

Thanks for your response, however I have already read, re-read and read again all the related whitepapers on this that you have available, I have even read articles from others on the net regarding similar issues, but none have yet helped solve this issue.

On another note, I have discovered that with only one server that is running on an ADSL internet connection, this problem is non-existent. It seems to be the combination of the two servers, and that they are running on a 56k dialup connection.