Home News Forum Articles
  Welcome back Join CF
You are here You are here: Home | Forum | Too many TCP ports listening?

You are currently viewing our boards as a guest which gives you limited access to view most of the discussions, articles and other free features. By joining our Virgin Media community you will have full access to all discussions, be able to view and post threads, communicate privately with other members (PM), respond to polls, upload your own images/photos, and access many other special features. Registration is fast, simple and absolutely free so please join our community today.


Welcome to Cable Forum
Go Back   Cable Forum > Virgin Media Services > Virgin Media Internet Service
Reload this Page Too many TCP ports listening?
Register FAQ Community Calendar

Too many TCP ports listening?
Reply
Page 1 of 2 1 2
 
Thread Tools
Old 25-11-2010, 20:26   #1
dillinger88
Inactive
 
Join Date: Nov 2010
Services: VirginMedia XL
Posts: 7
dillinger88 is an unknown quantity at this point
Too many TCP ports listening?
Hi guys,

I've been on the phone to Virgin Media about packet loss issues that have been going on for months. I got a strange answer today. Apparently pinging my modem returned all packets, so the chap asked me to do a netstat and said that I have way too many TCP ports listening and that is what is causing my packet loss etc. Possibly due to spyware etc.

Below is a copy of my netstat output, could anyone confirm that this may be an issue and if so what could be causing it? I've done some spyware and virus scans and found nothing.

Cheers,

Dan


Code:
C:\Users\Dillinger>netstat -a

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            Dillinger-PC:0         LISTENING
  TCP    0.0.0.0:445            Dillinger-PC:0         LISTENING
  TCP    0.0.0.0:554            Dillinger-PC:0         LISTENING
  TCP    0.0.0.0:2869           Dillinger-PC:0         LISTENING
  TCP    0.0.0.0:5357           Dillinger-PC:0         LISTENING
  TCP    0.0.0.0:10243          Dillinger-PC:0         LISTENING
  TCP    0.0.0.0:49152          Dillinger-PC:0         LISTENING
  TCP    0.0.0.0:49153          Dillinger-PC:0         LISTENING
  TCP    0.0.0.0:49154          Dillinger-PC:0         LISTENING
  TCP    0.0.0.0:49155          Dillinger-PC:0         LISTENING
  TCP    0.0.0.0:49156          Dillinger-PC:0         LISTENING
  TCP    81.108.156.39:49365    lhr14s01-in-f104:https  ESTABLISHED
  TCP    81.108.156.39:49372    209.85.143.155:http    ESTABLISHED
  TCP    81.108.156.39:49376    lhr14s01-in-f164:http  ESTABLISHED
  TCP    81.108.156.39:49377    209.85.143.165:http    ESTABLISHED
  TCP    81.108.156.39:49378    209.85.143.165:http    ESTABLISHED
  TCP    81.108.156.39:49379    209.85.143.155:http    ESTABLISHED
  TCP    81.108.156.39:49380    209.85.143.155:http    ESTABLISHED
  TCP    81.108.156.39:49381    ww-in-f101:http        ESTABLISHED
  TCP    81.108.156.39:49382    209.85.143.165:http    ESTABLISHED
  TCP    [::]:135               Dillinger-PC:0         LISTENING
  TCP    [::]:445               Dillinger-PC:0         LISTENING
  TCP    [::]:554               Dillinger-PC:0         LISTENING
  TCP    [::]:2869              Dillinger-PC:0         LISTENING
  TCP    [::]:5357              Dillinger-PC:0         LISTENING
  TCP    [::]:10243             Dillinger-PC:0         LISTENING
  TCP    [::]:49152             Dillinger-PC:0         LISTENING
  TCP    [::]:49153             Dillinger-PC:0         LISTENING
  TCP    [::]:49154             Dillinger-PC:0         LISTENING
  TCP    [::]:49155             Dillinger-PC:0         LISTENING
  TCP    [::]:49156             Dillinger-PC:0         LISTENING
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:5004           *:*
  UDP    0.0.0.0:5005           *:*
  UDP    0.0.0.0:5355           *:*
  UDP    0.0.0.0:51677          *:*
  UDP    81.108.156.39:1900     *:*
  UDP    81.108.156.39:55411    *:*
  UDP    127.0.0.1:1900         *:*
  UDP    127.0.0.1:55412        *:*
  UDP    [::]:3540              *:*
  UDP    [::]:3702              *:*
  UDP    [::]:3702              *:*
  UDP    [::]:5004              *:*
  UDP    [::]:5005              *:*
  UDP    [::]:5355              *:*
  UDP    [::]:51678             *:*
  UDP    [::1]:1900             *:*
  UDP    [::1]:55410            *:*
  UDP    [fe80::d32:48bb:7f1b:f8f9%11]:1900  *:*
  UDP    [fe80::d32:48bb:7f1b:f8f9%11]:55409  *:*
dillinger88 is offline   Reply With Quote
Advertisement
Old 25-11-2010, 20:43   #2
Andrewcrawford23
Inactive
 
Join Date: Aug 2005
Location: Scotland
Age: 42
Services: Virgin Media - XL Plus package with XXL broadband SKY HD Multiroom Freeview HD Freesat HD
Posts: 2,816
Andrewcrawford23 has reached the bronze age
Andrewcrawford23 has reached the bronze ageAndrewcrawford23 has reached the bronze ageAndrewcrawford23 has reached the bronze ageAndrewcrawford23 has reached the bronze age
Re: Too many TCP ports listening?
they are right that is to many it might be other things it looks like you have program running in the background, reboot to safe-mode with networking and repeat the command and see if you have less if you do try your connection see if it better if so you need to optimise your computer start-up
Andrewcrawford23 is offline   Reply With Quote
Old 25-11-2010, 21:09   #3
Peter_
Permanently Banned
 
Join Date: Jan 2009
Location: In a world of no buffering!!
Services: Samsung V+ XL TV XL Phone 30Mb Superhub Samsung Galaxy 3 32GB sd card In a world of no buffering!
Posts: 20,915
Peter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered stars
Peter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered stars
Re: Too many TCP ports listening?
What operating system are you running, if XP then it is a few to many but Vista and Windows 7 have more but are fine, my netstat -an has a similar amount to your own above.

Try netstat -b and it will list what the established connections actually are by name such as Itunes etc.
Peter_ is offline   Reply With Quote
Old 25-11-2010, 21:14   #4
Aragorn
Inactive
 
Aragorn's Avatar
 
Join Date: Apr 2004
Location: Minas Tirith, Gondor
Age: 58
Posts: 3,458
Aragorn has a nice shiny star
Aragorn has a nice shiny starAragorn has a nice shiny starAragorn has a nice shiny starAragorn has a nice shiny starAragorn has a nice shiny starAragorn has a nice shiny starAragorn has a nice shiny starAragorn has a nice shiny starAragorn has a nice shiny starAragorn has a nice shiny starAragorn has a nice shiny starAragorn has a nice shiny star
Re: Too many TCP ports listening?
Quote:
Originally Posted by dillinger88 View Post
Hi guys,

I've been on the phone to Virgin Media about packet loss issues that have been going on for months. I got a strange answer today. Apparently pinging my modem returned all packets, so the chap asked me to do a netstat and said that I have way too many TCP ports listening and that is what is causing my packet loss etc. Possibly due to spyware etc.

Below is a copy of my netstat output, could anyone confirm that this may be an issue and if so what could be causing it? I've done some spyware and virus scans and found nothing.

Cheers,

Dan
Sorry - absolute bull.

Packet loss and open ports have nothing to do with each other. Just an excuse to try and fob you off
If you really want to see what is open, visit www.grc.com and run his port scanner. But that list doesn't look abnormal anyway.

to CF anyway.

---------- Post added at 21:14 ---------- Previous post was at 21:13 ----------

Btw, the 209.85.143.0 range is registered to Google!
Aragorn is offline   Reply With Quote
Old 25-11-2010, 21:15   #5
Peter_
Permanently Banned
 
Join Date: Jan 2009
Location: In a world of no buffering!!
Services: Samsung V+ XL TV XL Phone 30Mb Superhub Samsung Galaxy 3 32GB sd card In a world of no buffering!
Posts: 20,915
Peter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered stars
Peter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered stars
Re: Too many TCP ports listening?
Quote:
Originally Posted by Aragorn View Post
Sorry - absolute bull.

Packet loss and open ports have nothing to do with each other. Just an excuse to try and fob you off
If you really want to see what is open, visit www.grc.com and run his port scanner. But that list doesn't look abnormal anyway.

to CF anyway.
Quite true, I hate agents who pull stunts like this as it gives customers a totally wrong impression.
Peter_ is offline   Reply With Quote
Old 25-11-2010, 21:15   #6
pip08456
Sad Doig Fan!
 
pip08456's Avatar
 
Join Date: Aug 2007
Location: Barry South Wales
Age: 68
Services: With VM for BB 250Mb service.(Deal)
Posts: 11,652
pip08456 has a nice shiny starpip08456 has a nice shiny star
pip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny star
Re: Too many TCP ports listening?
I'd hate to post mine with a torrent client running!
pip08456 is offline   Reply With Quote
Old 25-11-2010, 21:18   #7
Peter_
Permanently Banned
 
Join Date: Jan 2009
Location: In a world of no buffering!!
Services: Samsung V+ XL TV XL Phone 30Mb Superhub Samsung Galaxy 3 32GB sd card In a world of no buffering!
Posts: 20,915
Peter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered stars
Peter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered stars
Re: Too many TCP ports listening?
Quote:
Originally Posted by pip08456 View Post
I'd hate to post mine with a torrent client running!
You can get a few with just itunes running especially on XP.
Peter_ is offline   Reply With Quote
Old 25-11-2010, 21:44   #8
pip08456
Sad Doig Fan!
 
pip08456's Avatar
 
Join Date: Aug 2007
Location: Barry South Wales
Age: 68
Services: With VM for BB 250Mb service.(Deal)
Posts: 11,652
pip08456 has a nice shiny starpip08456 has a nice shiny star
pip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny starpip08456 has a nice shiny star
Re: Too many TCP ports listening?
I have a lot more due to using the EvID4226 patch in which you can change the default XP setting.

I'll do a netstat and post it if you want, I'll have to look for a torrent though (should only take all of 20secs).

A legal torrent BTW (The Wizard of Speed and Time)

TCP pips:26442 localhost:30606 ESTABLISHED
TCP pips:26478 localhost:30606 ESTABLISHED
TCP pips:26544 localhost:30606 ESTABLISHED
TCP pips:27152 localhost:30606 ESTABLISHED
TCP pips:27552 localhost:30606 ESTABLISHED
TCP pips:28996 localhost:30606 ESTABLISHED
TCP pips:29006 localhost:30606 ESTABLISHED
TCP pips:29010 localhost:30606 ESTABLISHED
TCP pips:29012 localhost:30606 ESTABLISHED
TCP pips:29016 localhost:30606 ESTABLISHED
TCP pips:29030 localhost:30606 ESTABLISHED
TCP pips:29055 localhost:30606 ESTABLISHED
TCP pips:29064 localhost:30606 ESTABLISHED
TCP pips:29066 localhost:30606 ESTABLISHED
TCP pips:29084 localhost:30606 ESTABLISHED
TCP pips:29092 localhost:30606 ESTABLISHED
TCP pips:29094 localhost:30606 ESTABLISHED
TCP pips:29096 localhost:30606 ESTABLISHED
TCP pips:29106 localhost:30606 ESTABLISHED
TCP pips:29108 localhost:30606 ESTABLISHED
TCP pips:29114 localhost:30606 ESTABLISHED
TCP pips:29118 localhost:30606 ESTABLISHED
TCP pips:29120 localhost:30606 ESTABLISHED
TCP pips:29122 localhost:30606 ESTABLISHED
TCP pips:29126 localhost:30606 ESTABLISHED
TCP pips:29128 localhost:30606 ESTABLISHED
TCP pips:29130 localhost:30606 ESTABLISHED
TCP pips:29142 localhost:30606 ESTABLISHED
TCP pips:29145 localhost:30606 ESTABLISHED
TCP pips:29148 localhost:30606 ESTABLISHED
TCP pips:29149 localhost:30606 ESTABLISHED
TCP pips:29212 localhost:30606 ESTABLISHED
TCP pips:29214 localhost:30606 ESTABLISHED
TCP pips:29218 localhost:30606 ESTABLISHED
TCP pips:29220 localhost:30606 ESTABLISHED
TCP pips:29222 localhost:30606 ESTABLISHED
TCP pips:29223 localhost:30606 ESTABLISHED
TCP pips:29226 localhost:30606 ESTABLISHED
TCP pips:29228 localhost:30606 ESTABLISHED
TCP pips:29247 localhost:30606 ESTABLISHED
TCP pips:29252 localhost:30606 ESTABLISHED
TCP pips:29254 localhost:30606 ESTABLISHED
TCP pips:29258 localhost:30606 ESTABLISHED
TCP pips:29270 localhost:30606 ESTABLISHED
TCP pips:29294 localhost:30606 ESTABLISHED
TCP pips:29310 localhost:30606 ESTABLISHED
TCP pips:29312 localhost:30606 ESTABLISHED
TCP pips:29314 localhost:30606 ESTABLISHED
TCP pips:29316 localhost:30606 ESTABLISHED
TCP pips:29322 localhost:30606 ESTABLISHED
TCP pips:29328 localhost:30606 ESTABLISHED
TCP pips:29330 localhost:30606 ESTABLISHED
TCP pips:29336 localhost:30606 ESTABLISHED
TCP pips:29337 localhost:30606 ESTABLISHED
TCP pips:29340 localhost:30606 ESTABLISHED
TCP pips:29342 localhost:30606 ESTABLISHED
TCP pips:29343 localhost:30606 ESTABLISHED
TCP pips:29406 localhost:30606 ESTABLISHED
TCP pips:29418 localhost:30606 ESTABLISHED
TCP pips:29448 localhost:30606 ESTABLISHED
TCP pips:29452 localhost:30606 ESTABLISHED
TCP pips:29454 localhost:30606 ESTABLISHED
TCP pips:29458 localhost:30606 ESTABLISHED
TCP pips:29462 localhost:30606 ESTABLISHED
TCP pips:30606 pips:0 LISTENING
TCP pips:30606 localhost:14665 ESTABLISHED
TCP pips:30606 localhost:15167 ESTABLISHED
TCP pips:30606 localhost:26442 ESTABLISHED
TCP pips:30606 localhost:26478 ESTABLISHED
TCP pips:30606 localhost:26544 ESTABLISHED
TCP pips:30606 localhost:27152 ESTABLISHED
TCP pips:30606 localhost:27552 ESTABLISHED
TCP pips:30606 localhost:28996 ESTABLISHED
TCP pips:30606 localhost:29004 TIME_WAIT
TCP pips:30606 localhost:29006 ESTABLISHED
TCP pips:30606 localhost:29010 ESTABLISHED
TCP pips:30606 localhost:29012 ESTABLISHED
TCP pips:30606 localhost:29016 ESTABLISHED
TCP pips:30606 localhost:29030 ESTABLISHED
TCP pips:30606 localhost:29055 ESTABLISHED
TCP pips:30606 localhost:29064 ESTABLISHED
TCP pips:30606 localhost:29066 ESTABLISHED
TCP pips:30606 localhost:29084 ESTABLISHED
TCP pips:30606 localhost:29092 ESTABLISHED
TCP pips:30606 localhost:29094 ESTABLISHED
TCP pips:30606 localhost:29096 ESTABLISHED
TCP pips:30606 localhost:29106 ESTABLISHED
TCP pips:30606 localhost:29108 ESTABLISHED
TCP pips:30606 localhost:29114 ESTABLISHED
TCP pips:30606 localhost:29118 ESTABLISHED
TCP pips:30606 localhost:29120 ESTABLISHED
TCP pips:30606 localhost:29122 ESTABLISHED
TCP pips:30606 localhost:29126 ESTABLISHED
TCP pips:30606 localhost:29128 ESTABLISHED
TCP pips:30606 localhost:29130 ESTABLISHED
TCP pips:30606 localhost:29142 ESTABLISHED
TCP pips:30606 localhost:29145 ESTABLISHED
TCP pips:30606 localhost:29148 ESTABLISHED
TCP pips:30606 localhost:29149 ESTABLISHED
TCP pips:30606 localhost:29212 ESTABLISHED
TCP pips:30606 localhost:29214 ESTABLISHED
TCP pips:30606 localhost:29218 ESTABLISHED
TCP pips:30606 localhost:29220 ESTABLISHED
TCP pips:30606 localhost:29222 ESTABLISHED
TCP pips:30606 localhost:29223 ESTABLISHED
TCP pips:30606 localhost:29226 ESTABLISHED
TCP pips:30606 localhost:29228 ESTABLISHED
TCP pips:30606 localhost:29247 ESTABLISHED
TCP pips:30606 localhost:29252 ESTABLISHED
TCP pips:30606 localhost:29254 ESTABLISHED
TCP pips:30606 localhost:29258 ESTABLISHED
TCP pips:30606 localhost:29266 TIME_WAIT
TCP pips:30606 localhost:29270 ESTABLISHED
TCP pips:30606 localhost:29294 ESTABLISHED
TCP pips:30606 localhost:29310 ESTABLISHED
TCP pips:30606 localhost:29312 ESTABLISHED
TCP pips:30606 localhost:29314 ESTABLISHED
TCP pips:30606 localhost:29316 ESTABLISHED
TCP pips:30606 localhost:29322 ESTABLISHED
TCP pips:30606 localhost:29328 ESTABLISHED
TCP pips:30606 localhost:29330 ESTABLISHED
TCP pips:30606 localhost:29336 ESTABLISHED
TCP pips:30606 localhost:29337 ESTABLISHED
TCP pips:30606 localhost:29340 ESTABLISHED
TCP pips:30606 localhost:29342 ESTABLISHED
TCP pips:30606 localhost:29343 ESTABLISHED
TCP pips:30606 localhost:29406 ESTABLISHED
TCP pips:30606 localhost:29418 ESTABLISHED
TCP pips:30606 localhost:29448 ESTABLISHED
TCP pips:30606 localhost:29450 TIME_WAIT
TCP pips:30606 localhost:29452 ESTABLISHED
TCP pips:30606 localhost:29454 ESTABLISHED
TCP pips:30606 localhost:29456 TIME_WAIT
TCP pips:30606 localhost:29458 ESTABLISHED
TCP pips:30606 localhost:29462 ESTABLISHED
TCP pips:30606 localhost:29464 TIME_WAIT
TCP pips:30606 localhost:29466 TIME_WAIT
TCP pips:netbios-ssn pips:0 LISTENING
TCP pips:14666 unknown.logmein.com:12975 ESTABLISHED
TCP pips:15168 unknown.logmein.com:http ESTABLISHED
TCP pips:26444 nook.axonpro.sk:6881 ESTABLISHED
TCP pips:26479 CPE-72-133-221-194.wi.res.rr.com:2121 ESTABLISH
ED
TCP pips:26545 chtwpe01bba-142177250148.pppoe-dynamic.High-Spee
d.pei.bellaliant.net:50101 ESTABLISHED
TCP pips:27153 ns208717.ovh.net:51413 ESTABLISHED
TCP pips:27553 cpe-72-134-43-123.socal.res.rr.com:55231 ESTABL
ISHED
TCP pips:28997 coral.getaseedbox.com:65006 ESTABLISHED
TCP pips:29007 60-240-10-207.tpgi.com.au:13777 ESTABLISHED
TCP pips:29011 cpe-24-90-18-160.nyc.res.rr.com:24170 ESTABLISH
ED
TCP pips:29013 c-24-20-151-19.hsd1.or.comcast.net:51250 ESTABL
ISHED
TCP pips:29017 h108.221.189.173.dynamic.ip.windstream.net:63924
ESTABLISHED
TCP pips:29031 sd-1163.dedibox.fr:27440 ESTABLISHED
TCP pips:29057 cpe-76-84-162-179.neb.res.rr.com:52000 ESTABLIS
HED
TCP pips:29065 c-98-231-95-194.hsd1.fl.comcast.net:50001 ESTAB
LISHED
TCP pips:29067 ool-457cd8a1.dyn.optonline.net:49929 ESTABLISHE
D
TCP pips:29085 71-81-72-232.dhcp.stls.mo.charter.com:http ESTA
BLISHED
TCP pips:29093 c-68-34-210-119.hsd1.tn.comcast.net:42946 ESTAB
LISHED
TCP pips:29095 c-98-203-182-241.hsd1.wa.comcast.net:32626 ESTA
BLISHED
TCP pips:29097 ip68-97-18-236.ok.ok.cox.net:12383 ESTABLISHED
TCP pips:29107 66.183.229.122:51515 ESTABLISHED
TCP pips:29109 pool-98-113-32-41.nycmny.fios.verizon.net:13753
ESTABLISHED
TCP pips:29115 64.150.197.65:10057 ESTABLISHED
TCP pips:29119 c-98-223-224-111.hsd1.in.comcast.net:44713 ESTA
BLISHED
TCP pips:29121 c-98-250-19-166.hsd1.mi.comcast.net:60434 ESTAB
LISHED
TCP pips:29123 50.165-62-69.ftth.swbr.surewest.net:41180 ESTAB
LISHED
TCP pips:29127 76-10-154-132.dsl.teksavvy.com:786 ESTABLISHED
TCP pips:29129 ool-457eb22a.dyn.optonline.net:62193 ESTABLISHE
D
TCP pips:29131 190-50-81-11.speedy.com.ar:32827 ESTABLISHED
TCP pips:29143 89.130.210.206:33637 ESTABLISHED
TCP pips:29147 cpc9-leic14-2-0-cust214.8-1.cable.virginmedia.co
m:47750 ESTABLISHED
TCP pips:29150 host96.190-225-69.telecom.net.ar:20060 ESTABLIS
HED
TCP pips:29151 cpe-70-123-190-26.stx.res.rr.com:63497 ESTABLIS
HED
TCP pips:29213 S010600223f90f21c.cg.shawcable.net:59679 ESTABL
ISHED
TCP pips:29215 S0106002275e3c9e3.cg.shawcable.net:47539 ESTABL
ISHED
TCP pips:29219 ip98-176-73-156.sd.sd.cox.net:55997 ESTABLISHED

TCP pips:29221 semi066b.xirvik.com:51741 ESTABLISHED
TCP pips:29224 85.17.5.25:54106 ESTABLISHED
TCP pips:29225 81-232-157-170-no28.tbcn.telia.com:64505 ESTABL
ISHED
TCP pips:29227 79.103.124.31.dsl.dyn.forthnet.gr:35475 ESTABLI
SHED
TCP pips:29229 129.137.8.67.cfl.res.rr.com:26889 ESTABLISHED
TCP pips:29249 h-72-244-63-38.dnvtco56.dynamic.covad.net:10027
ESTABLISHED
TCP pips:29253 host-67-226-234-29.drytel.net:50611 ESTABLISHED

TCP pips:29255 varsbox.com:49732 ESTABLISHED
TCP pips:29261 dsl.static-187-116-74-220.electronicbox.net:3030
6 ESTABLISHED
TCP pips:29271 246.220.191.90.dyn.estpak.ee:34003 ESTABLISHED
TCP pips:29295 lhr14s02-in-f104.1e100.net:http ESTABLISHED
TCP pips:29311 lhr14s02-in-f104.1e100.net:http ESTABLISHED
TCP pips:29313 lhr14s02-in-f104.1e100.net:http ESTABLISHED
TCP pips:29315 lhr14s02-in-f104.1e100.net:http ESTABLISHED
TCP pips:29317 lhr14s02-in-f104.1e100.net:http ESTABLISHED
TCP pips:29323 ww-in-f102.1e100.net:http ESTABLISHED
TCP pips:29329 84.6.23.197:39926 ESTABLISHED
TCP pips:29331 75-169-142-4.slkc.qwest.net:42377 ESTABLISHED
TCP pips:29338 212-95-32-87.local:41805 ESTABLISHED
TCP pips:29339 pool-74-102-1-45.nwrknj.fios.verizon.net:23574
ESTABLISHED
TCP pips:29341 c-71-235-161-226.hsd1.ct.comcast.net:29615 ESTA
BLISHED
TCP pips:29344 c-66-41-5-37.hsd1.mn.comcast.net:61821 ESTABLIS
HED
TCP pips:29345 d60-65-105-221.col.wideopenwest.com:41857 ESTAB
LISHED
TCP pips:29407 ABTS-TN-dynamic-201.73.174.122.airtelbroadband.i
n:54321 ESTABLISHED
TCP pips:29419 178-25-228-206-dynip.superkabel.de:60650 ESTABL
ISHED
TCP pips:29449 ns353386.ovh.net:17401 ESTABLISHED
TCP pips:29453 r180-216-126-45.cpe.vividwireless.net.au:51414
ESTABLISHED
TCP pips:29455 5ac3ea18.bb.sky.com:64327 ESTABLISHED
TCP pips:29459 mail.crenterprises.us:44035 SYN_SENT
TCP pips:29463 CPE00222d5a43a8-CM00222d5a43a5.cpe.net.cable.rog
ers.com:1720 ESTABLISHED
TCP pips:29465 70-140-21-44.lightspeed.hstntx.sbcglobal.net:460
00 LAST_ACK
TCP pips:55500 host-68-169-141-220.MIDOLT1.epbfi.com:58935 EST
ABLISHED
TCP pips:55500 69.169.130.156.provo.static.broadweavenetworks.n
et:2966 ESTABLISHED
TCP pips:55500 c-69-242-198-57.hsd1.sc.comcast.net:61755 ESTAB
LISHED
TCP pips:55500 wnpgmb0284w-ad02-9-250.dynamic.mts.net:60660 ES
TABLISHED
TCP pips:55500 78-105-113-17.zone3.bethere.co.uk:60305 ESTABLI
SHED
TCP pips:55500 81.0.83.245.pool.invitel.hu:2448 ESTABLISHED
TCP pips:55500 c83-252-11-167.bredband.comhem.se:53219 ESTABLI
SHED
TCP pips:55500 85.65.116.208.dynamic.barak-online.net:53995 TI
ME_WAIT
TCP pips:55500 e177004025.adsl.alicedsl.de:62848 ESTABLISHED
TCP pips:55500 1503027191.dong.dbnet.dk:55161 ESTABLISHED
TCP pips:55500 srv123.myseedbox.net:50386 ESTABLISHED
TCP pips:55500 cpe-107-9-140-78.neo.res.rr.com:54729 ESTABLISH
ED
TCP pips:55500 173-8-101-2-Minnesota.hfc.comcastbusiness.net:62
854 ESTABLISHED
TCP pips:55500 DD-WRT:29457 TIME_WAIT
TCP pips:55500 DD-WRT:29467 TIME_WAIT
TCP pips:55500 200-56-220-13-cable.cybercable.net.mx:64764 EST
ABLISHED
TCP pips:55500 206.173.81.209.ptr.us.xo.net:3903 ESTABLISHED
TCP pips:55500 dhcp-0-1a-a0-5e-71-59.cpe.quickclic.net:50820 E
STABLISHED
TCP pips:55500 user-387o32q.cable.mindspring.com:58167 ESTABLI
SHED
TCP pips:55500 mail.startpo.co.il:33443 ESTABLISHED
TCP pips:55500 cpc4-stre5-2-0-cust52.1-1.cable.virginmedia.com:
61381 ESTABLISHED
UDP pips:microsoft-ds *:*
UDP pips:isakmp *:*
UDP pips:4500 *:*
UDP pips:6771 *:*
UDP pips:55500 *:*
UDP pips:ntp *:*
UDP pips:netbios-ns *:*
UDP pips:netbios-dgm *:*
UDP pips:1900 *:*
UDP pips:20931 *:*
UDP pips:56480 *:*
UDP pips:ntp *:*
UDP pips:1900 *:*
UDP pips:13498 *:*
UDP pips:14704 *:*
UDP pips:ntp *:*
UDP pips:netbios-ns *:*
UDP pips:netbios-dgm *:*
UDP pips:1900 *:*
UDP pips:41582 *:*

C:\Documents and Settings\Pip>

C:\Documents and Settings\Pip>
pip08456 is offline   Reply With Quote
Old 25-11-2010, 22:32   #9
dillinger88
Inactive
 
Join Date: Nov 2010
Services: VirginMedia XL
Posts: 7
dillinger88 is an unknown quantity at this point
Re: Too many TCP ports listening?
Thanks for all the replies guys. And thanks for the welcome Aragorn.

I've booted the computer into safe mode and the number of ports dropped drastically. As expected there was no improvement in line quality.

As I mentioned earlier, this has been going on for approximately 2 months now. Apparently some work was carried on Friday to alleviate the problem and for the the weekend that was the case. By Monday, though, I was back to the 10-30% packet loss.

They say that all the pings to my modem returned without fault and that it's my equipment.

I ran a test over 24 hours using hostmycalls.com and got the results below. Seems like a UBR problem to me, they just won't admit it.

[img]Download Failed (1)[/img]

Pathping to bbc.co.uk:

Code:
C:\Users\Dillinger>pathping bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:
  0  Dillinger-PC [192.168.1.3]
  1  192.168.1.1
  2  10.147.208.1
  3  leed-core-1b-ge-300-2201.network.virginmedia.net [80.0.55.233]
  4     *     leed-bb-1b-as5-0.network.virginmedia.net [213.105.175.69]
  5  leed-bb-1a-ae0-0.network.virginmedia.net [62.253.187.185]
  6  nrth-bb-1b-as2-0.network.virginmedia.net [62.253.185.101]
  7  nrth-tmr-2-ae6-0.network.virginmedia.net [213.105.159.34]
  8  tele-ic-1-as0-0.network.virginmedia.net [62.253.184.2]
  9  pos6-1.rt0.thdo.bbc.co.uk [212.58.239.237]
 10  212.58.238.153
 11  virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Computing statistics for 275 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Dillinger-PC [192.168.1.3]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                                4/ 100 =  4%   |
  2  ---     100/ 100 =100%    96/ 100 = 96%  10.147.208.1
                                0/ 100 =  0%   |
  3   46ms    10/ 100 = 10%     6/ 100 =  6%  leed-core-1b-ge-300-2201.network.virginmedia.net [80.0.55.233]
                                0/ 100 =  0%   |
  4   48ms    10/ 100 = 10%     6/ 100 =  6%  leed-bb-1b-as5-0.network.virginmedia.net [213.105.175.69]
                                0/ 100 =  0%   |
  5   53ms     4/ 100 =  4%     0/ 100 =  0%  leed-bb-1a-ae0-0.network.virginmedia.net [62.253.187.185]
                                0/ 100 =  0%   |
  6   53ms     9/ 100 =  9%     5/ 100 =  5%  nrth-bb-1b-as2-0.network.virginmedia.net [62.253.185.101]
                                0/ 100 =  0%   |
  7   52ms     6/ 100 =  6%     2/ 100 =  2%  nrth-tmr-2-ae6-0.network.virginmedia.net [213.105.159.34]
                                0/ 100 =  0%   |
  8   54ms     9/ 100 =  9%     5/ 100 =  5%  tele-ic-1-as0-0.network.virginmedia.net [62.253.184.2]
                                0/ 100 =  0%   |
  9   55ms     7/ 100 =  7%     3/ 100 =  3%  pos6-1.rt0.thdo.bbc.co.uk [212.58.239.237]
                                0/ 100 =  0%   |
 10   49ms     6/ 100 =  6%     2/ 100 =  2%  212.58.238.153
                                0/ 100 =  0%   |
 11   47ms     4/ 100 =  4%     0/ 100 =  0%  virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.
Code:
C:\Users\Dillinger>ping bbc.co.uk -n 30

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=105ms TTL=118
Request timed out.
Reply from 212.58.224.138: bytes=32 time=57ms TTL=118
Request timed out.
Request timed out.
Reply from 212.58.224.138: bytes=32 time=27ms TTL=118
Reply from 212.58.224.138: bytes=32 time=50ms TTL=118
Reply from 212.58.224.138: bytes=32 time=130ms TTL=118
Reply from 212.58.224.138: bytes=32 time=44ms TTL=118
Reply from 212.58.224.138: bytes=32 time=40ms TTL=118
Reply from 212.58.224.138: bytes=32 time=62ms TTL=118
Reply from 212.58.224.138: bytes=32 time=61ms TTL=118
Reply from 212.58.224.138: bytes=32 time=67ms TTL=118
Reply from 212.58.224.138: bytes=32 time=83ms TTL=118
Reply from 212.58.224.138: bytes=32 time=54ms TTL=118
Reply from 212.58.224.138: bytes=32 time=131ms TTL=118
Reply from 212.58.224.138: bytes=32 time=162ms TTL=118
Reply from 212.58.224.138: bytes=32 time=38ms TTL=118
Request timed out.
Reply from 212.58.224.138: bytes=32 time=45ms TTL=118
Reply from 212.58.224.138: bytes=32 time=104ms TTL=118
Reply from 212.58.224.138: bytes=32 time=31ms TTL=118
Reply from 212.58.224.138: bytes=32 time=29ms TTL=118
Reply from 212.58.224.138: bytes=32 time=41ms TTL=118
Reply from 212.58.224.138: bytes=32 time=53ms TTL=118
Reply from 212.58.224.138: bytes=32 time=62ms TTL=118
Reply from 212.58.224.138: bytes=32 time=15ms TTL=118
Reply from 212.58.224.138: bytes=32 time=21ms TTL=118
Reply from 212.58.224.138: bytes=32 time=23ms TTL=118
Reply from 212.58.224.138: bytes=32 time=142ms TTL=118

Ping statistics for 212.58.224.138:
    Packets: Sent = 30, Received = 26, Lost = 4 (13% loss),
Approximate round trip times in milli-seconds:
    Minimum = 15ms, Maximum = 162ms, Average = 64ms
Any ideas what to do?

Cheers,

Dan
dillinger88 is offline   Reply With Quote
Old 26-11-2010, 17:16   #10
Andrewcrawford23
Inactive
 
Join Date: Aug 2005
Location: Scotland
Age: 42
Services: Virgin Media - XL Plus package with XXL broadband SKY HD Multiroom Freeview HD Freesat HD
Posts: 2,816
Andrewcrawford23 has reached the bronze age
Andrewcrawford23 has reached the bronze ageAndrewcrawford23 has reached the bronze ageAndrewcrawford23 has reached the bronze ageAndrewcrawford23 has reached the bronze age
Re: Too many TCP ports listening?
Quote:
Originally Posted by dillinger88 View Post
Thanks for all the replies guys. And thanks for the welcome Aragorn.

I've booted the computer into safe mode and the number of ports dropped drastically. As expected there was no improvement in line quality.

As I mentioned earlier, this has been going on for approximately 2 months now. Apparently some work was carried on Friday to alleviate the problem and for the the weekend that was the case. By Monday, though, I was back to the 10-30% packet loss.

They say that all the pings to my modem returned without fault and that it's my equipment.

I ran a test over 24 hours using hostmycalls.com and got the results below. Seems like a UBR problem to me, they just won't admit it.



Pathping to bbc.co.uk:

Code:
C:\Users\Dillinger>pathping bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:
  0  Dillinger-PC [192.168.1.3]
  1  192.168.1.1
  2  10.147.208.1
  3  leed-core-1b-ge-300-2201.network.virginmedia.net [80.0.55.233]
  4     *     leed-bb-1b-as5-0.network.virginmedia.net [213.105.175.69]
  5  leed-bb-1a-ae0-0.network.virginmedia.net [62.253.187.185]
  6  nrth-bb-1b-as2-0.network.virginmedia.net [62.253.185.101]
  7  nrth-tmr-2-ae6-0.network.virginmedia.net [213.105.159.34]
  8  tele-ic-1-as0-0.network.virginmedia.net [62.253.184.2]
  9  pos6-1.rt0.thdo.bbc.co.uk [212.58.239.237]
 10  212.58.238.153
 11  virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Computing statistics for 275 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Dillinger-PC [192.168.1.3]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                                4/ 100 =  4%   |
  2  ---     100/ 100 =100%    96/ 100 = 96%  10.147.208.1
                                0/ 100 =  0%   |
  3   46ms    10/ 100 = 10%     6/ 100 =  6%  leed-core-1b-ge-300-2201.network.virginmedia.net [80.0.55.233]
                                0/ 100 =  0%   |
  4   48ms    10/ 100 = 10%     6/ 100 =  6%  leed-bb-1b-as5-0.network.virginmedia.net [213.105.175.69]
                                0/ 100 =  0%   |
  5   53ms     4/ 100 =  4%     0/ 100 =  0%  leed-bb-1a-ae0-0.network.virginmedia.net [62.253.187.185]
                                0/ 100 =  0%   |
  6   53ms     9/ 100 =  9%     5/ 100 =  5%  nrth-bb-1b-as2-0.network.virginmedia.net [62.253.185.101]
                                0/ 100 =  0%   |
  7   52ms     6/ 100 =  6%     2/ 100 =  2%  nrth-tmr-2-ae6-0.network.virginmedia.net [213.105.159.34]
                                0/ 100 =  0%   |
  8   54ms     9/ 100 =  9%     5/ 100 =  5%  tele-ic-1-as0-0.network.virginmedia.net [62.253.184.2]
                                0/ 100 =  0%   |
  9   55ms     7/ 100 =  7%     3/ 100 =  3%  pos6-1.rt0.thdo.bbc.co.uk [212.58.239.237]
                                0/ 100 =  0%   |
 10   49ms     6/ 100 =  6%     2/ 100 =  2%  212.58.238.153
                                0/ 100 =  0%   |
 11   47ms     4/ 100 =  4%     0/ 100 =  0%  virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.
Code:
C:\Users\Dillinger>ping bbc.co.uk -n 30

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=105ms TTL=118
Request timed out.
Reply from 212.58.224.138: bytes=32 time=57ms TTL=118
Request timed out.
Request timed out.
Reply from 212.58.224.138: bytes=32 time=27ms TTL=118
Reply from 212.58.224.138: bytes=32 time=50ms TTL=118
Reply from 212.58.224.138: bytes=32 time=130ms TTL=118
Reply from 212.58.224.138: bytes=32 time=44ms TTL=118
Reply from 212.58.224.138: bytes=32 time=40ms TTL=118
Reply from 212.58.224.138: bytes=32 time=62ms TTL=118
Reply from 212.58.224.138: bytes=32 time=61ms TTL=118
Reply from 212.58.224.138: bytes=32 time=67ms TTL=118
Reply from 212.58.224.138: bytes=32 time=83ms TTL=118
Reply from 212.58.224.138: bytes=32 time=54ms TTL=118
Reply from 212.58.224.138: bytes=32 time=131ms TTL=118
Reply from 212.58.224.138: bytes=32 time=162ms TTL=118
Reply from 212.58.224.138: bytes=32 time=38ms TTL=118
Request timed out.
Reply from 212.58.224.138: bytes=32 time=45ms TTL=118
Reply from 212.58.224.138: bytes=32 time=104ms TTL=118
Reply from 212.58.224.138: bytes=32 time=31ms TTL=118
Reply from 212.58.224.138: bytes=32 time=29ms TTL=118
Reply from 212.58.224.138: bytes=32 time=41ms TTL=118
Reply from 212.58.224.138: bytes=32 time=53ms TTL=118
Reply from 212.58.224.138: bytes=32 time=62ms TTL=118
Reply from 212.58.224.138: bytes=32 time=15ms TTL=118
Reply from 212.58.224.138: bytes=32 time=21ms TTL=118
Reply from 212.58.224.138: bytes=32 time=23ms TTL=118
Reply from 212.58.224.138: bytes=32 time=142ms TTL=118

Ping statistics for 212.58.224.138:
    Packets: Sent = 30, Received = 26, Lost = 4 (13% loss),
Approximate round trip times in milli-seconds:
    Minimum = 15ms, Maximum = 162ms, Average = 64ms
Any ideas what to do?

Cheers,

Dan
your losing 100% at yoru rotuer so i look there first there always appears to eb network problem but your oruter could be affecting it do it straight to the modem and repeat then if there is anetowrk problem easier to identify but your rotuer is faulty in some way it losing 100 packets
Andrewcrawford23 is offline   Reply With Quote
Old 26-11-2010, 17:32   #11
vanman
cf.mega poster
 
Join Date: Apr 2010
Location: Luton
Services: Sky
Posts: 1,689
vanman has reached the bronze age
vanman has reached the bronze agevanman has reached the bronze agevanman has reached the bronze agevanman has reached the bronze agevanman has reached the bronze agevanman has reached the bronze age
Re: Too many TCP ports listening?
i may be wrong here but showing your ip and what ports are open on here may cause you a security problem
vanman is offline   Reply With Quote
Old 26-11-2010, 19:34   #12
Peter_
Permanently Banned
 
Join Date: Jan 2009
Location: In a world of no buffering!!
Services: Samsung V+ XL TV XL Phone 30Mb Superhub Samsung Galaxy 3 32GB sd card In a world of no buffering!
Posts: 20,915
Peter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered stars
Peter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered stars
Re: Too many TCP ports listening?
Quote:
Originally Posted by vanman View Post
i may be wrong here but showing your ip and what ports are open on here may cause you a security problem
That is not his ip address.
Peter_ is offline   Reply With Quote
Old 26-11-2010, 19:39   #13
vanman
cf.mega poster
 
Join Date: Apr 2010
Location: Luton
Services: Sky
Posts: 1,689
vanman has reached the bronze age
vanman has reached the bronze agevanman has reached the bronze agevanman has reached the bronze agevanman has reached the bronze agevanman has reached the bronze agevanman has reached the bronze age
Re: Too many TCP ports listening?
Quote:
Originally Posted by Masque View Post
That is not his ip address.
wot that
10.147.208.1
vanman is offline   Reply With Quote
Old 26-11-2010, 19:40   #14
Peter_
Permanently Banned
 
Join Date: Jan 2009
Location: In a world of no buffering!!
Services: Samsung V+ XL TV XL Phone 30Mb Superhub Samsung Galaxy 3 32GB sd card In a world of no buffering!
Posts: 20,915
Peter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered stars
Peter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered starsPeter_ is seeing silvered stars
Re: Too many TCP ports listening?
Quote:
Originally Posted by vanman View Post
wot that
10.147.208.1
That is his private ip not his public ip so you cannot get to his connection.
Peter_ is offline   Reply With Quote
Old 26-11-2010, 19:53   #15
vanman
cf.mega poster
 
Join Date: Apr 2010
Location: Luton
Services: Sky
Posts: 1,689
vanman has reached the bronze age
vanman has reached the bronze agevanman has reached the bronze agevanman has reached the bronze agevanman has reached the bronze agevanman has reached the bronze agevanman has reached the bronze age
Re: Too many TCP ports listening?
Quote:
Originally Posted by Masque View Post
That is his private ip not his public ip so you cannot get to his connection.
by googling that ip i find that he plays world of warcraft
and his name begins with s
and lives in leeds
vanman is offline   Reply With Quote
Reply
Page 1 of 2 1 2

« Previous Thread | Next Thread »

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 03:32.

Contact Us - Service Status - Cable Forum - Archive - Privacy Statement - Terms of Service - Top

Server: osmium.zmnt.uk
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.

Copyright © 2024 Cable Forum Hosted On Hetzner Cloud