Avatar of kpiller
kpiller
Flag for United States of America asked on

Domian controller not respond to UDP 389 query

Hi,

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
Microsoft Server OS

Avatar of undefined
Last Comment
kpiller

8/22/2022 - Mon
DMTechGrooup

Try using etheral and sniff the network to see what is happening on the port.
ormerodrutter

Can you determine if port 389 is actually open?
ASKER CERTIFIED SOLUTION
kpiller

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck