[ExchangeList] Re: LDAP port 389 problem

http://www.msexchange.org
-------------------------------------------------------Do you have Exchange 
installed on a DC?

-----Original Message-----
From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Jin Siew
Sent: Tuesday, January 30, 2007 4:15 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] LDAP port 389 problem

http://www.msexchange.org
-------------------------------------------------------Hi! Have a
problem with one of our exchange servers. The LDAP protocol is already
enabled, port 389. But it is not accessible and when we did a netstat
-a, we cannot see this port being listed. Not sure what else to check or
how to fix this problem. Appreciate any help and advise. 

Thanks! 

Regards, 
Jin
-------------------------------------------------------
List Archives: http://www.freelists.org/archives/exchangelist/  
MSExchange Newsletter: http://www.msexchange.org/pages/newsletter.asp 
MSExchange Articles and Tutorials:
http://www.msexchange.org/articles_tutorials/ 
MSExchange Blogs: http://blogs.msexchange.org/ 
-------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com 
-------------------------------------------------------
To unsubscribe visit http://www.msexchange.org/pages/exchangelist.asp
Report abuse to listadmin@xxxxxxxxxxxxxx 

-------------------------------------------------------
List Archives: http://www.freelists.org/archives/exchangelist/
MSExchange Newsletter: http://www.msexchange.org/pages/newsletter.asp
MSExchange Articles and Tutorials: http://www.msexchange.org/articles_tutorials/
MSExchange Blogs: http://blogs.msexchange.org/
-------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com
-------------------------------------------------------
To unsubscribe visit http://www.msexchange.org/pages/exchangelist.asp
Report abuse to listadmin@xxxxxxxxxxxxxx

Other related posts: