Ok.. do you remember if you had to restart LW to get it to connect, or was just selecting "connect" from the menu enough?

Selected connect it worked.

__________________










A little common sense goes a long way

Later Grandpa

I had the same happen also. Left LW running overnight in the morning I had the message you do not appear to have an internet connection.

I closed the warning box, and checked LW. It was still d/l and u/l.
It was as though LW had just come out of idle mode. Only had 1 connection in the connection tab window, and showed it being connected for about 9+ hours. It was connecting to other as I was checking it.

I did not have to restart or reconnect LW.

__________________
The Forum Search is easy to use
Upper right of this page between f.a.q. and home

WindowsXP MCE sp2
P4 3.0 Ghz HT
4 Gb DDR2 @ 533 Mhz

So limewire was showing that it did not have an internet connection when in fact it had a stable ultrapeer connection? Interesting.

But keep in mind that such a warning dialog may appear at some stage, yet LW is happily going about its business. I noticed that happen many times. I turn the monitor on in the morning with LW 4.8.1 even. As you suggested, it may be a bug with the idle/sleep function.

Ah this is probably a small bug in the GUI; the "You don't have an Internet connection" window may not disappear if a connection is restored.

I'll put this on my todo list. =)

Question for everyone that had connection issues: did you see the

or the

message?

I also get the 'no internet connection', but I'm still on 4.9.17. Sometimes even when downloading, but most of the time it's while starintg/connecting to the first ultrapeer.
(while downloading means: it's downloading, but is connected to 0 ultrapeers)

What seems to happen is that limewire tries to contact ultrapeers from whatever list it has/keeps/gets/whatever and goes through all of them, connecting to none. Then it reports no the 'internet connection' dialog. I can't tell which one of the above it is, I hope you can find out from this info.

This has been happening a lot, and seems version independant (it is why I updated from 4.8.x to 4.9.17 in the first place). It also feels like a bug more than network conditions, since it happens so much. But that isn't consistent with the fact that it started happening in 4.8.x out of the blue. A bug in other ultrapeers? (Or are some ultrapeers refusing Limewire, and are users accidentally hitting only those? Too much of a conspiracy theory I guess.)

But what then? I'm not sure... some more facts: it stops randomly as well. It happened on startup just now, I reselected file/connect, and saw it go through a million non-connectiong ones again, but it found some in the end apparently, as it's working fine now. 3 ultrapeers, 2 4.8.1 and 1 4.9.1 limewire.

hope this may help... (about to install the beta)

LimeWire 4.9.24 has been released. It contains a very minor change that we hope will make LimeWire try harder to reconnect in case it loses its internet connection.

Give it a spin - we'd like to see how long it can stay connected.

Thanks!
- The LimeWire dev team

I had the first one ZAB

__________________
Later Grandpa

@Grandpa:

Were you using the computer at the time?

sorry david, there is a no refund policy. you should have tried the free version before paying for the pro version.

just an FYI: i have been having some connection/disconnection problems every now-and-then.

1) freezing on connections when waking up the computer. (i do have a screen shot (see attachment) of this while i was acting as a leaf.) i wasnt lucky enough to be running it in debug mode to capture a stack trace

2) LW does not want to reconnect to the network if i remove all UPs.

3) LW seems to connect to other vendors in a rather fast connection to the network. which i thought it would only try other vendors if LW couldnt establish connections with its own subnet after a period of time.

----

other problems:

icons are still displaying the wrong icon for its condition. such as:

1) if i were to cancel a corrupt download, it will turn back into the quality stars in the search window.

2) if i download the file from one search result window, and find it in another, when the download finally completes, it will only give the window from which i downloaded it a green check which the other one still has a manilla folder.
--
sometimes limewire reverts to "need more sources" even though this file has many sources to choose from. if i press "find more sources" it will stay in the "connecting" state for ~20 secs or so, then it will immediatley start downloading this file. we have also been getting alot of complaints about resume support in LW within these forums.

an online contact of mine is showing that LW is using near 100% CPU with his configuration. i have seen this for myself using remote desktop access. i will post more about this when i get more information. (this happens everytime he launches LW and it stays like that during his whole session with it.)

***keep in mind that these bugs occur every now-and-then. i will also post more elusive bugs as i see them.

Attached Images

limefreeze01.png (50.0 KB, 54 views)

Maybe it's a configuration problem

killing an active upload will cause the current queues to back up even though there is open slots.