vps-update-error

[machines]

hello,

in a customer network i have the following conditions:

a win2k-server as domain-controller
a winxp pro-system with avm ken! as internet proxy

i installed the adnm client on the xp machine, and i get
the clients pushed through this machine.

the problem is with the updates. there´s a job in the
scheduler to update the vps every at 12:00. the job
starts, but i only get two or three machines updated.

i get the following errors:
failed 0x000005B4
failed 0x20000004

i thougt that there is a problem with the avm ken! and
so i installed the adnm on the domain-controller with the
same result and after that on a single xp machine therefore
with the same result.

it is possible to update the clients manually, but sometimes
it works and sometimes don´t, but without a scheme.

i can reach the internet from the clients and from the
server. the clients are win2kpro and a few xp pro systems.

is there someone around with an idea, how i can solve
this ?

thanks for reply.

greetings marco.

[Vlk]

Is the proxy server specified in the computer catalog group's properties? Because if the updates are being fetched from the MIRROR, typically, you should NOT specify the proxy settings (even if there's a proxy server on the network) because it can be used only to access the Internet, not the local mirror. I think that the current version of avast uses the proxy server settings no matter if downloading the update from the mirror or from the Internet - so if the mirror cannot be accessed thru the proxy server (which is usually the case), the update process will fail.


BTW congrats for the Bronze, and thanks for the great event!

Thanks
Vlk

[machines]

... thankx for your hint and thanx for your wishes and compliment ...
... and the weather was also really great ...
... hope we can keep and store this vibrations ...

... back to my problem ... it seems a little bit more difficult:

there are two ethernet-controllers in the adnm-machine and they
are configured in the following way:

LAN1 - external:
ip:              192.168.100.6
gateway:   192.168.100.100 (fritz!-box)
dns:           192.168.100.100

LAN2 - internal:
ip:              192.168.200.6
gateway:   192.168.100.6
dns1:         192.168.200.5 (domain-controller)
dns2:         192.168.100.6

i think that the problem might be somewhere in this
configuration.

i checked the settings for the proxy in the adnm,
but without result.

so installed the adnm again today, and i can see
this behaviour: i can push the installation to the clients
(in the network 192.168.200.x), but even when i start
a vps-update throug the adnm ... it needs a couple of
minutes before starting the process and then after a while,
i get the errors ...

thanks in advance for some input  .

greetings marco.

[Vlk]

OK, thanks, but that didn't really my question (related to proxy settings).

Could you please send me the file <avast>\setup\setup.log from one of the problematic machines?

Thanks
Vlk

[machines]

hello,

because of the proxy-settings i wrote this ... the logs
are in your mail ...

greetings marco.

[machines]

since i made a new installation of the adnm (as i wrote in the email,
it works ... that´s really strange, bur the clients are updated ...

greetings marco.

[Agron]

Hello,
I am having a similar problem.
When I try to update VPS I get the following errors:
(0x000005B4)
(0x0000045A) - I managed to sort this out by restarting the client but not for all machines.

Please help.

Regards,
Agron Fazliu

[Vlk]

Are you running the latest version of the netclients? The last version should definitely not have the problem any more... (although I understand that if you DON'T, it's not so easy to change that as the updating subsystem itself is malfunctioning)...

Thanks
Vlk