![]() |
|
Register | FAQ | The Twelve Commandments | Members List | Calendar | Arcade | Find the Best VPN | Today's Posts | Search |
Connection Problems Problems getting the LimeWire or WireShare program connecting to the Gnutella network.
(not about connecting to files, that is a Download/Upload Problems section issue.) Please supply system details as described in the forum rules.
Start here Suggestions to help you get connected, * try here first *, then see below (click on 'this' blue link) Did you FORGET something BEFORE you posted? If you post in this section you MUST provide these details: System details - help us to help you (click on 'this' blue link), else do not be surprised if your posting is ignored :) |
![]() |
| LinkBack ![]() | Thread Tools ![]() | Display Modes ![]() |
| |||
![]() I have Limewire installed on two machines. I can Connect OK from the desktop PC used as the gateway machine to the internet. The problem lies with a laptop computer that is connected via a wireless link through the desktop. Both computers run XP and both can access the internet. The PC has XP firewall enabled with no modifications to the default settings. Disabling the firewall makes no difference at all. All problems are with the laptop which will usually connect on a new install and that is it. If the .Limewire folder is deleted then a connection can be made as mentioned on other posts, but, this is not really a fix. If a connection is lost then usually internet access for the laptop is also lost. The desktop PC always connects and as yet as never failed to connect. I suspect that LW remembers something between connections that does not allow it to re-connect - since removing the .Limewire folder usually half fixes the problem. It's a pain having to reset all the options - especially when $18 has been paid for the pro version. Re-booting also does not fix the problem. Is there some sort of clash within the network settings and LW that is causing this? Any thoughts on this would be appreciated ... Thanks. |
| |||
![]() pturner I suspect your problem is caused by your router. I assume your laptop works on the internet with the exception of Limewire. Try direct connecting your laptop to the internet bypassing your router. If that works for limewire you need to configure your router to allow your Limewire connection. I can explain why it works on a new install. Norm |
| |||
![]() I just upgraded to the latest limewire and I'm running on MacOSX with a netgear wireless router. When I first installed limewire it ran and connected and worked beautifully. But any subsequent attempt to connect would actually kill my router and kill the connections of any other wireless hosts connected to it. I would have to go upstairs and pull the power cord on the router and come back downstairs and then (without CLOSING limewire) as it to connect and it WOULD without killing the connection... I shut down the app and lauched it again and my wireless connection was gone once again... How ANNOYING! |
| |||
![]() Norm I don't use a router as such, an 'ad hoc' system with just the desktop as the host and the laptop as the client. I would agree that there seems to be a problem with routing but this does not happen with a new install or when the prefences are deleted in the .Limewire folder - it will connect in these instances. So the question is - What does Limewire do in a fresh install/preference setting routine as far as connections are concerned that it does not do on subsequent runs? Thanks |
![]() |
| |
![]() | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Wireless Connection - HELP!!! | t4tolu | Connection Problems | 4 | December 3rd, 2006 07:51 PM |
Wireless vs Wired Connection | 15784953 | Open Discussion topics | 3 | October 30th, 2006 03:49 PM |
Wireless Connection | 15784953 | Download/Upload Problems | 0 | October 25th, 2006 11:11 PM |
Wireless Connection Problem | w0rt3x | Connection Problems | 4 | September 21st, 2006 02:53 AM |
Problem Connecting--Wireless Internet Connection | hurricane | Connection Problems | 1 | July 30th, 2004 03:32 AM |