Encryption password for SNAC DHCP integrated enforcer
Created: 14 Mar 2011 | 9 comments
I've confirmed the encryption password (using ODBC and PHP settings) but I still can't get the coneection between the enforcer and SEPM to work. The red icon keep on and integrated enforcer does not show up on SEPM console.
Discussion Filed Under:
Comments
which version are you
which version are you running?
Thanks
Im running 11.0.6 MP2.
Im running 11.0.6 MP2.
any error message in the
any error message in the logs?
Cheers!
Pete
Help Link: http://www.symantec.com/business/support/overview.jsp?pid=54619
The NAC enforcer console does
The NAC enforcer console does not show any error, in debuglog file I see:
SPM return bad request for the registration request!! Share secret could be wrong!
Registration failed!
But as I said I've confirmed the encryption password.
Hmmm
Hello,
I understand, however, logs are not wrong either...
This is caused by a mismatch of the encryption password (pre-shared secret) between the Enforcer and the SEPM server. The encryption password string entered in the Enforcer GUI has to be exactly the same as the string entered on the SEPM server during installation.
Mithun Sanghavi
Symantec Technical Support Engineer, SEP
MIM | MCSA | SCTS | ITIL v3
Follow me on Twitter: @mithun_sanghavi
Don't forget to mark your thread as 'SOLVED' with the answer that best helped yo
hi
can you check if you are able to type the special charectors in the console..does your password has special char?
I spl char is not getting typed
Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq
Password does not have
Password does not have special chars, its a very simple one. Thanks.
I used the steps in this
I used the steps in this topic:
https://www-secure.symantec.com/connect/articles/how-find-database-password-odbc
The password that appears is exactly what I'm using at the enforcer configuration.
no clue?
Don't know what to do here to make MS DHCP Integrated Enforcer work with SEPM. I have two sites, one I used to migrate from the other, both have the same encryption password and I get the same "Share secret could be wrong" error on both servers.
Would you like to reply?
Login or Register to post your comment.