xplornet says i have to many ports open
Hi i was just wondering if anyone can help me with a problem. My computer has win xp sp3 and everything works fine but sometimes i get connection timed out. i called xplornet and they said it was my computer. They said it was opening to many ports. When i talked to them they said i had over 2000 ports open. i scannned my computer for viruses and spyware and maleware and found nothing. So they said as long as i am using that many ports i will have problems. Does anyone know what is causing this.
Thanks for you help
Sounds to me like you are being fed a line.
You can run MalWareBytes, to scan for bugs. It's free and small enough to download.
Install, then update and scan, either quick scan or full system.
But do you have a Firewall running? Run one software firewall only. Windows firewall is incoming only.
Comodo does bug you a bit more with alerts than ZoneAlarm.
A router has an incoming hardware firewall, but a software firewall blocks programs from listening to the Internet or doing small communications to home base.
Connection timing out can be due to slow Satellite speeds(Lag and primetime) or if you visit webpages that have many links(sources) to be able to load the whole page(timing out from lag).
Do a speed test.
To determine if you are slow all the time, via a misaligned dish. OR is your timing out between 5pm to about 10pm(primetime)?
Testing times of abouts 7am and 7pm(primetime).
Torrents can also cause many connections to be open at once.
You can also ask phone support to have them look at your dish numbers to determine if your dish is properly aligned(signal strength).
Last edited by xplornetsuck : 12-08-2009 at 03:02 PM.
Thanks for your help. I did a malwarebyte scan and it found nothing and the only firewall i have is windows firewall. I do use torrents alot. All the software that i use is telling me that im not connectable. xplornet also told me my network adapter might have been installed wrong so i uninstalled and reinstalled and i still have the same problem. i even updated the drivers. Any other advise would be appreciated and i will try the speed test.
Xplornet blocks stuff at the servers, so a test like "shields up" from http://www.grc.com/default.htm , would show as ports in a position that is not set on your machine(ports showing open that are actually closed on your machine). Due to the fact that the pings did not hit your machine, as would show in the logs of your own firewall.
Network adapter installed wrong? The driver does sometimes get corrupted, but then usually you can't get online. Or your speed is dead slow.
And support may be just giving random causes for slowness that could be just Xplornet's problem. Some ISP's do play the blame game, instead of admitting system problems.
Last edited by xplornetsuck : 12-09-2009 at 04:56 PM.
This may be a new line of B.S. from Xplornet....BUT:
Try running your computer will all torrents disabled. Don't even run the bittorrent software, whatever you're using. Torrent software can open up a lot of ports, especially those programs -- most of them -- whose default is to allow torrent uploads as well as downloads. Your Windows firewall probably won't help, because the software running on your computer will open ports as it needs them.
Unfortunately I don't know the Windows command to find out how many ports are open on your PC. There may be a firewall option to absolutely prevent programs from opening ports, but I don't know that either. (I don't use Windows.) Perhaps someone else can help?
4G Fixed Wireless Formerly Echostar 17 "Jupiter"; Rogers Rocket Hub; Everus 3.5 GHz Wireless; Telesat Kazam plan; HughesNet Ku.
A computer without Windows is like a chocolate cake without mustard. http://www.goodbyemicrosoft.net
Use the command "netstat -an"
That will work on windows, shows all open ports and what IP they are connecting to.
Most routers are only capable of 200 simultaneous ports before they just 'crap out' :P
The canopy modules I think have a max of 2000, but will likely 'crap out' at 200...
If you set your torrent clients to have maximum simultaneous connections of something like 150 ports you should be ok... by default I think browsers will do 25 ports, but you can change that with the right tools... but use them at your own risk, where it patches the TCP/IP DLL.
i have utorrent set at 130 connections and this is the netstat -an
i had utorrent running when i did this
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
D:\Documents and Settings\Computer>netstat -an
Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1164 0.0.0.0:0 LISTENING
TCP 0.0.0.0:56860 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1030 0.0.0.0:0 LISTENING
TCP 127.0.0.1:4085 127.0.0.1:4086 ESTABLISHED
TCP 127.0.0.1:4086 127.0.0.1:4085 ESTABLISHED
TCP 127.0.0.1:4107 127.0.0.1:4108 ESTABLISHED
TCP 127.0.0.1:4108 127.0.0.1:4107 ESTABLISHED
TCP 127.0.0.1:5354 0.0.0.0:0 LISTENING
TCP 127.0.0.1:10110 0.0.0.0:0 LISTENING
TCP 127.0.0.1:27015 0.0.0.0:0 LISTENING
TCP 169.254.1.2:139 0.0.0.0:0 LISTENING
TCP 169.254.1.2:1173 220.127.116.11:4242 ESTABLISHED
TCP 169.254.1.2:1184 18.104.22.168:24779 ESTABLISHED
TCP 169.254.1.2:1223 22.214.171.124:5005 ESTABLISHED
TCP 169.254.1.2:1524 126.96.36.199:32611 ESTABLISHED
TCP 169.254.1.2:3288 188.8.131.52:26010 ESTABLISHED
TCP 169.254.1.2:3563 184.108.40.206:6346 ESTABLISHED
TCP 169.254.1.2:3801 220.127.116.11:6346 ESTABLISHED
TCP 169.254.1.2:3914 18.104.22.168:45653 TIME_WAIT
TCP 169.254.1.2:3917 22.214.171.124:41957 ESTABLISHED
TCP 169.254.1.2:3930 126.96.36.199:31817 ESTABLISHED
TCP 169.254.1.2:3951 188.8.131.52:40714 ESTABLISHED
TCP 169.254.1.2:3982 184.108.40.206:9034 ESTABLISHED
TCP 169.254.1.2:4129 220.127.116.11:35344 TIME_WAIT
TCP 169.254.1.2:4197 18.104.22.168:55196 ESTABLISHED
TCP 169.254.1.2:4199 22.214.171.124:13111 ESTABLISHED
TCP 169.254.1.2:4203 126.96.36.199:28783 ESTABLISHED
TCP 169.254.1.2:4206 188.8.131.52:46683 ESTABLISHED
TCP 169.254.1.2:4207 184.108.40.206:29686 ESTABLISHED
TCP 169.254.1.2:4208 220.127.116.11:29868 ESTABLISHED
TCP 169.254.1.2:4209 18.104.22.168:64391 ESTABLISHED
TCP 169.254.1.2:4210 22.214.171.124:56390 ESTABLISHED
TCP 169.254.1.2:4213 126.96.36.199:23306 ESTABLISHED
TCP 169.254.1.2:4216 188.8.131.52:50101 ESTABLISHED
TCP 169.254.1.2:4218 184.108.40.206:47168 ESTABLISHED
TCP 169.254.1.2:4219 220.127.116.11:47846 ESTABLISHED
TCP 169.254.1.2:4221 18.104.22.168:24359 ESTABLISHED
TCP 169.254.1.2:4231 22.214.171.124:50200 ESTABLISHED
TCP 169.254.1.2:4232 126.96.36.199:56691 ESTABLISHED
TCP 169.254.1.2:4246 188.8.131.52:64732 ESTABLISHED
TCP 169.254.1.2:4255 184.108.40.206:22805 ESTABLISHED
TCP 169.254.1.2:4256 220.127.116.11:63299 ESTABLISHED
TCP 169.254.1.2:4278 18.104.22.168:63660 ESTABLISHED
TCP 169.254.1.2:4280 22.214.171.124:54639 ESTABLISHED
TCP 169.254.1.2:4307 126.96.36.199:64676 TIME_WAIT
TCP 169.254.1.2:4309 188.8.131.52:43037 ESTABLISHED
TCP 169.254.1.2:4311 184.108.40.206:39987 ESTABLISHED
TCP 169.254.1.2:4314 220.127.116.11:54480 ESTABLISHED
TCP 169.254.1.2:4321 18.104.22.168:26931 ESTABLISHED
TCP 169.254.1.2:4324 22.214.171.124:47209 ESTABLISHED
TCP 169.254.1.2:4327 126.96.36.199:54000 ESTABLISHED
TCP 169.254.1.2:4331 188.8.131.52:80 TIME_WAIT
TCP 169.254.1.2:4333 184.108.40.206:3421 ESTABLISHED
TCP 169.254.1.2:4343 220.127.116.11:45653 ESTABLISHED
TCP 169.254.1.2:4351 18.104.22.168:12281 ESTABLISHED
TCP 169.254.1.2:4360 22.214.171.124:80 ESTABLISHED
TCP 169.254.1.2:4361 126.96.36.199:80 ESTABLISHED
TCP 169.254.1.2:4378 188.8.131.52:24315 SYN_SENT
TCP 169.254.1.2:4379 184.108.40.206:24791 SYN_SENT
TCP 169.254.1.2:4380 220.127.116.11:44145 SYN_SENT
TCP 169.254.1.2:4381 18.104.22.168:64154 SYN_SENT
TCP 169.254.1.2:4382 22.214.171.124:11221 SYN_SENT
TCP 169.254.1.2:4383 126.96.36.199:38368 SYN_SENT
TCP 169.254.1.2:4384 188.8.131.52:13031 SYN_SENT
TCP 169.254.1.2:4385 184.108.40.206:54492 SYN_SENT
TCP 169.254.1.2:4386 220.127.116.11:15960 SYN_SENT
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:1025 *:*
UDP 0.0.0.0:1164 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:6771 *:*
UDP 0.0.0.0:49312 *:*
UDP 0.0.0.0:56860 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1900 *:*
UDP 169.254.1.2:123 *:*
UDP 169.254.1.2:137 *:*
UDP 169.254.1.2:138 *:*
UDP 169.254.1.2:1900 *:*
UDP 169.254.1.2:5353 *:*
i don't know what any of this means but if you could let me know if something is wrong
i did the netstat when my browser was showing problem loading page
thanks alot for your help
Are you running through a DLink router per chance?
The results you posted *shouldn't* be causing an issue.
I'll try to find the source of the DLink router firmware to work better with the canopy modules... will update post in a few.
EDIT: SO I think I had this backwards... I think xplornet is updating the canopy firmware............ so god only knows when that will happen.
Last edited by x_savvy : 12-09-2009 at 09:45 PM.