Re: Pulling hair out - and there ain't much left

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Steven L Umbach (n9rou_at_nospam-comcast.net)
Date: 04/19/04


Date: Mon, 19 Apr 2004 18:16:42 GMT

Hmm. If this Dell computer is a domain member run netdiag [on install disk in
support/tools folder -run setup] on it to see if any failed tests/errors/warnings
show, particularly for dns, dclist, and domain membership/secure channel. Enable
auditing of logon events in Local Security Policy on your Dell and on one of the
workstations you are trying to mange and then look in the security log in Event
Viewer for anything that may provide a clue. Try connecting to the target computer
with IP address instead of computer name to see if that makes any difference. I don't
know if it will work but I would also try booting into safe mode with networking and
try it that way to see if it makes any difference by bypassing many startup
programs/services. --- Steve

"Doug" <d@a.c> wrote in message news:2JQgc.25579$pk5.22322@fe03.usenetserver.com...
> Thanks Matt & Rob for your responses but still no dice. The Reg keys for
> current user are already blank and I have confirmed there is no existing
> connection to the remote.
>
> I feel the leading clue here is that this only happens on these three
> machines. I can log onto any other workstation and use remote admin without
> a hitch. Again, I can see the configurations of other machines I just cannot
> do changes, primarily manipulate a users permissions or group membership.
>
> Any other thoughts are most welcome.
>
> Doug
>
> --------
>
> I Can't solve this !
>
> I have three Dell Precision workstations that came pre-installed with W2k -
> SP3. With only these three workstations, I cannot administer other computers
> remotely. I can connect to other systems with Computer Administration and
> can see everything but when I attempt changes I get the error message that -
> "I am logged into a account that does not have access to 'computer name'. "
> and am presented with a dialog for a logon.
>
> I then attempt to logon with a known admin logon, (works fine on any other
> system) and get - "Cannot display objects from this location because of the
> following error: The credentials supplied conflict with an existing set of
> credentials. "
>
> It is only a problem on these three systems and since I have inherited one,
> I have to fix this. I have installed SP4 and applied every MS patch
> available. I have checked any system setting I can find to no avail. Drive
> maps or lack of make no difference. Trying different logons including the
> actual administrators account do not work.
>
> Desperate for help,
>
> Doug
>
>
>
>
>
>



Relevant Pages

  • Re: How to access file on slave hdriv with xp using 2000 pro as master
    ... In XP Home you have to boot in safe mode to see the security tab. ... hooked it up in my non Dell computer as a slave. ... the slave hard drive with xp except his account. ... access..."Access denied" I have tried creating an account with his logon ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Event 2510 appears every 12 minutes in Server 2003 DC system l
    ... we have a very simple domian with one DC and three domain member ... Is that client a domain member? ... Succesful Network Logon: ... The client referred to in the event is running Windows XP. ...
    (microsoft.public.windows.server.general)
  • Re: No local logon - only to domain??
    ... There is no Group Policy to disable showing the local machine during logon ... to a non dc domain member. ...
    (microsoft.public.win2000.security)
  • Re: Cannot connect to computer not joined to domain
    ... The W2k pro machine is a domain member which by ... default authenticates against a domain controller. ... explains why it's looking for a DC during the logon ...
    (microsoft.public.win2000.networking)
  • Re: Cannot connect to computer not joined to domain
    ... The W2k pro machine is a domain member which by ... default authenticates against a domain controller. ... explains why it's looking for a DC during the logon ...
    (microsoft.public.windows.server.networking)