Archived from groups: microsoft.public.win2000.active_directory (
More info?)
Again, thank you for your fast reply.
I don't mean to sound rude but I really dont't think I've done something
wrong when configuring. I did already put the GPO on computers/startup and
all permissions are ok. As I said in my initial question "only" 20-30
computers/users out of aprox 90 are affected and the config are identical on
every one (exept hardware).
I've heard something about Gbit-NIC:s having this kind of problem and my
next action will be to replace one to see if it helps, but this is really
not a good solution since many affected computers are Laptops so NIC:s will
have to go in the PC-card-slot of the computer and the docking-station's NIC
will not be used (users will have to plug in network cable every day). It's
also an expensive solution.
So once again I'm grateful for every tip.
Thank you!
"Herb Martin" <news@LearnQuick.com> skrev i meddelandet
news:uK9R%23V7JFHA.3916@TK2MSFTNGP14.phx.gbl...
> "MED" <info@englund-it.se> wrote in message
> news:<dnTYd.19514$d5.147732@newsb.telia.net>...
>> Maybe I've done something wrong when configuring, but I don't think so. I
>> have done this too many times to do this wrong...but of course I'll be
> happy
>> for any suggestions. Anyway...I did already set the GP on
> computers/startup.
>
> In your earlier post you indicated very clearly
> that you don't get the scripts to run on startup of
> the computer, but do get them on logon/logoff.
>
> If the script that runs is running during
> USER logon but intended for the Computer
> startup then it is set in the wrong portion.
>
> If you mean that "other scripts" (not the
> same scripts you intended for the computer)
> are running then that is a separate issue.
> [Although it might give hints.]
>
> It may be that your computer is not authenticating
> properly but then it would be (somewhat) odd for
> the user to be able to authenticate.
>
> Authentication problems usually turn
> out to be DNS problems so I will append
> my DNS guide at the bottom.
>
> Another possibility, ESPECIALLY if you
> have placed the computer scripts manually,
> is that you didn't place PERMISSIONS for
> the computer accounts (or Everyone READ,
> or Authenticated Users READ).
>
> Check your NTFS permissions on the actual
> files in SysVol.
>
>> If I put a script in NetLogon (and don't use GP at all) it will run on
> some
>> computers but not the one's having this problem.
>
> NetLogon is usually used for user
> "account properties" script and not
> for GPO scripts (technically you may
> be able to put them there but it is
> best to let the GPO editor choose the
> location to avoid errors.)
>
> This could be the source of the permission
> problem.
>
>
> --
> DNS for AD
> 1) Dynamic for the zone supporting AD
> 2) All internal DNS clients NIC\IP properties must specify SOLELY
> that internal, dynamic DNS server (set.)
> 3) DCs and even DNS servers are DNS clients too -- see #2
> 4) If you have more than one Domain, every DNS server must
> be able to resolve ALL domains (either directly or indirectly)
>
> netdiag /fix
>
> ...or maybe:
>
> dcdiag /fix
>
> (Win2003 can do this from Support tools):
> nltest /dsregdns /server
C-ServerNameGoesHere
> http://support.microsoft.com/kb/q260371/
>
> Ensure that DNS zones/domains are fully replicated to all DNS
> servers for that (internal) zone/domain.
>
> Also useful may be running DCDiag on each DC, sending the
> output to a text file, and searching for FAIL, ERROR, WARN.
>
> Single Label domain zone names are a problem Google:
> [ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
>
>
Facebook
Twitter
Instagram