Remote Management Access Denied

From: Michael Morgan (nobbynobnob@hotmail.com)
Date: 04/14/03 

From: "Michael Morgan" <nobbynobnob@hotmail.com>
Date: Mon, 14 Apr 2003 15:03:06 +0100

Hi All, hope I'm not repeating any previous posts here and that I'm in the
correct group, but frankly I'm pulling my hair out with this one.

Senario :

Win2K Server running all latest critical updates and service packs.
WAN consisting of mixed win2k and winxp pc's.
Logged in as administrator

Problem.
On all PC's the network administrator has been added to the local
administrators group to give complete access.
Running computer management, connect to another computer.
Works perfectly on all win2k desktops, but fails on part of the win xp
management.

I have had to add a registry key to allow access to the event logs (previous
to that I was getting access denied).
I still cannot go into system information and view the contents. The message
"the connection to pcname.domainname could not be established..."

I can do most other things.
I am a local administrator ?
It is also affecting the remote rollout of Sophos AV - Win2k pc's no
problem, WinXP will not complete the update.AAAARRGGGGHHHHH!
I have changed the local security policy on the xp pc's to set network
access to classic as advised by Microsoft.

The PC's are Dell Optiplex GX260's.
I have upgraded to SP1.
I have applied all fixes.
One strange thing is that I had to create a registry key to allow dfs to
operate as I was getting grp policy errors. Microsofts kb article assumed
that this key was already there.

Could it be an image problem with the xp from Dell ? I seem to remember
reading somewhere about possible image errors on Dell PC's.

Any help would be very, very, very much appreciated.

Relevant Pages

  • Re: XP Security Question
    ... options are grayed out in local security policy. ... to have to completely re-install to move from win2k to XP ... >administrator and the domain admins group has been ... >> EXCEPT that I can no longer do any kind of remote ...
    (microsoft.public.windowsxp.security_admin)
  • Re: SBS 2003 Managing Computers
    ... logged in as Administrator. ... > as you may have a good reason to keep the Win2k pro machine standalone. ... > If you cannot join the Win2k box to the domain you can add permissions to ... >> not have permission to use this network resource. ...
    (microsoft.public.windows.server.sbs)
  • XP cannot access to Win2K Server
    ... My Win2K is a domain controller while my XP is just a standalone client ... I have the administrator ID with the same password in both PC and normally ... However I do not know why recently I cannot logon by this way. ...
    (microsoft.public.win2000.general)
  • XP cannot access to Win2K Server
    ... My Win2K is a domain controller while my XP is just a standalone client ... I have the administrator ID with the same password in both PC and normally ... However I do not know why recently I cannot logon by this way. ...
    (microsoft.public.windowsxp.general)
  • XP cannot access to Win2K Server
    ... My Win2K is a domain controller while my XP is just a standalone client ... I have the administrator ID with the same password in both PC and normally ... However I do not know why recently I cannot logon by this way. ...
    (microsoft.public.win2000.advanced_server)