tzuriel Posted December 23, 2007 Report Share Posted December 23, 2007 On Dime, I recently started getting this message:"protocol error 1 no/erroneous BT client listening or misconfigured router"My port forwarding is set up correctly, I have the green checkmark in uTorrent but I am still getting this error. I don't seem to be connecting to as many clients as I should.Any suggestions?Thanks! Link to comment Share on other sites More sharing options...
funchords Posted December 23, 2007 Report Share Posted December 23, 2007 Verify that you are connectible using http://www.canyouseeme.org/ If you are not connectible, then the uTorrent green light is incorrect.If you are connectible, then ask someone at Dime why this happens. Link to comment Share on other sites More sharing options...
jewelisheaven Posted December 23, 2007 Report Share Posted December 23, 2007 DUDE! that is a new site for my toolkit thanks funchords.btw, did you see my PM ? Link to comment Share on other sites More sharing options...
tzuriel Posted December 24, 2007 Author Report Share Posted December 24, 2007 I am connectable via canyouseeme.org but I still get that mesage from DIME. Their response was That message means that when DIME probes you for connectability, yourcomputer is accepting the connection and we're getting a response butit's not in BitTorrent syntax. It's as if a different application islistening on that port.You need to allow incoming connections in your firewall for the port(s)your client uses, and if you have a router, you have to forward the sameport(s) in your router as well.Oh well. Have to keep trying, I suppose. Thanks! Link to comment Share on other sites More sharing options...
jewelisheaven Posted December 24, 2007 Report Share Posted December 24, 2007 You can try http://sysinternals.com for a program called TCPViewWhat you'll need to do is sort by local address, and find the entry for the port you are using. If you see something bound there then there's definitely something wrong. Are you using 80 or 8080 by chance?If you're not sure what you're looking at feel free to take a picture of the window. (NOTE: you may want to change the default refresh time, or PAUSE it while you are looking, if you have ALOT of connections, it can overwhelm your CPU due to the refreshing of the listview. Link to comment Share on other sites More sharing options...
dazw2001uk Posted June 17, 2011 Report Share Posted June 17, 2011 This topic came up in google as I searched for the same problem where dime is showing "protocol error 1 no/erroneous BT client listening or misconfigured router. I read this thread and have followed these steps:Verify that you are connectible using http://www.canyouseeme.org/Success: I can see your service on 80.0.165.92 on port (39975)Your ISP is not blocking port 39975You can try http://sysinternals.com for a program called TCPViewNow I'm stuck, I don't know what to look for now, so I'd appreciate it if someone could help me out I have posted the results of the text file TCPView saved.svchost.exe 1156 UDP sonyvaio.cable.virginmedia.net ntp * * svchost.exe 1156 UDP SonyVaio ntp * * svchost.exe 1100 TCP SonyVaio epmap SonyVaio 0 LISTENING System 4 UDP sonyvaio.cable.virginmedia.net netbios-ns * * 68 3,400 System 4 UDP sonyvaio.cable.virginmedia.net netbios-dgm * * 1 205 1 System 4 TCP sonyvaio.cable.virginmedia.net netbios-ssn SonyVaio 0 LISTENING System 4 TCP SonyVaio microsoft-ds SonyVaio 0 LISTENING System 4 UDP SonyVaio microsoft-ds * * lsass.exe 840 UDP SonyVaio isakmp * * mDNSResponder.exe 1212 UDP SonyVaio 1025 * * alg.exe 2952 TCP SonyVaio 1038 SonyVaio 0 LISTENING svchost.exe 1156 UDP SonyVaio 1042 * * svchost.exe 1156 UDP SonyVaio 1043 * * svchost.exe 1500 UDP sonyvaio.cable.virginmedia.net 1900 * * 30 11,523 60 21,597 3,436 3,436 9 9 svchost.exe 1500 UDP SonyVaio 1900 * * uTorrent.exe 5052 UDP sonyvaio.cable.virginmedia.net 1900 * * 30 10,074 explorer.exe 1660 UDP SonyVaio 2338 * * AAWService.exe 1756 TCP sonyvaio.cable.virginmedia.net 2346 91.213.208.38 http CLOSE_WAIT firefox.exe 4784 TCP SonyVaio 2382 localhost 2383 ESTABLISHED 473 473 firefox.exe 4784 TCP SonyVaio 2383 localhost 2382 ESTABLISHED 473 473 firefox.exe 4784 TCP SonyVaio 2384 localhost 2385 ESTABLISHED 186 186 firefox.exe 4784 TCP SonyVaio 2385 localhost 2384 ESTABLISHED 186 186 firefox.exe 4784 TCP SonyVaio 2392 SonyVaio 0 LISTENING firefox.exe 4784 TCP SonyVaio 2427 localhost 12080 CLOSE_WAIT AvastSvc.exe 1996 TCP SonyVaio 2501 SonyVaio 0 LISTENING AvastSvc.exe 1996 TCP SonyVaio 2502 SonyVaio 0 LISTENING AvastSvc.exe 1996 TCP SonyVaio 2503 SonyVaio 0 LISTENING AvastSvc.exe 1996 TCP SonyVaio 2504 SonyVaio 0 LISTENING AvastSvc.exe 1996 TCP SonyVaio 2505 SonyVaio 0 LISTENING AvastSvc.exe 1996 TCP SonyVaio 2506 SonyVaio 0 LISTENING AvastSvc.exe 1996 TCP SonyVaio 2507 SonyVaio 0 LISTENING AvastSvc.exe 1996 TCP SonyVaio 2508 SonyVaio 0 LISTENING uTorrent.exe 5052 UDP sonyvaio.cable.virginmedia.net 2698 * * uTorrent.exe 5052 TCP sonyvaio.cable.virginmedia.net 2748 dhcp-077-249-067-160.chello.nl 49171 ESTABLISHED 10 122 19 17,744 uTorrent.exe 5052 TCP sonyvaio.cable.virginmedia.net 2755 nqhf001.dediseedbox.com 57000 ESTABLISHED 5 34 4 43 uTorrent.exe 5052 TCP sonyvaio.cable.virginmedia.net 2768 reverse.aeori.com 29454 ESTABLISHED 11 220 131 149,059 uTorrent.exe 5052 TCP sonyvaio.cable.virginmedia.net 2769 175-28-203-229.ppp.bbiq.jp 6881 ESTABLISHED 8 135 34 32,863 uTorrent.exe 5052 TCP sonyvaio.cable.virginmedia.net 2771 rs19603.rapidspeeds.com 58046 ESTABLISHED 15 186 100 133,547 uTorrent.exe 5052 TCP sonyvaio.cable.virginmedia.net 2845 h-81-188.a155.priv.bahnhof.se 2222 ESTABLISHED 9 64 7 53 svchost.exe 1500 TCP SonyVaio 2869 SonyVaio 0 LISTENING uTorrent.exe 5052 TCP sonyvaio.cable.virginmedia.net 3191 81-235-183-25-no20.tbcn.telia.com 37213 ESTABLISHED 11 673 4 914 [system Process] 0 TCP sonyvaio.cable.virginmedia.net 3210 wy-in-f102.1e100.net http TIME_WAIT 3 2,850 3 990 uTorrent.exe 5052 TCP sonyvaio.cable.virginmedia.net 3222 5adc058e.bb.sky.com 32534 ESTABLISHED 13 844 7 906 [system Process] 0 TCP sonyvaio.cable.virginmedia.net 3243 wy-in-f102.1e100.net http TIME_WAIT 2 2,367 2 660 [system Process] 0 TCP sonyvaio.cable.virginmedia.net 3248 2.19.213.115 http TIME_WAIT 1 581 1 389 [system Process] 0 TCP sonyvaio.cable.virginmedia.net 3284 wy-in-f104.1e100.net https TIME_WAIT 2 390 1 133 [system Process] 0 TCP sonyvaio.cable.virginmedia.net 3285 wy-in-f104.1e100.net https TIME_WAIT 1 27 [system Process] 0 TCP sonyvaio.cable.virginmedia.net 3286 wy-in-f104.1e100.net https TIME_WAIT 3 1,158 2 865 [system Process] 0 TCP sonyvaio.cable.virginmedia.net 3287 wy-in-f104.1e100.net https TIME_WAIT 3 1,314 6 4,158 [system Process] 0 TCP sonyvaio.cable.virginmedia.net 3288 wy-in-f104.1e100.net https TIME_WAIT 2 797 4 5,142 [system Process] 0 TCP sonyvaio.cable.virginmedia.net 3289 ww-in-f97.1e100.net https TIME_WAIT 5 2,416 13 13,390 uTorrent.exe 5052 TCP sonyvaio.cable.virginmedia.net 3301 212.7.207.30 60023 LAST_ACK 12 890 5 925 [system Process] 0 TCP sonyvaio.cable.virginmedia.net 3304 wy-in-f104.1e100.net http TIME_WAIT [system Process] 0 TCP sonyvaio.cable.virginmedia.net 3310 70.44.49.32.res-cmts.segc.ptd.net 62920 TIME_WAIT 7 597 4 770 [system Process] 0 TCP sonyvaio.cable.virginmedia.net 3312 ip98-169-71-236.dc.dc.cox.net 63411 TIME_WAIT 7 535 4 594 [system Process] 0 TCP sonyvaio.cable.virginmedia.net 3313 cpe-72-129-30-241.socal.res.rr.com 45121 TIME_WAIT 10 830 4 618 [system Process] 0 TCP sonyvaio.cable.virginmedia.net 3315 cpe-75-84-72-165.socal.res.rr.com 45027 TIME_WAIT 8 590 4 684 [system Process] 0 TCP sonyvaio.cable.virginmedia.net 3316 pd9e5ec12.dip.t-dialin.net 38052 TIME_WAIT 6 393 5 761 uTorrent.exe 5052 TCP sonyvaio.cable.virginmedia.net 3319 ppp-73-74.25-151.libero.it 54975 ESTABLISHED 11 788 5 982 lsass.exe 840 UDP SonyVaio 4500 * * svchost.exe 1056 UDP SonyVaio 4535 * * svchost.exe 1056 UDP SonyVaio 4536 * * jqs.exe 1572 TCP SonyVaio 5152 SonyVaio 0 LISTENING mDNSResponder.exe 1212 UDP sonyvaio.cable.virginmedia.net 5353 * * mDNSResponder.exe 1212 TCP SonyVaio 5354 SonyVaio 0 LISTENING svchost.exe 1056 TCP SonyVaio 9421 SonyVaio 0 LISTENING svchost.exe 1056 TCP SonyVaio 9422 SonyVaio 0 LISTENING svchost.exe 1056 TCP SonyVaio 9423 SonyVaio 0 LISTENING uTorrent.exe 5052 TCP SonyVaio 10000 SonyVaio 0 LISTENING AvastSvc.exe 1996 TCP SonyVaio 12080 localhost 3250 ESTABLISHED 16 20,885 4 3,049 AvastSvc.exe 1996 TCP SonyVaio 12080 SonyVaio 0 LISTENING AppleMobileDeviceService.exe 1064 TCP SonyVaio 27015 SonyVaio 0 LISTENING [system Process] 0 TCP sonyvaio.cable.virginmedia.net 39975 ains-202-134-254-85.ains.net.au 50200 TIME_WAIT uTorrent.exe 5052 TCP sonyvaio.cable.virginmedia.net 39975 cpc1-warw3-0-0-cust811.3-2.cable.virginmedia.com 49456 ESTABLISHED 27,661 35,158,007 13,985 621,386 3,474 304 5 3 uTorrent.exe 5052 TCP sonyvaio.cable.virginmedia.net 39975 pool-108-16-242-170.phlapa.fios.verizon.net 52432 ESTABLISHED 7 88 12 17,867 uTorrent.exe 5052 TCP sonyvaio.cable.virginmedia.net 39975 72.21.152.241 41988 ESTABLISHED 5 40 5 30 uTorrent.exe 5052 TCP sonyvaio.cable.virginmedia.net 39975 s23.gtokyofl26.vectant.ne.jp 53953 ESTABLISHED 5 40 16 84 uTorrent.exe 5052 TCP sonyvaio.cable.virginmedia.net 39975 5adc058e.bb.sky.com 1622 ESTABLISHED 4 26 2 8 uTorrent.exe 5052 TCP sonyvaio.cable.virginmedia.net 39975 ntt1-ppp444.tokyo.sannet.ne.jp 65388 ESTABLISHED 1 4 2 16 uTorrent.exe 5052 TCP sonyvaio.cable.virginmedia.net 39975 12.49.25.229 50640 ESTABLISHED 52 823,440 53 3,000 44 1 uTorrent.exe 5052 TCP sonyvaio.cable.virginmedia.net 39975 190-124-192-190.cab.prima.net.ar 57603 ESTABLISHED 10 190 96 82,027 uTorrent.exe 5052 TCP sonyvaio.cable.virginmedia.net 39975 212.7.207.30 61532 ESTABLISHED 2 187 2 595 uTorrent.exe 5052 TCP sonyvaio.cable.virginmedia.net 39975 pd9e91be9.dip0.t-ipconnect.de 53627 FIN_WAIT1 uTorrent.exe 5052 TCP SonyVaio 39975 SonyVaio 0 LISTENING uTorrent.exe 5052 UDP SonyVaio 39975 * * [system Process] 0 TCP sonyvaio.cable.virginmedia.net 39975 ains-202-134-254-85.ains.net.au 35765 TIME_WAIT [system Process] 0 TCP sonyvaio.cable.virginmedia.net 39975 ains-202-134-254-85.ains.net.au 35765 TIME_WAIT [system Process] 0 TCP sonyvaio.cable.virginmedia.net 39975 ains-202-134-254-85.ains.net.au 35765 TIME_WAIT [system Process] 0 TCP sonyvaio.cable.virginmedia.net 39975 sunct1.jinr.ru 46731 TIME_WAIT [system Process] 0 TCP sonyvaio.cable.virginmedia.net 39975 212.7.207.30 60620 TIME_WAIT [system Process] 0 TCP sonyvaio.cable.virginmedia.net 39975 212.7.207.30 60620 TIME_WAIT I know this thread is old but I thought it's the same problem and google brings this in top of the search Link to comment Share on other sites More sharing options...
dazw2001uk Posted June 18, 2011 Report Share Posted June 18, 2011 I've still got the same "protocol error 1 no/erroneous BT client listening or misconfigured router" message in dime but I've download 2.5GB & uploaded 6.8GB today, so I don't know if I even have the problem?? Link to comment Share on other sites More sharing options...
Drgiggles1 Posted September 1, 2011 Report Share Posted September 1, 2011 I have been getting the same thing for a while. I ran netstat and no other processes are listening except the one that should be. I restored my firewall settings to default as well as my router and re-installed router software. I also changed the static IP address on my PC as well as the port number. Even updated Utorrent to 3.0. After reconfiguring my client, router and firewall still getting the same message on DIME. After going through all my torrents on Dime I noticed I am only firewalled on http://b2.dimeadozen. On http://b0 and b1.dimeadozen I am fine. I pm'd the mods and will look forward to their response. Link to comment Share on other sites More sharing options...
Drgiggles1 Posted September 1, 2011 Report Share Posted September 1, 2011 Ok, I have found a work around. When you kick off a torrent on DIME it assigns it to either b0, b1, or b2.dimeadozen.org. Simply in your client right click on the torrent and click on properties. In my case all b2 assigned torrents were firewalling me and giving me that protocol error 1 on DIME. After changing the b2 in properties to either b0 or b1 I no longer had this error on DIME. I did stop all torrents and restart the client after the change. The error had no effect on downloading unless of course everone was firewalled, only sharing back as I could not share with other firewalled users.*** Edit 2011-10-27 *** You don't have to stop all torrents and restart client after change. Dime uses b0, b1, and b2.dime-a-dozen for load balancing. You may have to confirm for yourself if b2 is the issue, or if it is b0 or b1. If it is a problem with Dime it will be b2. If it is an issue with the way your system connects to a Dime server it can be anyone. Simply check all your torrents in Utorrent with the tracker tab selected and right click in tracker info window, click on add tracker, and there you will be able to edit b2 to b0 or b1, doesn't matter which one. Link to comment Share on other sites More sharing options...
hw3 Posted October 27, 2012 Report Share Posted October 27, 2012 Hi;I realize this is an old thread but it is the only one that seems to address this issue; anyway, I have the same problem on DIME, except mine says "protocol error 4 no/erroneous BT client listening". My port is correctly forwarded and utorrent 3.2.1 is set to use that port. TCPView is odd, it says I have 13 utorrent processes and only 4 are going to the forwarded port. I only have 7 torrents open (4 from DIME and 3 from another tracker) right now. All the DIME torrents are at b0.dimeadozen.org so nothing on b2.* One of the torrents on DIME, the seeder is firewalled and I am the only leech so there is 0 transfer; another has the same firewalled seeder, 2 firewalled leeches, myself, and an unblocked leech so I am downloading at the unblocked leech's rate and not uploading at all.Appreciate any insight on this.. Link to comment Share on other sites More sharing options...
DreadWingKnight Posted October 28, 2012 Report Share Posted October 28, 2012 It's a site-specific issue, not a uTorrent issue. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.