[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 579
  • Last Modified:

PC name clash with Domain Controller

Guys, we had a MAC on the network with the same name as our server. How?..Don't know. We took it off the network.However, it has taken our network down. We want to be able to resolve this issue without having to restart the DC. Is this possible at all, it's really urgent and any help would be great guys.

Thanks
0
Yashy
Asked:
Yashy
  • 13
  • 8
  • 5
2 Solutions
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Look for server name in ADUC (Computers container) and delete it make sure its the MAC system .... also verify the DNS with Host and PTR entry for that Client machine name and remove them
0
 
YashyAuthor Commented:
I have done this and we restarted the DC. Howver, we can't get the actual Exchange services to start either now (DC and Exchange sit on the same server...sadly). The actual Domain Controller is somehow not recognising itself? If that sounds correct?

We are logged on, but for example in AD we can't search for anyone. It returns an error. It's as though the domain controller can't see anything. We can ping it, it can ping other machines but it's messed up bad and we're talking a big business here that's about to go down....

Please guys, your help will be much appreciate.
0
 
Darius GhassemCommented:
On the server run ipconfig /flushdns, ipconfig /registerdns, and dcdiag /fix. Make sure this process creates record in DNS for this server including SRV and A. Post dcdiag.


I have had to fully demote a DC after someone name a PC the same name.
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Ohk so we are done and its just the services dont start .... try starting the System Attendant and see the event viewer App logs and give me the errorID with source as "MSExchangeSA"
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
SO you can open and go through Active Directory Users and Computers without any issues ??
Dcdiag /fix
Netdiag /fix
Check in the services console if the following services are started Netlogon, Remote Registry, KDC, FRS, DFS
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Also run the following commands and  and post the comments
netdiag /v
dcdiag /v
0
 
YashyAuthor Commented:
I am about to post guys in a moment. Just a quick thing, when we ping our main server it resolves to an external Ip address?!! So our domain controller is for example Yash.com. The DC name is called Matches01. However, when we do a ping on Matches01.Yash.com, we get an external Ip address coming up of 216.246.74.34. Also, we have found that there is another machine that is called 'CIFS' which is on our domain and resolves to that exact same external Ip address.

This is the result from the netgiag /v

    Bind Name: NdisWan
    Binding Paths:
        Owner of the binding path : Remote Access NDIS WAN Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiscowan
            Upper Component: Remote Access NDIS WAN Driver
            Lower Component: Direct Parallel

        Owner of the binding path : Remote Access NDIS WAN Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiswan
            Upper Component: Remote Access NDIS WAN Driver
            Lower Component: WAN Miniport (PPPOE)

        Owner of the binding path : Remote Access NDIS WAN Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiswan
            Upper Component: Remote Access NDIS WAN Driver
            Lower Component: WAN Miniport (PPTP)

        Owner of the binding path : Remote Access NDIS WAN Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiscowan
            Upper Component: Remote Access NDIS WAN Driver
            Lower Component: WAN Miniport (L2TP)

        Owner of the binding path : Remote Access NDIS WAN Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiswanasync
            Upper Component: Remote Access NDIS WAN Driver
            Lower Component: RAS Async Adapter


    Component Name : Message-oriented TCP/IP Protocol (SMB session)
    Bind Name: NetbiosSmb
    Binding Paths:

    Component Name : WINS Client(TCP/IP) Protocol
    Bind Name: NetBT
    Binding Paths:
        Owner of the binding path : WINS Client(TCP/IP) Protocol
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndis5
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: BCM5703 Gigabit Ethernet

        Owner of the binding path : WINS Client(TCP/IP) Protocol
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndiswanip
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: WAN Miniport (IP)


    Component Name : Internet Protocol (TCP/IP)
    Bind Name: Tcpip
    Binding Paths:
        Owner of the binding path : Internet Protocol (TCP/IP)
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndis5
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: BCM5703 Gigabit Ethernet

        Owner of the binding path : Internet Protocol (TCP/IP)
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiswanip
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: WAN Miniport (IP)


    Component Name : Client for Microsoft Networks
    Bind Name: LanmanWorkstation
    Binding Paths:
        Owner of the binding path : Client for Microsoft Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios_smb
            Upper Component: Client for Microsoft Networks
            Lower Component: Message-oriented TCP/IP Protocol (SMB session)

        Owner of the binding path : Client for Microsoft Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: Client for Microsoft Networks
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndis5
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: BCM5703 Gigabit Ethernet

        Owner of the binding path : Client for Microsoft Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: Client for Microsoft Networks
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndiswanip
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: WAN Miniport (IP)


    Component Name : WebClient
    Bind Name: WebClient
    Binding Paths:

    Component Name : Symantec Endpoint Protection Firewall
    Bind Name: Teefer2
    Binding Paths:
        Owner of the binding path : Symantec Endpoint Protection Firewall
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndis5
            Upper Component: Symantec Endpoint Protection Firewall
            Lower Component: BCM5703 Gigabit Ethernet

        Owner of the binding path : Symantec Endpoint Protection Firewall
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiswanip
            Upper Component: Symantec Endpoint Protection Firewall
            Lower Component: WAN Miniport (IP)


    Component Name : DHCP Server
    Bind Name: DHCPServer
    Binding Paths:

    Component Name : Wireless Configuration
    Bind Name: wzcsvc
    Binding Paths:

    Component Name : Network Load Balancing
    Bind Name: Wlbs
    Binding Paths:
        Owner of the binding path : Network Load Balancing
        Binding Enabled: No
    Interfaces of the binding path:
        -Interface Name: ndis5
            Upper Component: Network Load Balancing
            Lower Component: BCM5703 Gigabit Ethernet


    Component Name : Steelhead
    Bind Name: RemoteAccess
    Binding Paths:

    Component Name : Dial-Up Server
    Bind Name: msrassrv
    Binding Paths:

    Component Name : Remote Access Connection Manager
    Bind Name: RasMan
    Binding Paths:

    Component Name : Dial-Up Client
    Bind Name: msrascli
    Binding Paths:

    Component Name : File and Printer Sharing for Microsoft Networks
    Bind Name: LanmanServer
    Binding Paths:
        Owner of the binding path : File and Printer Sharing for Microsoft Netwo
rks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios_smb
            Upper Component: File and Printer Sharing for Microsoft Networks
            Lower Component: Message-oriented TCP/IP Protocol (SMB session)

        Owner of the binding path : File and Printer Sharing for Microsoft Netwo
rks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: File and Printer Sharing for Microsoft Networks
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndis5
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: BCM5703 Gigabit Ethernet

        Owner of the binding path : File and Printer Sharing for Microsoft Netwo
rks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: File and Printer Sharing for Microsoft Networks
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndiswanip
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: WAN Miniport (IP)


    Component Name : NetBIOS Interface
    Bind Name: NetBIOS
    Binding Paths:
        Owner of the binding path : NetBIOS Interface
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: NetBIOS Interface
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndis5
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: BCM5703 Gigabit Ethernet

        Owner of the binding path : NetBIOS Interface
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: NetBIOS Interface
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndiswanip
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: WAN Miniport (IP)


    Component Name : Generic Packet Classifier
    Bind Name: Gpc
    Binding Paths:

    Component Name : Application Layer Gateway
    Bind Name: ALG
    Binding Paths:

    Component Name : WAN Miniport (IP)
    Bind Name: NdisWanIp
    Binding Paths:

    Component Name : Direct Parallel
    Bind Name: {AD10C987-BC05-43F9-8AB0-FD72A56873F5}
    Binding Paths:

    Component Name : WAN Miniport (PPPOE)
    Bind Name: {93384A05-13CC-49D6-9C96-9CD07F38B440}
    Binding Paths:

    Component Name : WAN Miniport (PPTP)
    Bind Name: {A911C60C-B9B6-4227-961C-8B65F06AB648}
    Binding Paths:

    Component Name : WAN Miniport (L2TP)
    Bind Name: {ABD20A0E-B8FB-472C-A641-3644DFB15830}
    Binding Paths:

    Component Name : RAS Async Adapter
    Bind Name: {0E351486-BC65-43FC-BF51-D6EFF5EF042B}
    Binding Paths:

    Component Name : BCM5703 Gigabit Ethernet
    Bind Name: {1F507EB0-EE57-4C1F-BEB7-4482C99A9C60}
    Binding Paths:



WAN configuration test . . . . . . : Skipped
    No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

    Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully

C:\>
0
 
YashyAuthor Commented:
Please note that the machine CIFS that I mentioned is not on our network. It does not resolve to an internal Ip address at all, but ONLY external.

Also guys, our DNS is completely lost. There are no forward lookup zones or reverse lookup zones.
But, we can browse through AD no problem.

Also, in the event viewer this is one of the errors for DNS:

"the dns server was unable to open active directory. This DNS server is configured to obtain and use information from the ....."
0
 
YashyAuthor Commented:
Okay, we have realised that the external IP address problem is because we're currently not running any DNS.

What is the fastest way to rebuild the DNS again? Or maybe delete and re-add?
0
 
YashyAuthor Commented:
Guys, here is the NETDIAG /FIX:


C:\>netdiag/fix

.....................................

    Computer Name: MATCHES01
    DNS Host Name: matches01.matches.com
    System info : Microsoft Windows Server 2003 R2 (Build 3790)
    Processor : x86 Family 15 Model 6 Stepping 4, GenuineIntel
    List of installed hotfixes :
        KB921503
        KB925398_WMP64
        KB925902
        KB926122
        KB927891
        KB928090-IE7
        KB929123
        KB929969
        KB930178
        KB931784
        KB931836
        KB932168
        KB933360
        KB933566-IE7
        KB933729
        KB933854
        KB935839
        KB935840
        KB935966
        KB936021
        KB936357
        KB936782
        KB938464-v2
        KB939653-IE7
        KB941202
        KB941569
        KB941672
        KB942830
        KB942831
        KB943055
        KB943460
        KB944653
        KB945553
        KB946026
        KB949014
        KB950760
        KB950762
        KB950974
        KB951066
        KB951748
        KB952004
        KB952069
        KB952954
        KB954600
        KB955069
        KB955839
        KB956572
        KB956802
        KB956803
        KB957097
        KB958644
        KB958687
        KB958690
        KB959426
        KB960225
        KB960803
        KB961063
        KB961064
        KB961373
        KB963027-IE7
        KB967715
        Q147222


Netcard queries test . . . . . . . : Passed



Per interface results:

    Adapter : Local Area Connection

        Netcard queries test . . . : Passed

        Host Name. . . . . . . . . : matches01
        IP Address . . . . . . . . : 10.0.0.2
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 10.0.0.253
        Dns Servers. . . . . . . . : 10.0.0.2


        AutoConfiguration results. . . . . . : Passed

        Default gateway test . . . : Passed

        NetBT name test. . . . . . : Passed
        [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge
r Service', <20> 'WINS' names is missing.

        WINS service test. . . . . : Skipped
            There are no WINS servers configured for this interface.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{1F507EB0-EE57-4C1F-BEB7-4482C99A9C60}
    1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed
    [WARNING] You don't have a single interface with the <00> 'WorkStation Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Failed
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.matches.com. re-registeration
 on DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._site
s.matches.com. re-registeration on DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.pdc._msdcs.matches.com. re-re
gisteration on DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.gc._msdcs.matches.com. re-reg
isteration on DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._site
s.gc._msdcs.matches.com. re-registeration on DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.5aec9a38-7abf-4123-a272-a3bc4
48b9c0c.domains._msdcs.matches.com. re-registeration on DNS server '10.0.0.2' fa
iled.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry bc5d5e4c-0e5e-455f-ad0f-49e971090b7b._ms
dcs.matches.com. re-registeration on DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.dc._msdcs.matches.com. re
-registeration on DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-First-Site-Name._
sites.dc._msdcs.matches.com. re-registeration on DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.dc._msdcs.matches.com. re-reg
isteration on DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._site
s.dc._msdcs.matches.com. re-registeration on DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.matches.com. re-registera
tion on DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-First-Site-Name._
sites.matches.com. re-registeration on DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _gc._tcp.matches.com. re-registeration o
n DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _gc._tcp.Default-First-Site-Name._sites.
matches.com. re-registeration on DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _kerberos._udp.matches.com. re-registera
tion on DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _kpasswd._tcp.matches.com. re-registerat
ion on DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _kpasswd._udp.matches.com. re-registerat
ion on DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.DomainDnsZones.matches.com. r
e-registeration on DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._site
s.DomainDnsZones.matches.com. re-registeration on DNS server '10.0.0.2' failed.

DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.ForestDnsZones.matches.com. r
e-registeration on DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._site
s.ForestDnsZones.matches.com. re-registeration on DNS server '10.0.0.2' failed.

DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry matches.com. re-registeration on DNS ser
ver '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry gc._msdcs.matches.com. re-registeration
on DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry DomainDnsZones.matches.com. re-registera
tion on DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry ForestDnsZones.matches.com. re-registera
tion on DNS server '10.0.0.2' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Fix Failed: netdiag failed to re-register missing DNS entries for th
is DC on DNS server '10.0.0.2'.
    [FATAL] No DNS servers have the DNS records for this DC registered.


Redir and Browser test . . . . . . : Passed
    List of NetBt transports currently bound to the Redir
        NetBT_Tcpip_{1F507EB0-EE57-4C1F-BEB7-4482C99A9C60}
    The redir is bound to 1 NetBt transport.

    List of NetBt transports currently bound to the browser
        NetBT_Tcpip_{1F507EB0-EE57-4C1F-BEB7-4482C99A9C60}
    The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
    No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

    Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully

C:\>
0
 
Darius GhassemCommented:
Go into DNS right-click Forward Lookup zone then choose to create a new zone.
0
 
YashyAuthor Commented:

We tried doing that. At the end it says 'The Zone cannot be replicated to all DNS servers in the (null) active directory domain.....'.

Any ideas?
0
 
Darius GhassemCommented:
How many DCs do you have?
0
 
YashyAuthor Commented:
We have just one
0
 
Darius GhassemCommented:
Don't make the zone Active Directory Integrated just make it a primary zone.
0
 
YashyAuthor Commented:
I tried and it allowed me to create it. Where do I go from there?

Thanks by the way.
0
 
Darius GhassemCommented:
When you look in your DNS console under your domain.com zone do you have folders like msdcs, etc, etc? If you do run ipconfig /flushdns, ipconfig /registerdns, and dcdiag /fix.
0
 
YashyAuthor Commented:
Yes, they're now slowly being picked up. I ran flushdns, registerdns and dcdiag /fix also.
Everything seemed to pass other than this:

The account matches01 is not a DC account. It cannot replicate. Warning: attribute userAccountControl of Matches01 is : 0x10000 ......

By the way, we also tried to make this AD intergrated but it failed to do so.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Do you have a system state backup of the AD ??
0
 
YashyAuthor Commented:
We do have a backup on tape of through Backup Exec. Do you think that will be a good option to take?
0
 
Darius GhassemCommented:
Now since you have DNS setup correctly again then restore system state.
0
 
YashyAuthor Commented:
How do I restore system state? Sorry, but I think I've lost all logic today with the manicness of what's happened.
0
 
Darius GhassemCommented:
What is the server verison you are having trouble with?
0
 
YashyAuthor Commented:
It is Server 2003 Standard Edition SP2. Exchange 2003 sits on the same server.
0
 
Darius GhassemCommented:
0
 
YashyAuthor Commented:
Thanks for your help Darius. You were a great asset. We ended up having to call up Microsoft Professional Support due to the severity of it.

Here's what they did to resolve it:

Hello Yashr,

In order to find out if the domain controller had lost a secure channel to itself we ran this command:

At 21:30 /interactive /next: cmd.exe (this would startup the command prompt in the system context)
Note the 21:30 would be according to the time if it was 10:00 AM, we would have given one minute ahead i.e. 10:01 (10 PM would be 22:01)
/next: after which would come a space and then cmd.exe

2.       Once in the system context command prompt we gave this command adsiedit.msc

3.       This failed with a logon failure (meant the machine couldnt connect to itself)

Once we were sure that the PDC had lost the secure channel to itself. We ran this command to reset the secure channel to itself with this command:
netdom /resetpwd /server:matches01 /userd:matches.com\administrator /passwordd:*



Once they did this, it resolved the problem entirely and DNS was picking up. So basically, believe it or not, a MAC was connected to the network and when it joined the domain it gained the DC name for itself. How? Why? Beats me yet to this moment. But, all we know is that everything is back up and wanted to thank everybody for their help. I hope the material from everyone and Microsoft themselves will help someone in the future.

Cheers
Yash
0

Featured Post

Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

  • 13
  • 8
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now