CryptoAPI error

[Larry McDowall (Symantec)]

Hello Rich,

Thank you for using our online support newsgroups.

On 27 Sep 1998 08:21:44 GMT, Rich wrote:

>I'm trying to make a remote connection from my Windows 98 machine to
>a Windows NT 4.0 machine using either public key or symmetric
>encryption. When I try to connect, I get lowered to PCAnywhere
>encryption, with a CryptoAPI on host error. I looked through your
>site and searched the web, and noticed this is a common problem,
>however, when I applied the fixes, I still get the same error. So far
>I have updated to NT service pack 3 (128 bit encryption), and updated
>using Live Connect to 8.02 (I also restarted the machine after
>updating). Am I missing something here?

Are you using Public-Key or Symmetric encryption (your message states
both)? Your error message regarding Crypto API refers to Microsoft's
Symmetric encryption.

Please double check that both the remote and host have:

1. Symmetric encryption selected in their Security features for
pcANYWHERE32.
2. pcANYWHERE32 8.02 is installed on both remote and host. Check under
the Help menu's About pcANYWHERE32 to confirm this.

If this fails, can the remote connect to another host, or can another
remote connect to your host successfully?

Please let us know if these recommendations do not resolve the issue.
---------------------------
Larry McDowall
Symantec Online Support
Symantec Corporation

Please continue to post your messages to the public discussion groups as Symantec does not provide support via private email.

If you have difficulty getting a response, please read the following article:

Tips on Using Symantec's Online Tech Support Discussion Groups
http://service1.symantec.com/SUPPORT/sharedtech.nsf/docid/1998527114414

For free technical support newsletters, Knowledge Base support articles, our Online Support Genie, and FAQs, visit our technical support page:

Technical Support
http://www.symantec.com/techsupp/
---------------------------

[Jelly Jack]

Hi Larry,
Thanks for the reply. Still having problems though. Both machines are
updated to 8.02, and it happens from 2 different machines. I can make
a connection, but only because I have it set to accept lower
encryption levels. The host is set for public key (which also does
not work, but I think it's because of something I read about problems
with IIS 4.0 keys), so it drops me to symmetric (which is what I have
my remote machines currently set at). That's when I get the cryptoapi
error from the host.
Anything else I can try?

Rich

[Jelly Jack]

Hi Larry,
Wanted to let you know that JellyJack and Rich are one in the same.
Also, I did try a connection between my two machines here. I can
connect them just fine using symmetric level encryption, so it seems
that the problem is with the host.

Rich

[Larry McDowall (Symantec)]

Hello Rich,

Thanks for this information. I assumed that Jelly Rack was you; you
closed with "Rich". Please see my first reply for additional
recommendations. Thanks.

On 29 Sep 1998 19:26:54 GMT, Jelly Jack wrote:

>Wanted to let you know that JellyJack and Rich are one in the same.
>Also, I did try a connection between my two machines here. I can
>connect them just fine using symmetric level encryption, so it seems
>that the problem is with the host.

[Larry McDowall (Symantec)]

Hello Rich,

Thanks for this additional information.

On 29 Sep 1998 06:48:55 GMT, Jelly Jack wrote:

>Thanks for the reply. Still having problems though. Both machines are
>updated to 8.02, and it happens from 2 different machines. I can make
>a connection, but only because I have it set to accept lower
>encryption levels. The host is set for public key (which also does
>not work, but I think it's because of something I read about problems
>with IIS 4.0 keys), so it drops me to symmetric (which is what I have
>my remote machines currently set at). That's when I get the cryptoapi
>error from the host.

Is there anything specified in the host's security section for the
encryption Private Key Container, or the Certificate Common Name? If
so, it may be possible that if Public-Key is failing, it may be
causing some other issue with Symmetric.

I recommend creating a new host item, so that it does not have
anything in these two fields. Just set it to use Symmetric. Also
ensure that you have uninstalled any Public-Keys from VeriSign. Then
try the connection again. If this fails, then I recommend contacting
Microsoft for additional assistance for Symmetric, or VeriSign for
Public-Keys.

Please let us know if you need additional information or assistance
with this issue. Thanks.