cybercrusader2000

Hello. I have been working around a single-label dns domain problem in my network and I came across this MS KB article that suggests to make registry changes to enable dynamic dns registrations incase of single-label dns domains. The link is : http://support.microsoft.com/?kbid=300684 . Could someone tell me, the type of the value mentioned in there for "UpdateTopLevelDomainZones" and "AllowSingleLabelDnsDomain" are REG_DWORD , REG_SZ or REG_BINARY . The value support by the registry entry is "0x1" which is only accepted by REG_SZ. Please reconfirm. Thanks. Regards, C|C

Ummm, I made some changes to the connection strings in Active Directory Sites and Services and now replication is taking place. Also, AD Replication Monitor states that last replication attempt was successfull. But, I am still facing some errors in the event log. I will list them in a while. Untill then, take care guys.

Ok. I will check that as well and revert back.

Yeah, I am sure that the rest of the 3 network adapters are in disabled state. The Master Browser errors are due to the presence of Windows XP clients having the Computer Browser service running. Those can be disabled whenever required. Also, I don't think this is related to the replication failure error.

DC01 = Single Adapter ( Single IP - Internal IP ) DC02 = 4 Adapters ( 1 Active , 3 Disabled , Single IP - Internal IP )

Hi guys, I am facing this problem with Active Directory not replicating between the DC and the ADC in my Domain. The domain name is a single-label domain name with no extensions ("."). The following are the errors from Event Log. =========== SysLog :- NETLOGON Warning None 5781 N/A DC01 Dynamic registration or deregistration of one or more DNS records failed because no DNS servers are available. w32time Warning None 64 N/A DC01 "Because of repeated network problems, the time service has not been able to find a domain controller to synchronize with for a long time. To reduce network traffic, the time service will wait 960 minutes before trying again. No synchronization will take place during this interval, even if network connectivity is restored. Accumulated time errors may cause certain network operations to fail. To tell the time service that network connectivity has been restored and that it should resynchronize, execute ""w32tm /s"" from the command line. " w32time Error None 62 N/A DC01 This Machine is a PDC of the domain at the root of the forest. Configure to sync from External time source using the net command, 'net time /setsntp:<server name>'. MRxSmb Error None 8003 N/A DC01 The master browser has received a server announcement from the computer COMPUTER that believes that it is the master browser for the domain on transport NetBT_Tcpip_{15676B6E-58D3. The master browser is stopping or an election is being forced. File Replication Log :- NtFrs Warning None 13562 N/A DC01 Following is the summary of warnings and errors encountered by File Replication Service while polling the Domain Controller dc01.domain for FRS replica set configuration information. The nTDSConnection object cn=dc01,cn=ntds settings,cn=dc02,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=domain is conflicting with cn=\<automatically generated\>,cn=ntds settings,cn=dc02,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=domain. Using cn=dc01,cn=ntds settings,cn=dc02,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=domain The nTDSConnection object cn=dc02,cn=ntds settings,cn=dc01,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=domain is conflicting with cn=8aa06a8d-c60a-4ccf-8240-99808ebcd538,cn=ntds settings,cn=dc01,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=domain. Using cn=dc02,cn=ntds settings,cn=dc01,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=domain Directory Service Log :- NTDS KCC Warning (1) 1265 N/A DC01 The attempt to establish a replication link with parameters Partition: CN=Schema,CN=Configuration,DC=domain Source DSA DN: CN=NTDS Settings,CN=DC02,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain Source DSA Address: 26bffa7d-fba6-456b-bd2c-ad5cafc67545._msdcs.domain Inter-site Transport (if any): failed with the following status: The DSA operation is unable to proceed because of a DNS lookup failure. The record data is the status code. This operation will be retried. ================= The SysVol and NetLogon folders on DC02 are blank, that shows that there is no replication. If compared, DC01 & DC02, under Active Directory Sites and Services, DC02 seems to be somewhat missing parameters. I can successfully ping DC01 from DC02 and vise-versa using IP , NetBIOS & DNS name. Forward and reverse DNS seem to work while communicating between the 2 DCs. But, AD zones under the Forward Lookup Zones in the AD-integrated DNS ( the dns residing on DC01 , there is no DNS/DHCP on DC02 , DC01 has DHCP running too ) for example _msdc , _sites , _tcp , _udp , etc. are missing. DHCP is integrated with DNS but DNS records don't get updated in Forward Lookup Zone. However, they get updated in Reverser Lookup Zone. I wonder how they get created when there is no Forward Lookup entry created ( host A record ) for the PTR record in Reverse DNS. I ran Netdiag /fix and i get a dns lookup error. DcDiag gives an error. "DC01 failed test kccevent". Connectivity test results via DcDiag test gave the following error : DcDiag Test :- Testing server: Default-First-Site-Name\DC01 Starting test: Connectivity 14067e65-e6e5-45a9-bbc0-e8c781409a0a._msdcs.domain's server GUID DNS name could not be resolved to an IP address. Check the DNS server, DHCP, server name, etc Although the Guid DNS name (14067e65-e6e5-45a9-bbc0-e8c781409a0a._msdcs.domain) couldn't be resolved, the server name (dc01.domain) resolved to the IP address (192.168.0.2) and was pingable. Check that the IP address is registered correctly with the DNS server. ......................... DC01 failed test Connectivity ================= Thats all I can remember as of now. I have followed a few articles : http://support.microsoft.com/default.aspx?...kb;en-us;300684 http://support.microsoft.com/?kbid=193888 ( tried this but the reg entry showed invalid charectors after modification, so I reset it back ) I understand that all this seems to be due to a invalid/corrupt dns server running. I have thought of demoting DC02, rectifying DNS on DC01 and the promoting DC02 back to the domain ( after freshly installing the OS and updating it on DC02 ). As for the changes described on MS KB 300684 , I need to know, do we make the changes in the workstations only or also in the server ( as I have done, after testing the changes in the client ) , and what other changes have to be made in the client / server incase of a single-label domain name based domain to function properly ? Any / all suggestions are welcomed.

Well lets hope someone shoots a valid solution which will help resolve my problem. Otherwise, i guess i have to contact MS support. Anyways, thanks for for your effort guys. I apprieciate it.

Ok, first of all, I believe its not an OEM version because the license doesn't state as OEM in it. Secondly, this MSDN copy was not bundled with any machine, it comes from the MSDN pack which includes all other versions of software. So this CD is not machine dependent. Thirdly, I have tried this CD in 2 different environments, 1. a branded pc which has an included version of windows xp with it ( which I don't use to install the OS ), 2. a virtual machine in my system's environment ( which is an assembled machine ). In both the cases, no matter whether its a real machine or a virtual machine, the software never asked for activation untill I tried slipstreaming SP-2 in it. And, after slipstreaming, I have only tested it on my virtual machine by mounting the image onto a virtual cd drive, so that only once its tested to be working as OK, I can burn the image onto a CD for future deployment. By this I mean that it never asked for activation no matter whether I used a mounted images ( with no SP-2 ) to install it on a virtual machine, or installed the OS directly from the CD ( again with no SP-2 ) on a real machine.

Source : NETLOGON Type : Warning Category : None Event ID : 5781 User : N/A Computer : SERVER Description : Dynamic registration or deregistration of one or more DNS records failed because no DNS servers are available. MS KB Link : http://support.microsoft.com/default.aspx?...kb;en-us;300684 ==================== I just need to know as to where the modifications need to be made ... if you scroll down on the MS KB link, you would see a few steps of troubleshooting defined. Do I do that on the domain controller or on the Windows XP client machine ?

Well, I just checked for the type of license and noticed that it doesn't have OEM in it. It has a number like XXXXX-327-XXXXXXX-XXXXX . Also, this is a MSDN version which I believe should be preactivated. Please suggest.

Maybe this will help you. 1. Take a backup of your registry. 2. Change the reg values for 'SourcePath' and 'ServicePackSourcePath' at the location 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\' to a folder on your 'C:\' drive for example 'C:\BackUp\' . Also do the same for 'SourcePath' at the location 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\' . Just this time make it 'C:\BackUp\I386\' . 3. Next copy all the contents of your Windows XP CD onto the folder. Verify the path 'C:\BackUp\I386\' to make sure it contains all the files that are within '<CD Drive>:\I386\' . 4. Download Windows XP Service Pack 2 from the location below : http://download.microsoft.com/download/1/6...935-SP2-ENU.exe Save the file at 'C:\' . 5. Open a command prompt. Go to 'C:\' . Type 'C:\WindowsXP-KB835935-SP2-ENU.exe /s:C:\BackUp\' without the quotes. This will Slipstream Windows XP with the latest service pack i.e. Service Pack 2 ( which you had downloaded previously ). 6. Once integrating the service pack is over, restart the machine so that the changes that you have made to the registry will be reflected. 7. Try reinstalling IE.

Hi, I followed the Windows XP SP-2 Slipstreaming process and it worked fine. I tried out 3 procedures : 1. Simple unattended Windows XP Professional setup - Worked Fine. 2. Windows XP unattended setup with Slipstreaming SP-2 - Process worked fine but after installation its asking for activating windows although the original CD is pre-activated ( legal ) version hopefully OEM or VLK ( not sure which of the two ). 3. Windows XP unattended setup with Slipstreaming SP-2 and also Slipstreaming hotfixes - slipstreaming hotfixes didn't work well, probably I didn't use the correct procedure for it ( maybe someone can provide me with detailed information for slipstreaming hotfixes after slipstreaming SP-2 ). My query as of now is regarding procedure 2 . After installing the slipstreamed version of windows xp on a test virtual machine in my box, the procedure ran fine as expected but after installation it asked to activate windows which I believe shouldn't do because this is a preactivated version of windows xp ( atleast it doesn't ask for activation if we install from the original cd using the same cd ). Details of the WINNT.SIF file are as below ( NOTE : Some options are changed for confidentiality reasons ) : ================= ;SetupMgrTag [Data] MsDosInitiated="0" UnattendedInstall="Yes" [unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=No TargetPath=\WINDOWS [GuiUnattended] AdminPassword=* EncryptedAdminPassword=No OEMSkipRegional=1 TimeZone=XXX OemSkipWelcome=1 [userData] ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX FullName="localhost" OrgName="localhost" ComputerName=localhost [TapiLocation] CountryCode=XXX Dialing=Tone [identification] JoinWorkgroup=WORKGROUP [Networking] InstallDefaultComponents=No [NetAdapters] Adapter1=params.Adapter1 [params.Adapter1] INFID=* [NetClients] MS_MSClient=params.MS_MSClient [NetServices] MS_SERVER=params.MS_SERVER [NetProtocols] MS_TCPIP=params.MS_TCPIP MS_NetBEUI=params.MS_NetBEUI [params.MS_TCPIP] DNS=Yes UseDomainNameDevolution=No EnableLMHosts=Yes AdapterSections=params.MS_TCPIP.Adapter1 [params.MS_TCPIP.Adapter1] SpecificTo=Adapter1 DHCP=Yes WINS=No NetBIOSOptions=0 ==================