Server 2012 essentials host acting strange

Critical Alerts and Warnings

Warnings(2)

Alert details: The DNS information for the server cannot be updated because the domain name provider cannot be contacted. You must contact your domain name provider.

Last occurrence: Monday, April 29, 2013 5:49:16 AM

Total occurrence(s): 1

Device(s): EXPRESSWAY

Alert details: Can only partially assess the health of this computer. The failing components are: ConnectivityFeature!RouterConfiguration

Last occurrence: Monday, April 29, 2013 5:22:11 AM

Total occurrence(s): 1

Device(s): EXPRESSWAY

Critical Errors in Event Logs in Last 24 Hours

Event ID: 2147487661

The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.

Last occurrence: Sunday, April 28, 2013 3:14:33 PM

Total occurrence(s): 1

Event ID: 2147486534

The security of this directory server can be significantly enhanced by configuring the server to reject SASL (Negotiate,
Kerberos, NTLM, or Digest) LDAP binds that do not request signing (integrity verification) and LDAP simple binds that
are performed on a cleartext (non-SSL/TLS-encrypted) connection. Even if no clients are using such binds,
configuring the server to reject them will improve the security of this server.

Some clients may currently be relying on unsigned SASL binds or LDAP simple binds over a non-SSL/TLS connection,
and will stop working if this configuration change is made. To assist in identifying these clients, if such binds occur this
directory server will log a summary event once every 24 hours indicating how many such binds
occurred. You are encouraged to configure those clients to not use such binds. Once no such events are observed
for an extended period, it is recommended that you configure the server to reject such binds.

For more details and information on how to make this configuration change to the server, please seehttp://go.microsoft.com/fwlink/?LinkID=87923.

You can enable additional logging to log an event each time a client makes such a bind, including
information on which client made the bind. To do so, please raise the setting for the "LDAP Interface Events" event logging category
to level 2 or higher.

Last occurrence: Sunday, April 28, 2013 3:14:06 PM

The other problems I'm having; remote access is a mess.  It was prevoiusly working so this is new.

Upon logging into remote web access I see my servers and clients.  Clicking connect does nothing and throws an IE error:

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C; InfoPath.3; .NET4.0E; MS-RTC LM 8)
Timestamp: Mon, 29 Apr 2013 12:48:33 UTC

Total occurrence(s): 1