User assignmet problem (The server is not operational)

[norberts]

Good afternoon!

After full 3 days of reading manuals and installing software and setting up a new server, I have managed to set up a 90day evaluation version (got ir from local software distributer) of ePo 4.5 with all extensions including Data Loss Prevention 9.1.0.504 with full 90-day McAfee Host DLP Full License.

It's installed on a separate server (file server) that is joined into our main domain controler.

Also WCF service works on the same server as McAfee ePo.

But after starting to do some tests on DLP server (ePo), to check how the offered features work, I got stuck!

The problem starts in "DLP policy" section, when you want to assign any policy (e.g. device policy) to an AD user, the "User Assignment Group" windows opens, then you press "Add..." and an Error jumps out saying:

"Failed editing user groups and OU. Exception information: The server is not operational. Name: "ABC"" See attachment.

I can't list the AD users.

This means, that for now I can't test the software properly.

The DC server works fine. The DLP server can list the Active Directory outside off the ePo, e.g. assign security user right to a folder, where AD is lised when you open User assignment window.

Could you please help, or point me to the right direction where to look, because I have read all the manuals and guides that came with this test package and nothing!

Thank you in advance,

N

[norberts]

Good morning!

Any ideas?

Message was edited by: norberts on 5/23/11 1:13:02 AM CDT

[norberts]

Good morning!

Fixed it myself!

Everything works now fine! The error does not show anymore and AD is properly read!

The problem wasn't on the McAfee side, but on the server side.

If you need more details, ask!

Have a good day you all!

[SafeBoot]

so, what was the problem? If you can tell us here, others can learn from it.

[norberts · Accepted solution]

The problem was hiding in Network Connections settings.

I have a separate DNS server and DC server, so in Network Connections by default as Primary DNS server I entered DNS servers IP, but to fix the issue I entered DC (AD) servers IP into secondary DNS servers field.

Thats it!

Hope this helps someone!