WNetAddConnection2 failed

From: Geenie (Geenie_at_discussions.microsoft.com)
Date: 09/22/04


Date: Wed, 22 Sep 2004 08:13:04 -0700

When pushing out clients, I get the following error messages on some WinXP
computers:

---> Trying each entry in the SMS Client Remote Installation account
list SMS_CLIENT_CONFIG_MANAGER 9/22/2004 9:12:30 AM 2040 (0x07F8)
---> Attempting to connect to administrative share '\\computername\admin$'
using account 'admin\account'
SMS_CLIENT_CONFIG_MANAGER 9/22/2004 9:12:30 AM 2040 (0x07F8)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account
admin\account (00000035)
SMS_CLIENT_CONFIG_MANAGER 9/22/2004 9:12:32 AM 4884 (0x1314)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account
admin\account(00000035)
SMS_CLIENT_CONFIG_MANAGER 9/22/2004 9:12:32 AM 1096 (0x0448)
---> ERROR: Unable to connect to remote registry for machine name
"computername", error 53.
SMS_CLIENT_CONFIG_MANAGER 9/22/2004 9:12:32 AM 4464 (0x1170)
---> ERROR: Unable to access target machine for request: "computername",
machine name: "computername", error code: 53
SMS_CLIENT_CONFIG_MANAGER 9/22/2004 9:12:32 AM 4464 (0x1170)
---> WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account
admin\account(00000035)
SMS_CLIENT_CONFIG_MANAGER 9/22/2004 9:12:32 AM 1096 (0x0448)
---> The device computername does not exist on the network. Giving up.
SMS_CLIENT_CONFIG_MANAGER 9/22/2004 9:12:32 AM 1096 (0x0448)

Basically, I'm concerned about the following three errors from above:
1.
WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account
adminaccount (00000035)
2.
ERROR: Unable to access target machine for request: "computername", machine
name: "computername", error code: 53
3.
WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account
adminaccount(00000574)

>From what I've read, error 53 means that the site server could not access
admin$ on the client computer. The computer may of been off, or off the
network at the time. File and print sharing MUST be turned on for this to
work, correct? What if I'm getting these errors and file and print sharing
is turned on. What else could be wrong?

Thanks.



Relevant Pages

  • Problems connecting clients
    ... On one client I sucseeded to run the computerconnect wizard. ... But on all the other I hade to connect the clients manually. ... First I had to re-add Computername and domanin name ... Than I had to give in the administrators account, ...
    (microsoft.public.windows.server.sbs)
  • Security Event ID 533 - user cant access OWA or RWW
    ... SBS 2003 Premium, ... Computer: <computername> ... User not allowed to logon at this computer ... I've tried backing up her email and docs, then deleting her account, before adding her back in -- same result. ...
    (microsoft.public.windows.server.sbs)
  • Re: WNetAddConnection2 failed
    ... The machine may not be on the network as you say or name resolution is not ... working from the site server to the machine. ... > ---> Trying each entry in the SMS Client Remote Installation account ... > "computername", error 53. ...
    (microsoft.public.sms.setup)
  • Re: Security Event ID 533 - user cant access OWA or RWW
    ... Is the user a member of the Remote Web Workplace security group? ... Checked her account in ADUC and found nothing wrong compared to other users. ... Computer: <computername> ... User not allowed to logon at this computer ...
    (microsoft.public.windows.server.sbs)
  • Re: How do I join a WinXP PC to domain during mini-setup
    ... Like Benjamin said, run setupmgr.exe. ... Create domain user account just for joining domain. ... Specify this account in answer ... Include computername, username, password, domain. ...
    (microsoft.public.win2000.setup_deployment)