frostwire does not connect

wabbalee · 12-24-2006, 03:42 AM

Hello, I have frostwire 4.1 installed on two systems, on mepis 6 and kubuntu 6. the one on mepis will not connect even with a disabled firewall (guarddog). when i check upnp settings on both frostwire and on my router they use the same port. i do not believe the router is the problem as the other machine with kubuntu uses it too and has no connecting problems. has any one any idea's?

thanks
ron

corbintechboy · 12-24-2006, 05:07 AM

I had the same problem and moved to limewire and all works now. I don't really know what the deal is with frostwire that makes it not work but limewire does, don't really know....Try limewire it will work!

wabbalee · 12-25-2006, 04:00 AM

thanks, will do that, i have limewire on my daughter's box and she never complains either.

figfighter · 01-04-2007, 06:10 PM

I can't seem to connect with either Frostwire or BitTorrent. Before I try Limewire, I'm wondering if it has something to do with a firewall issue.

Any advice on how to check?

wabbalee · 01-06-2007, 07:00 PM

i think so too, i have tried without and have had connectivity, but i find it very hard to interpretate the firewall jargon (no offense) used in guarddog. i am not comfortable to run without so i leave it on because everything else that needs to connect or login works without any problems. i am use to how the windows firewall called 'zonealarm' handles permissions for opening and closing ports and how it interacts with its (human) user; by default and in theorie (i have no way of verifying this as i am not a software specialist) zonealarm closes every port and asks its user, in the form of a cartoonlike text balloon to its icon in the tray, if a program named 'foo' is allowed to acces the local network? the user can then decide to have zonealarm remember or not whether the user wants to allow or deny. after that it does the same thing for internet access. and does the same for server access too. in the beginning it is rather talkative but it quiets down over time. to me it made sense first time i worked with it. after having fiddled around with 'black ice defender' or 'sygate' and few others. now i have been using linux for a few years (3 or so) and enjoying it but this is one of those things (a firewall) that i find quiet hard to configure in linux.

figfighter · 01-09-2007, 06:02 PM

so... i tried to install LimeWire but it says i need jre2. but that's SO WIERD, because doesn't FrostWire use Java? Frostwire opens, but just doesn't connect.

i'm cool with sticking with Frostwire, but how to i get it to connect?

craigevil · 01-13-2007, 05:13 AM

Se this thread at the Frostwire forum:
FrostWire Community :: View topic - Connection troubles with FW 4.10, the solution
http://www.frostwire.com/forum/viewtopic.php?t=666

I also had to allow the specific port to connect in Guarddog.

Too bad more people haven't started using mute:
"MUTE File Sharing is a peer-to-peer network that provides easy search-and-download functionality while also protecting your privacy." http://mute-net.sourceforge.net/

wabbalee · 01-15-2007, 09:38 PM

Thanks Craig, i will have a look and try and will come back here to report my findings.

regards, ron

shadowsnipes · 02-19-2008, 03:29 AM

For those still having trouble with FrostWire using the guarddog firewall see this post on the FrostWire forum.

Here is the interesting part

Quote:

Launch Guardog > Protocols>File Transfer> Then check the box Network File Systems-Sun Microsystem> Save guarddog settings and restart Frostwire.

For others, first check you firewall logs to see if anything is getting blocked. If you don't have UPnP enabled on your router then you will have to manually configure the port.

Perhaps try replacing the gnutella.net file if none of this helps.

alan_ri · 02-19-2008, 10:11 AM

I use Frostwire with Shorewall firewall and don't have any problems.Limewire and Frostwire don't have same dependencyes and sometimes one won't work if other will.One solution that I found useful is to change listening port of the Frostwire in Frostwire.That should enable the connection.Sometimes running FW as root will solve the problem too.Sometimes is just question of wright jre.

shadowsnipes · 02-19-2008, 12:37 PM

Quote:

Originally Posted by alan_ri

Sometimes running FW as root will solve the problem too.

That should never be done!

alan_ri · 02-19-2008, 01:44 PM

Quote:

Originally Posted by shadowsnipes

That should never be done!

It depends who is doing it,when and why.

fair_is_fair · 02-19-2008, 10:59 PM

Thankyou Shadowsnipes!

I've been fiddling with Guarddog and Frostwire for some time with no success till I read your post. Not sure what sun microsystems have to do with frostwire/gnutella.

shadowsnipes · 02-20-2008, 03:32 AM

It works, but it seems like trying to kill a fly with a shotgun. Out of curiosity I decided to see what ports guarddog is actually opening for this NFS - Sun Microsystems protocol. After reading it, it doesn't surprise me at all why it works.

exert of /usr/share/apps/guarddog/networkprotocoldb.xml

Code:

<protocol name="nfs">
  <longname>Network File System - Sun Microsystems</longname>
  <longname lang="de">Network File System - Sun Microsystems</longname>
  <longname lang="nl">Network File System - Sun Microsystems</longname>
  <longname lang="fr">Système de fichiers distribué (NFS) - Sun Microsystems</longname>
  <longname lang="it">Network File System - Sun Microsystems</longname>
  <longname lang="es">Network File System - Sun Microsystems</longname>
  <classification class="file"/>
  <network>
        <tcp>
          <description>RPC port mapper service</description>
          <description lang="de">RPC Port Mapper Dienst</description>
          <description lang="nl">RPC Port Mapper-service</description>
          <description lang="fr">Service RPC port mapper</description>
          <description lang="it">Servizio di Port Mapper RPC</description>
          <description lang="es">Servicio de Port Mapper RPC</description>
      <dest><port portnum="111"/></dest>
      <source><port portnum="any"/></source>
    </tcp>
        <udp direction="both">
          <description>RPC port mapper service</description>
          <description lang="de">RPC Port Mapper Dienst</description>
          <description lang="nl">RPC Port Mapper-service</description>
          <description lang="fr">Service RPC port mapper</description>
          <description lang="it">Servizio Port Mapper RPC</description>
          <description lang="es">Servicio Port Mapper RPC</description>
          <dest><port portnum="111"/></dest>
      <source><port portnum="any"/></source>
        </udp>

        <tcp>
          <description>mountd</description>
          <description lang="de">mountd</description>
          <description lang="nl">mountd</description>
          <description lang="fr">Démon serveur NFS</description>
          <description lang="it">mountd</description>
          <description lang="es">Demonio servidor NFS</description>
      <dest><port portnum="dynamic"/></dest>
      <source><port portnum="any"/></source>
    </tcp>
        <udp direction="both">
          <description>mountd</description>
          <description lang="de">mountd</description>
          <description lang="nl">mountd</description>
          <description lang="fr">Démon serveur NFS</description>
          <description lang="it">mountd</description>
          <description lang="es">Demonio servidor NFS</description>
          <dest><port portnum="any"/></dest>
      <source><port portnum="any"/></source>
        </udp>

    <tcp source="client" dest="server">
          <description>NFS data</description>
          <description lang="de">NFS Daten</description>
          <description lang="nl">NFS-data</description>
          <description lang="fr">Données NFS</description>
          <description lang="it">Dati NFS</description>
          <description lang="es">Datos NFS</description>
      <dest><port portnum="2049"/></dest>
      <source><port portnum="any"/></source>
    </tcp>
    <udp source="client" dest="server">
          <description>NFS data</description>
          <description lang="de">NFS Daten</description>
          <description lang="nl">NFS-data</description>
          <description lang="fr">Données NFS</description>
          <description lang="it">Dati NFS</description>
          <description lang="es">Datos NFS</description>
      <dest><port portnum="2049"/></dest>
      <source><port portnum="any"/></source>
    </udp>
  </network>
  <security threat="high" falsepos="low"/>
  <reference href="http://www.robertgraham.com/pubs/firewall-seen.html">
  FAQ: Firewall Forensics (What am I seeing?)</reference>
</protocol>

It would seem that a better solution would be to open the needed ports per specific IP that are specified in the gnutella.net file, but you would probably want to limit which ones (not all are needed). I'm not really concerned about this, though, because I only use the above protocol while running FrostWire, which isn't very often, and I don't use this machine in unprotected networks.

wabbalee · 02-20-2008, 04:54 PM

It is good to see that it works for some people, i am not a big user of frost- or limewire. The latter seems to work without fiddling so i stuck to that one for the rare occasion. My daughter on the other hand is a frequent user. I recently installed Ubuntu Gutsy on her machine with all the whistles and bells, including limewire 4.16 and all works good. May be not exactly sticking to the philosophy of free software, but it saves me a lot of fiddling. Thank you shadowsnipes for excellent advice.