Discussion Locked

Login Scrip not Functioning

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

I have recently change our IP address from private to Class c. I changed the DHCP information to reflect the new IP address and scope range. Changed the IP address manually on all PDC an BDC. WHen I log on to the NT machine, my script works great.However, when logging on to the clients machine (95 - 98), it authenticates the user but doesn't run the scripts. I have check all users to ensure the script is there and working. All this worked great until I change the IP address.... any idea asto what it may be?

THanks!

15 replies

by ben_az

This does not sound like a tcp/ip issue but more like a rights issue. Are you sure that you did not modify the rights for your users. Also if you use winipcfg on the Win95/98 stations are they being assigned correct IP addresses from your new IP scheme?

by ahartman

Your problems are most likely caused by an ip lease on the win9x machines. Use the wincfg comand and release the machines from the old ip scheeme. Then reboot the machine and see if you are getting the right ip by issuing the same command.

by fpillow

maybe they are hitting a different BDC due to the new network configuration and the scripts aren't replicated there yet?? Can you tell if they are still being authenticated by the usual domain controller?

by lorelli

Are you using lmhosts files? It sounds similar to the problem I had where we
were getting authenticated, but we couldn't change passwords, among other things.

If you are using lmhost files, make sure that the file on the workstation has the correct address for the PDC. Also make sure, that if you are using an "include statement" that it points in the right place.

You can do an "nbtstat -R" and then "nbtstat -c" to purge, refresh, and view cache, but I would just restart it to be sure.

An lmhosts file that incorrectly points to the PDC causes some strange problems.

Hope it helps.

by tfran11

Upgrade all clients to Windows NT Workstation. Windows 95 or 98 clients will not be able to authenticate to this change because they use a different method of authentication.

by sdfgsdf

check the permissions on the scripts to ensure that they are at least read only.

by bill.parks

Make sure to replicate the logon scripts to all Netlogon shares in your network, i.e. NT's Replication, Robocopy, or manual copies... 95/98 by default always hit the same PDC (there is a load balance feature through policies or manual Reg edits), make sure this PDC is in the same subnet as the clients. To check the DC they hit, type echo "%logonserver% at a DOS prompt. Verify that DC's Netlogon share has your logon scripts.
If using NT's Replication, make sure to explicity specify the server names you are importing from and exporting to. This used to be a problem in subnetted enviroments.

This discussion is closed to new replies.