Logon Script Problems

I wanted to know if anybody could tell me what could cause this problem:

We have a mixed NT/W2K network.  The only NT machines are our DCs.  Well, first of all the replicator does not work on it, and we are using a program called robocopy.exe to copy all of the domain info off the PDC to the BDCs.  Now we are constantly getting calls from different users that have problems getting the logon script to run on the computer that person works on, but when someone else logs onto that PC, they get a logon script.  Then we ask the person that can not get the logon script to try another PC, it works and the logon script works well.  Do anybody know how we can resolve this issue?  It is a real pain.  Thanks.
ckt-77Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

BembiCEOCommented:
I would say, go to the machine which failed, logon as user who failed, open explorer, navigate to the LOGON directory of your server and try top run the script manually. Make sure, that you run the script from that server, where the client really logs on. You can use WINS or the registry to determine the Logon-Server. Maybe there is something wrong with the combination of logon-server and access permissions.

If your replicator is not working, there must be something wrong with the configuration. I made the experience, that you have to add the replication agreement manually (nevertheless it should work automatically), but we've got it allway to run.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
helpnetCommented:
It would be good to resolve the replication problem, and I would go with the above suggestions, but if that fails, disable replication before using robocopy.

Do you know if the script is not working at all on the problem machine/login combinations, or in part.  Do you use the environment variable %LOGONSERVER% in your logi scripts.  

It may be useful to determine if the problem logins are using a BDC or a PDC at the time.  To double check go to a command prompt and type set, and look for the value of LOGONSERVER.

Are there any error messages in the workstations event logs at around login time that may point to a solution.  

If the person having the problem logs out and logs in again, does the login script run on the second login?

Regards

Anne
helpnetCommented:
It is possible some of the win2k machines are having name resolution problems at the time of the first login, are using a cached profile, by the second login the name resolution is working and a real/online login complete with login script is occuring.  If this is the case, check netbios over TCPIP is configured on the machines in question, and look at NBTSTAT to assist with troubleshooting.  

A Windows NT server and Windows 2000 workstations is not an ideal configuration, and funny problems often occur.  W2K workstations work best with an Active Directory, which requires Windows 2000 Servers or better.

Regards

Anne
Defend Against the Q2 Top Security Threats

Were you aware that overall malware worldwide was down a surprising 42% from Q1'18? Every quarter, the WatchGuard Threat Lab releases an Internet Security Report that analyzes the top threat trends impacting companies worldwide. Learn more by viewing our on-demand webinar today!

helpnetCommented:
Windows 2000 workstations tend to preferentially use DNS for name resolution, Windows NT servers are not equiped with a DNS server that is able to have service entries typical for an Active Directory (which is probably what a W2K workstation looks for preferentially when trying to find a domain - I do not know enough about the inner workings of name resolution to be certain) using and specifying a wins server may help.  Windows NT computers tend to preferentially use NETBIOS and Wins for name resolution.  In my experience in a mixed environment name resolution can be dodgy, and using WINS can help stabilise things somewhat.
PaulHiebCommented:
Shouldn't be anything wrong with this scenario, but the lack of replication is a deep concern in my book, this points an ugly finger at the servers being a few fries short of a happy meal -- lacking some basic NT server functionality. Basic troubleshooting comes to mind here, event log, all services running, etc.

Are you using WINS, cause WINS makes a huge difference in an NT4 domain. I have seen on several occasions Windows 2000 machines working quite well on NT4 domains.

In all honesty though, migrate to active directory, noone regrets it.
charade-you-areCommented:
Check the premission where the logon script is.  You have probably already done this.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
OS Security

From novice to tech pro — start learning today.