Did you follow the steps I outlined in my post?

What were the results?

Sorry, sberlin, I see now... I was unclear before about what it was that you are asking us to try... is this it:

in Options... Advanced... Firewall config...
REMOVE UPnP and then use Manual port forward?

Is that what you want us to try??? PLEASE CLARIFY. It seems to me like your last paragraph is suggesting that we go back to square one, where this all began, which did not work, so we started mucking around with the 2Wire (DSL firewall) settings...??? You want us to remove the port forwarding from the firewall box?

Please explain: do you want us to REMOVE ALL THE 2wire FIREWALL/router SETTINGS, going back to square one on the 2Wire DSL box? That did NOT work before...

I'll have to wait till tonite, to test again with Dave... I have put out requests on other forums for anyone with a SBC-Yahoo!-DSL and with a 2Wire DSL box...

MEANWHILE, sberlin, is there a BETA version of LW that we can test?? I guess that only makes sense if some bugs have been fixed in this area, or if there is any debug code to test, or more statistics to help, or access to expert help...

We are preparing a beta. There may be a bug in LimeWire 4.8.1, there may also be a bug in your setup.

Please remove any configuration you have done on your router, on both sides, and tell both LimeWire's to use UPnP. See if that works. If it does, great.

If not, tell one side to use 'Manual Port Forward' and set the listening port & forwarding port to the same number (like 6666). Then set up that side's router to forward from requests at 6666 to your internal IP address. See if that works. If it does, great.

If not, tell the other side to use to use 'Manual Port Forward' and set the listening port & forwarding port to the same number (like 6666). Then set up that side's router to forward from requests at 6666 to your internal IP address. See if that works. If it does, great.

If not, we may have a bug.

I cannot help further unless I know what happens at each step. Telling me, "I tried this before" won't help.

OK, we will take it step by step and report our results.
 

SO, is UPnP an alternative scheme to TCP/UDP port forwarding?

If/when Dave will cooperate, or if I find a willing tinkerer with SBC DSL+2Wire DSL modem...[list=1][*] Reset DSL modem/firewall to factory defaults, also switch to UPnP in LimeWire, do same for both ends.[*] Test LimeWire Direct Connect Downloads... [*] IF nogo, then on side A: setup manual port forwarding,
also setup 2Wire DSL box for TCP/UDP port forwarding,
then test.[*] IF still nogo, do same for side B, test.[*] Report all results for each step.[/list=1] OK?

Is it ok to use port 6346 (it works AOK for me with others...) or do we need to switch to another port like 6969? Why does the port number matter? ISP throttling maybe? Does not seem to matter for me <> fabion... it's working fine between us... exept the private IP number stuff and chat icon stuff noted already (LW bug).

Thanks for your help, sberlin. Let us know when we can test a beta.

THE oddest thing here is it worked one time. Then immediately after that, it failed... (Dave<>Geo DC DL)

Dave is getting frustrated, wants to try Shareaza... :rolleyes: but we already have a lot of time invested in LimeWire... I want to keep trying, as long as we can get some expert support to tell us what to try... otherwise we are just shooting in the dark... :) :cool: :D :confused:

Ready to test DC DL, anyone???
 

sberlin :: I have reset my DSL modem/NAT router to defaults:
no more TCP/UDP port forwarding, per your request.

I have set LimeWire to UPnP.

Ordinary LimeWire DOWNLOADS + UPLOADS seem AOK.

PROBLEM: Received incoming this session = false !? So, there may be no hope... ?!

Now, I just need someone willing to test DC DL...

My buddy Dave is not available till Sunday. I hope to find someone who can duplicate the SBC (ISP) and 2Wire (modem/firewall) config, and test before then. Otherwise further tests for that ISP are on hold till Sunday.

It seems possible that you are authenticating yourself on startup against your friend running as an ultrapeer (or someone else on SBC Yahoo) and this ISP uses one set of IPs internally whereas the broader internet sees you as a different IP.

Could be a multi-IP nat issue and if so, we have never really addressed that issue in LimeWire. Basically the same as having a large corporate network and then the public internet.

Interesting idea... please explain more...

• We don't specify untrapeer in our LimeWire configs...
• We're both running as a normal leaf nodes...
• What's invoking this authentication? Is it LimeWire, or is it being done at some other layer?
  Why is it being done? How can we disable it?
• I do not know about any authentication in this context. I'd like to know more...

This should be a very normal config. Two SBC-Yahoo!-DSL Home Network customers, connecting normally to the internet via standard off-the-shelf products and services...

By authenticate, I mean the communications that you receive back from the ultrapeers that you connect to.

Your TCP connection to an ultrapeer reports back the IP address that it sees you as. If you connect to an ultrapeer behind some nat on a private network, it would report one IP address. If you connect to an ultrapeer through a nat, the IP address could be different. So, the question is, does SBC Yahoo have this type of configuration.

If it is common, then LimeWire needs to improve its handling of this. I've wanted better private network support for a while.

Note that this is only an actual problem if the last Gnutella connection it made (like UP->Leaf, Leaf->UP, or UP->UP) was to someone else on your private network. Chances of that consistently being the case are rather small.

*We should, though, prevent LW from accepting a 'Remote-IP' address from someone else who has the same class A address.

Is there any way to make both work and coexist? Like "I'm either at this IP or this IP".