Author Topic: Avast using UPD destination Port 0 in VMWare  (Read 2773 times)

0 Members and 1 Guest are viewing this topic.

tr.security

  • Guest
Avast using UPD destination Port 0 in VMWare
« on: March 16, 2010, 08:42:21 PM »
I installed the latest Avast in a WinXP Pro SP3 VMWare guest, hosted on WinXP Pro SP3.
I have the same firewall in both the guest and the host and I'm using VMWare nat translation.

After installing Avast 5, and setting up new TCP rules to allow it to update properly, the host firewall reports connections to

  • a832sm.avast.com [174.120.185.154]
  • a833sm.avast.com [174.120.185.130]
  • ...etc. etc. for *.avast.com [174.120.*.*]

And all using a destination port of UDP Port 0 (zero).

Interestingly, the firewall on the guest does not report these (and it has the same rules).

Is this expected behavior?  What might it be doing?

Avast 5.0.462
VMWare Player 3.0.1

Thanks.