DNS , Authentication Issue

Microsoft Windows server 2003 r2 standar...
November 2, 2010 at 09:07:38
Specs: Windows Server 2003
Hi,

We have 2 domain controllers (for simplicity lets call them ServerA and Server B) running MS Server 2003. Only 1 is a global catalogue server (ServerA).

Clients obtain their server addresses automatically and are given the records for the 2 domain controllers plus a couple of our internet providers’ dns servers.

Users often complain that their Outlook is disconnected. If they close Outlook, do a network connection ‘repair’ on their machine and re-open Outlook it then connects.

Similarly users often complain they can’t print. If they do a network connection ‘repair’ they are able to print.

If on a client I choose Use the following DNS addresses and put in ServerA or/and ServerB only then I don’t seem to get the above issues however internet browsing is incredibly slow. If I change the DNS addresses to ServerA or ServerB and also add a dns server from our internet provider then the internet speed is as expected but the above issue appears again.

This issue occurs on Windows 7 and XP clients.

Has anyone else had this problem? Do you think this is an AD authentication and/or a DNS issue?

Thanks in advance for your help.

Mark


See More: DNS , Authentication Issue

Report •

#1
November 2, 2010 at 09:34:30
" Only 1 is a global catalogue server"
they should both be GC holders

"Clients obtain their server addresses automatically and are given the records for the 2 domain controllers plus a couple of our internet providers’ dns servers."
you should only list the MS DNS servers assuming both server A and B are dns servers

Appears to me you did not configure the forwarders tab with the isp's dns servers.


Report •

#2
November 2, 2010 at 10:14:20
Hi,

"you should only list the MS DNS servers assuming both server A and B are dns servers"
Yes both server A and B are DNS servers. If I only list these servers and not the isp's dns servers then the internet is unusably slow (it returns if I add the isp servers back in).

"Appears to me you did not configure the forwarders tab with the isp's dns servers."
The Forwarders tab is configured with the other internal DNS server and the ISP's dns servers. e.g. Server A's forwarders tab includes ServerB and the isp dns servers.

Any other ideas?


Report •

#3
November 2, 2010 at 10:18:01
You, in effect, have created a loop of server A asking server B for a name/ip they can't resolve.

More is not better.

Only list the isp dns servers in the forwarders tab
Only list the ms dns servers in the workstations for dns

Then name resolution will work as designed by microsoft.


Report •

Related Solutions

#4
November 12, 2010 at 06:36:34
Hi,

Have implemented this and all seems to be working well.

Many thanks for your help.

Mark


Report •

#5
November 12, 2010 at 06:40:21
Glad it worked out for you. Thanks for posting the results.

How to properly post a question: http://tinyurl.com/2fsqqmu


Report •

Ask Question