WRVS4400N v2 DHCP/DNS-Probleme

Hallo,
ich habe seit kurzem den WRVS4400N v2, leider habe ich ein schwerwiegendes Problem.
Alle DHCP-Clients verlieren nach ca.24h (DSL-Disconnect) die Internetverbindung. Über NS-Lookup kann keine ip/webseite aufgelöst werden. das Problem lässt sich nur durch Hardwarereset(Stecker ziehen) oder duch reboot über das Webinterface beheben.
Die DHCP-Lease-Time ist auf 0(1Day) gestellt. LAn funktioniert noch, auf das Webinterface kommt man auch noch aber es Lässt sich von keinem Client eine Webseite öffnen (DNS-Probleme). Aus dem Webinterface des Routers kann über Ping/Trace auf Webseiten zugegriffen werden.
Firmware 2.0.1.3 und Firmware 2.0.2.1 haben beide dieses Problem. Hardwarereset und Factorydefaults haben nichts gebracht.
Eine Internetrecherche hat ergeben das dieses Problem scheinbar mehrere Personen haben, können Sie mir helfen.
Gibt es eine Beta-Firmware oder eine HowTo für das Problem?
Gruß
Sören Strauß
ConfigFile anbei!

Hallo Friedrich Scharz,
nein ich kann von Client aus keine Webseite Pingen!
Ich habe das ganze jetzt nocheinmal weiter eingrenzen können.
Nach genau einem Tag funktioniert DNS nicht mehr.
www.google.de kann ich nicht pingen und auch nicht im Browser öffnen, wenn ich aber die IP-Adresse von Google.de (173.194.69.94) in den Browser eingebe öffnet sich die Google-Webseite ohne Probleme.
Es ist also definitiv ein DNS Problem des DHCP-Servers/Routers.
Dieses Problem Betrifft alle Clients, egal ob WLAN oder Kabel / DHCP oder Feste-IP-Adresse.
Ich vermute das es evtl. etwas mit der 24h-Zwangstrennung des ISP(Provider: Telekom) zu tun hat. da das Problem nach genau 1Tag (24h) auftritt.
Wie kann ich das Problem jetzt beheben? Bitte dringend um Hilfe (Deutsch/Englisch; was schneller geht!!!!)!!
Gruß
Sören Strauß

Similar Messages

SBS 2011 no longer issues DHCP leases: DHCP, DNS, and AD Errors

Hi all. On early 8/13/2012 and into the morning, our UPS failed several times. The battery seems to be fine but the unit was shutting off power to the unit which means the (Windows SBS 2011 Standard) server shut off unexpectedly several times.I replaced
the UPS.
Now I'm trying to figure out what in the world this did to the server. It seems DHCP, DNS, and AD all have issues, as seen in the logs below. The client PC's are going offline one-by-one because the leases are expiring and it can't connect to the server
to renew. When trying to start the DHCP service, I get a 20013 error saying it cannot be started.
So I attempted to follow a kb article and repair the database but that didn't work because it seems the Jetpack utility is not in SBS 2011? And even at that, I'm thinking it may not even be a corrupted DHCP database due to the other errors in the event log.
This is a small office and I only know enough to be dangerous but usually I can just follow a kb to fix any issues. But there are so many errors, this one has me stumped.. Could any Server whizzes identify the big picture here?
Level Date and Time Source Event ID Task Category
Critical 8/13/2012 1:33:12 PM Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Critical 8/13/2012 11:30:37 AM Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Critical 8/13/2012 8:23:24 AM Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Critical 8/13/2012 8:05:08 AM Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Critical 8/13/2012 7:38:04 AM Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Critical 8/13/2012 7:29:29 AM Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Critical 8/13/2012 12:55:11 AM Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Critical 8/13/2012 12:15:49 AM Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Critical 8/13/2012 12:09:49 AM Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Level Date and Time Source Event ID Task Category
Error 8/15/2012 12:48:02 PM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 8/14/2012 2:23:37 PM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 8/14/2012 1:14:33 PM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 8/13/2012 8:06:12 AM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 8/13/2012 7:38:59 AM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 8/13/2012 12:16:52 AM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 5/31/2012 12:00:19 PM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 5/31/2012 11:14:20 AM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 4/18/2012 4:32:07 PM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 9/2/2011 2:14:09 AM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 8/30/2011 11:37:18 PM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 8/23/2011 1:52:28 PM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Level Date and Time Source Event ID Task Category
Error 8/15/2012 8:23:17 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 2:45:22 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:52:46 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:52:38 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:52:17 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:48:02 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:27:04 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:22:27 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 8:03:57 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 8:03:35 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 7:52:07 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 7:48:46 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 7:28:39 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 4:47:56 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 3:41:50 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 2:53:42 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 2:42:26 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 2:42:08 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 2:23:24 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 2:16:13 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 1:14:33 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 1:33:58 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 11:48:37 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 11:45:31 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 11:41:43 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 11:39:43 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 11:31:22 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 8:24:08 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 8:06:12 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 7:38:47 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 7:30:14 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 12:55:59 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 12:16:52 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Level Date and Time Source Event ID Task Category
Error 8/15/2012 12:52:46 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/15/2012 12:52:38 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/15/2012 12:52:17 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/15/2012 12:48:02 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/15/2012 12:27:04 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/15/2012 12:22:27 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 8:03:57 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 8:03:35 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 7:52:07 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 7:48:47 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 7:28:40 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 4:47:56 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 3:41:50 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 2:53:42 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 2:42:26 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 2:42:08 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 2:23:25 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 2:16:13 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 1:14:33 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 1:33:59 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 11:48:37 AM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 11:45:33 AM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 11:41:43 AM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 11:39:43 AM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 11:31:23 AM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 8:24:09 AM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 8:06:13 AM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 7:38:48 AM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 12:55:59 AM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 12:16:52 AM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Level Date and Time Source Event ID Task Category
Error 8/15/2012 8:23:17 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 2:45:22 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:52:46 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:52:38 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:52:17 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:48:02 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:27:04 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:22:27 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 8:03:57 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 8:03:35 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 7:52:07 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 7:48:47 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 7:28:40 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 4:47:56 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 3:41:50 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 2:53:42 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 2:42:26 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 2:42:08 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 2:23:25 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 2:16:13 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 1:14:33 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 1:33:59 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 11:48:37 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 11:45:33 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 11:41:43 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 11:39:43 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 11:31:23 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 8:24:09 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 8:06:13 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 7:38:48 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 7:30:15 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 12:55:59 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 12:16:52 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Level Date and Time Source Event ID Task Category
Error 8/15/2012 12:48:28 PM NtFrs 13552 None "The File Replication Service is unable to add this computer to the following replica set:
""DOMAIN SYSTEM VOLUME (SYSVOL SHARE)""
This could be caused by a number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0
The information below may help to resolve the problem:
Computer DNS name is ""SERVER2011.vhf.local""
Replica set member name is ""SERVER2011""
Replica set root path is ""c:\windows\sysvol\domain""
Replica staging directory path is ""c:\windows\sysvol\staging\domain""
Replica working directory path is ""c:\windows\ntfrs\jet""
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
Other event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time."
Error 8/15/2012 12:22:55 PM NtFrs 13552 None "The File Replication Service is unable to add this computer to the following replica set:
""DOMAIN SYSTEM VOLUME (SYSVOL SHARE)""
This could be caused by a number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0
The information below may help to resolve the problem:
Computer DNS name is ""SERVER2011.vhf.local""
Replica set member name is ""SERVER2011""
Replica set root path is ""c:\windows\sysvol\domain""
Replica staging directory path is ""c:\windows\sysvol\staging\domain""
Replica working directory path is ""c:\windows\ntfrs\jet""
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
Other event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time."
Error 8/14/2012 2:23:56 PM NtFrs 13552 None "The File Replication Service is unable to add this computer to the following replica set:
""DOMAIN SYSTEM VOLUME (SYSVOL SHARE)""
This could be caused by a number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0
The information below may help to resolve the problem:
Computer DNS name is ""SERVER2011.vhf.local""
Replica set member name is ""SERVER2011""
Replica set root path is ""c:\windows\sysvol\domain""
Replica staging directory path is ""c:\windows\sysvol\staging\domain""
Replica working directory path is ""c:\windows\ntfrs\jet""
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
Other event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time."
Error 8/14/2012 1:15:00 PM NtFrs 13552 None "The File Replication Service is unable to add this computer to the following replica set:
""DOMAIN SYSTEM VOLUME (SYSVOL SHARE)""
This could be caused by a number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0
The information below may help to resolve the problem:
Computer DNS name is ""SERVER2011.vhf.local""
Replica set member name is ""SERVER2011""
Replica set root path is ""c:\windows\sysvol\domain""
Replica staging directory path is ""c:\windows\sysvol\staging\domain""
Replica working directory path is ""c:\windows\ntfrs\jet""
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
Other event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time."
Error 8/13/2012 1:34:27 PM NtFrs 13552 None "The File Replication Service is unable to add this computer to the following replica set:
""DOMAIN SYSTEM VOLUME (SYSVOL SHARE)""
This could be caused by a number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0
The information below may help to resolve the problem:
Computer DNS name is ""SERVER2011.vhf.local""
Replica set member name is ""SERVER2011""
Replica set root path is ""c:\windows\sysvol\domain""
Replica staging directory path is ""c:\windows\sysvol\staging\domain""
Replica working directory path is ""c:\windows\ntfrs\jet""
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
Other event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time."
Error 8/13/2012 11:31:55 AM NtFrs 13552 None "The File Replication Service is unable to add this computer to the following replica set:
""DOMAIN SYSTEM VOLUME (SYSVOL SHARE)""
This could be caused by a number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0
The information below may help to resolve the problem:
Computer DNS name is ""SERVER2011.vhf.local""
Replica set member name is ""SERVER2011""
Replica set root path is ""c:\windows\sysvol\domain""
Replica staging directory path is ""c:\windows\sysvol\staging\domain""
Replica working directory path is ""c:\windows\ntfrs\jet""
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
Other event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time."
Error 8/13/2012 8:24:36 AM NtFrs 13552 None "The File Replication Service is unable to add this computer to the following replica set:
""DOMAIN SYSTEM VOLUME (SYSVOL SHARE)""
This could be caused by a number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0
The information below may help to resolve the problem:
Computer DNS name is ""SERVER2011.vhf.local""
Replica set member name is ""SERVER2011""
Replica set root path is ""c:\windows\sysvol\domain""
Replica staging directory path is ""c:\windows\sysvol\staging\domain""
Replica working directory path is ""c:\windows\ntfrs\jet""
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
Other event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time."

Level Date and Time Source Event ID Task Category
Error 8/15/2012 12:48:28 PM NtFrs 13555 None "The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed:
Recovery Steps:
[1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window:
net stop ntfrs
net start ntfrs
If this fails to clear up the problem then proceed as follows.
[2] For Active Directory Domain Services Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled:
If there is at least one other Domain Controller in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
If there are NO other Domain Controllers in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary.
If there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative.
[3] For Active Directory Domain Services Domain Controllers that host DFS alternates or other replica sets with replication enabled:
(3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location.
(3-b) If this server is the only Active Directory Domain Services Domain Controller for this domain then, before going to (3-c), make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for
Sites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS.
(3-c) Restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
(3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published.
[4] For other Windows servers:
(4-a) If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location.
(4-b) net stop ntfrs
(4-c) rd /s /q c:\windows\ntfrs\jet
(4-d) net start ntfrs
(4-e) Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time).
Note: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members."
Error 8/15/2012 12:22:55 PM NtFrs 13555 None "The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed:
Recovery Steps:
[1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window:
net stop ntfrs
net start ntfrs
If this fails to clear up the problem then proceed as follows.
[2] For Active Directory Domain Services Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled:
If there is at least one other Domain Controller in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
If there are NO other Domain Controllers in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary.
If there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative.
[3] For Active Directory Domain Services Domain Controllers that host DFS alternates or other replica sets with replication enabled:
(3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location.
(3-b) If this server is the only Active Directory Domain Services Domain Controller for this domain then, before going to (3-c), make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for
Sites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS.
(3-c) Restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
(3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published.
[4] For other Windows servers:
(4-a) If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location.
(4-b) net stop ntfrs
(4-c) rd /s /q c:\windows\ntfrs\jet
(4-d) net start ntfrs
(4-e) Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time).
Note: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members."
Error 8/14/2012 2:23:56 PM NtFrs 13555 None "The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed:
Recovery Steps:
[1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window:
net stop ntfrs
net start ntfrs
If this fails to clear up the problem then proceed as follows.
[2] For Active Directory Domain Services Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled:
If there is at least one other Domain Controller in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
If there are NO other Domain Controllers in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary.
If there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative.
[3] For Active Directory Domain Services Domain Controllers that host DFS alternates or other replica sets with replication enabled:
(3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location.
(3-b) If this server is the only Active Directory Domain Services Domain Controller for this domain then, before going to (3-c), make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for
Sites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS.
(3-c) Restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
(3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published.
[4] For other Windows servers:
(4-a) If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location.
(4-b) net stop ntfrs
(4-c) rd /s /q c:\windows\ntfrs\jet
(4-d) net start ntfrs
(4-e) Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time).
Note: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members."
Error 8/14/2012 1:15:00 PM NtFrs 13555 None "The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed:
Recovery Steps:
[1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window:
net stop ntfrs
net start ntfrs
If this fails to clear up the problem then proceed as follows.
[2] For Active Directory Domain Services Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled:
If there is at least one other Domain Controller in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
If there are NO other Domain Controllers in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary.
If there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative.
[3] For Active Directory Domain Services Domain Controllers that host DFS alternates or other replica sets with replication enabled:
(3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location.
(3-b) If this server is the only Active Directory Domain Services Domain Controller for this domain then, before going to (3-c), make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for
Sites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS.
(3-c) Restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
(3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published.
[4] For other Windows servers:
(4-a) If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location.
(4-b) net stop ntfrs
(4-c) rd /s /q c:\windows\ntfrs\jet
(4-d) net start ntfrs
(4-e) Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time).
Note: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members."
Error 8/13/2012 1:34:27 PM NtFrs 13555 None "The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed:
Recovery Steps:
[1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window:
net stop ntfrs
net start ntfrs
If this fails to clear up the problem then proceed as follows.
[2] For Active Directory Domain Services Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled:
If there is at least one other Domain Controller in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
If there are NO other Domain Controllers in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary.
If there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative.
[3] For Active Directory Domain Services Domain Controllers that host DFS alternates or other replica sets with replication enabled:
(3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location.
(3-b) If this server is the only Active Directory Domain Services Domain Controller for this domain then, before going to (3-c), make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for
Sites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS.
(3-c) Restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
(3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published.
[4] For other Windows servers:
(4-a) If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location.
(4-b) net stop ntfrs
(4-c) rd /s /q c:\windows\ntfrs\jet
(4-d) net start ntfrs
(4-e) Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time).
Note: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members."
Error 8/13/2012 11:31:55 AM NtFrs 13555 None "The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed:
Recovery Steps:
[1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window:
net stop ntfrs
net start ntfrs
If this fails to clear up the problem then proceed as follows.
[2] For Active Directory Domain Services Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled:
If there is at least one other Domain Controller in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
If there are NO other Domain Controllers in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary.
If there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative.
[3] For Active Directory Domain Services Domain Controllers that host DFS alternates or other replica sets with replication enabled:
(3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location.
(3-b) If this server is the only Active Directory Domain Services Domain Controller for this domain then, before going to (3-c), make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for
Sites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS.
(3-c) Restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
(3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published.
[4] For other Windows servers:
(4-a) If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location.
(4-b) net stop ntfrs
(4-c) rd /s /q c:\windows\ntfrs\jet
(4-d) net start ntfrs
(4-e) Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time).
Note: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members."
Error 8/13/2012 8:24:36 AM NtFrs 13555 None "The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed:
Recovery Steps:
[1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window:
net stop ntfrs
net start ntfrs
If this fails to clear up the problem then proceed as follows.
[2] For Active Directory Domain Services Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled:
If there is at least one other Domain Controller in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
If there are NO other Domain Controllers in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary.
If there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative.
[3] For Active Directory Domain Services Domain Controllers that host DFS alternates or other replica sets with replication enabled:
(3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location.
(3-b) If this server is the only Active Directory Domain Services Domain Controller for this domain then, before going to (3-c), make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for
Sites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS.
(3-c) Restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
(3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published.
[4] For other Windows servers:
(4-a) If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location.
(4-b) net stop ntfrs
(4-c) rd /s /q c:\windows\ntfrs\jet
(4-d) net start ntfrs
(4-e) Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time).
Note: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members."
Level Date and Time Source Event ID Task Category
Error 8/15/2012 8:23:17 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/15/2012 2:45:22 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/15/2012 12:52:46 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/15/2012 12:52:38 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/15/2012 12:52:17 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/15/2012 12:48:22 PM Service Control Manager 7024 None The SQL Server (SBSMONITORING) service terminated with service-specific error %%17058.
Error 8/15/2012 12:48:02 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/15/2012 12:27:04 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/15/2012 12:25:19 PM Service Control Manager 7024 None The Windows Search service terminated with service-specific error %%-1073473535.
Error 8/15/2012 12:22:48 PM Service Control Manager 7024 None The SQL Server (SBSMONITORING) service terminated with service-specific error %%17058.
Error 8/15/2012 12:22:27 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 8:03:57 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 8:03:35 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 7:52:07 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 7:48:47 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 7:28:40 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 4:47:56 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 3:41:50 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 2:53:42 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 2:42:26 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 2:42:08 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 2:23:25 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 2:16:13 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 1:14:33 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 1:33:59 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 11:48:37 AM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 11:45:33 AM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 11:41:43 AM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 11:39:43 AM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 11:31:23 AM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 8:24:09 AM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 8:06:13 AM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 7:38:48 AM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 12:55:59 AM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 12:16:52 AM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.

Internet DHCP/DNS issues with WRT1900ac

I've had a WRT1900ac now for about 2 weeks and the problems seem to be escalating. Need help. And yes, I've already read dozens of threads about these issues and nothing seems to be working.
Most of the problems seem to be centered around this DHCP/DNS issue that so many have been reporting.
First, the symptoms:
Galaxy S4 phones when connected via wifi have some apps that don't update (facebook and google play)
Some computers (both Win 7) will connect to the network just fine, both wired and wireless - but won't be able to get to the internet
I've spent the last 2-3 days of my life reading forums and trying all sorts of things to get this to work properly (like my old router) and I'm still stuck. Some things I've tried:
Firmware is up-to-date (latest version: 1.1.8.164461)
Manually assigned static DNS in router config settings (connectivity -> local network) to various combinations including the router address, 8.8.8.8, 8.8.4.4, 75.75.75.75, 75.75.76.76 (I have comcast), OpenDNS addresses, etc. I read that the router address is not needed, so I stopped including it.
I manually assigned IPs and DNS on the Galaxy S4 phones and that seemed to work... but also seems unnecessary.
I've reserved DHCP addresses on the computers in question, that didn't seem to work, I also manually set DNS on one of the comupters (can't on the other... long story/not my computer) and that worked for a while and then stopped working.
The only way to get one of the computers on the internet now is to turn on the guest network (even though the computer is hard wired to the router), connect, and then the wired network works. No clue why this is, but my guess is that it needs the guest network for DNS, then it fails back over to the wired network. Once that happens, I can actually turn off the wifi on the computer and everything works great... until I reboot. Key point: I can't change any settings on that box other than entering in SSID/passphrase info for the wireless connection. I can connect to the regular (non-Guest) wifi just fine - I just can't ever get to the internet.
I've tried massaging DHCP settings on the router until I'm blue in the face - Static DNS, reserving DHCP addresses, hell I even put one of the computers in the DMZ to see if that would work and it still can't connect to the internet (it's worth noting that with my old router, Linksys WRT310N, the setup was literally plug-and-play - no hassle with any of this).
I've tried countless router reboots, factory resets, turning off my modem and router for 2+ minutes, and nothing is working.
I even read somewhere that if you modify your DHCP settings at all that the WRT1900ac stops doing DNS properly and breaks, so I even tried several "hard" factory resets and used all the default DHCP/DNS settings. And it worked... for a few hours.
Seriously, I'm at my wit's end. I'm out a lot of money on this thing and it's been one headache after another. Please help.

I think for most people its a bad idea to hold out that hope, lol. It seems like a great piece of hardware but if you really need a router and don't want to have to 'play' with it, its probably not a good choice. I have an EA6900 that I am very happy with but it has the same restrictions as far as DNS and I really hate the idea that I am forced to use the smartwifi portal. I would really like for them to give me a choice of the old gui or the new one and let ME decide. Lots of routers to choose from out there now and new ones seem to be coming out all the time so do some reading and see if something suits you better. Good luck!

Windows 7 VM has DNS Problem When Using Wireless

Hello All,
I've been fighting this virtual machine networking problem for over a week now. If anyone has a well-informed suggestion (not a guess) I would appreciate hearing about it.
Here's the problem in a nutshell and then I'll give more details: I'm running Windows 7 Ultimate (64 bit) as my primary (i.e., host) OS. I'm running Windows 7 Home Professional (32 bit) as the guest OS in "Windows Virtual PC" (note that this is *not* the same as "Virtual PC 2007"). If I configure the VM to use my host's wired Ethernet connection, the guest OS can always see the machines on my local network and can always reach the Internet just fine. On the other hand, if I configure the VM to use only my host's wireless connection then the guest OS can still see machines on my local network but CANNOT reach the Internet, except very intermittently (e.g., for maybe 1-2 minutes every hour or so).
I've tried to anticipate the questions you might ask so here is some additional information:
The computer is a Lenovo W500 laptop running Windows 7 Ultimate, 64-bit. The wireless network adapter is an "Intel WiFi Link 5300 AGN".
My Internet connection is via AT&T DSL using a wire2 wireless modem/router.
I have all the updates from Microsoft and Lenovo for this machine. It is 100% up to date with the latest patches and drivers.
I'm running the 64-bit version (or at least I used the 64 bit installer) of "Windows Virtual PC" which I downloaded from this link.
I am *not* running and I did not download "XP Mode".
When the guest OS loses it's connection to the Internet the following message appears in the Windows Event Log:
"Name resolution for the name address.yahoo.com timed out after none of the configured DNS servers responded."
I am able to ping an external machines outside my network but only if I use the IP address. If I specify the host name it cannot be resolved.
ARE YOU GETTING THE IMPRRESSION THIS IS A DNS PROBLEM??? It looks like I do not have access to a DNS when using the host's wireless connection.
On the host OS, the "Virtual PC Network Filter Driver" *IS* installed and selected under my "Wireless Network Connection Properties" settings.
Below are the results of running ipconfig on the guest OS and then the host OS. Note that I am able to ping 192.168.1.254 from the host OS but not from the guest OS. I think this is the crux of the problem.
Here's what I get from an ipconfig /all executed on the guest OS:
Windows IP Configuration
   Host Name . . . . . . . . . . . . : Win7_01
   Primary Dns Suffix . . . . . . . :
   Node Type . . . . . . . . . . . . : Broadcast
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : gateway.2wire.net
Ethernet adapter Local Area Connection:
   Connection-specific DNS Suffix . : gateway.2wire.net
   Description . . . . . . . . . . . : Intel 21140-Based PCI Fast Ethernet Adapter (Emulated)
   Physical Address. . . . . . . . . : 00-03-FF-5A-E5-8C
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::6452:ad20:724a:4d3a%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.75(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Friday, May 14, 2010 7:22:30 PM
   Lease Expires . . . . . . . . . . : Friday, May 21, 2010 7:22:30 PM
   Default Gateway . . . . . . . . . : 192.168.1.254
   DHCP Server . . . . . . . . . . . : 192.168.1.254
   DHCPv6 IAID . . . . . . . . . . . : 234882047
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-79-57-1A-00-03-FF-5A-E5-8C
   DNS Servers . . . . . . . . . . . : 192.168.1.254
   NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.gateway.2wire.net:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . : gateway.2wire.net
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
   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
And here's what I get when I do ipconfig /all on the host OS:
Windows IP Configuration
   Host Name . . . . . . . . . . . . : LEONA
   Primary Dns Suffix . . . . . . . :
   Node Type . . . . . . . . . . . . : Broadcast
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : gateway.2wire.net
Wireless LAN adapter Wireless Network Connection:
   Connection-specific DNS Suffix . : gateway.2wire.net
   Description . . . . . . . . . . . : Intel(R) WiFi Link 5300 AGN
   Physical Address. . . . . . . . . : 00-21-6A-59-E5-8C
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::94b0:4080:c30f:95da%12(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.78(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Friday, May 14, 2010 6:20:52 PM
   Lease Expires . . . . . . . . . . : Friday, May 21, 2010 6:20:53 PM
   Default Gateway . . . . . . . . . : 192.168.1.254
   DHCP Server . . . . . . . . . . . : 192.168.1.254
   DHCPv6 IAID . . . . . . . . . . . : 218112362
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-79-34-70-00-22-68-14-2F-CB
   DNS Servers . . . . . . . . . . . : 192.168.1.254
   NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . : gateway.2wire.net
   Description . . . . . . . . . . . : Intel(R) 82567LM Gigabit Network Connection
   Physical Address. . . . . . . . . : 00-22-68-14-2F-CB
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.gateway.2wire.net:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . : gateway.2wire.net
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
   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
   IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e74:3ca6:3214:b4fb:72d4(Preferred)
   Link-local IPv6 Address . . . . . : fe80::3ca6:3214:b4fb:72d4%13(Preferred)
   Default Gateway . . . . . . . . . : ::
   NetBIOS over Tcpip. . . . . . . . : Disabled

Hello,
I am not very familiar wth Microsoft Security Essentials, but believe that it just makes use of the existing Windows Firewall which is present with the operating system.
To me it is odd that the guest OS reports 192.168.1.254 as the IP address for its gateway and DHCP server yet it cannot access them when pinged. Let's try pinging from host to guest (and vice-versa) and see what happens:
From the host OS at 192.168.1.78, try pinging the guest OS at 192.168.1.75.
Then, from the guest OS at 192.168.1.75, trying ping the host OS at 192.168.1.78.
Is each operating system able to ping each other?
Regards,
Aryeh Goretsky
I am a volunteer and neither a Lenovo nor a Microsoft employee. • Dexter is a good dog • Dexter je dobrý pes
S230u (3347-4HU) • X220 (4286-CTO) • W510 (4318-CTO) • W530 (2441-4R3) • X100e (3508-CTO) • X120e (0596-CTO) • T61p (6459-CTO) • T43p (2678-H7U) • T42 (2378-R4U) • T23 (2648-LU7)
Deutsche Community Comunidad en Español Русскоязычное Сообщество

Snow Leopard and DNS problems

Hi
I read a lot about SL and DNS problems while accessing websites. It seems that you have to put your DNS server in system settings/network so that you don't get the error message "can't connect to the internet' in your browser window. My problem is that I change locations with my mac quite frequently (home, uni etc) so whenever I am a a new location I have to go to the network settings and manually put in the DNS server. Why do I have to do that with SL when it worked completely fine before the upgrade to SL?
Cheers
Martin

waschbaer22 wrote:
That is exactly what is happening. The problem with my DHCP server at home is that it doesn't submit the DNS address to the computer somehow. That's why I have to put it in manually each time I reconnect the MB at home after I had it at uni. Once back at uni I then have to go into the settings and delete my manually added home DNS server. Right after that the uni DNS server address appears automatically. So I guess that is just how SL now works and I have to live with it, right? However, why do we need a DNS server anyway to connect to the internet. I thought a DNS server just facilitates the connection to websites but I didn't know that it is crucial.
You should really try to figure out why your home router isn't providing you with a DNS server address and fix that. It could be a firmware issue, or it could be as simple as you have things set up so that one must manually be set up in the router, and one is not.
You are also misinformed as to DNS' importance.
DNS is the service that translates names - say "apple.com" - to the IP addresses - say "17.149.160.49" - that your machine needs to be able to connect to any site.
Without being able to resolve names to addresses, you have to manually specify numeric IP addresses for everything - effectively meaning you will be unable to use the Internet.

DNS Problems (Oxted)

Hello,
Having some problems accessing websites, but ok if I used the IP address, therefore wondering whether DNS problem.
Email client doesn't work. Skype OK.
Tablet android (using wifi) OK.
Several hardwired machines affected, one wifi laptop affected.
BT HH3 rebooted countless times.
Ping of BT DNS servers fail.
Ping of 8.8.8.8 (Google) ok.
Using DNS from Google ok.
Nothing on BT site to indicate problems.
Infinity installation in local exchange, connected????
Regards, Stephen.
Solved!
Go to Solution.

A factory reset will simply reset the admin and wifi password to its default values, and reset any port forwarding that you may have set up.
Android devices, by default, use DHCP, so will get the settings from the home hub. Some devices, like the Kindle, do things differently.
It quite possible for the internal routing within the HH, to get corrupted. It usually happens when the DHCP table gets full, as the HH does not appear to release unused addresses properly. This shows as missing DNS server settings on the network properties of a PC, even though the default gateway is present.
A factory reset is often suggested by the helpdesk.
There are some useful help pages here, for BT Broadband customers only, on my personal website.
BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

Interesting explanation and fix for obscure DNS problems

This blog is a real eye-opener:
*10.5.3 Fixes DNS Problems Plaguing Some Leopard Users*
http://hunter.pairsite.com/blogs/blog20080603.html
Who knew?!
"I had tangled with name lookup issues during early stages of Leopard development, and learned that Leopard changed the way name lookups were made.
"... Some people had been carrying DNS baggage for years with no idea, and this had likely been hampering name lookup operations at some level for a long time, even before 10.5 came along.
"In other cases, it was a major challenge. The average user doesn't know (and probably shouldn't need to know) where their DNS settings are, or what they do. And then consider the common situation of a user with a Mac connected to an Airport connected to a cable modem, with various DHCP leases sprinkled into the mix. In most of those cases, DNS settings are provided far upstream and inherited down through the line. The user may see no DNS settings on the Mac, or it might be using the address of the Airport router. The Airport might contain DNS settings inherited from the cable modem, which it picked up from the ISP through the DHCP lease. The issue then becomes one of figuring out where to purge old DNS settings, if that's even possible, and replacing or overriding them with known good ones (such as from OpenDNS.org). It was a challenge in many cases. Just convincing the user they had a DNS issue was a challenge in some cases!"

I think DNS lookup issues are relatively rare these days and so are perhaps not the obstacle to trouble-free internet access that they used to be in the days when ISPs were less Mac friendly and Apple seemed to have issues with DNS lookups without the network preferences having declared DNS server IPs. Even then, I think much of that was timing, with MacOS flavors at the time being rather more critical than ISPs expected and that Windows tends to be.
Much of the DNS hullabaloo had died out until recently, due to the appearance of active IPv6, which once again seemed have caused timing issues. Thankfully since IPv6 is not much in use yet, it can be switched off in the TCP/IP pane of the appropriate network preference and that seemed to cure DNS lookup issues for those who had them once again.
I've found though, both at work with our commercial T1s, and at home with my (not altogether Mac-friendly) ISP, that DNS has not been an issue sine perhaps the mid MacOS 10.3, or maybe even earlier. And as I found at the time when I had issues at home but not with the same system and configuration at work, it turned out to be the ISP's primary DNS server which was not configured correctly and timed out routinely.
Even with IPv6 still enabled I've not have DNS issues with any Mac for some time, and have not experienced any difference in internet behavior between 10.5.3 and anything prior. Even my iPhone, which had DNS problems if the first DNS IP was the local router, has been behaving correctly since the first firmware update last summer!

Strange DNS problems

I have been seeing very strange DNS problems running 10.4.7 on my MacBook Pro.
I travel a fair amount, and in certain places, I have problems with DNS. I will Google a topic for example, and I will get a response that "www.google.com" cannot be found.
Simply refreshing the page will many times cause the request to "take".
This does not happen under Windows XP (I am converting from XP and actually am carrying two laptops) from the same hotel room, using the same hardwire Ethernet connection.
It also doesn't happen using an XP install under Parallels.
Not sure where to go from here - I have done a DCHP "renew" from within the hotel room - no help.
Note that this doesn't happen everywhere. Today I happen be a stone's throw from Apple HQ in Cupertino, and I am getting it like crazy.l
Any ideas what to look for?

I can hopefully add a little more background to this being on the network end of things.
First, a little background:
I work at a hotel and we provide free wireless (a/b/g) and 100 Mbps wired to each of the guest rooms. For a long time we would receive a large number of support calls from guests whose laptops were configured to use a static IP address in an office environment rather than DHCP. We'd have to walk them through changing their network settings to DHCP, which can be very difficult with most computer users who have no idea what any of that means.
To solve this problem we purchased a Nomadix AG5000 (http://www.nomadix.com/products/platforms/ag5000/), which essentially ignores everything the computer provides for its network settings (identifying it solely by its MAC address) and gives it a DHCP address from our pool. We use the 172.16.0.0/16 range, which also avoids the majority of VPN problems related to NATting. This device is used in a large number of publicly available networks for just this reason.
This is when our problems started. Windows computers it seems have no problem with this kind of configuration, static IP already configured or no. Mac computers do. When they first connect, they'll often have trouble resolving anything but start to after a couple refreshes. The longer they're connected, the better they get at being able to resolve things and it eventually mostly disappears.
I can fairly reliably duplicate this problem with my Powerbook and I've deliberately placed myself on a VLAN separate from the Nomadix box for this reason.
Other than reloading a bunch, I have not yet figured out a solution to this problem that does not require manually doing everything DHCP is supposed to automate.
Powerbook 17 1.67 Ghz Mac OS X (10.4.7)

I am having a DNS problem with my computer. My laptop connects to the internet and my skype works normally but when i try to surf the web it says "DNS Look up failed".

MY PROBLEM
I am having a DNS problem with my laptop. It connects normally to th e wifi internet but when i try to surf the net it says "DNS Look up failed"
This problem only occurs when with the internet at my house. whenever i connect elsewhere my computer works normally. My ipod, iphone, tablet and other friends computers work normally when they are connected to my internet. i use dmy neigbours nework a couple of times from my house and it wrks normally.
Also when i turn my laptop on or off i can browse for a few minutes or seconds before it fails again. My skype works like there is no problem
WHAT I HAVE TRIED TO RESOLVE IT
I have tried changing the DNS, i used open DNS and google free DNS and it still didnt make a difference.
I have rebooted router many times, nothing
I have changed my home router, nothing
I backed up my computer, resored everything it to factory setting and put everything back on; still nothing
Run a diagnostics at 'Best buy' and they say nothing is wrong; but i know there is something wrong with the DNS
I have tried different "sudo" type of codes on my comupter from stuff i got online and nothign has proved fruitful yet.
i tried using safari, Google chrome and firefox, all not loading
WHAT DO I DO TO FIX THIS?

You are correct. Syncing should transfer any purchased media, including videos, from your device to your iTunes library provided your computer is authorized for the Apple ID used to make these purchases. You mentioned that you have uninstalled iTunes before, but if you didn't follow this guide exactly, uninstalling iTunes and all of its components in the order specified, it may not have been successful so you should try again: Windows XP or Windows Vista/7.

DHCP DNS Management Console Error

Downloaded the DHCP DNS Management Console and logged in......login error
ERROR_INCORRECT_PORT_IP
New to linux.
thanks for your help

Is this a DSfW server? Because on a DSfW server you have to use port
1636 instead of 636 to connect to the Edir side of the server.
Don't try to use port 389 (or 1389 on a DSfW server) as this does only
work on servers which are specifically configured to allow that.
W. Prindl
kvnimrls wrote:
>
>Downloaded the DHCP DNS Management Console and logged in......login
>error
>
>ERROR_INCORRECT_PORT_IP
>
>New to linux.
>
>thanks for your help

Database DNS problem while uploading jsp's

We create DNS while working with localhost on winodws machine but when we upload the jsp's and database then how do we manage the DNS problem do we have to create the DNS there too or there is some other way out

Sorry for spelling mistake actually it was DSN data source that had been asked

DNS problems on Lion

Hello,
Ever since I "upgraded" to Lion I have had DNS issues.
I know it's a DNS problem because IP addresses work fine. And I know it's not a browser issue, because I am running 'ping google.com' from the command line.
The symptoms are non-responsive queries to DNS servers, in web browsers or the command line (using ping). Currently I am using google's DNS servers: 8.8.8.8 and 8.8.4.4. I'm absolutely sure that there is nothing wrong with those servers. The request to the DNS servers eventually times out, and then I hit "Refresh" and the page loads fine.
Also, if I recylce the network adapter, e.g.
$ sudo ifconfig en1 down
$ sudo ifconfig en1 up
DNS starts working again, temporarily until the next time. It happens again (randomly, not at regular intervals), I then run the ifconfig down/up again, and DNS works again, and so on.
This started happening when I went to Lion.
Thank you

I have just purchased a brand new Mac Mini Server with Lion Server running. Managed to set up DNS service and 5 zones configured and running fine for 1 to 2 days.
The DNS in Server Admin suddenly stopped loading the information and buttons are all greyed out last night, with no changes made since I was away at work. It keeps getting the same situation as thread starter mentioned. I have tried all possible means but it just stop loading zones information anymore.
I would like to try John's approach but it seems I am unable to get 'root' access to perform those actions. Thus would appreciate some advice on how to proceed forward to resolve the issue.
1. Tried the Directory Utility approach to "Enable Root" but when enter terminal, 'sudo root' does not seem to accept the password I have set. Is there any other means to enable an account to have sufficient access to perform those DNS related resolution steps?
2. Is there any location to obtain a copy of the default named.conf?

Strange DNS problems wrt160n v2

My router worked fine with 60mbit internet, i bumped up to 90mbit, and it worked fine for 2 weeks or so, and then one day my desktop, with a wired connection, started to go nuts with the DNSserver, what screwed up the internet, pages would not load, when i refreshed the page it would load, but 5 or 6 mouseclicks further and the DNS was gone again... i changed everything, all the settings, the utp cable, even Vista had to go, just to be sure.. but nothing worked, except removing the router, but that was no option for my laptop, which was working perfect, never had a bad connection or DNS problems....
I went back to the store with the router and there it worked fine, tested everything, but no problems, i came back home, hooked it up, and the problems where back...
Anybody got a clue, my only idea about this is that the 160n cant cope with the 90mbit,i got p. off and bought myself a wrt320n which works perfect, wired and wireless.

WRT160N does work with 90 Mbit...might be the settings are not proper on the router.
However its great that your were able to resolve the issue by WRT160N...

DHCP & DNS Server 2008

Hello,
I'm not sure how the following is working.
asa5525
anyconnect version 3.1
windows server 2008R2
When you come in via VPN I send clients to the windows server for DHCP/DNS info and records get created in the FLZ and RLZ. When folks disconnect from VPN those records in both FLZ and RLZ get purged instantly. When your on wired and disconnect those records in both zones do not get purged. I have my VPN scope and wired scope setup exactly the same. I'm new to managing DNS and DHCP and know there's a lot to learn but it seems odd that when leaving a VPN session those records fall off right away. I'm not sure if the ASA has something to do with it or the anyconnect client itself.
thanks for any help!
This topic first appeared in the Spiceworks Community

Hello,
I'm not sure how the following is working.
asa5525
anyconnect version 3.1
windows server 2008R2
When you come in via VPN I send clients to the windows server for DHCP/DNS info and records get created in the FLZ and RLZ. When folks disconnect from VPN those records in both FLZ and RLZ get purged instantly. When your on wired and disconnect those records in both zones do not get purged. I have my VPN scope and wired scope setup exactly the same. I'm new to managing DNS and DHCP and know there's a lot to learn but it seems odd that when leaving a VPN session those records fall off right away. I'm not sure if the ASA has something to do with it or the anyconnect client itself.
thanks for any help!
This topic first appeared in the Spiceworks Community

DNS Problems with WRT54G

2 Nights ago we had storms in the area; next morning wife calls me at work and says that internet connection does not work. Get home and take a look at it. I can connect to router wired or wirelessly, was able to look at the configurations, etc. but when I try to access internet pages I get an error indicating DNS problems.
I have cycled power on cable modem (also Linksys but don't remember model number at the moment) and router. Still had the same problem wired and wirelessly.
I reset the router to factory defaults, connected to it both wired and wirelessly and still had the DNS rpoblems.
I reconfigured the router with my original security settings, connected to it wired and wirelessly and still had the DNS problems.
I connected directly to the cable modem and had no problems accessing internet at all.
Is there any way that I can force the router into updating DNS information? Or possibly reset DNS information?
I have run out of things that I know to try. I hope someone can help.

Usually a DNS problem is caused because the router is not connecting to the Internet properly.
Since you have a cable modem, you can usually leave the WRT54G set to its factory default settings, except that you might need to "Clone the MAC address" of the computer that works when connected to your modem.
Hope this helps.
If you need more help, please do the following:
1) state your ISP
2) state the make and exact model number of your modem (not the WRT54G).
3) Connect your computer, by ethernet cable, directly to your modem (not the WRT54G). Verify that you have a properly working Internet connection, then do the following test:
Go to "Start" > All Programs > Accessories > Command Prompt.
A black DOS box will appear. Type in "ipconfig /all" (with no quotes), then hit the Enter key. Post all of the results, except if your "IP address" does not start with 192, then post only the first 3 digits of it, along with the rest of the info. To copy the info to your post, highlight (select) the info, then use the copy (Ctrl-c) and paste (Ctrl-v) keys.
Message Edited by toomanydonuts on 05-16-2008 07:13 AM

WRVS4400N v2 DHCP/DNS-Probleme

Similar Messages

Maybe you are looking for