Hello
I have 2 IP segment in one company , I installed one more network card in the avast server and when I search for computers I found both
IP range Computers , But I can’t install clients remotely I got error 5 and error 53
Is there any solution I can do this instead of installing another AMS Server?
Regards
Hi Agshar,
You mean you can’t push install to the PC on your network or only one segment that you can do the push install?
Error 5 is mean access denied, and Error 53 mean the path can’t be access.
Please check the username and password is correctly and the firewall have been stop.
for more easy just build the msi file, and share the installation file to your’s user and let them do it manually.
Hello
Yes , I can’t do push install. Firewall and Username all correct , but still same problem.
We need to do push install , I am not sure if they will accept manual installation.
Regards
what is your client OS(XP, Vista, 7, 2000Pro, 2000SRV, 2003SP2 SRV, 2008)?
please upload the remote installation logs also
Regards
Error 5 is mean access denied, and Error 53 mean the path can't be access.
you say you have 2 segments
do you have the same domain on those segments?
if you have 2 different domains on those segments then you need to have 2 different usernames in the settings for deployment…
best would even be a separate deployment job
whats the domain of the segments
whats the OS’s on the segments
for the rest see last post from SPI
Hello
In first segment they have domain and in second there is no domain it’s normal workgroup
the server configured for first time in first segment.
The OS is Windows XP , Account is Administrator with Password.
are the passwords from administrator of the non-domain computers all the same??
did you specify the administrator account for those computers in the ADNM?
if you did, try it with .\administrator
the . means local computer
I will try this.
I don’t know id it’s supporting multiple IP. and id supports , does it fix the issue ?
any body test this issue with two NIC or two IP.
Regards
Hello Again
I tried the following
I Added two IP address to one NIC and Discover the Network Computer and I got the list but without IP address for
Second IP address.
This is the Remote/Install Log
01/23/11 20:37:28: rinstInstall begin
01/23/11 20:37:28: Init 50 60 C:\WINDOWS\TEMP\asw199.tmp C:\Program Files\Alwil Software\Management Tools\InstPkgs NULL C:\WINDOWS\TEMP\asw198.tmp 0
01/23/11 20:37:30: Store
01/23/11 20:37:30: Domains: WORKGROUP,
01/23/11 20:37:30: Init WORKGROUP\FUTUREGATE
01/23/11 20:37:30: FUTUREGATE: GetAccount
01/23/11 20:37:30: FUTUREGATE: Queueing
01/23/11 20:37:30: StartThread
01/23/11 20:37:30: Loop
01/23/11 20:37:30: SpawnThreads
01/23/11 20:37:30: FUTUREGATE: StartSetup
01/23/11 20:37:30: FUTUREGATE: Connecting
01/23/11 20:37:39: FUTUREGATE: WNetAddConnection2 \pc1\C$ pc1\Administrator error 53 (The network path was not found)
01/23/11 20:37:39: FUTUREGATE: WNetAddConnection2 \pc1\ADMIN$ pc1\Administrator error 53 (The network path was not found)
01/23/11 20:37:39: FUTUREGATE: RemoveOnError
01/23/11 20:37:39: FUTUREGATE: Finished with error
01/23/11 20:37:39: TerminateAll
01/23/11 20:37:39: rinstInstall end 0
When I discover the computers in the network , I am getting all of them , but the second segment with no IP address in the ADNM Console
the console tries to push to a NETBIOS name, since there is no netbios provider on the workgroup domain the path cannot be found…
in the discovery job you can edit several settings, one of the has to do with IP addresses, see whats checked in there and adjust accordingly… let us know if that works
the workgroup computers, how do they get their IP address?? are they static or dynamic?
Hello
How to do the option to install using netbios name.
IP is DHCP , even static is same
no one have idea about how to do that ?
???
curiosity: why is the other segment without a domain?
I havent had time to think of a way to solve your problem so far… except for manual installation of the Avast client.
Create an MSI package on the ADNM and install that on the clients in the workgroup segment