Port 3269 not available on Domain Controller?

I have upgraded my domain controllers to Windows server 2003 R2 SP2 x64 bit and since then no one can do ldap queries on port 3269 i have no firewalls between the machine i am using an the DCs and telnet machinename 3269 gets accepted then instantly closed. Please help
imcservicesAsked:
Who is Participating?
 
PlaceboC6Connect With a Mentor Commented:
You have to install a certificate:

http://support.microsoft.com/kb/321051
0
 
PlaceboC6Commented:
3269 is the SSL port for a global catalog only.

389 is the standard LDAP port.
3268 is the standard Global Catalog port.
0
 
bhnmiCommented:
Why on that port?
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

 
PlaceboC6Commented:
As in my previous post,  I would try 389.  If the server is a global catalog,  you can also do 3268.  Those are only available if the server is a GC though.
0
 
imcservicesAuthor Commented:
3268 works just fine however we need to make 3269 work and for some reason it doesnt. I neve set anything up to make it work on the previous server other than make it a GC. Any other suggestions?
0
 
imcservicesAuthor Commented:
Thanks for you help i will try to recover the previous certificate.....
0
 
PlaceboC6Commented:
You are welcome.
0
All Courses

From novice to tech pro — start learning today.