If you are using NAT meaning your IP address is 192.168.x.x or 10.x.x.x. and don't have any kinds of special firewalls installed people should be able to download from you without any problems. You haven't indicated why you feel you need to force your ip address.

I assume that the ip shown in whatsmyip.org is different from the one you see when you do an ipconfig. If you are not using a static ip address option with your isp then the IP you see on whatsmyip.org will in all likely-hood change if you reboot your equipment.

__________________
Lee Evans, President
LeeWare Development
http://www.leeware.com

If dev is using NAT & a dynamic ip, I wonder what their incoming report says on the bug report: dev do this test: Bug Report instructions & sample image If it's True then nothing to worry about in that regard.


LeeWare are you sure about the NAT! I'm aware you posted a thread about NAT some time ago. But to my understanding of it (which is limited), then it will block out all but the 'legal' ports. For p2p, high-end games & video conferencing, multiple ports would need to be opened (port forwarding.) Otherwise they would appear as firewalled to other p2p users. That's where the force ip comes into play. I'd like a better understanding of this issue myself.

Why do you think your upld success has hit a 50% snag? Firewalls/NAT, etc. not properly configured, etc.?

Let me take a moment to clear a bit of confusion. Earlier in this thread I mentioned that in order to improve your search and download success you should try to make sure you have a good and open connection to the network. I made several recommendations about how you might go about doing this. Obviously, these statements were made at a time when firewalled users presented a big problem for the network in fact, it was nearly impossible to download from them or get files uploaded when you were also firewalled.


There have been many new developments and features added to limewire to improve this situation. So here's what I know for a fact. If people setup limewire in the way that I had recommended to do so in the past they would effectively filter out all of the firewalled sources when doing searches. This was a configuration which lead to some long running debates regarding the practice. However, it would eliminate the possibility of you trying to download from a firewalled users.


But let's assume that most users today are either firewalled or NATed. As far as limewire is concerned they are all firewalled.

I know for a fact that Firewalled to Firewalled transfers work however for a variety of reasons they also have a high failure rate for example.

If I normally upload 1000 files in one hour when not firewalled.
If I run all of my nodes as VPS (Virtual Private Servers) then the number drops to something like 70-100 uploads. I assume that this is because I don't show up in results where people are filtering out addresses like 172.16.x.x, 10.x.x.x and 192.168.x.x

Hope this helps.

__________________
Lee Evans, President
LeeWare Development
http://www.leeware.com

I have seen something around a 1% successful upload rate.
Right now I have five people attempting to upload. One is at 14 kbs the others are sitting there at 0.
I have both upload and download bandwidth at 'unlimited' to see if that made any difference.
Should I reduce the download bandwidth somewhat, since I have no trouble downloading? Or does that make any difference?
What on earth is causing people so much trouble to upload from me? When looking at my files, I see (in the x/y column), 1/1..., 9/1..., etc. So there are many attempted downloads but hardly any successful ones.
The person who was uploading was up to 63% and just quit.
Any further advice??
I know there are no firewalls, NAT, etc.
Oh, and Cobra, sorry I got miffed about the 'assumption' thing. I'm still new to this. Thanks for your help.

Most of my uploads have resulted in a "transfer interupted" alarm,
only 2 uploads have been sucessfull.(downloads are working fine). In the past, no one had problems uploading off my computer. I recently updated and began using limewire again when I noticed most uploads were failing.( I have Norton Internet security firewall, but it didn't seem to be a problem before. Maybe Norton updates have created one?)
The limewire "direct connect" says my ip address is.........
68.103.144.249:6348 . Should I attempt to force this address?
My default lime wire "listen port" was 6346. I changed it to 6348 to match the limewire "direct connect" numbers. Was this correct? Or should the "listen port" number be different than the "dirert connect" number. Feedback will be appreciated as this issue has me confused. Thank you.

According to the statistics you posted x = number of completed uploads / y = number of attempted uploads. Therefore, it looks like you had 9 uploads and 1 attempt unless you accidentally reversed the results. Which means that you had 1/9.

__________________
Lee Evans, President
LeeWare Development
http://www.leeware.com

If I were you I would change everything back to the default. Especially, if you are making changes and don't understand what affects they will have. This could create more problems for you. Therefore, it is highly recommended that you only change that which is necessary. What you might want to consider is configuring your norton firewall to allow an exception for limewire.

__________________
Lee Evans, President
LeeWare Development
http://www.leeware.com

The 9/1... for example:
The 1 literally has dots after it, I assumed this meant it was over 100, which would mean I had 9 successful uploads out of over 100 attempts.
Is that correct? Sorry to keep dragging this on, by the

Cobra8007 glad to hear you sorted out your issues. I saw in an earlier thread of yours about the isp you use. I was wondering if you'd heard about THIS issue?

Yes, as I had posted earlier in this thread and others. Cox says that they do not block P2P traffic and this was confirmed by switching OS to win2003server. It worked fine then. I pay Cox for a commercial cable line which does not block anything. It is used for servers, etc. They do block port 80 requests on residential to prevent servers being run on residential lines though.

This is true for this area (Oklahoma City).