|
Awaiting sources... after buddy IP search??? Trying to share a few files with a friend -- using LimeWire DIRECT CONNECT -- via IP address: we both can see and browse each other 's shared file list -- AOK! But, when we try to download anything we see in that list, we each have this problem, same on both ends: Queued... then Connecting... then Awaiting sources... forever!!! :confused: :( :confused: :mad: :confused: Please help? What's causing this?? How can we fix it???
|
Has anybody out there been successful with LimeWire DIRECT CONNECT via IP address, while using a DSL modem with built-in FIREWALL? {Specifically: SBC Yahoo! DSL with a 2wire (tm) brand modem} and if so, how did you configure it, please? I am using Windows 2000 Pro. My firewall is set to forward port 6346 to my PC for LimeWire. My firewall IP is 67.124.__.___ My machine IP is 172.16.__.___ -- Connection Type: Ethernet IP Address: 172.16.__.__ IP Address Allocation: DHCP IP Address Type: Private (NAT) -- My LimeWire connection says TURBOCHARGED... sharing 47 files. I have seen many UPLOADS completing in the past... -- while using LimeWire 4.0.x, 4.2.x, ... otherwise, SAME PC, same DSL modem, etc... -- but since upgrading to LimeWire 4.8.1 today, NO uploads have started or completed yet, and I have been connected for two hours, or more. Something seems fishy... UPDATE: Three more hours later, a few dozen guest uploads have been done -- I guess it DOES take awhile for a leaf node to get hooked into the LimeWire/Gnutella ultrapeer network ... Help? Is there any hope to get our IP file transfers going? What to do? |
STILL no joy... Fabion -- Thanks for your response, and the suggestions... good to know it works for someone! Well -- all our parental controls are turned off... Our ISP {SBC Yahoo! DSL} and our DSL modem/firewall vendor {2Wire.net} don't give out much documentation, it seems... But, I did find out -- from some SHAREAZA documentation on the web -- how to set up firewall port forwarding -- just by poking around... SO, our port 6346 firewall handling is all set up, and seems to be working AOK -- evidence: there have been a few dozen successful P2P GUEST uploads completed via LimeWire PRO... after waiting over FOUR hours for the ultrapeers to detect my node... But -- still no joy with LimeWirePRO Direct Connect -- via IP address -- with my friend... WHY???
|
Any LimeWire experts out there willing to try doing a Direct Connect to my IP address for troubleshooting??? |
Just 30 seconds ago I successfully direct connected to you! Audioslave, dave mathews, Serenade, Ciara ft Lil Jon, etc. Sounds like the issue is with your friend's set ups. It is almost impossible to direct connect (DC) if one of you are firewalled (ie: don't have your firewalls properly configured to allow LW full access.) It might also be a modem or router issue. Get your friend to do this test: Bug Report instructions & sample image If it's False then they're firewalled. You should do the test also! I noticed your files are all red under Location column which suggests you're firewalled. Configure firewalls here: http://www.limewire.com/english/content/firewalls.shtml More on DC here: How to Direct Connect, Browse & Chat |
Lord of the Rings -- Thanks!!! I've got "Received incoming this session = TRUE" ... :D Woo hoo !!! I'm running Win2k PRO. With a NAT firewall in my DSL modem/router/WiFi box, why should I run any software firewall, isn't that redundant and excessive??? The only firewall I'm running here is in my SBC home network "2Wire (tm)" DSL/WiFi Modem/Router box -- supplied by my ISP... and it has a NAT firewall, and I've set up port 6346 for my LimeWire usage... lots of this terminology seems misleading for us non-experts... I'm FIREWALLED, since there IS a firewall in my DSL box, yes? ... but as far as LimeWire is concerned, I am NOT firewalled... since I have forwarded port 6346 properly... yes??? I'll ask Dave (the friend who wants to share files) to try the test on his side in a few hours -- and report back here... fortunately, we both have the same ISP, and the same DSL modem/router... and we both stepped through the port 6346 setup together yesterday... so I am ANTICIPATING he will get the SAME result as I just did... unless he is running some extra software firewall... tbd! WHAT THEN??? {i.e. What can we try next, if we both have "Received incoming this session = TRUE" ... but we STILL cannot mutually share our files???} :confused: |
STILL no joy... Here is an update: Tools... Options... Bug Reports... View Example... We now both have this result: Received incoming this session: true We can search each other by IP address, and see the list of files to share... He was able to download only ONE small .mid file from me, AOK! I still could not download anything from him, results: Queued... then Connecting... then Awaiting sources... Just a minute after the first successful DL, he tried to DL a larger file from me, then he also got that result: Awaiting sources... And yet, we both checked and could still see: Received incoming this session: true WTF??? What next??? :confused: :( :confused: :( :confused: We are going to stay connected for a few hours and try again... |
k when I dc'd you I searched under one address but got another under the Location column & they were all in red. There was also another member-mod who dc'd you with same results but neither of us were able to downld from you. Basically what it means is that your devices don't seem to be set up properly! That's realy odd to search under one address but to find you under another address. Very odd & means you're not set up properly. Odd again that if that be the case that we could browse you at all. You manually port forwarded right? You MUST have a static ip for this to work properly. There's definitely something odd about the way you're set up. |
What's the secret to config for DC via DHCP/NAT? Thanks again, Lord of the Rings for your reply. I think we have set up properly (our port 6346 configs look ok.) Look for the AHA below... it explains a possible bug in LimeWire? What's DC? OH, Direct Connect... Both my friend and I use the standard PacBell / SBC Yahoo! DSL / home networking service... Most DSL home networks use DHCP and NAT, not static IP, right? (That's what the standard, popular SBC Yahoo! DSL home networking package offers... DHCP and NAT...) That can work, yes??? How do we get LimeWire PRO Direct Connect to work here??? :confused: The 2Wire (tm) DSL box: We've each set up our 2Wire DSL modem / WiFi / NAT Router / Firewall box supplied by the ISP (SBC) to forward from a public IP addr (like 67.124.60.__) outside the firewall to a PC (at 172.16.1.__) inside the firewall, via TCP port 6346 forwarding. Does that sound OK? I'm doing normal LimeWire searches and downloads AOK, I'm seeing incoming searches AOK, I'm seeing public uploads completing AOK... Right now -- I'm seeing connections with five ultrapeers AOK -- but... there should be MORE than five with LimeWire PRO, yes??? :confused: SOMETIMES, after more than six hours, I've seen like six or more ultrapeers...) :confused: Whenever I reboot my 2Wire box, I'd expect my IP address will change. Otherwise, it seems stable, but I'm not sure how long the DHCP lease time is... probably a few days. Our 2Wire DSL modem/ NAT router's config takes care of mapping port 6346 from the Public IP addr to the Private IP addr automatically, even after a reboot of the 2Wire box. This seems to be a standard, typical home DSL setup, right? IF SO... why are we having LimeWire problems with DIRECT CONNECT and host chat? What's the secret config to make this work? SITUATION: When I setup for DIRECT CONNECT with his host via his public IP addr, it always succeeds. (Both ways, vice versa.) We can each see the list of files on the other host. When we try to do a LimeWire host chat, or BROWSE, it fails. When I try using LimeWire DC to download anything from his host, it fails. (Awaiting sources...) But, one time last nite, he was able to DL one small file from my host, then a minute later, trying with a larger file, the DL failed... AWAITING SOURCES... :confused: Weird??? AHA!!! LimeWire uses his public IP addr (64.168.20.__:6346) when searching his host via DC -- BUT, when trying to CHAT, or BROWSE, {or DL?} LimeWire is using his PRIVATE IP addr (172.16.1.__:6346) AHA!!! -- Could THAT be causing all these problems... hmmm... a LimeWire BUG??? :eek: If it's not a bug in LW, then what's the solution? I could try contacting the second level support for 2Wire (my DSL modem/ NAT router/ firewall box) and see what they say about all this, now that we have some more info to give them... I do not think the ISP support will help us solve any P2P issues... Any other suggestions? Is this a LimeWire bug, or a config issue? Does anyone here know how to config a 2WIRE (tm) DSL box that uses DHCP/NAT for LimeWire Direct Connect? I thought I had done everything right... I'll attach my screen shots from my 2Wire config... if that may help? IS THERE ANY SETUP CHECKLIST for a DHCP/NAT firewall config??? :confused: |
Seems like a bug??? See AHA! in post above... How does this info get to the developer or 2nd level support for a review? It's been 48 hours since I sent a help request to LimeWire PRO support... no reply yet... what's up with that? Can anyone please explain the difference between the FORUM here, and the PRO support? Are there different resources available for help? |
| All times are GMT -7. The time now is 07:00 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 ©2011, Crawlability, Inc.
Copyright © 2020 Gnutella Forums.
All Rights Reserved.