Discussion Locked

ATT Global and login scripts

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

Hi,
I have set up AT&T GLOBAL NETWORK access on a number of Toshiba 3020ct Portege laptops. It works great! Most connections are at 56K or a little less. The problem comes in with our login script. SOME of these laptops never get it. They can't even map drives manually. The odd thing is however, that they are able to get e-mail from the exchange server without a hitch. I can get validated in DOS and get the mappings in DOS, but not in windows. They all have Windows 95. Can anyone help me out with this one?

Thanks in advance!

Joe

6 replies

by calves

The fact that some machines get and some don't led me to two possibilities:

first, the Domain controllers all have to have the script in the right folder nt\system32\repl\scripts\import - and the user must have that on their profile in the UserManager for Domains.
If one don't have it and a user is authenticated by it, he/she won't get the scrtipt (if you make changes now, make sure that you syncronize the domain b4 try it again).
Another is the setup on the clients machine, do they have the Clients for Microsoft Networks setup correctly? Right protocols?
and also, on the properties of the dialup, do they have marked, logon to domain?

Good luck!

by jhook

Thank you so much for all your effort. The AT&T Dialer allows us to connect remotely at high speeds to our network through nodes accross the country. The authentication request is getting lost in the "cloud" at AT&T. (They acknowledge no problem on their end of course.) We created a batch file logs on in dos at connection time. We install DUN 1.3 a while ago for Y2k.

by henkverbeek

Try using DNS/WINS when you are using the dailin connection.

I think you have a name resolution problem

regards

Henk

by jdroland

1 and 2 above are both things you can check. Are they getting their email via POP or Exchange Connection? If POP, then they are getting DNS resolutions, but not WINS since they can't map. Are the "no-login script" clients the same ones not resolving names? If not, I remember a couple of years ago having a problem with msnet32.dll on the client not running the login scripts at random. It's probably in technet, but I don't think that's your problem, just resolution.

This discussion is closed to new replies.