Author Topic: Avast! Antivirus Managed: Cannot connect to 127.0.0.1: 5033 (unknown: 5033)  (Read 7199 times)

0 Members and 1 Guest are viewing this topic.

fastshark

  • Guest
I have a user that can not seem to get there def. updated from my server.  I tried to push from ADMN VPS...and fail with same type message "tried 1 servers to get file 'servers.def.vpu', but failed (0x20000004)"

Offline scythe944

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 2913
    • My Tech Blog
Firewall on client PC?
For generic computer (not avast) problems, you can also visit my forum for help: http://www.jacobytech.net/forum

fastshark

  • Guest
Windows, but exceptions were created and enabled when aVast was installed.  Also noticed that the user did not have any files/folders shered..so maybe a file/folder shared issue.  I have created a shared folder as well as disabled Windows firewall so I can attempt to push VPS again...i'll report back.

Offline scythe944

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 2913
    • My Tech Blog
Possibly.  I've seen where file and printer sharing wasn't turned on, it blocked all sorts of things, regardless of firewall settings.

That's probably the problem.
For generic computer (not avast) problems, you can also visit my forum for help: http://www.jacobytech.net/forum

fastshark

  • Guest
Still was not able to push VPS to user from ADNM.  No other firewalls are install and/or enabled on this users machine.  Is there another means 9as a temp solution until this can be resolved) for me to update this users def's other than pushing via ADNM or trying from the users machine to hit my server?

fastshark

  • Guest
Does aVast Support actually check this message board?

Offline scythe944

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 2913
    • My Tech Blog
Yes they do but truthfully, they don't touch every post.  I think the majority of posts are taken care of by Avast customers such as myself.

As for your question, yes, you can create a manual installation package (msi) and copy it to a network share / removable media to install the client.

Instructions can be found in the ADNM admin guide.
For generic computer (not avast) problems, you can also visit my forum for help: http://www.jacobytech.net/forum

fastshark

  • Guest
I do have an msi that I used for all my users.  This is the only user that can not get updates to my knowledge.

Offline scythe944

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 2913
    • My Tech Blog
Well, being as how all the other computers are able to get their def updates correctly, and this machine is the only one that doesn't want to cooperate, I'm inclined to look at it to find the problem.

Were there any other A/V products installed on this machine prior to avast being installed?

Have you tried repairing the installation?

A clean installation might remedy the problem.  Uninstall via Add/Remove Programs, grab the uninstall utility from avast's website, reboot in safe mode and run the uninstaller.

Then, reboot again into normal mode and give the installation another shot.
For generic computer (not avast) problems, you can also visit my forum for help: http://www.jacobytech.net/forum

Offline essexboy

  • Malware removal instructor
  • Avast √úberevangelist
  • Probably Bot
  • *****
  • Posts: 40589
  • Dragons by Sasha
    • Malware fixes
127.0.0.1: 5033 did you set this proxy ?

Offline scythe944

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 2913
    • My Tech Blog
Re: Avast! Antivirus Managed: Cannot connect to 127.0.0.1: 5033 (unknown: 5033)
« Reply #10 on: November 09, 2010, 09:24:37 PM »
I was assuming that he did, but now that you mention it, it does sound odd.  I'll have to look at the ADNM admin guide to see what ports it's supposed to use
For generic computer (not avast) problems, you can also visit my forum for help: http://www.jacobytech.net/forum

Offline essexboy

  • Malware removal instructor
  • Avast √úberevangelist
  • Probably Bot
  • *****
  • Posts: 40589
  • Dragons by Sasha
    • Malware fixes
Re: Avast! Antivirus Managed: Cannot connect to 127.0.0.1: 5033 (unknown: 5033)
« Reply #11 on: November 09, 2010, 10:54:29 PM »
It's just that when I see them it is usually directing to a malware site  ;D

fastshark

  • Guest
Re: Avast! Antivirus Managed: Cannot connect to 127.0.0.1: 5033 (unknown: 5033)
« Reply #12 on: November 10, 2010, 02:40:59 PM »
This machine is a new build.
No other AV software has ever touched the machine.
Originally the .msi was used and the user let me know that he was getting 127.0.0.1: 5033 communication errors.
Uninstalled aVast (did not run uninstall tool, rather just add/remove)
rebooted
reinstalled same .msi
same issue

No I did not setup that proxy.  

Link to aVast uninstall utility?


Edit:  for future reference for me/others, here is the link to the uninstall tool:  http://www.avast.com/uninstall-utility

Offline scythe944

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 2913
    • My Tech Blog
Re: Avast! Antivirus Managed: Cannot connect to 127.0.0.1: 5033 (unknown: 5033)
« Reply #13 on: November 10, 2010, 07:29:18 PM »
I usually put a link to the uninstall utility, but I've done it so much that I figured it would be an easily searchable term, my bad.

So, after using the uninstall utility, it still doesn't work, eh?

Link to the ADNM Admin guide is here: http://www.avast.com/distributed-network-manager#tab4

I'm downloading it to take a look at which port we're supposed to be using here.
For generic computer (not avast) problems, you can also visit my forum for help: http://www.jacobytech.net/forum

Offline scythe944

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 2913
    • My Tech Blog
Re: Avast! Antivirus Managed: Cannot connect to 127.0.0.1: 5033 (unknown: 5033)
« Reply #14 on: November 10, 2010, 07:35:26 PM »
Alright, 5033 is the port that the AMS server uses, but I don't know why it's using the local loopback address.

Is that error
Quote
Cannot connect to 127.0.0.1: 5033 (unknown: 5033)
from the remote install log from the ADNM console, or is that a client error (forgive me if you have already stated this)?

If it's a client error, it should be the IP address of the AMS server:5033

If it's a remote install log error, then I would assume the IP address should be what the machine's IP address is, not itself.

Does that make any sense?

Instead of using the MSI file, could you try a push install instead?  Does the computer show up in your computer catalog after you do a discovery task?
For generic computer (not avast) problems, you can also visit my forum for help: http://www.jacobytech.net/forum