It sounds like you have a good grasp of the NT4 domain architecture, Me too!

We have obviously been around for awhile... LOL
Quote:
|
I am not using the group policy to do the logon script. I just have it defined in the users profile. The same way that I did under NT4.
|
that's what I figured and the reason why I replied with the previous information...
Under Win2000- Active Directory or AD needs to be implemented before your server can act as the primary domain controller for your LAN. Unfortunately the AD structure used by Win2000 is nowhere near what we were used to with NT4. I like the old way of doing things a lot better! To me AD is a piece of CR*P (sorry,

) but it's more like Novell then, well... novell!
Quote:
|
Are you saying that I have to make the setting on the users machine under group policy?
|
Since your Win2000 server is not acting as the PDC of your LAN- I am not clear on what steps to take in order to troubleshoot this. I do know that if one of my clients was unable to run a login script from my PDC- the "AD Group Policy" MMC would definitely be where I would go to resolve it...
Sorry, but I haven't played around a lot with login scripts on a standalone server. If I were to guess- I would definitely go to the client machine and see what group policy had to offer on the local level.
Normally- I wouldn't implement a login script unless the client was logging on to a PDC or BDC and needed it to access or share domain resources...
Quote:
|
When I bring up the group policy on the serve it says it is for the local machine.
|
This is why I have never used a login script on a standalone server.
I know this doesn't help you out that much and I apologize... When I first read your post I assumed your machine was the PDC of your LAN and the fix would be a slam dunk (group policy/not like NT4, yes!

)...

Not!
Oh well, sorry again-
Good Luck!
Pakalolo
ps- if you do end up promoting your machine as the PDC let me know if there is anything I can help out with
