Author Topic: Avast Free and port 1433 (MSSQL)  (Read 2868 times)

0 Members and 1 Guest are viewing this topic.

REDACTED

  • Guest
Avast Free and port 1433 (MSSQL)
« on: September 19, 2016, 11:56:57 PM »
Not sure exactly when this happened, but Avast v11.1.2253 is recently took over port 1433. I am a developer that utilizes MSSQL Server which by default listens on port 1433. Now that Avast has taken over this port, this has caused a lot of issues with my configurations that utilize my local instance of MSSQL Server. I've had to disable Avast completely and restart in order to get the MSSQL Server service to run without having to reconfigure everything.

Is there a way to simply disable this "feature" of Avast without completely disabling / uninstalling Avast?

Offline Rednose

  • Pirate Party Member
  • Avast Überevangelist
  • Massive Poster
  • *****
  • Posts: 3739
  • Bits of Freedom : https://www.bof.nl
    • Nederlandstalig Avast! forum
Re: Avast Free and port 1433 (MSSQL)
« Reply #1 on: September 20, 2016, 12:26:33 AM »
Hi c.dwinell, welcome to the forum :)

I am really a noob in this, but what I don't understand is why you think Avast Free  ( which doesn't have a Firewall ) could interfere with port 1433 ?
Besides that, we are already with Avast version 12.3.2280

Greetz, Red.
OS: Win 10 / iOS 17 / Debian 12 / Tails 5
Real Time: Avast Premium Security
On Demand: Malwarebytes
VPN: NordVPN ( NordLynx ) with Threat Protection ( Lite )

Offline Eddy

  • Avast Evangelist
  • Maybe Bot
  • ***
  • Posts: 31079
  • Watching (over?) you
    • Malware removal, Biljart and other things.
Re: Avast Free and port 1433 (MSSQL)
« Reply #2 on: September 20, 2016, 12:31:24 AM »
I agree with Rednose (he got that red nose after I punched him lol)

1]
avast free doesn't have a firewall.

2]
You are using a (real) old version of avast.

3]
avast doesn't "take over" ports.

REDACTED

  • Guest
Re: Avast Free and port 1433 (MSSQL)
« Reply #3 on: September 20, 2016, 01:08:12 AM »
Yeah, I did notice it was outdated. I just updated to the latest version and wouldn't you know it, Avast doesn't have the port open...  :o

As for how I determined it was Avast, I noticed that my MSSQL service wasn't running. Went to start it and Windows kicked back an error telling me to check the Event Log. Checked the error chain and found that something already had port 1433 open. I then ran NirSoft's CurrPorts and it showed that "AvastSvc.exe" had port 1433 open along with a bunch of other ports in the 14xx range (really wish I had taken a screenshot...).

In any case, it's fine for the moment. I'll keep on eye on it...

Thanks for your responses!