almost-freeze on connect Dear Sberlin, Thanks for the advice. I followed the instructions with the same result. Although I notice that LW loads more quickly in the beginning, it still freezes when it tries to load the core components. (I apologize for the triple post. The Gnutellaforums server didn't confirm my browser's request.) Mark |
Do the files out.txt or err.txt in the LimeWire folder contain anything? (They might be called system.err or system.out too, I'm not sure of the names.) |
almost-freeze on connect When the beta version crashed, yes. The currently installed version doesn't crash but doesn't report any errors either. I simply press command-option-escape when I have to get on with my work. Mark |
Will still not connect Hi I am on mac os 10.3.2 and had thesame problem where the green connect button flashed for a short second before it disconected agan, this started about a month ago. I have tried to delete the prefrence file, disable autoconnect and running limewire as soon as i restart. None of these seem to help. I have also downloaded the new beta version. The differense is that now i get an error message saying that My machine does not appear to have an active internet connection or a firewal is blocking my connection. In System Prefrences/sharing/firewall I have opened for lime wire (port 6346) and also tried turning off my firewall compleatly. This does not seem to have an effect. I have also tried to change the port number in preferences/advanced/port&firewall to a different number, and opening to the same port number in my firewall settings on my computer. Non of the above has worked. Anyone? |
Connection problems Worked for me too |
I can't connect to limewire either. I see a lot of people are having the same trouble and it's very frustrating. I am running windows 98, and I can't get anything to work. Please give me some help. |
almost-freeze on connect solved Hello, I was working on an application of mine, which didn't want to connect to the internet. Reason: Open Transport error -3158. Fortunately, I always check for errors and quickly found the cause. It appears that particular router configurations cause this error. Probably, there are more causes of this error. After removing my router, I fired up LimeWire without a problem. Removing the router also meant changing TCP/IP settings and limiting the Mac's network interface (AppleTalk) to remote access only. This is not an apparent fix, it is a definite solution. Please, developers, make sure that LimeWire checks Open Transport availability. If it gets an error, have LW report it in an error dialog and let it exit. This will avoid a lot of frustrations. Mark |
:mad: no such luck! |
I had been having connection problems for several days. As suggested, I deleted my limewire preference folder. After doing this, I was able to connect again. Thanks for the tip. |
thanks for the tip. if i wouldnt have looked on the forums i would still be sitting here trying to do things that have no effect on the program. thanks again. |
All times are GMT -7. The time now is 01:15 AM. |
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.