Hey I think I’m having the same errors that I was having before except with a different computer. Some how I got the others to work but with this one I tried every account that we have on the domain and also every account that is on that local machine. our domain is wbe.com I was wondering when it ask for a domain name do you have to have the .com at the end or can you just leave it as wbe…also for account that is on the domain I would just have to use for example wbe\loerts. I have tried local users and domain user names and passwords but still get an error message…here is the log file for the client machine
Interesting. Error 1203 translates to No network provider accepted the given network path – which pretty much indicates a connection problem (not a logon problem).
Can you access the computer from the AMS by other means?
Like running
yea that didn’t work either i found out that I couldn’t even ping the computer. had to do some network troubleshooting since she could get on everything…it all boils down to service pack 2 for xp. I found out that on default the windows firewall wasn’t accepting file and print sharing so I just had to check that under the programs and it worked out for me…another question though that I ran into after I installed this on her computer is that the license could not be found i had to manually point the program to where the license file was any suggestions
nope just tried another machine and it didn’t have the license file either. had to manually locate it again on our network drive. also this machine had norton antivirus on it when I push installed avast the console said that it was installed successfully but when I go to that machine it doesn’t have the little A icon by the clock also it didn’t install the folder in the start menu but I did noticed it installed it when I went to the C: the folder was in there and I could open the program but I went to the look at chest and it came up with errors. It said something about RPC connection failed error or could not connect with RPC something with RPC I check in the services.msc and all of the RPC programs are started…any suggestions??
The missing license – seems like a bug in RC-1a but it’s not repro in the latest internal build. I guess it’s been fixed already. Let’s see tomorrow – there’ll be most likely a RC-2 release.
The RPC problem – that’s classic. Please check that the avast antivirus service is running. Control Panel → Administrative Tools → Services. If not, try to run it.
another question for you…I installed netclient on a pc with the push install…when I checked out this pc the avast service was installed correctly but the resisdent scanner or on-access scan was not on. there was a red X on the A by the clock. everytime I tried to manual start it on the local machine by opening avast4 it wouldn’t stay on
well the only log file that was on the local computer was an error.log the os is XP
9/9/2004 1:35:22 PM 1094754922 SYSTEM 2376 avast! Antivirus service is not running, computer is not protected!
9/9/2004 1:35:24 PM 1094754924 SYSTEM 2376 Unable to start avast! Antivirus service, error 00000433 has occured
9/9/2004 1:41:03 PM 1094755263 SYSTEM 1600 avast! Antivirus service is not running, computer is not protected!
9/9/2004 1:41:03 PM 1094755263 SYSTEM 1600 Unable to start avast! Antivirus service, error 0000042D has occured
9/10/2004 7:48:09 AM 1094820489 SYSTEM 1608 avast! Antivirus service is not running, computer is not protected!
9/10/2004 7:48:09 AM 1094820489 SYSTEM 1608 Unable to start avast! Antivirus service, error 0000042D has occured
9/13/2004 9:49:08 AM 1095086948 SYSTEM 1604 avast! Antivirus service is not running, computer is not protected!
9/13/2004 9:49:08 AM 1095086948 SYSTEM 1604 Unable to start avast! Antivirus service, error 0000042D has occured
Error 0000042D means “The service did not start due to a logon failure”. Please check the username/password on the Log On tab of the service properties window (for the service “Avast antivirus”). This is the same info as was specified on the Account page of the Installation Package creation wizard.
yea I thought so otherwise it wouldn’t have installed…how do I change it…and is the user/password that I type in that it is looking for under the installation package or deployment task where you can enter more than one???
No no, this is the one where you can enter only one. It’s in the wizard.
In the console, open the Properties of the installation package (not the Deployment task), and click Edit. A wizard will be shown. I think it’s on the second or third page.
okay I tried I switched it to the console admin rights and still didn’t work then I used the domain administrative rights and still nothing…she doesn’t have the console admin rights on her local machine but she does have the domain admin rights on her local machine…should I just use her account???
....she doesn't have the console admin rights on her local machine but she does have the domain admin rights on her local machine....should I just use her account????
Is the computer part of the domain?
If so, Domain admins (members of the Domain Admins group) should automatically have local administrative rights on all workstations residing in the domain…
BTW what if you change the service log on settings directly on the target?
yea she is part of a domain…I did another push installation on another PC I don’t know whats going on lately but they used to work fine…I can manually fix the problem by going in to services and changing the log on user like you said before. I’m using the admin account for adnm console in the installation package…the question is what account are you suppose to you for that the domain admin or the console admin…my brain hurts hehe
I'm using the admin account for adnm console in the installation package...the question is what account are you suppose to you for that the domain admin or the console admin...
It’s quite simple.
You’re supposed to use e.g. the domain admin account here.
In short, exactly the same account as you’re then specifying in the service Log On settings when fixing the problem…
Just a note about the Win XP SP2 firewall issue. I had same issue. for more details, I actually had to walk to each workstation, log on, and change the firewall settings. and go to the Exceptions tab, and click “file and print sharing”, so that the File/Print services would NOT be blocked by firewall. This setting, of course, is automatically checked IF you happen to turn on printer sharing or file sharing on the workstation. Most of my workstations do NOT have sharing. I found that on the 3 that did share a printer, there was no need to make this adjustment.
there is no mention of this in the Documentation. There is a vague reference to the SP2 firewall, and a reference to a non-existent section of the document.
