![]() |
nothing works for me! I disabled the tips and the auto login and i still cant get on. The thing is that sometimes it lets me connect no problem and other times it wont connect. The green light lights for about a second or less. Its really starting to **** me off. I had to get rid of my kazaa because of my popup blocker so i decided to go with limewire but its giving me more problems than kazaa did! and sorry but the downloading is not faster than kazaa...its about the same but oh well. im not gonna upgrade to pro because i wont pay for something i cant connect to. |
my isp port thing is 6348 not 6343 or whatever you said....who frickin knows im done with messing with it. ill just let it fix itself. its gay. |
Quote:
Morgwen |
no i didnt touch it...i didnt even know you could change it until you said something. it was 6348 originally. |
Quote:
Morgwen P.S.: I installed Limewire yesterday and checked the default port - it is 6346!!! I was sure about this it without the need to check it! |
If port 6346 is not available for some reason, LimeWire will try other ports automatically. It's possible that LimeWire found port 6348 to be working and made that your new standard port. |
Quote:
Morgwen |
Quote:
There is no efficient way of finding out on which ports a firewall allows incoming connections since you would have to ask a number of other Gnutella peers to try to connect to you before you can be absolutely sure a port is not working (limewire will send 10 connectback messages AFAIK to determine if you are firewalled). I'm pretty sure the LimeWire developers will have strong objections against sending even a hundred TCPConnectBack vendor messages to test a small range of ports. |
thinks Quote:
|
Quote:
If not...:confused: Morgwen |
Quote:
For leaf-ultrapeer connections LimeWire uses random ports from the higher ranges (32768 - 65535). I rather suspect that someone was downloading something from you and this took up so much of your bandwidth that you couldn't sustain your gnutella connections. - In that case going to tools->options->upload-> basic and moving the slider to the far left should help. If an ISP is blocking p2p traffic, it usually takes him only a few bytes of the message stream to identify it. So you would be disconnected in a matter of seconds. |
Some ISPs give connections to ports 8080, 80 and a couple of other ports a higher priority. So you could fool primitive traffic shapers to give your traffic a higher priority if the remote host is listening on port 80. Many ISPs have already been using solutions like the one described in the article for a while, which allows them to give only verified web & email traffic priority. |
sohow do you change your port setting.? |
Changing your own port doesn't help you. You need all the other servents to change their ports to take advantage of a sloppy ISP giving priority to traffic from and to port 80. Your own outgoing connections come from random ports in the 32768-65535 range. |
Quote:
Morgwen |
All times are GMT -7. The time now is 11:41 AM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 ©2011, Crawlability, Inc.
Copyright © 2020 Gnutella Forums.
All Rights Reserved.