Tracing a connection coming into my computer

[Quantum Particle]

First off, I know you aren't really 1337 h4xx0rz, but some of you are quite good with computers, so I thought you may be able to help.

My computer keeps connecting to itself at a certain port, and I was wondering if there was any way I could trace what it is actually connecting too, as in which file/folder?

PS I'm not that skilled in the art of computing, so not too many long words please.
PPS when I connect to myself at that port, firefox tells me 'connection refused'.

[Deepsmeg]

unless it's a protocol firefox can "talk", it won't work.

I'm going to assume you use Windows, I am going to go further and assume you have an NT based Windows version, thus having semidecent network tools.

Type in netstat -an on a command line and look for anything interesting.

[Quantum Particle]

All that said is that it is a UDP connection coming from *:*

[Deepsmeg]

That's all it said? Nothing else at all?

[Quantum Particle]

Nope, the 'state' column is blank.

P.S. XP SP2, in case it is important anymore.

[ruhoward]

that's weird...maybe you can try security task manager(free) to see what program's connecting your pc to another computer.

[Quantum Particle]

But the thing is, its connecting to itself, and I want to know where in itself it is connected to. (am I still making sense?)

[Luigi300]

OMG SPYWAREZ

[Deepsmeg]

Code: Select all

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:21             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:25             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:110            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:6667           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:8080           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:20025          0.0.0.0:0              LISTENING
  TCP    <MY IP>:2377       <IP>:1863       ESTABLISHED
  TCP    127.0.0.1:1028         0.0.0.0:0              LISTENING
  UDP    0.0.0.0:445            *:*
  UDP    0.0.0.0:500            *:*
  UDP    0.0.0.0:1030           *:*
  UDP    0.0.0.0:1076           *:*
  UDP    0.0.0.0:1186           *:*
  UDP    0.0.0.0:1269           *:*
  UDP    0.0.0.0:1275           *:*
  UDP    0.0.0.0:3456           *:*
  UDP    0.0.0.0:4500           *:*
  UDP    <MY IP>:9          *:*
  UDP    <MY IP>:123        *:*
  UDP    <MY IP>:1900       *:*
  UDP    127.0.0.1:123          *:*
  UDP    127.0.0.1:1037         *:*
  UDP    127.0.0.1:1204         *:*
  UDP    127.0.0.1:1900         *:*
  UDP    127.0.0.1:3629         *:*


There we go.
That's my one.
XP SP2.
Yours only has the UDP lines?

[Quantum Particle]

No, the port i'm looking for is a UDP, there are TCP ones; should I post a transcript?

[Deepsmeg]

Up to you.
I'm too tired to do thinking at the moment.

[Mr. Roboto]

Sounds like what's needed is a good firewall, one that actually logs incoming/outgoing traffic.

Sygate has a good personal firewall that does that, plus it's free!

It may not tell you what files it's trying to access, but at least you can find out who is trying to acess them.

[Stewsburntmonkey]

First off it would help to provide actual port number and any other information you have about it.

When something connects to the computer it is not connecting to a file or folder, but to a program. Each port has a type of program "listening" on it which handles any connections on that port. Different ports use different types of connection protocols which are used for different things, FTP, TCP, SSH, TelNet, etc. The port number will generally allow you to figure out which program is using that port.

[Blasted heath]

Installing a firewall which blocks incoming/outgoing traffic until you say otherwise may be of use, that way you can see what is trying to connect where, and what is trying to receive the connection.

[Quantum Particle]

Ah; I tried that, and found that it is a game I have, why it is accessing itself I'm not sure.
PS port kept changing