No you can use something like selfssl to generate it.

Thanks,
Brian Desmond
[email protected]<mailto:[email protected]>

c - 312.731.3132

From: Chyka, Robert [mailto:[email protected]]
Sent: Friday, November 20, 2009 1:35 PM
To: NT System Admin Issues
Subject: RE: Cisco Question

Oh sweet... do we need a dedicated certificate server?  Well I will research 
instead of bothering you...

________________________________
From: Don Ely [mailto:[email protected]]
Sent: Friday, November 20, 2009 2:32 PM
To: NT System Admin Issues
Subject: Re: Cisco Question

Roll your own internal, doesn't have to be public...
On Fri, Nov 20, 2009 at 11:29 AM, Chyka, Robert 
<[email protected]<mailto:[email protected]>> wrote:
Thanks for the extra pointer...  Who has cheap certs?  I haven't shopped for 
one in a few years when we redid our Exchange box.

________________________________
From: Don Ely [mailto:[email protected]<mailto:[email protected]>]
Sent: Friday, November 20, 2009 2:27 PM
To: NT System Admin Issues
Subject: Re: Cisco Question

create an ACL allowing only access from their IP address to your NAT'd address. 
 Also, I'd put an SSL cert on your AD servers and use 636 instead...
On Fri, Nov 20, 2009 at 11:25 AM, Chyka, Robert 
<[email protected]<mailto:[email protected]>> wrote:
Hello,

We have a Library Catalog server that is hosted by the company that we 
subscribe to their databases.  It is a server dedicated to our school, but 
hosted in their data center.  They need to have LDAP access from their 
outsourced box to our internal AD Controllers for LDAP authentication for our 
users to the database server.

Our AD servers sit behind a ASA Firewall.  How would I set up the rule to allow 
port 389 to be open for the IP address of the outsourced server?

Any help is greatly appreciated.

Bob























~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to