3000 NT domain\username authentication

[bdedek]

Hi,

Is there a way to force a Windows domain prefix or, prevent or strip the Windows domain portion of a username on the 3000 client so as to lock a person into authenticating against the domain controller specified in the configuration? A company has a trusted domain configuration with strong passwords on the authenticating server for the 3000. However, their users are able to prefix their username with a trusted domain and use a less secure password to obtain access to the VPN 3000.

[mostiguy]

I am not aware of any way to do that.

Why are not all domains at the same password strength level? There is no point to having a strong password policy for domain A if it trusts B, which has a weaker one, as users residing in B can then generally access resources in A.

Also, it sounds like users have a choice of user accounts - accts w/ strong passwords in A, and weak in B. Is there a reason for this?