Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

PCAnywhere 12.5 Not Promting to Confirm Connection

Updated: 21 May 2010 | 7 comments
lone_ranger's picture
0 0 Votes
Login to vote

I have created an Autostart - Host package using the packager and have included my custom . BHF and .CIF files. I chose the options to run as a service (success) , what AD group to allow connection (success) , and prompt to confirm connection which is not working. When I connect to the host, I type in my user name, password, and domain name and I'm automatically in which is not going to work for our security team. I’ve double checked to make sue that it is using my customized file by looking at the registry as well as changing the option to do so when I created the msi.

Does anyone know of the registry key I can use to enforce this? I look at this link but can't really seen anything.

http://service1.symantec.com/SUPPORT/pca.nsf/0/223...

discussion Filed Under:

Comments

ICHCB's picture
16
Jul
2009
1 Vote +1
Login to vote

In your host do you have the check box to disconnect if time out

In your host do you have the check box to disconnect if time out on the security tab?   If you don't then it will prompt the user and then after the # of seconds that you selected it will let you connect.   You need to check the box Disconnedt if time out if you want to be denied connection if no one at the host allows your connection. 

 imagebrowser image
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! 

thomas.hoefler's picture
20
Aug
2009
0 Votes 0
Login to vote

I have the same problem

I have the same problem here.
Has anybody a solutuion for this "Bug" ??

ICHCB's picture
20
Aug
2009
1 Vote +1
Login to vote

In your host do you have the check box to disconnect if time out

Thomas,  

Have you confimed the settings noted in my last post?  That you have the same problem isn't very helpful.  The steps you are takeing and the settings you have selected may be more helpful to finding a resolution.

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! 

thomas.hoefler's picture
20
Aug
2009
0 Votes 0
Login to vote

offcourse i have confirmed

offcourse i have confirmed the settings!

ICHCB's picture
21
Aug
2009
1 Vote +1
Login to vote

Would you mind elaborating on how you have it set up?

Based on results it seems like a setting some place is not set up correctly with your host.   Possibly if you were to provide some details on how yours is set up you and I could determine what is different in your environment that isn't working and mine that is.

My set up is 12.5 build 442 and the connections are network based with pcA authentication.

How are your callers set up?  are they super users?  This also allows the bypassing of the prompt if you don't want your users supper user then uncheck that and specify the individual rights that they should have.

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! 

thomas.hoefler's picture
24
Aug
2009
1 Vote +1
Login to vote

Hi! i found the problem in

Hi!
i found the problem in our environment.
the remote user was defined as Super User ....

thanks for your help!

ICHCB's picture
25
Aug
2009
1 Vote +1
Login to vote

Glad we got to the bottom of that.

Thanks for posting back that that was the issue.  It helps for any one else that sees this post at a later date.    Glad I could help.

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!