PHWinfo - Afficher un message

09/06/2007, 17h47

Hi

If as you say, all the DNS config is fine, those event ids may .

There is a basic requirement of kerberos to have the correct time,from what I
have read (and experienced on my test network).Have all these machines got
the same time?I believe the threshold is 5 mins difference by default before
things fail. I know its very basic but sometimes you do overlook these things:
-)

Like Ace says the more info the better, hope you get it fixed.

Regards

S

Ace Fekay [MVP] wrote:
>> Yup - but my trouble is tracking it down! However the symptons are
>> slightly worse than long log on times, if a member server creates a
>[quoted text clipped - 27 lines]
>> pass yesterday it all looked good. I'm considering a change to
>> 172.16 just to make things clearer <g>
>
>Read the following information closely. Please post the any information
>(without editing it please) it is asking so we can ALL be clear on your
>configuration. This info will us determine where the problem may lie.
>
>--------
>Here are some possible causes:
>1. Single label name.
>2. SRV records missing.
>3. Disjointed namespace.- AD domain name doesn't match the Primary DNS
>Suffix and/or the zone name.
>4. Using an ISP's DNS in IP properties of the DC and clients.
>5. DHCP Client service disabled.
>6. DC is multihomed
>7. 3rd party firewalls
>8. etc....
>
>If you like to get specific to diagnose this issue, and to elimiante
>guesswork on our part, for starters, please post the following information:
>1. Unedited ipconfig /all from two of your DCs, and one of your clients..
>2. The exact zone name spellng in DNS and whether updates are allowed on the
>zone.
>3. The AD DNS domain name as it shows up in ADUC.
>4. If the SRV records exist under your zone.
>5. Any errors in the Event logs on the DC under System, Replication Service
>and Directory Services (post the Event ID# and source please)
>6. Dcdiag /v /fix > c:\dcdiag.txt (post the dcdiag.txt as an attachment)
>7. Netdiag /v /fix > c:\netdiag.txt (post the dcdiag.txt as an attachment)
>8. More than one subnet?
>9. Forwarder(s) configured?
>-----
>
>Ace

--
Message posted via WinServerKB.com
http://www.winserverkb.com/Uwe/Forum...r-dns/200706/1

09/06/2007, 17h47	#8
si via WinServerKB.com Messages: n/a Hébergeur:	Re: Odd DNS issue Hi If as you say, all the DNS config is fine, those event ids may . There is a basic requirement of kerberos to have the correct time,from what I have read (and experienced on my test network).Have all these machines got the same time?I believe the threshold is 5 mins difference by default before things fail. I know its very basic but sometimes you do overlook these things: -) Like Ace says the more info the better, hope you get it fixed. Regards S Ace Fekay [MVP] wrote: >> Yup - but my trouble is tracking it down! However the symptons are >> slightly worse than long log on times, if a member server creates a >[quoted text clipped - 27 lines] >> pass yesterday it all looked good. I'm considering a change to >> 172.16 just to make things clearer <g> > >Read the following information closely. Please post the any information >(without editing it please) it is asking so we can ALL be clear on your >configuration. This info will us determine where the problem may lie. > >-------- >Here are some possible causes: >1. Single label name. >2. SRV records missing. >3. Disjointed namespace.- AD domain name doesn't match the Primary DNS >Suffix and/or the zone name. >4. Using an ISP's DNS in IP properties of the DC and clients. >5. DHCP Client service disabled. >6. DC is multihomed >7. 3rd party firewalls >8. etc.... > >If you like to get specific to diagnose this issue, and to elimiante >guesswork on our part, for starters, please post the following information: >1. Unedited ipconfig /all from two of your DCs, and one of your clients.. >2. The exact zone name spellng in DNS and whether updates are allowed on the >zone. >3. The AD DNS domain name as it shows up in ADUC. >4. If the SRV records exist under your zone. >5. Any errors in the Event logs on the DC under System, Replication Service >and Directory Services (post the Event ID# and source please) >6. Dcdiag /v /fix > c:\dcdiag.txt (post the dcdiag.txt as an attachment) >7. Netdiag /v /fix > c:\netdiag.txt (post the dcdiag.txt as an attachment) >8. More than one subnet? >9. Forwarder(s) configured? >----- > >Ace -- Message posted via WinServerKB.com http://www.winserverkb.com/Uwe/Forum...r-dns/200706/1