Discussion Locked

Login scripts for remote users

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

We're running NT 4 with Proxy Server 2 controlling access to our DSL line. Our CFO has gone part time and moved to the country. I've set him up with a local ISP and created a VPN connection so he can connect to the ISP, then click the VPN connectoid, and he's logged on to the system. This works fine for Outlook synchronizing with MS Exchange.

However, now he wants access to data files. That's handled by "use" commands in a KIX32 command file called by startup.bat in the server's \netlogon share, and startup.bat is set in User Manager to run as the login script. This works fine when he (and everyone else) logs in locally.

However, it doesn't run automaticcally when he logs on from home, and when he tries to run it manually it gets a GPF. Can anybody tell me why the login script doesn't run automatically for remote logins, and how to fix that?

Thanks,
Kevin

9 replies

by calves

a simple batch file with Net use commands works fine. Why don't you create a Batch logon file and set it for the remote users?
You need more help, send me a note.

Good luck!

by jewright

You will be better off if you simply talk him through creating a shortcut on his desktop to the drive he wants. This way you don't have to map a drive and will not have to disconnect the drive when he logs off of your network (un-connected mapped drives are a real pain in the Windows Explorer)

If I rember right, the issues is a known problem with KIX32 but I can't find the article so I can not be sure.

Thanks.....Jeremy

by curlergirl

Have you installed the necessary KIX32 files for Win95 on this remote workstation? You could try this if not. Another simple solution would be to write a plain (non-KIX) batch file to map drives and put it on his desktop. He can then double click to run it manually after he has connected to the office. Hope this helps!

by bblunden

First, everybodys answer before mine was good advise (for the most part). However, it would appear that the solution might be simple.

It sounds like your question is, "Why isn't my RAS user running the same logon script as local users?"

Do you have "Client for Microsoft Networks" configured on the remote machine? If not, go to Network Neighborhood - Properties and make sure that it is installed and "Windows Logon" is still the "Primary Network Logon"

As someone who uses the login script as a way to make sure my users have the latest virus definition loaded, you may want to look at your login script and see if you can put a few "IF EXIST" commands to bypass any long instructions.

Hope this helps. Feel free to email me for more information.

Good luck,
Bill Blunden

This discussion is closed to new replies.