Freezing problem clue.

The Seeker · #1 (**permalink**) September 10th, 2001

I woke up to a frozen XoloX. I was running the debugger, but I couldn't understand what was going on past the fact that it wasn't in a small infinate loop so far as I could tell.

What I did to was run a netstat to see who I was connected to, and lo and behold, I saw this:

Code:

Proto  Local Address          Foreign Address        State
TCP    computer:4414          127.16.255.17:6346     ESTABLISHED
TCP    computer:6346          127.16.255.17:4414     ESTABLISHED

Which I assume is very very bad, considering that this is a loopback address. Somewhere in your code I think you made it so you can't connect to your own IP, but it seems that some people are 'force real IP'ing to be a loopback address, and it's killing XoloX.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
I really haven't got a clue!	Loops	Getting Started Using LimeWire + WireShare	2	February 24th, 2007 10:59 AM
not a clue	cobalt	General Windows Support	1	August 13th, 2005 04:59 PM
Same problem.....more ppl please respond to my freezing problem!!	bomb13	General Windows Support	3	August 7th, 2005 03:06 PM
A clue please?	ST	Open Discussion topics	0	November 9th, 2002 01:15 PM
not a clue	thumper71	General Discussion	1	April 14th, 2001 02:53 AM