DNS Error? 1

[BiJae]

This morning when I came in to the office several users approached me stating they could not connect to the share drives. I verified that they were not able to attach using their credentials. I restarted the server and then launched my workstation. I was able to connect using the UNC path.

To further test I logged in as another user on my workstation. This time the computer reported that the server was unavailable using the UNC path. I logged out and logged back in as me. Everything connected as expected using the UNC path.

This confuses me, the same computer will resolve for one user that's logged in but not another user that logs in just a moment later?

Yet a third oddity happened a few moments later. I was reconnecting every one to the IP address when I found that one user was able to connect to \\DATA\SHARE but not to \\DATA\USER. This made me scratch my head a little harder.

Can some one shed some light on this problem for me? As it stands now I cannot run my backups because my backup server cannot locate the DATA server.

Thank you,

http://www.bijae.net

"If the only prayer you said in
your whole life was, 'thank you,'
that would suffice."
-- Meister Eckhart

 

[ShackDaddy]

What's your environment look like? Are you a Windows shop? Are you running DNS on Windows NT, 2000 or 2003? Are there errors in the DNS log on the server (it's one of the event logs)? Are you running WINS? Are there other errors in the System log?

Sounds like the situation on the server is not static, and in addition, there is some caching of connect/mapping info on the workstations, but answer some of the earlier questions, and we can get this resolved.

ShackDaddy

 

[BiJae]

AWESOME, thanks for the reply ShackDaddy!

Yes, I'm a Microsoft shop, running three Windows 2003 servers, one with Exchange installed. (I inherited this mess and it's not static and giving me fits!) Here's what I could find in answer to your questions.

Three Windows Servers:

EX1 : running Exhange, DNS, Server 2003

DATA: Running Sever 2003

Exchng: Running Backup Exec, Server 2003

One Linux Server with a Samba Share

WEB: Samba Share, CVS

DNS LOG Entry:
The DNS server was unable to connect to the domain naming FSMO "". No modifications to Directory Partitions are possible until the FSMO server is available for LDAP connections. The event data contains the error code.

For more information, see Help and Support Center at [URL unfurl="true"]http://go.microsoft.com/fwlink/events.asp.[/URL]

The above "WARNING" appears once every twelve hours.

The FSMO server has not been available since before I started working here six months ago. I've been trying to get it siezed by DATA but it's not been successful.

WINS is configured to point to server EXCHNG

I browsed through the system logs and found several errors. I had to go back several days to see a repeating pattern. I found a dozen errors about twice a day for the past four days that had codes similar to the following:

The dynamic registration of the DNS record '81db2227-71a6-494b-bd3d-4b7de1934ee5._msdcs.tcud.state.tx.us. 600 IN CNAME tcud-EX1.tcud.state.tx.us.' failed on the following DNS server:  

DNS server IP address: 141.198.136.6 
Returned Response Code (RCODE): 5 
Returned Status Code: 9017  

For computers and users to locate this domain controller, this record must be registered in DNS.  

USER ACTION  
Determine what might have caused this failure, resolve the problem, and initiate registration of the DNS records by the domain controller. To determine what might have caused this failure, run DCDiag.exe. You can find this program on the Windows Server 2003 installation CD in Support\Tools\support.cab. To learn more about  DCDiag.exe, see Help and Support Center. To initiate registration of the DNS records by  this domain controller, run 'nltest.exe /dsregdns' from the command prompt on the domain  controller or restart Net Logon service. Nltest.exe is available in the Microsoft Windows  Server Resource Kit CD. 
  Or, you can manually add this record to DNS, but it is not recommended.  

ADDITIONAL DATA 
Error Value: DNS bad key.

The most recent and most frequent errors for today are:

The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/data.tcud.state.tx.us.  The target name used was cifs/Data. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named  machine accounts in the target realm (TCUD.STATE.TX.US), and the client realm.   Please contact your system administrator.

For more information, see Help and Support Center at [URL unfurl="true"]http://go.microsoft.com/fwlink/events.asp.[/URL]

Let me know what else I can provide! I've been searching far and wide for answers and getting close to nowhere. I appreciate your help.

http://www.bijae.net

"If the only prayer you said in
your whole life was, 'thank you,'
that would suffice."
-- Meister Eckhart

 

[ShackDaddy]

Ok, next you need to find a copy of DCDIAG (not hard to find) and run it. It will give us a lot of pertinent information about your DNS/AD environment. In the meantime, I'm going to get you some information about how to fix the FSMO problem.

ShackDaddy

 

[ShackDaddy]

Also, which servers are actually domain controllers? EX1 and DATA? Did someone do a DCPROMO on DATA in the past to remove the DC role? DCDIAG will help sort some of this out.

 

[BiJae]

Great!

I have a copy of DCDIAG and have been reading several posts on how to resolve some of the issues. However, I'm not having much success. I look forward to any assistance you can provide.

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\EX1
      Starting test: Connectivity
         The host 81db2227-71a6-494b-bd3d-4b7de1934ee5._msdcs.tcud.state.tx.us c
ould not be resolved to an
         IP address.  Check the DNS server, DHCP, server name, etc
         Although the Guid DNS name
         (81db2227-71a6-494b-bd3d-4b7de1934ee5._msdcs.tcud.state.tx.us)
         couldn't be resolved, the server name (-EX1.tcud.state.tx.us)
         resolved to the IP address (192.168.20.106) and was pingable.  Check
         that the IP address is registered correctly with the DNS server.
         ......................... EX1 failed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\EX1
      Skipping all tests, because server EX1 is
      not responding to directory service requests

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : tcud
      Starting test: CrossRefValidation
         ......................... tcud passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... tcud passed test CheckSDRefDom

   Running enterprise tests on : tcud.state.tx.us
      Starting test: Intersite
         ......................... tcud.state.tx.us passed test Intersite
      Starting test: FsmoCheck
         Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
         A Primary Domain Controller could not be located.
         The server holding the PDC role is down.
         Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
         A Time Server could not be located.
         The server holding the PDC role is down.
         Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 135
5
         A Good Time Server could not be located.
         ......................... tcud.state.tx.us failed test FsmoCheck

http://www.bijae.net

"If the only prayer you said in
your whole life was, 'thank you,'
that would suffice."
-- Meister Eckhart

 

[BiJae]

Both Data and EX1 are domain controllers. However, there are traces of servers that were DC's in the past. The server TCUD-2004 and TCUD-BDC are still listed as DC's in Active Directory. However, I've been here since March and the person I replaced cannot recall ever having seen those servers (he was only here for six months). So for at least a year now those servers have been off the network.

I've tried to delete them from AD, selecting the option saying they are no longer and will never be available again but it errors out every time.

http://www.bijae.net

"If the only prayer you said in
your whole life was, 'thank you,'
that would suffice."
-- Meister Eckhart

 

[ShackDaddy]

Check these out to get rid of those old servers. In the meantime, I'll look at your DCDIAG log.

http://www.petri.co.il/delete_failed_dcs_from_ad.htm

http://briandesmond.com/blog/archiv...-Domain-Controller-from-Active-Directory.aspx

http://support.microsoft.com/kb/216498

ShackDaddy

 

[ShackDaddy]

Go into your DNS Admin tool and open the Forward Lookup Zone for your domain. Look in the folder called:

_msdcs.tcud.state.tx.us

There should be a Alias (CNAME) record there for

81db2227-71a6-494b-bd3d-4b7de1934ee5

that points to EX1.tcud.state.tx.us

Add that entry, if it's not there, and run DCDIAG again.

ShackDaddy

 

[BiJae]

That's an affirmative on the CNAME record. It was in there. I ran the DCDIAG again:

Domain Controller Diagnosis

Performing initial setup:
   * Verifying that the local machine EX1, is a DC.
   * Connecting to directory service on server EX1.
   * Collecting site info.
   * Identifying all servers.
   * Identifying all NC cross-refs.
   * Found 3 DC(s). Testing 1 of them.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\EX1
      Starting test: Connectivity
         * Active Directory LDAP Services Check
         The host 81db2227-71a6-494b-bd3d-4b7de1934ee5._msdcs.tcud.state.tx.us c
ould not be resolved to an
         IP address.  Check the DNS server, DHCP, server name, etc
         Although the Guid DNS name
         (81db2227-71a6-494b-bd3d-4b7de1934ee5._msdcs.tcud.state.tx.us)
         couldn't be resolved, the server name (EX1.tcud.state.tx.us)
         resolved to the IP address (192.168.20.106) and was pingable.  Check
         that the IP address is registered correctly with the DNS server.
         ......................... EX1 failed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\EX1
      Skipping all tests, because server EX1 is
      not responding to directory service requests
      Test omitted by user request: Topology
      Test omitted by user request: CutoffServers
      Test omitted by user request: OutboundSecureChannels
      Test omitted by user request: VerifyReplicas
      Test omitted by user request: VerifyEnterpriseReferences

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : tcud
      Starting test: CrossRefValidation
         ......................... tcud passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... tcud passed test CheckSDRefDom

   Running enterprise tests on : tcud.state.tx.us
      Starting test: Intersite
         Skipping site Default-First-Site-Name, this site is outside the scope
         provided by the command line arguments provided.
         ......................... tcud.state.tx.us passed test Intersite
      Starting test: FsmoCheck
         GC Name: \\EX1.tcud.state.tx.us
         Locator Flags: 0xe00001bc
         Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
         A Primary Domain Controller could not be located.
         The server holding the PDC role is down.
         Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
         A Time Server could not be located.
         The server holding the PDC role is down.
         Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 135
5
         A Good Time Server could not be located.
         KDC Name: \\EX1.tcud.state.tx.us
         Locator Flags: 0xe00001bc
         ......................... tcud.state.tx.us failed test FsmoCheck

http://www.bijae.net

"If the only prayer you said in
your whole life was, 'thank you,'
that would suffice."
-- Meister Eckhart

 

[ShackDaddy]

Stop and restart your Netlogon service on DATA1 and see if things change.

 

[ShackDaddy]

And check out this article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;241505&Product=winsvr2003

Sounds like your situation.

 

[BiJae]

I'm not sure if that's my error or not. The server was configured with a static IP, we verified the host name record, and the zone was configured to receive dynamic updates (secure only). It still tells me the FSMO holder is unavailable.

Domain Controller Diagnosis

Performing initial setup:
   * Verifying that the local machine EX1, is a DC.
   * Connecting to directory service on server EX1.
   * Collecting site info.
   * Identifying all servers.
   * Identifying all NC cross-refs.
   * Found 3 DC(s). Testing 1 of them.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\EX1
      Starting test: Connectivity
         * Active Directory LDAP Services Check
         The host 81db2227-71a6-494b-bd3d-4b7de1934ee5._msdcs.tcud.state.tx.us c
ould not be resolved to an
         IP address.  Check the DNS server, DHCP, server name, etc
         Although the Guid DNS name
         (81db2227-71a6-494b-bd3d-4b7de1934ee5._msdcs.tcud.state.tx.us)
         couldn't be resolved, the server name (EX1.tcud.state.tx.us)
         resolved to the IP address (192.168.20.106) and was pingable.  Check
         that the IP address is registered correctly with the DNS server.
         ......................... EX1 failed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\EX1
      Skipping all tests, because server EX1 is
      not responding to directory service requests
      Test omitted by user request: Topology
      Test omitted by user request: CutoffServers
      Test omitted by user request: OutboundSecureChannels
      Test omitted by user request: VerifyReplicas
      Test omitted by user request: VerifyEnterpriseReferences

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : tcud
      Starting test: CrossRefValidation
         ......................... tcud passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... tcud passed test CheckSDRefDom

   Running enterprise tests on : tcud.state.tx.us
      Starting test: Intersite
         Skipping site Default-First-Site-Name, this site is outside the scope
         provided by the command line arguments provided.
         ......................... tcud.state.tx.us passed test Intersite
      Starting test: FsmoCheck
         GC Name: \\EX1.tcud.state.tx.us
         Locator Flags: 0xe00001bc
         Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
         A Primary Domain Controller could not be located.
         The server holding the PDC role is down.
         Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
         A Time Server could not be located.
         The server holding the PDC role is down.
         Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 135
5
         A Good Time Server could not be located.
         KDC Name: \\EX1.tcud.state.tx.us
         Locator Flags: 0xe00001bc
         ......................... tcud.state.tx.us failed test FsmoCheck

I restarted the netlogon on both servers. The situation remains the same.

http://www.bijae.net

"If the only prayer you said in
your whole life was, 'thank you,'
that would suffice."
-- Meister Eckhart

 

[ShackDaddy]

Have you read this article on FSMO seizure?

http://www.petri.co.il/seizing_fsmo_roles.htm

The particular role you are missing sounds like the PDC emulator.

What do you actually get as far as errors when you try to seize roles when using NTDSUTIL on EX1?

ShackDaddy

 

[BiJae]

Actually I had read that article when I first brought DATA on line. I seized all the roles to DATA. When I looked in AD on Data, it reported that it was the RID, PDC, and Infrastructure master. When I viewed the same information on EX1 it showed ERROR in the line that should have reported the server name.

Here are the errors I received when I seized the roles:

fsmo maintenance: seize rid master
Attempting safe transfer of RID FSMO before seizure.
ldap_modify_sW error 0x34(52 (Unavailable).
Ldap extended error message is 000020AF: SvcErr: DSID-0321090A, problem 5002 (UN
AVAILABLE), data 1753

Win32 error returned is 0x20af(The requested FSMO operation failed. The current
FSMO holder could not be contacted.)
)
Depending on the error code this may indicate a connection,
ldap, or role transfer error.
Transfer of RID FSMO failed, proceeding with seizure ...
Searching for highest rid pool in domain
Server "tcud-ex1" knows about 5 roles
Schema - CN=NTDS Settings,CN=DATA,CN=Servers,CN=Default-First-Site-Name,CN=Sites
,CN=Configuration,DC=tcud,DC=state,DC=tx,DC=us
Domain - CN=NTDS Settings,CN=TCUD-EX1,CN=Servers,CN=Default-First-Site-Name,CN=S
ites,CN=Configuration,DC=tcud,DC=state,DC=tx,DC=us
PDC - CN=NTDS Settings,CN=TCUD-EX1,CN=Servers,CN=Default-First-Site-Name,CN=Site
s,CN=Configuration,DC=tcud,DC=state,DC=tx,DC=us
RID - CN=NTDS Settings,CN=TCUD-EX1,CN=Servers,CN=Default-First-Site-Name,CN=Site
s,CN=Configuration,DC=tcud,DC=state,DC=tx,DC=us
Infrastructure - CN=NTDS Settings,CN=TCUD-EX1,CN=Servers,CN=Default-First-Site-N
ame,CN=Sites,CN=Configuration,DC=tcud,DC=state,DC=tx,DC=us

and

fsmo maintenance: seize infrastructure master
Attempting safe transfer of infrastructure FSMO before seizure.
ldap_modify_sW error 0x34(52 (Unavailable).
Ldap extended error message is 000020AF: SvcErr: DSID-0321034A, problem 5002 (UN
AVAILABLE), data 8

Win32 error returned is 0x20af(The requested FSMO operation failed. The current
FSMO holder could not be contacted.)
)
Depending on the error code this may indicate a connection,
ldap, or role transfer error.
Transfer of infrastructure FSMO failed, proceeding with seizure ...
Server "tcud-ex1" knows about 5 roles
Schema - CN=NTDS Settings,CN=DATA,CN=Servers,CN=Default-First-Site-Name,CN=Sites
,CN=Configuration,DC=tcud,DC=state,DC=tx,DC=us
Domain - CN=NTDS Settings,CN=TCUD-EX1,CN=Servers,CN=Default-First-Site-Name,CN=S
ites,CN=Configuration,DC=tcud,DC=state,DC=tx,DC=us
PDC - CN=NTDS Settings,CN=DATA,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN
=Configuration,DC=tcud,DC=state,DC=tx,DC=us
RID - CN=NTDS Settings,CN=DATA,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN
=Configuration,DC=tcud,DC=state,DC=tx,DC=us
Infrastructure - CN=NTDS Settings,CN=TCUD-EX1,CN=Servers,CN=Default-First-Site-N
ame,CN=Sites,CN=Configuration,DC=tcud,DC=state,DC=tx,DC=us
fsmo maintenance: seize pdc
Attempting safe transfer of PDC FSMO before seizure.
ldap_modify_sW error 0x34(52 (Unavailable).
Ldap extended error message is 000020AF: SvcErr: DSID-032104F9, problem 5002 (UN
AVAILABLE), data 1753

Win32 error returned is 0x20af(The requested FSMO operation failed. The current
FSMO holder could not be contacted.)
)
Depending on the error code this may indicate a connection,
ldap, or role transfer error.
Transfer of PDC FSMO failed, proceeding with seizure ...
Server "tcud-ex1" knows about 5 roles
Schema - CN=NTDS Settings,CN=DATA,CN=Servers,CN=Default-First-Site-Name,CN=Sites
,CN=Configuration,DC=tcud,DC=state,DC=tx,DC=us
Domain - CN=NTDS Settings,CN=TCUD-EX1,CN=Servers,CN=Default-First-Site-Name,CN=S
ites,CN=Configuration,DC=tcud,DC=state,DC=tx,DC=us
PDC - CN=NTDS Settings,CN=TCUD-EX1,CN=Servers,CN=Default-First-Site-Name,CN=Site
s,CN=Configuration,DC=tcud,DC=state,DC=tx,DC=us
RID - CN=NTDS Settings,CN=DATA,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN
=Configuration,DC=tcud,DC=state,DC=tx,DC=us
Infrastructure - CN=NTDS Settings,CN=TCUD-EX1,CN=Servers,CN=Default-First-Site-N
ame,CN=Sites,CN=Configuration,DC=tcud,DC=state,DC=tx,DC=us

http://www.bijae.net

"If the only prayer you said in
your whole life was, 'thank you,'
that would suffice."
-- Meister Eckhart

 

[ShackDaddy]

Are both servers set to be Global Catalog servers? I'd make the one that doesn't own the roles be the GC. If you only had one system, I'd suggest a restore of System State, but we have to work this out through the config since you have multiple DCs.

I'm even wondering about trying to seize all roles with DATA, DCPROMO on EX1 to remove DC role, then sort out the problems with ghost DCs just on DATA, then once things look good, doing another DCPROMO on EXCHANGE to bring another DC online. I assume EXCHANGE doesn't currently have Exchange running on it.

One thing I'll tell you though, running Exchange on a DC will cause you trouble, so you might want to have DATA be your only DC, or make the other non-Exchange server an additional DC.

To resolve the client resolution issues, you might want to install DNS service on DATA and make your DNS AD-integrated. Then point your clients at DATA. If data is holding all the roles, then the errors you are getting about not being able to resolve EX1 related records might not be an issue and you can DCPROMO EX1 and have it stop being a DC.

ShackDaddy

 

[ShackDaddy]

Oh, I forgot to tell you, if your DNS is currently AD-integrated, you could undo that, so that when you DCPROMO EX1 out of the DC role, it could continue to serve out DNS to your clients from a regular zone file.

 

[BiJae]

I installed DNS on DATA, choosing the option to integrate to AD. I received an error when I named the zone. It said the zone was already created and it couldn't be created again. When the DNS console came up I could see all my computers in the network listed.

EX1 has exchange running on it and is our only mail server. It also hosts the current DNS Configuration. I did not remove that DNS prior to installing it on DATA because it's a production server and people are using it at this time. I may have to come in this weekend and do my testing on this.

I was told in another post (

http://www.tek-tips.com/viewthread.cfm?qid=1300174&page=1

) that a server running Exchange could not be demoted or promoted. So I have not attempted to run DCPROMO on EX1 for fear of destroying my e-mail server.

Should I, at this point, uninstall DNS from DATA. Then Uninstall DNS from EX1. After both are gone install DNS on DATA. We have a small network as such I chose FORWARD lookup zones only. I did not choose forward and reverse. Is this the correct installation?

http://www.bijae.net

"If the only prayer you said in
your whole life was, 'thank you,'
that would suffice."
-- Meister Eckhart

 

[BiJae]

EX1 seized the roles properly. Both Data and Ex1 are showing EX1 as the primary domain controller when I view them in AD.

http://www.bijae.net

"If the only prayer you said in
your whole life was, 'thank you,'
that would suffice."
-- Meister Eckhart

 

[BiJae]

I did a couple more tests to see the extent of the problem. It appears that the only way to not find the computer is using the windows explorer. I have a web application that is hosted on that computer. I used internet explorer to lookup the sever

http://data.tcud.state.tx.us

and it found it no problem. When I perform a NSLOOKUP for data it reports back the correct address.

I ran some NDS logs on EX1. I see the following activity on the IP address assigned to DATA:

11/21/2006	9:03:26	B3C	PACKET	UDP	Rcv	192.168.20.100	714		Q	[0001	D	NOERROR]	(4)data(4)tcud(5)state(2)tx(2)us(0)
11/21/2006	9:03:26	B3C	PACKET	UDP	Snd	192.168.20.100	714	R	Q	[8085	A DR	NOERROR]	(4)data(4)tcud(5)state(2)tx(2)us(0)
11/21/2006	9:03:26	B3C	PACKET	UDP	Rcv	192.168.20.100	6b13		Q	[0001	D	NOERROR]	(4)tcud(5)state(2)tx(2)us(0)
11/21/2006	9:03:26	B3C	PACKET	UDP	Snd	192.168.20.100	6b13	R	Q	[8085	A DR	NOERROR]	(4)tcud(5)state(2)tx(2)us(0)
11/21/2006	9:03:26	B3C	PACKET	UDP	Rcv	192.168.20.100	7d10		Q	[0001	D	NOERROR]	(4)tcud(5)state(2)tx(2)us(0)
11/21/2006	9:03:26	B3C	PACKET	UDP	Snd	192.168.20.100	7d10	R	Q	[8085	A DR	NOERROR]	(4)tcud(5)state(2)tx(2)us(0)
11/21/2006	9:03:26	B3C	PACKET	UDP	Rcv	192.168.20.100	dd10		U	[0028		NOERROR]	(4)tcud(5)state(2)tx(2)us(0)
11/21/2006	9:03:26	33C	PACKET	UDP	Snd	192.168.20.100	dd10	R	U	[00a8		NOERROR]	(4)tcud(5)state(2)tx(2)us(0)
11/21/2006	9:05:08	B3C	PACKET	UDP	Rcv	192.168.20.100	322b		Q	[0001	D	NOERROR]	(5)_ldap(4)_tcp(3)pdc(6)_msdcs(4)tcud(5)state(2)tx(2)us(0)
11/21/2006	9:05:08	B3C	PACKET	UDP	Snd	192.168.20.100	322b	R	Q	[8385	A DR	NXDOMAIN]	(5)_ldap(4)_tcp(3)pdc(6)_msdcs(4)tcud(5)state(2)tx(2)us(0)
11/21/2006	9:10:20	B3C	PACKET	UDP	Rcv	192.168.20.100	e454		Q	[0001	D	NOERROR]	(36)93293e7e-61c6-4aee-b605-cc3835ad0aa9(6)_msdcs(4)tcud(5)state(2)tx(2)us(0)
11/21/2006	9:10:20	B3C	PACKET	UDP	Snd	192.168.20.100	e454	R	Q	[8385	A DR	NXDOMAIN]	(36)93293e7e-61c6-4aee-b605-cc3835ad0aa9(6)_msdcs(4)tcud(5)state(2)tx(2)us(0)
11/21/2006	9:10:20	B3C	PACKET	UDP	Rcv	192.168.20.100	5c5a		Q	[0001	D	NOERROR]	(36)93293e7e-61c6-4aee-b605-cc3835ad0aa9(6)_msdcs(4)tcud(5)state(2)tx(2)us(0)
11/21/2006	9:10:20	B3C	PACKET	UDP	Snd	192.168.20.100	5c5a	R	Q	[8385	A DR	NXDOMAIN]	(36)93293e7e-61c6-4aee-b605-cc3835ad0aa9(6)_msdcs(4)tcud(5)state(2)tx(2)us(0)
11/21/2006	9:10:20	B3C	PACKET	UDP	Rcv	192.168.20.100	355b		Q	[0001	D	NOERROR]	(9)tcud-data(4)tcud(5)state(2)tx(2)us(0)
11/21/2006	9:10:20	B3C	PACKET	UDP	Snd	192.168.20.100	355b	R	Q	[8085	A DR	NOERROR]	(9)tcud-data(4)tcud(5)state(2)tx(2)us(0)
11/21/2006	9:10:20	B3C	PACKET	UDP	Rcv	192.168.20.100	bf58		Q	[0001	D	NOERROR]	(36)93293e7e-61c6-4aee-b605-cc3835ad0aa9(6)_msdcs(4)tcud(5)state(2)tx(2)us(0)
11/21/2006	9:10:20	B3C	PACKET	UDP	Snd	192.168.20.100	bf58	R	Q	[8385	A DR	NXDOMAIN]	(36)93293e7e-61c6-4aee-b605-cc3835ad0aa9(6)_msdcs(4)tcud(5)state(2)tx(2)us(0)
11/21/2006	9:17:26	B3C	PACKET	UDP	Rcv	192.168.20.100	4424		Q	[0001	D	NOERROR]	(5)_ldap(4)_tcp(3)pdc(6)_msdcs(4)tcud(5)state(2)tx(2)us(0)
11/21/2006	9:17:26	B3C	PACKET	UDP	Snd	192.168.20.100	4424	R	Q	[8385	A DR	NXDOMAIN]	(5)_ldap(4)_tcp(3)pdc(6)_msdcs(4)tcud(5)state(2)tx(2)us(0)

I was looking around the DNS Zones on Ex1 to see if I could find anything odd. There was something that I thought might be causing an issue. Under _msdcs there are two entries for DATA.

91de8727-9580-44db-b90b-5d1798b45451
and
9287acbf-8738-4b71-9d99-86ede63c6078

Should there be two entries for DATA on in the _msdcs?

I found that there were several entries for the old servers under the folder _sites/default..../ There are three _gc records, 6 _keberos records, and 6 _ldap records. Is it safe to remove the references to the computers that no longer live on the network?

http://www.bijae.net

"If the only prayer you said in
your whole life was, 'thank you,'
that would suffice."
-- Meister Eckhart