Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

pcAnywhere solution 12.6.7 slow

Created: 14 May 2012 • Updated: 28 May 2012 | 4 comments
This issue has been solved. See solution.

After upgrading to pcA solution 12.6.7, it takes much longer time before successful connect to host computer.
Is there anyway to boost the performance?

Comments 4 CommentsJump to latest comment

ICHCB's picture

Is it just the time to authenticate or is it the remote control performance that is slower for you?

The encryption is higher than it was but don't change it to lower encryption or you can't connect using quick connect any more.     

What kind of authentication do you use NT AD or pcA?   Try pcA as it is local.   If pcAnywhere authentication is fast and it is just NT or AD that is slow there have been some registry hacks to change how authentication is done and you might want to test out.  I would first make sure that the problem is really the authentication step not just a total slow down with the new version.

cheers,

If you find this post helpful please give it a thumbs up!
If you find that this solves your problem please mark it as the solution! 

isaacho's picture

the authentication process takes longer.

We use AD authentication now.

We also use AD to authenticate before we upgrade. we roughly need to wait twice longer than before.

JimChud's picture

Hi,

Theres a hotfix for this that i run out to our clients via a hotfix.

http://www.symantec.com/business/support/index?page=content&id=TECH109926

If this doesn't work there is also a Tech guide that goes in to what to try afterward attached:

http://www.symantec.com/business/support/index?page=content&id=TECH174098

Hope this Helps

 

Regards Jim.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem and give a thumbs up to useful comments, articles and downloads.

SOLUTION
ICHCB's picture

hopefuly the quick ads auth key works.  The patch in the second kb isn't for the 12.6.7 version of the product.   If the quickadsauth key doesn't do the job then a new verison of the file attached to TECH174098 would need to be requested.

cheers,

 

If you find this post helpful please give it a thumbs up!
If you find that this solves your problem please mark it as the solution!