Why is my 2008 R2 server not allowing remote desktop connections internally or externally?

I have 1 DC and 1 application server.  Today the DC stopped accepting RDC connections internally or externally.  And internally, I cannot ping, or browse to the DC at all.  dcdiag /q provides the following:

         Warning: POOLER-SRV1 is not advertising as a time server.

         ......................... POOLER-SRV1 failed test Advertising

         There are warning or error events within the last 24 hours after the

         SYSVOL has been shared.  Failing SYSVOL replication problems may cause

         Group Policy problems.
         ......................... POOLER-SRV1 failed test FrsEvent

         Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have

            Replicating Directory Changes In Filtered Set
         access rights for the naming context:

         DC=ForestDnsZones,DC=poolerped,DC=local
         Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have

            Replicating Directory Changes In Filtered Set
         access rights for the naming context:

         DC=DomainDnsZones,DC=poolerped,DC=local
         ......................... POOLER-SRV1 failed test NCSecDesc

            Could not open w32time Service on POOLER-SRV1, error 0x424

            "The specified service does not exist as an installed service."

         ......................... POOLER-SRV1 failed test Services

         Warning: DcGetDcName(TIME_SERVER) call failed, error 1355

         A Time Server could not be located.

         The server holding the PDC role is down.

         Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error

         1355

         A Good Time Server could not be located.

         ......................... poolerped.local failed test LocatorCheck

Need help on where to start!!
chj12316Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Lee W, MVPTechnology and Business Process AdvisorCommented:
I've seen 2008 Servers that lose the network location settings and think they are on public networks and not domain networks.  FIRST thing I'd check is if NLA (Network Location Awareness) thinks it's connected to a Public network or a Domain network.  Open the "Network and Sharing Center" and check what it says under "View your active networks".

If that checks out, then what you should always do when you have problems you don't know exactly where to resolve is check the event logs and start searching the failures to see why.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
chj12316Author Commented:
excellent point and a good place to start
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Server Software

From novice to tech pro — start learning today.

Question has a verified solution.

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

Have a better answer? Share it in a comment.