I have setup an isa server to allow LDAP through to an Oracle database on port 389.
For some reason though the rule is not seeing the ldapsearch as ldap traffic and drops the connection. If I throw in a allow all rule it will be allowed through but of course it isn't published to the database server I need it to.
I have a protocol created for ldap and created a published rule for it but I am not sure what I am missing.
If I go from the server and do a direct connection with ldapsearch it works fine and isa allows the connection and I get the info I need. Not sure why the connection coming in to the production interface is not seen as 389 traffic outside of the logs is there a way with ISA to see that actually port it is coming in on?
More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.
There are three types of ISA client that can be configured - these can be individual clients or multiples of a client on each PC or server
SecureNAT. A SecureNAT client for ISA server is a client machine, work station or server, that has its defa…
I have been asked to explain on many, many occasions the correct way to setup network cards and DNS settings on ISA Server 2004, 2006 and forefront Threat management gateway (FTMG) and have willing done so. I have also promised my self everytime tha…