troubleshooting Question

Domian controller not respond to UDP 389 query

Avatar of kpiller
kpillerFlag for United States of America asked on
Microsoft Server OS
3 Comments1 Solution3166 ViewsLast Modified:

We have 3 MS 2003 domian controllers that are not authenticating users. When doing a port query to UDP 389 it fails. As of yet we have not been able to determine what is blocking port 389 for LDAP requests.

I have been working with MS on it but no luck with them yet.

The domain controllers have Exchange 2003 on them along with McAfee Virus Scan and Groupshield for Exchange (groupshield uses Java). We have stopped all McAfee services and still cannot query port 389. Port blocking in Virus Scan is also turned off.

Is there a way I can determine what service or process is using 389 or blocking it. MS wants me to disable all non MS services and reboot the server. I would think there is a better way to just find out what is using 389. We are a 24/7 operation so I'm hoping not to have to down the server like that.

Thank you very much

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 1 Answer and 3 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 3 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros