This guide replaces the old wiki page G2ConnectingGuide. It covers general steps for any Gnutella2-capable client. Menu names differ between versions, so check your client’s documentation for exact options.
1. Understand how connecting works
A G2 client must first discover at least one live hub, through a built-in host cache, a list saved from your last session, or historically a Gnutella Web Cache. Then it connects to a few hubs as a leaf. If discovery fails, you’ll see endless “connecting…” messages. If connections fail, you’ll see hubs found but dropped.
2. Quick checks
- Is your internet connection working in a browser?
- Is the network enabled in the client’s settings? Multi-network clients let you toggle Gnutella, G2, eD2k and BitTorrent separately.
- Is the system clock correct? Large clock errors can break some handshakes and HTTPS-based bootstrapping.
- Restart the client after changing network settings.
3. Refresh the host cache
Stale host lists are the most common cause on old installations. Most clients let you clear or reload the host cache, or import a fresh list from the project’s official site. Only use host lists from official sources. Hostile lists can point your client at fake peers.
4. Firewall software
Allow the client through your operating-system firewall and any third-party security suite, for both TCP and UDP. G2 relies on UDP for searches. See Firewalls and routers.
5. Router, NAT and “firewalled” status
Behind a home router you can usually connect out without changes, but peers can’t connect in. You’ll appear “firewalled”, with fewer sources and slower downloads. Forward the client’s listening port (TCP and UDP) to your computer, or enable UPnP on the router, which carries some security trade-offs.
Carrier-grade NAT (CGNAT), common on mobile and some fibre ISPs, makes inbound connections impossible from your side. You’ll stay firewalled, but searching and downloading still work, just less efficiently.
6. VPNs and P2P
If you use a VPN, the client sees the VPN’s network. Many VPNs block P2P on some servers or don’t support port forwarding, which leaves you firewalled. Check the provider’s P2P policy. Use a kill switch so traffic never falls back to your real connection; see P2P security.
7. ISP interference
Some networks throttle or block P2P traffic, especially on workplaces, campuses and some mobile carriers. Follow the network’s rules; on networks you don’t control, P2P may simply not be allowed.
Still stuck?
The official Shareaza community is reachable via the support page.