Gnutella Forums  

Go Back   Gnutella Forums > Current Gnutella Client Forums > LimeWire+WireShare (Cross-platform) > Technical Support > Connection Problems
Register FAQ The Twelve Commandments Members List Calendar Arcade Find the Best VPN Today's Posts

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 :)


Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old October 1st, 2001
Novicius
 
Join Date: October 1st, 2001
Posts: 1
rlively is flying high
Question Announces 6346, but really listens on 6347?

I'm running LimeWire on Windows 98 SE behind a Linksys router and using ZoneAlarm Personal Firewall.

ZoneAlarm was blocking many requests coming in on port 6346 even though I told ZoneAlarm to allow javaw.exe to act as a server and forwarded port 6346 to my machine. When I investigated, ZoneAlarm reported that javaw.exe was listening on port 6347, NOT 6346. I looked in the LimeWire settings, and on the Connections tab the port was 6346 and under Tools | Options | Port 6346 was also specified.

When I changed the Port number to 6347 and forwarded that same port through my router all was well and users could start downloading from me. How did this happen and why was it really listening on 6347 instead of the stated 6346?
Reply With Quote
  #2 (permalink)  
Old October 3rd, 2001
Novicius
 
Join Date: October 3rd, 2001
Location: canada
Posts: 3
dezine is flying high
Angry same exact scenario here

I have the same problem here, using Zone Alarm and all. So, I disabled Zone Alarm and changed everything to 6347. Did you also change the "Auto Connect Hosts" to be 6347 instead of 6346? I did but I am still not connecting for some reason. The program worked wonderfully as version 1.6d and now I am very frustrated.
Reply With Quote
  #3 (permalink)  
Old October 3rd, 2001
Unregistered
Guest
 
Posts: n/a
Lightbulb Changed all back to 6346

I've changed all my settings back to 6346, changed my router to forward only port 6346, restarted everything and now LimeWire is listening on 6346 and everything is peachy. People can even connect to me from behind the LinkSys as long as I specify my IP # and port under Advanced | Firewalls.
Reply With Quote
  #4 (permalink)  
Old October 30th, 2001
Unregistered
Guest
 
Posts: n/a
Default

I suspect this port-listening discrepancy is responsible for many of the problems. I have the problem where I can only establish Outgoing connections, not Incoming. Bearshare works fine using the same Forced IP and Port 6346.
Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
6346!!!! :( JayJay04 General Windows Support 1 February 16th, 2006 02:57 AM
other gates than the 6346 possible lbol General Discussion 3 August 26th, 2002 07:04 AM
difference between 6346 and 6347? JackDCLee General Gnutella / Gnutella Network Discussion 6 December 5th, 2001 03:20 PM
Problems with 6346? Unregistered Connection Problems 2 November 7th, 2001 04:50 AM
2 instances on 127.0.0.1:6346 rip General Discussion 1 March 6th, 2001 03:26 PM


All times are GMT -7. The time now is 07:11 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.