The specified domain controller could not be contacted

Im trying to access information and devices on my network but im getting the following message.

I'm not able to manage my group policy through the group policy management console nor can i search for printers in the active directory listing.

Any help? Please note that im using windows server 2k3 standard and a pix 501 firewall.

Thanks
Salim

The specified domain controller could not be contacted. This affects the following domain in the console.
Domain: admin.jordan.local

The error was:

The specified domain either does not exist or could not be contacted
skhutatAsked:
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.

bmquintasCommented:
Is the pix firewall between the pc you are using and the domain controller? Try to detail your network diagram.
Also check for the dns settings, as Active Directory depends heavy on DNS.
0
Jay_Jay70Commented:
Hi skhutat,

can you post the exact error including the event number - this helps big time with these errors

no firewall enabled on your macine?

Cheers!
0
skhutatAuthor Commented:
Bmquintas, The pix firewall is not between between me and the rest of the network. Here's a short description of my network:

T1 modem ---> Pix 501 firewall -->router -->switches --->clients

The reason i mentioned the pix 501 is because all these problem occured when we had an extended power outage and some settings seemed to have been erased from the firewall, such as dynamically assigning IP addresses to clients. Perhaps the pix has some settings regarding the active directory listings?

0
Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

skhutatAuthor Commented:
HI Jay Jay,

Unfortunaltly, I didnt get any errors at all in the pop up window. I copied everything from the window as I saw it. I hope that helps.

Thanks
Salim
0
Jay_Jay70Commented:
can you check your event viewer for me   right click my computer and select manage
0
skhutatAuthor Commented:
I  checked it and i think the following is the only one relevant that shows up when I try the GPMC.

Source: UserNv
EventID: 1053

Windows cannot determine the user or computer name. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0
Jay_Jay70Commented:
0
Jay_Jay70Commented:
sorry wrong error - are your dns settings pointing to the DC as primary
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
skhutatAuthor Commented:
"are your dns settings pointing to the DC as primary" could you explain that to me again please, the default gateway is pointing to 192.168.1.1 - which is my firewall.

DHCP is pointing to 192.168.1.5 - which is my server

however, the DNS servers entry is pointing to 66.XX.1.2 and 66.XX.2.2

On my w2k3 server, the dns server shows as 192.168.1.5 and the directory lists fine in there. Could that be the problem, the DNS server isnt configured correctly?

Thanks
Salim
0
Jay_Jay70Commented:
what are those 66.x.x.x. adressess?

your dns servers should point to themselves and any ISP dns servers as forwarders
0
skhutatAuthor Commented:
these are external IP addresses , the static IP address I have is 66.xx.1.1XX .
0
skhutatAuthor Commented:
I just did someone that seemed to have fixed the problem. I manually assigned my network connection the IP address, gateway, dns, etc. parameters and then took it back to the dynamically assigned settings and problem Solved!

Jay Jay, you pointed me into the right direction, you deserve the points. Thanks.

Salim
0
Jay_Jay70Commented:
ah well thanks mate,

as long as your DNS settings are pointing to the internal IP range you are using you shouldnt have any grief in the future

Thanks Salim

James
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
Windows Networking

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.