Re: error code 53

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Luke Packard [MSFT] (lukep_at_online.microsoft.com)
Date: 12/22/04

  • Next message: Luke Packard [MSFT]: "Re: Help with client install issue..."
    Date: Wed, 22 Dec 2004 13:05:26 -0800
    
    

    Is this just for some clients and not all? From the site server are you
    successfully able to ping a problem machine by name? Does it resolve to the
    correct IP address? Might flush netbios cache on site server. Could also
    be WINS replication latency.

    -- 
    Luke Packard [MSFT]
    SMS 2003 Technical FAQ:
    http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default.mspx
    This posting is provided "AS IS" with no warranties, and confers no rights.
    "Mark Cowan" <MarkCowan@discussions.microsoft.com> wrote in message 
    news:84D160AF-DA89-4AAE-9781-28995C6E89DA@microsoft.com...
    > When trying to push the client to our workstations we keep getting the 
    > error
    > ERROR: Unable to connect to remote registry for machine name 
    > "PCSFH-01D09",
    > error 53. ERROR: Unable to access target machine for request: "BLOCMNVH",
    > machine name: "PCSFH-01D09", error code: 53
    > $$<SMS_CLIENT_CONFIG_MANAGER><Wed Dec 22 12:42:15.614 2004 Pacific 
    > Standard
    > Time><thread=408 (0x198)>  The account sms is using has admin rights. we 
    > can
    > map the admin$ share manually using the sms account. Any ideas would much
    > appreciated. Also these are win2k pro machines. 
    

  • Next message: Luke Packard [MSFT]: "Re: Help with client install issue..."

    Relevant Pages

    • Re: Clients Discovered but not assigned to site
      ... role on the SMS Site Server you're using. ... Advanced Clients and an MP. ... > that only the subnet of the primary site server is included. ...
      (microsoft.public.sms.setup)
    • SMS 2003 Hierarchy Design
      ... I'm looking for some help with my SMS hierarchy design. ... Main European Location = 100 clients ... needs to be able to manage all systems globally and the asia and europe main ... I originally planned a primary site server at each of the 3 main locations ...
      (microsoft.public.sms.setup)
    • RE: Upgrade SMS 2.0 to SMS 2003
      ... clients on our intranet. ... We would like to upgrade our current SMS 2.0 infrastructure to ... Run the DRW on the central site server and secondary site server and ... Do an in-place upgrade of the primary central site server to SMS 2003 ...
      (microsoft.public.sms.setup)
    • Admin Acct
      ... With SMS 2003 Deployed, supporting 15,000 mixed clients in an NT domain and ... local admin rights and no domain admin rights ... How do you troubleshoot corrupt clients or run scripts or do manual client ...
      (microsoft.public.sms.admin)
    • Domain Admin Acct
      ... With SMS 2003 Deployed, supporting 15,000 mixed clients in an NT domain and ... local admin rights and no domain admin rights ... How do you troubleshoot corrupt clients or run scripts or do manual client ...
      (microsoft.public.sms.misc)