![]() |
|
Register | FAQ | The Twelve Commandments | Members List | Calendar | Arcade | Find the Best VPN | Today's Posts | Search |
General Windows Support For questions about Windows issues regarding LimeWire or WireShare or related questions |
| LinkBack ![]() | Thread Tools ![]() | Display Modes ![]() |
|
| |||
![]() I've been connected to the internet via cable connection for 2 months now - turns out I have a static IP Address (at least it hasn't changed yet!). I've had Limewire installed for several months. Two weeks ago I installed ZoneAlarm Pro, and ever since I've noticed that as my computer boots I start getting attacked on port 6346 from IP Address 64.229.72.239. This 'bombardment' never ceases, and connection attempts are being made to my computer about every minute or two for as long as my computer's up and running. This happens even when Limewire's not running. Because the connection attempt is to port 6346, I'm guessing that it's a Limewire-related issue. My ZoneAlarm logs indicate two types of connection attempts, both FWIN and FWROUTE. FWIN indicates an inbound packet of data coming to your computer. FWROUTE indicates a packet that was not addressed to or from your computer, but was routed through it. Considering the nature of a Gnutella network, this might be normal. But should this be happening even when I'm not running Limewire? Is IP Address 64.229.72.239 trying to hack me, or route through me to hack into other computers? Or could they possibly have me listed as a host IP and keep trying to connect to me constantly? Any words of wisdom would be most appreciated. Here's a fraction of my ZoneAlarm log: type date time source destination transport FWIN 2002/01/10 23:48:02 -5:00 GMT 64.229.72.239:2804 67.160.161.216:6346 TCP (flags:S) FWIN 2002/01/10 23:49:18 -5:00 GMT 64.229.72.239:3213 67.160.161.216:6346 TCP (flags:S) FWIN 2002/01/10 23:50:34 -5:00 GMT 64.229.72.239:3609 67.160.161.216:6346 TCP (flags:S) FWIN 2002/01/10 23:51:49 -5:00 GMT 64.229.72.239:4010 67.160.161.216:6346 TCP (flags:S) FWIN 2002/01/10 23:53:03 -5:00 GMT 64.229.72.239:4401 67.160.161.216:6346 TCP (flags:S) FWIN 2002/01/10 23:54:18 -5:00 GMT 64.229.72.239:4824 67.160.161.216:6346 TCP (flags:S) FWIN 2002/01/10 23:55:33 -5:00 GMT 64.229.72.239:1289 67.160.161.216:6346 TCP (flags:S) FWIN 2002/01/10 23:56:49 -5:00 GMT 64.229.72.239:1682 67.160.161.216:6346 TCP (flags:S) FWIN 2002/01/10 23:58:05 -5:00 GMT 64.229.72.239:2084 67.160.161.216:6346 TCP (flags:S) FWIN 2002/01/10 23:59:22 -5:00 GMT 64.229.72.239:2500 67.160.161.216:6346 TCP (flags:S) |
| |
![]() | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
when a port is busy like say 6346 what is another good port # to use for my other | Butterfly9 | LimeWire+WireShare Tips and Tricks | 0 | January 31st, 2007 11:47 AM |
My ISP blocks port 6346 | FreeStuffRules! | Connection Problems | 1 | January 27th, 2006 05:42 AM |
Port 6346 hits... | dilbert666 | General Gnutella / Gnutella Network Discussion | 2 | June 27th, 2002 05:49 PM |
?connect through a different port-not 6346? | ehamel | Connection Problems | 0 | October 31st, 2001 02:29 PM |
Can I use servers not on port 6346? | Dev | Gnotella (Windows) | 3 | March 3rd, 2001 11:18 PM |