|
Posted by Steven L Umbach on October 14, 2005, 5:59 pm
Please log in for more thread options Try Process Explorer from SysInternals. In the properties of each process is
a page for tcp/ip info that will show if any port is used. TCPView may also
be helpful but Process Explorer is the king of process identification. You
also have the option to kill the process or process tree though that does
not work all the time. Also check your services as sometimes malware will
install as a service that you could try to stop/disable. --- Steve
http://www.sysinternals.com/Utilities/ProcessExplorer.html http://www.sysinternals.com/Utilities/TcpView.html
> Hi all,
>
> I have a problem with my Sql Server 2000 server. A malware captured the
> 1433 port when we restarted the SQL Server service. Now we have some users
> (that uses TCP/IP to connect to the server instead named pipes) that can
> not access to the server. The server is mission critical, can not be reset
> until midnight to eliminate the virus. We want to kill the malware process
> but we can not get the process id of the malware. We tryed with fport last
> version downloaded from Foundstone but it does't lists the 1433 port as
> being in use. But netstat -an clearly shows the 1433 port is listening.
> The Sql Server Log says it could not be binded to 1433. So is it possible
> fport fails to detect a process? Which other way can I use to detect the
> process id of the malware apart of fport?
>
> Thanks in advance
> Sammy
>
|