Link to home
Start Free TrialLog in
Avatar of sree av
sree av

asked on

server 2012 throwing netlogon and dcom error frequently

hello
we have simple windows server 2012 with firewall and no domain control. we just created during installation dns. then in in local server properties its showing as computer name: ABC and domain name ABCServer.com

however last few days i can see events of netlogon and dcom errors every an hour or so. due to this i believe our internet is disconnecting for few seconds and agin up.
can you pl. help these are the errors when i run dcdiag.exe

Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   Home Server = ABC
   * Identified AD Forest.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\ABC
      Starting test: Connectivity
         The host 5ea46ae9-dd4f-43fe-a122-588fa36389c1._msdcs.ABCSERVER.COM
         could not be resolved to an IP address. Check the DNS server, DHCP,
         server name, etc.
         Got error while checking LDAP and RPC connectivity. Please check your
         firewall settings.
         ......................... ABC failed test Connectivity

Doing primary tests

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


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

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

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

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

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

   Running enterprise tests on : ABCSERVER.COM
      Starting test: LocatorCheck
         ......................... ABCSERVER.COM passed test LocatorCheck
      Starting test: Intersite
         ......................... ABCSERVER.COM passed test Intersite
Avatar of Rob Williams
Rob Williams
Flag of Canada image

I assume you mean by; "no domain control" that you have not made this a domain controller and installed active directory?  If so you cannot run domain controller tests (DCDiag) on a server and expect not to get many errors.

Can you please provide the results of     ipconfig  /all

What is the DHCP server?  the router or the server itself?
Avatar of sree av
sree av

ASKER

thank you. the following are the ipconfig/all results
   Host Name . . . . . . . . . . . . : ABC
   Primary Dns Suffix  . . . . . . . : ABCSERVER.COM
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : ABCSERVER.COM

Ethernet adapter NIC1:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #2
   Physical Address. . . . . . . . . : B0-83-FE-C8-6D-53
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.1.4(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1
   DNS Servers . . . . . . . . . . . : XXX.XX.XX.X1 (OUR ISP DNS IP1)
                                       XXX.XX.XX.X2 (OUR ISP DNS IP2)
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter NIC2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
   Physical Address. . . . . . . . . : B0-83-FE-C8-6D-54
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{FE11BE09-56EC-4F37-A2E6-185788D48A49}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{ABE036FD-CCB6-435D-BC88-21F1976B9958}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter 6TO4 Adapter:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft 6to4 Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2002:6a33:513::6a33:513(Preferred)
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 106.51.115.146
                                       106.51.115.154
   NetBIOS over Tcpip. . . . . . . . : Disabled
If you have enabled DNS you need to use your DNS server.  The server and all PC's must point to it for DNS, and cannot have an alternate, even and ISP or router.  The ISPs DNS are then added as forwarders in the DNS management console.  Without doing so you will have NETLogon errors, name resolution issues, and more.
Avatar of sree av

ASKER

thanq. the same setup was working fine from last three years. if we put our server ip as dns we r not getting internet.
If you add the ISP's DNS servers as forwarders and PCs point only to the server for DNS internet, access and local name resolution will work fine.  If you do not point the PCs to the server for DNS, there is no point in adding the DNS service to the server.
ASKER CERTIFIED SOLUTION
Avatar of Rob Williams
Rob Williams
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.