SNX VPN & Windows domain

[curmudge1]

Just testing Connectra's SSL Network Extender, and I ran into this problem.

Got the SSL Network Extender VPN working OK, I think, but this is the problem we're experiencing: When someone takes their laptop out, they login in using cached credentials, since the laptop cannot "see" our Windows 2003 Server Active Directory controller. Then, they connect via SSL Network Extender. When they try to see the Windows 2003 server shares in a Windows browser (e.g., \\server), they get prompted for the username & login: our_domain\username and user_password. Then they get a message to the effect: "the user name you typed is the same as the user name you logged in with. that user name has already been tried. A domain controller cannot be found to verify that name". Any fixes/workarounds? Seems to be a Windows phenomenon. If the remote user isn't logged into our domain before connecting w/ SNX, he/she can supply domain login when accessing the windows server & it works just fine, displays shares & can access the shares. The problem is only when a user is off-site & logs in on the laptop with their domain username & password.

We're not interested in using the Connectra's portal features, just the SSL VPN.

[RayPesek]

You might want to re-post this in the Connectra section.

Are you using Application Mode or Network Mode with SNX?

What version of Connectra?

Ray

[curmudge1]

Got a fix for this...

We aren't running Active-Directory integrated DNS... so we had to set up a special internal DNS with AD-required records. Some SRV, some A. That was the fix. And changed the SNX setting on connectra to use this dns server.