Networks

Ask something
Discussion Locked

Domain Access/login scripts via VPN

0 helpful
5 replies

by kevin.murphy

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello,
We are currently developing a VPN solution involving a national ISP and CheckPoint SecuRemote VPN.
The idea is to dial into the ISP, then establish the VPN connection. This in of iteslf works well.
My issue is that I want to be able to have the users be able to authenticate to the domain, and run the login script. I'm open to any way that this could be done, but I need a manageable solution that win9x, NT and 2000 users can us that doesn't involve managing individual laptops.
I'd really like a way to have the domain login box show up again, but am open to other alternatives.
Currently on 9x clients, if "logon to network" is checked, then the "no domain server available" box results when you try to logon. If you click OK to this, and then try to map drives, they work.
However, I'd like a solution that doesn't involve error messages so that I can support a community of not-very-computer-savvy users.
Might there be a utility out there somewhere? I way to get the domain login sequence to show up again?
Any help would be most apprecated.

Kevin Murphy
kevin.murphy@paymentech.com

5 replies

by filip.francis

Hi Kevin,

You need to use the properties of the lmhosts file.
You need to make sure that the file is in the right directory
for NT it is winnt\system32\drivers\etc
for win95/98/ME it is windows

Also make sure that the lmhosts file is not with an extension it has to be LMHOSTS
in that file you can put all the servers and domains.

if you need an example just send me an email
filip francis
email:ffrancis@mce.be

by kent.manley

The real problem is the way Microsoft has the login set up. There is one and only one "login event," which fires off the domain name registration and login script events. So basically, if you set up a couple of prerequisites, you can do what you want. First, have your users CANCEL the logon screen when they login. If possible, have the Windows Networking (three boxes with Domain Name) and Window (two boxes, name and password only) passwords synchronized in advance. Second, ensure that the clients (laptops) are using the 1.3 version of the Dial Up Networking client, which should fire the login event after the connection is made.

The LMHOSTS file also is helpful, however, depending on how your infrastructure is set up, dns and/or wins should take care of those identification issues.

Good luck.

Kent

This discussion is closed to new replies.