Interesting problem-- we put in a LinkSys EtherFast Cable/DSL router, and Gnutella, which had been running perfectly, now loses the outgoing GnutellaNet connections it establishes within minutes-- and no incoming connections ever seem to get through. We have enabled WAN requests on the router, and forwarded port 6346 requests hitting the router to the internal private IP that is running the client. Outgoing GnutellaNet connections now get established, but drop after one to two minutes. We have tried forcing our local IP to the IP given the router by the WAN, and also tried leaving the "force local IP" box unchecked. Deinstalling the router lets Gnutella run properly again, but that is not a useful solution. Any ideas? Many thanks -- lwm

It seems the suggestion below about running SFC and scanning for corrupt system files has some value. Now we can get several terabytes of available files, but GnutellaNet connections still do not persist. This is apparently not a router issue but a GnutellaNet issue. Our suspicion is that users quickly disconnect when achieving poor results. It may be, therefore, that we need to get the word out better that replacing this corrupt system file (setupx.dll or setupdx.dll?) is part of the solution. (Go to START, then RUN, then type in SFC, and it will detect and replace the corrupt file. You will need to have your Windows installation CD at hand.) It is highly likely that RIAA would fund a hack on GnutellaNet, and that is what I suspect has happened.

I agree.
Tried it and have had some improvement

I also have the Linksys router. Force the IP to that that which you have have assigned to the router (the one your isp assigned you) not the internal ip on your lan.