TrojanHunter 2.0-- - Mischel Internet Security Forum

Jobs | About | Blog | Contact

Download TrojanHunter Now
Free 30-day trial!

Latest TrojanHunter Version:
TrojanHunter 5.0

Order Now
License file delivered within minutes.

Welcome, Guest. Please Login or Register.

Jul 5^th, 2008, 5:58am

   Mischel Internet Security Forum
   TrojanHunter
   TrojanHunter Scanner (Moderators: Helena, Gavin_Coe, Magnus)
   TrojanHunter 2.0--

« Previous topic | Next topic »

Pages: 1

Notify of replies

Send Topic

Author

Topic: TrojanHunter 2.0-- (Read 575 times)

Walter
Veteran

Gender:

Posts: 573

TrojanHunter 2.0--
« on: Dec 18^th, 2001, 2:32am »

Quote

Modify

Though I am looking forward to TrojanHunter 2.5, I am still learning how to fully use (and understand

) 2.0. Thus, my question has to do with some of the "tools" available in 2.0. When I click on "tools," then "View Connection Info...", I am then looking at the "TCP/UDP Connection Info" window. Here, in this window is a display of what ports are currently being used, correct? If so, then I am not sure I understand how to interpret what I am seeing. Specifically, occasionally, I see a connection that says, "closing," but then several minutes later, it still says "closing." Why is it still in a "closing" mode? Why is it taking so long to close? Or, sometimes, I see "Time Wait" (I hope my terms are correct). Hm...what is it "waiting for"? These are some of the terms, and processes, I do not understand. What I thought I understood concerning "ports," is that a port can be 1. open, 2. closed, or 3. listening. Apparently though, there are more possibilities (processes?) for ports and their functioning than only these three I just listed? Or, am I thinking about something different? Is there an article I could read or a web-site I could visit (books are OK, too), so I can learn more about the information (and its significance) that is being supplied to me when I look at this? I know ports--understanding and securing them--are very important; some of the most important functions of TrojanHunter (and Guard, too) are associated with ports. Right?
I am guessing, in some ways (perhaps, MANY ways) these may be elementary--perhaps really basic--concepts, though...not for me! Grin

But...rather than take up your energy and time explaining all this, I really am quite happy to read and learn about it on my own--I just need some guidance concerning where to look for this basic-type info. Also, I want to make certain that what I am looking at in this part of tools is, in fact, info regarding "ports," and not something else--so that I unwittingly confuse myself even more!
Finally, Cool

I want to ensure I thoroughly understand version 2.0 PRIOR TO installing the final 2.5 (whenever that may be), as it appears that 2.5 will have even more options, and more functions, and more info than does 2.0.
Help/comments from any and all quarters is--and will be--appreciated, I assure you!

« Last Edit: Dec 18^th, 2001, 2:52am by Walter »

IP Logged

Strange as it may seem, no amount of learning can cure stupidity, and formal education positively fortifies it. S Vizinczey

Magnus
Administrator

Ad astra per aspera.

Posts: 4082

Re: TrojanHunter 2.0--
« Reply #1 on: Dec 18^th, 2001, 3:53pm »

Quote

Modify

on Dec 18^th, 2001, 2:32am, Walter wrote:

When I click on "tools," then "View Connection Info...", I am then looking at the "TCP/UDP Connection Info" window. [...]Specifically, occasionally, I see a connection that says, "closing," but then several minutes later, it still says "closing." Why is it still in a "closing" mode? Why is it taking so long to close? Or, sometimes, I see "Time Wait" (I hope my terms are correct). Hm...what is it "waiting for"? These are some of the terms, and processes, I do not understand.

Basically, ports can be either 1) Listening 2) Connected 3) Closed or 4) Waiting to be closed (Closing)

Because of how TCP/IP works, it can sometimes take a long time for a port to close. This is why you can see FIN_WAIT persist for a long while. It's normal. If you want to read up on it, any paper/book on TCP/IP will do.

IP Logged