Author Topic: New TCP Ports used?  (Read 5839 times)

0 Members and 1 Guest are viewing this topic.

Offline Asyn

  • Avast √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 76213
  • Urlaub/Vacation
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: New TCP Ports used?
« Reply #15 on: March 29, 2010, 04:12:46 PM »
more than that...!!! at least 4 me... ;)
nice day, anyways! :) maybe someone stumbles over with better ideas...
i would b really interested in solving that puzzle. ;D
asyn
W8.1 [x64] - Avast PremSec 22.7.7366.BC [UI.713] - Firefox ESR 91.11 [NS/uBO/PB] - Thunderbird 91.11
Avast-Tools: Secure Browser 103.0 - Cleanup 22.2 - SecureLine 5.18 - DriverUpdater 22.2 - CCleaner 6.01
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Reiner

  • Guest
Re: New TCP Ports used?
« Reply #16 on: March 29, 2010, 04:16:58 PM »
what puzzles me is that until a few days ago, avast used 12xxx. Then i realized, that avast was not running. After i pressed repair/update, avast was running ok, but the ports had changed...

Offline Asyn

  • Avast √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 76213
  • Urlaub/Vacation
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: New TCP Ports used?
« Reply #17 on: March 29, 2010, 04:21:45 PM »
so, that's a starting point.
maybe the repair moved the ports, as they were maybe just in use at time of repair...?!!?
asyn
W8.1 [x64] - Avast PremSec 22.7.7366.BC [UI.713] - Firefox ESR 91.11 [NS/uBO/PB] - Thunderbird 91.11
Avast-Tools: Secure Browser 103.0 - Cleanup 22.2 - SecureLine 5.18 - DriverUpdater 22.2 - CCleaner 6.01
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Reiner

  • Guest
Re: New TCP Ports used?
« Reply #18 on: March 29, 2010, 05:42:46 PM »
Very strange... I did, what everybody does, when something is not longer working as expected (remove / reinstall) and Avast uses again ports 12xxx.

Now it would be interesting, what caused Avast to abort using 12xxx and start using 39xx. It seems as Avast just used new ports for the whole mail-sacnning-subsystem (12080 stayed!).

Maybe one of the Avast developers could bring some light into this issue...