We have a network with one server (Windows Server 2003) and 19 workstations (all XP SP3). I just successfully installed ADNM on the server and pushed out the client successfully to 17 workstations. The other two I get the "access denied"error. The windows firewall and “simple file sharing” are both turned off on these two workstations. How can I troubleshoot this problem, or otherwise get the client installed on these two workstations? Thanks.
Welcome to the forum!
Have you had a look at the remote installation log in the ADNM console yet? It might give you a better idea of what/why it didn’t work.
I assume you’re using a domain administrator account in order to push the installation, if not, you should use one.
Are there any third-party firewalls installed on those two machines, or possibly remnants of an old A/V product?
Sometimes I get an access denied error when I do a push install, but after 2 or 3 tries it goes through.
Thanks for responding. There are no third party firewalls on these two machines, and I uninstalled all remnants of Symantec Endpoint Protection before I did the push. these two machines are basically the same as the ones I successfully pushed - in a domain, I used domain admin account, etc. I’ll try again, but I’ve already tried several times with no luck.
Anything strange in the remote install log in the ADNM console? Could you post part of the logs where the clients are failing?
Both of the clients where the install failed say exactly the same thing as the clients that succeeded.
Init DENTAL\STAFF5
12/06/09 11:19:06: STAFF5: GetAccount
12/06/09 11:19:06: STAFF5: Queueing
The log suggests they both installed but they don’t show as installed in the computer catalog, nor are they installed if you go to the clients themselves and look.
I just tried again - this log is more informative.
12/08/09 18:08:15: rinstInstall begin
12/08/09 18:08:15: Init 50 60 C:\WINDOWS\TEMP\asw2E.tmp C:\Program Files\Alwil Software\Management Tools\InstPkgs NULL C:\WINDOWS\TEMP\asw2D.tmp 0
12/08/09 18:08:16: Store
12/08/09 18:08:16: Domains: dental,
12/08/09 18:08:16: Init DENTAL\OP17
12/08/09 18:08:16: OP17: GetAccount
12/08/09 18:08:16: OP17: Queueing
12/08/09 18:08:16: StartThread
12/08/09 18:08:16: Loop
12/08/09 18:08:16: SpawnThreads
12/08/09 18:08:16: OP17: StartSetup
12/08/09 18:08:16: OP17: Connecting
12/08/09 18:08:32: OP17: WNetAddConnection2 \OP17\C$ dental\dan error 1326 (Logon failure: unknown user name or bad password)
12/08/09 18:08:32: OP17: WNetAddConnection2 \OP17\ADMIN$ dental\dan error 1326 (Logon failure: unknown user name or bad password)
12/08/09 18:08:32: OP17: RemoveOnError
12/08/09 18:08:32: OP17: Finished with error
12/08/09 18:08:32: TerminateAll
12/08/09 18:08:32: rinstInstall end 0
So it looks like a logon error, but I can’t figure out why it fails on these machines and ok on others.
Hi Dan,
Sycthe944 sorry for the interuption,
Dan please make sure are they could detected at your network sharring?
Are you able to access to those PC’s with Dos Command prompt like : netuse ?
Yes, a command from the server like net use \staff5\c$ user:dental\dan connects to the client after I enter the password.
Weird… can you login to these machines under that account? Maybe check to see if the admin account has admin rights on the machines?
I don’t know why it would give a bad username and password if it’s joined to the domain. Sounds like the machines have other issues if they can’t query the server to authenticate users…
:)Thanks to everyone for their help on this. I finally got it to work. For some reason, domain admins weren’t in the local computer security account on these two machines. I know that’s supposed to happen automatically when a workstation is joined to a domain, but for some reason it didn’t.
Glad you got it to work. I’ve had that problem is some circumstances.