unable to connect to domain

when using the 'Network ID' button, after entering the domain name, I get a window asking for username, password and domain. after entring I get error "The specified server cannot perform the request iperation."

When using the 'Change' button i get the error:

Note: This information is intended for a network administrator.  If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt.

DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain "MYDOM.com":

The query was for the SRV record for _ldap._tcp.dc._msdcs.MYDOM.com

The following domain controllers were identified by the query:
MYDC.MYDOM.com


However no domain controllers could be contacted.

Common causes of this error include:

- Host (A) or (AAAA) records that map the names of the domain controllers to their IP addresses are missing or contain incorrect addresses.

- Domain controllers registered in DNS are not connected to the network or are not running.

LVL 3
OrenRozenAsked:
Who is Participating?
 
iimtiazConnect With a Mentor Commented:
Well, it seems  that there might be some communication gap b/w client and AD/DNS. Verify is there any firewall enabled on client or any other application which is playing a role like firewall.
Thanks
Iftikhar
0
 
Mike ThomasConsultantCommented:
Is the client machines dns servers set to that of your domain controller?

Where id you run dcdiag from?
0
 
mudassirahmedCommented:
The issue may be the DNS..

Your AD/DNS Server should have the DNS IP Address of itself....then configure your workstation's IP Address with the DNS IP of your AD/DNS Server....

Then try to join the workstation to the domain
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
OrenRozenAuthor Commented:
yes.
ran dcdiag from the DC. passed all tests.
0
 
OrenRozenAuthor Commented:
to mudassirahmed:
the WS dns is set to the DC IP.
the DC main DNS is set to its local IP.
0
 
mudassirahmedCommented:
i didn't understand

Is your client machine contains the Preferred DNS server as DC/DNS server IP?

0
 
OrenRozenAuthor Commented:
to mudassirahmed:
this link is in case the WS cannot find the DC. This is not the case here.

this is the error i get:

DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain "MYDOM.com":
The query was for the SRV record for _ldap._tcp.dc._msdcs.MYDOM.com

The following domain controllers were identified by the query:
MYDC.MYDOM.com

However no domain controllers could be contacted.
0
 
OrenRozenAuthor Commented:
to mudassirahmed:
>i didn't understand
>
>Is your client machine contains the Preferred DNS server as DC/DNS server IP?

the client Preferred DNS server is set to the DC (also the DNS) IP.
0
 
Mike ThomasConsultantCommented:
from the client can you ping the following ok

DC Server IP
Hostname MYDC
Domain name MYDOM.com
?
0
 
mudassirahmedCommented:
0
 
PorpathamCommented:
This PC was Caused by Virus. When virus affects DNS Cache will be lock and and the cache size will be reduce. Some entry there to enter in regedit.

I will try to upload it soon.
0
 
OrenRozenAuthor Commented:
the problem was with the local firewall.
added ALLOW rule to/for the DC.
0
 
terrybuck9Commented:
I Just got a new Dell laptop with Trend internet security installed.  I got this same problem not being able to connect to domain.  Disabled Trend, and it all worked. Thanks Terry
0
All Courses

From novice to tech pro — start learning today.