Page 1 of Port 1025 Open

Hi all

Just done a Shields Up! check on my PC and it appears that Port 1025 is open. It never used to be and I was wondering if anyone could give me any info on hiding it using Sygate Personal Firewall. I know other firewalls hide it by default and I am sure that Sygate used to, but I don`t want to change firewalls. I`ve done a Google search and just confused myslf even more.

<--EDIT-->

It is svchost.exe that is listening on Port 1025, if this is any help.

Any help greatly appreciated.

Ta

Nick

This item was edited on Tuesday, 19th August 2003, 15:07

Have you installed SQLServer ?

https://grc.com/port_1025.htm

If so make sure you have installed SQLServer SP3 or later.

Nope, not got SQL Server installed.

Cheers

Nick

Kazaa, something like that?

J Mark Oates

Shield`s Up found mine in "Stealth" mode using Sygate (free one), running Windows XP. Did you click on "1025" in Shield`s Up to find more info? It will do a port scan and give back more details on this paerticular port for your computer.
In my version of Sygate I can block particular ports under "Advanced Rules", "Add" then "Port and Protocols".

This item was edited on Wednesday, 20th August 2003, 01:33

Know you dont wanna change but I`m using Zone Alarm (free edition ) and my comps invisible, so says shields up!!

Now I`m worried. My port 1025`s open as well, and I`m running Norton Firewall.

J Mark Oates

I was able to use Sygate`s advanced rules to close Port 1025 to incoming traffic, svchost is still listening on the port which is okay. I am sure I will find out in time what I have stopped from working...LOL!

Thanks Guys.

Nick

Just for information purposes as I know it doesn`t cover the Port 1025 problem, but, at one point I did find my "Ident" port was open. Found the culprit, by trial and error, was the Trillain programme, nameley the IRC section of it. Once I closed that down, so the port was closed.

This port 1025 problem is all to do with the Blaster virus weakness in Windows. You need to download the DCOM patch (I got mine from Blueyonder ) then head over to Gibson Research for their DCOMbobulator check program to ensure the patch has worked and deactivated the naughty port in question.

Update: Ach du lieber! The damn port`s still open. Any idea how to get Norton Firewall to nail it shut?

J Mark Oates

This item was edited on Thursday, 4th September 2003, 22:56