Security package specific error occurred when trying to connect to Orchestrator with remote Runbook Designer

Question

When I try to connect to Orchestrator server with Runbook Designer installed on my laptop I get an error saying "A security  package specific error occurred.".
Entry from Designer log file is below. I've tried to set error level to 3 and 7 but got no additional info about the error. I'm unable to find any details of the error on server or client side in any logs (Event Log or Orchestrator trace logs).
Connecting to Orchestrator Management Server with local Designer installed on the server works fine. 
Orchestrator is installed in AD environment and security groups are properly configured.
Can anybody help?
2012-06-12 11:35:51 [7472] 1 Exception caught in long __cdecl `anonymous-namespace'::connectCommunicator(struct HWND__ *,const class std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class std::allocator<wchar_t> > &)
Connections.cpp(238):
<Exception>
<Type>Opalis::Exception</Type>
<Location>
void __thiscall ServiceCommunicator::connect(const class std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class std::allocator<wchar_t> > &)
ServiceCommunicator.cpp(118)
</Location>
<MsgCode>A security package specific error occurred.
</MsgCode>
</Exception>

Answer 1

I'm having a similar issue with one of our runbook servers. i cannot deploy any IPs to it. I get the error "A security package specific error occurred". I can open the designer on the runbook server, connect to the management server, and look at
runbooks. They wont run on the server without the IPs though, but it doesnt seem like a connection issue. i have also tried uninstalling/re-installing the runbook server and i get the same. 
Has anybody else run into this? 
Edit:
Heres an error fromthe event log:
The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server <Service Account>. The target name used was HOST/server.domain.domain.com. This indicates that the target server failed to decrypt the ticket provided by the client. This can
occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Please ensure that the target SPN is registered on, and only registered on, the account used by the server. This error can also
happen when the target service is using a different password for the target service account than what the Kerberos Key Distribution Center (KDC) has for the target service account. Please ensure that the service on the server and the KDC are both updated to
use the current password. If the server name is not fully qualified, and the target domain (domain.domain.COM) is different from the client domain (domain.domain.COM), check if there are identically named server accounts in these two domains, or use the fully-qualified
name to identify the server.
So maybe I was just given the wrong account.
- Slow is smooth and smooth is fast.