Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 48
  • Last Modified:

windows 2012 server gives error

we have windows 2008 domain environment.  users unable to logon to terminal server windows 2012 with error :  the specified domain could not be contacted.
0
shashi patel
Asked:
shashi patel
  • 6
  • 2
  • 2
  • +6
1 Solution
 
RizzleCommented:
Have you tried disjoining and rejoining the RDS server to the domain? Is the servers computer account in AD? Have the users got the correct rights to connect to the RDS server? Is the server physical or virtual? Have you ensured the server is connected to the network?
0
 
Raneesh RamananIT AdministratorCommented:
what was the exact error ? is it showing like this ?The specified domain either does not exist or could not be contacted.”

Could you please confirm the DNS is working fine
0
 
shashi patelAuthor Commented:
Have you tried disjoining and rejoining the RDS server to the domain? yes.
Is the servers computer account in AD? yes.
Have the users got the correct rights to connect to the RDS server? yes
 Is the server physical or virtual? physical
Have you ensured the server is connected to the network? yest
I run nslook up in RDS(terminal) server with dc name & ip & it gave correct results.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
shashi patelAuthor Commented:
pl. note i get this error while doing rdp to windows 2012  terminal server. Then after an hour or so, user can logon without any error & no  changes done by me during this time.
0
 
shashi patelAuthor Commented:
problem yet not resolved. i am getting following event ID s in event viewer.
1023,1054,46,5719,7023
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Please paste an IPConfig /All
0
 
AmitIT ArchitectCommented:
Check system logs first, then application logs for error. Run GPO simulation wizard on this machine from  your DC and check what all GPO's are getting applied on this machine. Sometime OS corruption also causes this issue. You can run sfc /scannow in admin mode and check again.
0
 
compdigit44Commented:
What network are using using please include the driver version..

Have you checked your switch for errors?
0
 
RizzleCommented:
Does this effect a specific server or all servers?
0
 
shashi patelAuthor Commented:
it affect 2 servers with windows 2012 servers.
GPO simulation wizard was successful.
again when this problem happened before some time, i removed its network cable from switch & reconnected. it started working.
0
 
SteveCommented:
in most cases this is a dns issue. are there any events related to the DNS service on either the DC or on the RDP server?
are the users connecting with stored credentials? have you tried getting them to connect manually in case their stored credentials are the issue?

can you log onto the RDP server *while the issue is occurring* using a local account so you can confirm if it can see/ping the DNS/DC servers?
0
 
Rob GMicrosoft Systems EngineerCommented:
what happens if you log into the system using the domainname\username vs the drop down?
Put the Domain info into the host file and give it another shot.. see if that helps
does group policy have the setting checked to wait for the network before allowing logon?
0
 
shashi patelAuthor Commented:
are the users connecting with stored credentials? ..........yes
have you tried getting them to connect manually in case their stored credentials are the issue? .......yes tried but failed.

can you log onto the RDP server *while the issue is occurring* using a local account so you can confirm if it can see/ping the DNS/DC servers?............. yes can log on with localaaccount. can ping dc & dns server with 1 mS speed.
what happens if you log into the system using the domainname\username vs the drop down?...... results r same.
Put the Domain info into the host file and give it another shot.. see if that helps. done but did not work.
does group policy have the setting checked to wait for the network before allowing logon? there is no group policy implemented.
0
 
SteveCommented:
can you log onto the RDP server *while the issue is occurring* using a local account so you can confirm if it can see/ping the DNS/DC servers?............. yes can log on with localaaccount. can ping dc & dns server with 1 mS speed.
Did you try an nslookup at all to confirm the domain resolves?

do you have more than one DNS set on the TS's NIC?
0
 
Rob GMicrosoft Systems EngineerCommented:
How many NIC's are on this server?
Are they teamed?
Make sure you only have one gateway on one NIC if there are more then one.

What is the server connected to?
Is the DC local, no firewall in the network, or separate VLANS?
Is the DC a full DC or a RODC?

You mentioned the DC is a 2k8 server?
What is the domain level?

is the DNS hosted off that server or an external source?
Is there an AV?
What is the AV?
Have you tried without the AV running?

The error you listed...
Is there an event ID that occurs with it?
Does this stop you from logging in, or does this error appear, and still allow login, (Cached)?

Are these servers physical or VM's?
if they are VM's what are they, hyper V or ESXI?
0
 
shashi patelAuthor Commented:
sorry i could not update status since was down with health issue. anyway, problem got resolved, it helped by adding entry of domain controller  in host file of windows 2012 server.
0
 
Seth SimmonsSr. Systems AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 6
  • 2
  • 2
  • +6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now