My LW suddenly had some probs so I had to close down. Will be a while before it's up & going. Another member will try.

Your public ip is different to yesterday. Your private ip should not be showing to others when using LW which is what's happening. Your setup is not per normal I would argue. So does your ip address show up on your DC search window? Is this your public or private address & is it the same everytime. We'll wait for the other member & until my LW fires up. Oh forgot to reopen lol. :D

How many hosts depends. If you're operating as an ultrapeer then you'll have more.

Fabion DC'd with you & i did also (my downld window hadn't even loaded yet.) I notice you have no chat enabled .. there's no chat icon which is needed for chatting & helps DC work better. that's one of your issues.

I still have a snapshot of yesterday & your files are no longer in red & they now show your public address & not your private address.

Fabion successfully downlded a file from you on the 3rd attempt (1st 2 went immediately to need more sources as it was yesterday. And had to re-search DC.) I'm not ready to downld yet.

* Fabion tells me he is seeing you in red text like happened yesterday & with your private ip. Hmm strange.

This is what I saw yesterday & today. Notice there's no Chat icon! I am now downlding one of your files at about 13 KB/s!

I still don't see any chat icon nor is the option available despite several dc searches. I also browsed. odd!

I started to downld again from you & found I could open a chat window but only from the downld window not from the search results & your chat icon is still not showing. Odd! lol :D

Have you checked to see if there's a chat window message waiting for you?

But apparently Fabion does see a chat icon. Hmm can't work that one out. lol :D

What's even more odd is that one of my DC searches came up the same as yesterday with your results in red & with your 172. address.

I notice your connection type changed from modem>cable.

I just got back from the gym and saw your msgs and chat windows... I left my LimeWire connected. No config changes done here since I posted my last message... now over 3 hours ago. I have been on DSL here for two years now. Not dialup... all these variable results are very puzzling...

You forwarded a port on your device is that right? So your are not using a static ip right? If you did the normal steps are:
1. Set up a static ip which is very important for it to work. 2. Forward (open) a port for your modem or router. 3. Set LW up for manual port forward under Tools>Option>Advanced>Frirewalls.

Or did I misunderstand you?

What a difference a day makes ... or... a little TCP/IP knowledge is dangerous!
 

Yesterday: only TCP port 6346 was being forwarded by my firewall. (MY BAD!)

Today: both TCP and UDP port 6346 is being forwarded. (Yeah, I fixed it!? Maybe...)

SO, the firewall uses NAT (Network Address Translation) and port numbers to map an external, dynamic, PUBLIC IP addr to an internal, STATIC, PRIVATE IP addr.

The internal LAN addr starts with 172....

My external, public IP addr changes only if I reboot my DSL modem. It may look like 64... or 67... or ... but never 172... My ISP assigns that addr via DHCP when I reboot my DSL modem.

LimeWire remote peer should always use the EXTERNAL addr like
67.124.63.161:6346 and never the internal addr like
172.1*.**.**:6346.

SOMETIMES, LimeWire remote peers use the INTERNAL 172... addr, while others are using the EXTERNAL 64... addr. this a bug in LimeWire, or a config problem, or a design problem for a future version of LimeWire so it can support NAT routers/ Firewalls???

More details below... later...

First, your modem is probably UPnP configurable, meaning that LW can open the port automatically, hence why incomings: true. Second, if you are opening ports, don't forget to open both TCP and UDP as those two protocols are used by LW. Just be sure that UDP is allowed and that should help a lot. SBC could also throttle the P2P traffic, did you called them to ask if they were limiting the Gnutella traffic?

Also: the fact that the cha window shows your lan address (172.x.x.x.) is probably a bug, Tell the user sberlin (LW dev) about that. Chat isn't a priority at LW, that's why the function of it is poor and buggy, you would prefer chatting via MSN or AIM.

Thanks!

Yes, UPnP is configured in my DSL box.

LW chat is rather nice, lightweight, simple, and clean. AND it shows you the IP addr so you can relate things within LW such as browsing a host whilst chatting... yes? I find it very usable...

Meanwhile, the idea that my ISP is doing some throttling could explain the cause of variable results from hour to hour and day to day... hmmm.... yeah... maybe... worth checking on that!

There is more than one thing going on here... bugs, config errors, and ISP details... more detailed analysis and reports later!