Securemote41 Problem with "error. communcation to site xxx has failed"

[faisulh]

We have just implemented the latest version of Securemote 4.1 Sp-3 3DES Build 4176 on NT 4 Workstation with sp6 for NT. The problem we seem to be experiencing is for our laptop users, everytime the securemote client loads up, it tries to initiate the daemon, before the user has dialed into the isp, causing it to give the error msg "error. communcation to site xxx has failed". Is there anyway we can edit or configure the userc.c to reflect that it doesn;t do the initiating before it makes a connection with the isp.
Help on this would be very much appreciated.

Faz

 

[dwilkinson]

I don't know about modifying the users.C file as you asked, but there are two other ways we have dealt with this.

1) Make SecuRemote NOT launch on startup - instead create a shortcut on the desktop or in the Start menu so that they can launch in manually after connecting. (Remove the executable from the registry - "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run".

2) If your users are accessing an NT domain, use the "Secure Domain Login" (SDL) feature to locally store encrypted NT credentials for a properly sequenced login.

Hope that helps.
Don

 

[KOATT]

Does this feature not exist in v 4.0? This would be a good reason to upgrade.