|
A lot
of issues in W2K come down to DNS. Logon scripts are pretty easy to troubleshoot
though if you look at network traces as you will see the request to get the
logon script right in the trace and whether or not the issue is name resolution
or something else.
The
most fun issue I have see with logon scripts is a site that is configured for
DNS and WINS and the way the DC's are configured they are not all in WINS
(involved hub and spoke multi-tier WINS environment) and in a disjoint dns name
space so when a DC is found through DNS and then the logon process says to bring
down logon script xyz the client gets the FQDN of the machine with the script
but for some reason it chops the dns name off and just tries to resolve the host
name through WINS and can't so the logon script doesn't come down. Have also
seen this when companies try to mix to separate networks while in a
consolidation process and they point at WINS for one network and DNS for another
and use the domain and logon process of where they are using the DNS and the
WINS is just to find old resources. Completely blows the logon script process.
Again,
simplest to get a network trace and see the exact failure than to try and fix
this and then that and then that to see what fixes it overall.
|
Title: Message
- [ActiveDir] OT: Login script problems rmcdonald
- RE: [ActiveDir] OT: Login script problems Joe
- RE: [ActiveDir] OT: Login script problems Rick Kingslan
- RE: [ActiveDir] OT: Login script problems Raymond McClinnis
- RE: [ActiveDir] OT: Login script problems Mulnick, Al
- RE: [ActiveDir] OT: Login script problems rmcdonald
