Duplicate Domain Profile Name (company.local 2)

I have a single server running Server 2008 R2 configured with AD DS and DNS.     Recently I noticed that sometimes the domain name in Network Connections list will be appended with the number 2.  At reboot the server will randomly boot to “company.local” or “company.local 2”.  

The problem has extended to the workstations where they will list either “company.local” or “company.local 2”.   If the server profile does not match the client profile I will have DNS issues.

I did a registry search on the server and found “company.local 2” at the following locations:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Wpad (WpadNetworkName)

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles (ProfileName)

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Signatures\Managed (Description), (FirstNetwork)

Is removing the duplicate profiles from the registry the proper way of correcting this issue or is there a deeper problem with my AD DS and/or DNS?
rpmapsAsked:
Who is Participating?
 
rpmapsAuthor Commented:
Thanks for all of the input and guidance.   It seems that removing the duplicate profile under network list in the registry has done the trick.  It has been almost a week and all seems to be running smoothly.
0
 
Guy LidbetterCommented:
That's really odd... it's kind of like you have two domains of the same name space on the same network.

Shot in the dark....

This could happen if in a DC Promo of a new DC was done incorrectly and the new server thinks it's the first DC, you end up with two domains.
As they have the same namespace's DNS would go whacky.

If this is the case...  the above would only be a temporary fix. I would be more interested in how these values got populated like that in the first place before I look into fixing the issue.
0
 
rpmapsAuthor Commented:
Under the Active Directory Domains & Trusts I am only showing the original domain.  Would it be advisable to remove the active directory through DC Promo, then reinstall?   What would be the proper steps?
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Guy LidbetterCommented:
Run this
netdom query dc

Open in new window

and see if all the DC's appear in the list.
0
 
rpmapsAuthor Commented:
I only have one DC and it is correctly listed.
0
 
compdigit44Commented:
can you upload the results of dcdiag /v /e
0
 
rpmapsAuthor Commented:
Attached is the results of the dcdiag.   PLEASE NOTE:   Yesterday I went through the registry and under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles and HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Signatures\Managed I removed the inactive "company.local" profiles.  Under the active profiles I renamed the instances of "company.local 2" to "company.local".    Before I deleted the inactive profile I noted that the DateCreated and DateLastConnected were both just minutes apart in June 2014 when the server was first placed into service which leads me to believe that it may have been some type of error during dcpromo.
dcdiag.txt
0
 
compdigit44Commented:
I am seeing the following error in the dcdiag log...


Starting test: DFSREvent
         The DFS Replication Event Log.
         There are warning or error events within the last 24 hours after the
         SYSVOL has been shared.  Failing SYSVOL replication problems may cause
         Group Policy problems.
         A warning event occurred.  EventID: 0x800008A4
            Time Generated: 03/07/2015   23:39:49
            Event String:
            The DFS Replication service has detected an unexpected shutdown on v
olume D:. This can occur if the service terminated abnormally (due to a power lo
ss, for example) or an error occurred on the volume. The service has automatical
ly initiated a recovery process. The service will rebuild the database if it det
ermines it cannot reliably recover. No user action is require


This is usually a sign of replication problems... Usually you would take the problem DC demoto it then promoto it to correct the issue
0
 
rpmapsAuthor Commented:
I will run dcpromo to demote the DC then rerun it to promote it back.  I won't be able to do this till Wednesday evening but I will report back.    THanks
0
 
compdigit44Commented:
good luck.......
0
 
rpmapsAuthor Commented:
Before going through the process of demoting and promoting the DC, I reran the dcdiag /v /e command.   I have attached the results which do not show any errors.
0
 
rpmapsAuthor Commented:
0
 
compdigit44Commented:
Yes, your DCdiag log does look clean
0
 
compdigit44Commented:
Thanks good to know... I still would like to understand why is even happen in the first place
0
 
rpmapsAuthor Commented:
I too would love to know why it happened even if only to prevent it from happening again.   I have been monitoring it and so far no return of the (2) on the server or any clients.  As you stated earlier it may have been a corruption during the dcpromo.    Either way it is not worth it for me to try to recreate it since everything is running smoothly ("If it ain't broke, don't fix it" seems to apply to this one)
0
 
Seth SimmonsSr. Systems AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.