The system cannot contact a domain controller, random problem.


Recommended Posts

This is a new Windows Server 2012 R2 Essentials setup, This server is basically running everything on the network as you would probably expect with an essentials setup, all the client PC?s are running Windows 8.1 Pro with Update 1 and are fully patched.

It is a pretty much out the box essentials setup integrated with Office 365 and Windows Azure (For an additional offsite backup) I have added a few additional group policy settings for mapping Network Printers, the Desktop Configuration (e.g. to disable the tablet lock screen) along with opening up open some ports on the client PC?s firewall as required for Sophos Endpoint Security to be deployed.

This has been running for around a month now with only one re occurring issue, randomly when users log on to their PC Windows asks the user to enter their Domain Credentials:

23ra3pv.jpg

?The system cannot contact a domain controller to service the authentication request, please try again later.?

This happened randomly to one user on the Monday after I had set the new network up, however this week its happened to that user again, along with three other users now. It appears once the user has logged on Windows is forgetting the users Domain Credentials:

 

21d0x2a.jpg

 

This basically means folder redirection does not work, no files can be accessed on the server, no printers, about all the user can do is access the internet.

When this has happened adding the user?s Domain Credentials in the Credentials manager appears to have fixed the problem, however im concerned about it happening again, and to other users.

 

1692t08.jpg

 

Basically I?m wondering if anyone has any idea what might randomly cause this, or how I could go about troubleshooting the issue? it really does appear to be very random when this happens.

Thank you!

network settings...

 

do an ipconfig/all on both the server and the client workstation and post them here.  if you don't want them posted pm me. 

 

 

 

99.999% of the time it is an improper configuration on your network card settings, pointing to a dns server out on the web and not the dc as your dns server.  also your server can only be the dns, there cannot be any internet dns servers setup on your nic cards of both the server and the workstations.  the server needs to point to itself, and the workstations need to point to the server for all dns resolution.  the dns service on the server will determine where to send the clients/server when it does a look up.

 

.001% of the time there is something going on and we will need to look at the eventlog to determine.  But being that an improper configuration is the most common cause by a landslide, lets look at your network card configuration on the computer and server.

I have sent you a PM with a full ipconfig from the server and a client PC

 

Thank you in advance for any insight in to this issue.

Domain controller should not be dhcp, I think you will find issues in the log regarding this.

When doing a dc promo, or running the wizard, I am positive it throws up a big warning about dhcp and forces you to manually set the address of the nic before continuing.

I don't think the dns service likes this either and you may see log entries the dns event viewer.

  • Like 1
  On 03/06/2014 at 17:24, sc302 said:

Domain controller should not be dhcp, I think you will find issues in the log regarding this.

When doing a dc promo, or running the wizard, I am positive it throws up a big warning about dhcp and forces you to manually set the address of the nic before continuing.

I don't think the dns service likes this either and you may see log entries the dns event viewer.

Thanks for the advice sc302, I had set the server to always be assigned the same IP address by the router, however that clearly causes issues!

Everything appears to be ok since manually assigning the IP address, and ensuring the servers DNS was set to the same as the servers IP address.

A newbie mistake I have certainly learned from, thanks once again :)

This topic is now closed to further replies.
  • Posts

    • i guess you need to learn hows transformers work and some Electro-inductive polarization before posting stupid answrs
    • Does the 4TB Crucial X10 still have the Data corruption issues that plague the previous generations?
    • Is the Start menu needed? Yes. Is it needed in its current form? No. I run lubuntu, it has all my apps sorted into categories, a bunch of preferences and system tools, the option to turn off, and search. It's all in a small rectangle and does everything you need it to.
    • Star Citizen Alpha 4.2 update lands with radiation hazards, dynamic rain, and more by Pulasthi Ariyasinghe The crowd-funded sci-fi RPG Star Citizen has received another update to its public alpha build. This time, developer Cloud Imperium Games has delivered new features like radiation as a brand-new hazard, irradiated creatures, the first implementation of a dynamic weather system for planets, and more. Dubbed Storm Breaker, Alpha update 4.2's cinematic trailer can be caught above, showing off the new sandbox activity. Storm Breaker is the name of the new sandbox activity too, continuing the ongoing Regen Crisis narrative. Players will be going to Pyro 1 and 4 while uncovering the experimentation secrets of the Associated Sciences & Development company while also weathering a never-ending storm, irradiated zones, and dangerous creatures to complete the event's tasks for hard-earned loot. Speaking of radiation, players will need to wear specialized gear and navigate carefully whenever they come across these special hazardous zones on planets. "This update adds new Radiation accumulation, resistance, and falloff thresholds to player status effects," says the developer. "These effects will appear as new visual and player status cues with REMs on the HUD and can cause consequences resulting in player injury or death if not treated." Locations on Stanton and Pyro planets can now have rain happen on them at various locations and times. Cloud Imperium calls this the first implementation of its Genesis: Dynamic Weather system. When ready, the full version of this tech will be rolling out to many more planets and will supposedly have rain and cloud formations, lightning, relevant audio, water pooling, and clothing shaders for wetness. Other changes of the update include better missile and torpedo tracking, new explorable locations, irradiated juvenile sandworms to fight, fixes for space stations and landing zones to reduce clipping and glitches, and much more. The complete release notes for the update can be found here. Star Citizen Alpha 4.2: Storm Breaker is now available for all backers in the Live channel.
  • Recent Achievements

    • Week One Done
      Wayne Robinson earned a badge
      Week One Done
    • One Month Later
      Karan Khanna earned a badge
      One Month Later
    • Week One Done
      Karan Khanna earned a badge
      Week One Done
    • First Post
      MikeK13 earned a badge
      First Post
    • Week One Done
      OHI Accounting earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      681
    2. 2
      ATLien_0
      269
    3. 3
      Michael Scrip
      209
    4. 4
      +FloatingFatMan
      170
    5. 5
      Steven P.
      148
  • Tell a friend

    Love Neowin? Tell a friend!