Fatboy0341
IS-IT--Management
OK - very simple:
We have a Webserver at a vendor's location that we need to connect to our network for LDAP purposes.
We created a security group in AD, created a domain user and added that user to the new security group.
We created a domain user with the same name on the vendor's domain and created a profile for it on the Webserver at their location. We also made sure that the passwords match.
We added the Secure Access client to the start up group of the server. We also checked the box for "single-sign on" in the Properties of the account on the Access Gateway.
Out intention or need is to have the client open and connect to the gateway automatically upon reboot or logon.
Here's the problem:
If we reboot the machine - the Access Client opens up and attempts to log on - but we get an "Authentication Failed" message. The correct username is in the field, nothing in the password field (expected). If we enter the password, it connects. If we close the client and open it again - it logs on automatically with no prompting. If we reboot again - same thing - "Authentication Failed".
My guess is there's some setting that clears the cache upon a reboot, thereby requiring it to be re-entered. What I am not sure of is whether that's just a default setting that can't be changed or is there somewhere to change it?
I think we can write a VB script that will run at the end of startup which will enter the password and key Enter - but I'd like to keep this within the confines of the applications already involved if possible.
Any suggestions?
"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."
We have a Webserver at a vendor's location that we need to connect to our network for LDAP purposes.
We created a security group in AD, created a domain user and added that user to the new security group.
We created a domain user with the same name on the vendor's domain and created a profile for it on the Webserver at their location. We also made sure that the passwords match.
We added the Secure Access client to the start up group of the server. We also checked the box for "single-sign on" in the Properties of the account on the Access Gateway.
Out intention or need is to have the client open and connect to the gateway automatically upon reboot or logon.
Here's the problem:
If we reboot the machine - the Access Client opens up and attempts to log on - but we get an "Authentication Failed" message. The correct username is in the field, nothing in the password field (expected). If we enter the password, it connects. If we close the client and open it again - it logs on automatically with no prompting. If we reboot again - same thing - "Authentication Failed".
My guess is there's some setting that clears the cache upon a reboot, thereby requiring it to be re-entered. What I am not sure of is whether that's just a default setting that can't be changed or is there somewhere to change it?
I think we can write a VB script that will run at the end of startup which will enter the password and key Enter - but I'd like to keep this within the confines of the applications already involved if possible.
Any suggestions?
"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."