- Posts: 2
- Thank you received: 0
Disconnecting an active connection
19 years 10 months ago #6513
by Shankar
Disconnecting an active connection was created by Shankar
Hi,
When I did a netstat -a on my windows box, I see some machine connected on TCP:1274. How do I disconnect this?
Thanks for help
Shankar
When I did a netstat -a on my windows box, I see some machine connected on TCP:1274. How do I disconnect this?
Thanks for help
Shankar
19 years 10 months ago #6516
by Wizmatic
Replied by Wizmatic on topic Re: Disconnecting an active connection
Port number:
1274
Common name(s):
t1distproc
Common service(s):
Service description(s):
t1distproc
or you can check this URL..
www.ultrasoftware.net/viruslist/descr.asp?id=101
1274
Common name(s):
t1distproc
Common service(s):
Service description(s):
t1distproc
or you can check this URL..
www.ultrasoftware.net/viruslist/descr.asp?id=101
19 years 10 months ago #6517
by Shankar
Replied by Shankar on topic Re: Disconnecting an active connection
Thank you, Wizmatic. Is there a way to close the connection using a DOS command or any app?
Shankar
Shankar
19 years 10 months ago #6526
by sahirh
Sahir Hidayatullah.
Firewall.cx Staff - Associate Editor & Security Advisor
tftfotw.blogspot.com
Replied by sahirh on topic Re: Disconnecting an active connection
Any port above 1024 is a non reserved port. These ports are arbitrarily taken by applications when they need to create a connection.. for example, your web browser, when you read this site.. your IM client when you message a friend.. or your mail when it downloads over POP3 or uploads via SMTP.
Before you run around killing connections, you should do this:
Identify what the IP is.. you can run a whois on the IP from www.geektools.com .. you'll most likely find its something you're legitimately using.
The next step is to identify what process is actually using that socket. I recommend TCPview from www.sysinternals.com for this. It will show you the connections (like netstat output, but real time) as well as what process owns the socket. From there you can kill the connection, or even terminate the process.
Cheers,
Before you run around killing connections, you should do this:
Identify what the IP is.. you can run a whois on the IP from www.geektools.com .. you'll most likely find its something you're legitimately using.
The next step is to identify what process is actually using that socket. I recommend TCPview from www.sysinternals.com for this. It will show you the connections (like netstat output, but real time) as well as what process owns the socket. From there you can kill the connection, or even terminate the process.
Cheers,
Sahir Hidayatullah.
Firewall.cx Staff - Associate Editor & Security Advisor
tftfotw.blogspot.com
Time to create page: 0.128 seconds