Slow browsing and baaad pings... :(

[Chrysalis]

depends on what you doing, for example if you loading a website it will temporarily open multiple connections, it doesnt download via 1 connection but they are temporary only.

Things that normally leave open connections are irc, msn and telnet sessions, if you have downloads going they will be using connections, p2p will add numerous connections.

Trojans can leave open connections depending on what they are doing but they will normally have at least 1 active connection and 1 listening connection.

netstat -n -a should show everything and adding -b will show the process name.

[V3n0m]

Yes i was told to do the same thing(netstat)and i had 7 connections running and the ntl guy said that is my problem.....

I explained to him that these were open in the daytime when i was not suffering with ping loss/packet loss so it couldn't be that,he said perhaps there wasn't so much traffic in the daytime so the open connections wouldn't effect it so much

I have a program which i can use that turns all activities off on my computer(except my firewall)just for gaming so i ran this and then checked again netstat...i had only one open,so then went online but it was no different with the bad pings and packet losses

So what next?

[patrickp]

Originally Posted by Chrysalis

depends on what you doing, for example if you loading a website it will temporarily open multiple connections, it doesnt download via 1 connection but they are temporary only.

Things that normally leave open connections are irc, msn and telnet sessions, if you have downloads going they will be using connections, p2p will add numerous connections.

Trojans can leave open connections depending on what they are doing but they will normally have at least 1 active connection and 1 listening connection.

netstat -n -a should show everything and adding -b will show the process name.

Is -b an XP switch? Doesn't do anything in W2K.

[Chrysalis]

its listed in the syntax when i do /? but when I try it myself the netstat command hangs after the 1st line.