Thanks very much, Lord of the Rings, but I'm beginning to suspect that open file sharing is inherently inconsistent with anonymizing: you cannot be anonymous while allowing a server access to your drive. This is only a suspicion, but it is based on having read all the posts you linked me to, and then doing a bunch of experimentation. All of the posts are discussing what might be called "open" proxies - in other words, proxies that aren't examining each and every connection and approving it based on some security criteria. Total Net Shield IS doing that.

I discovered that I can't use any port Anonymizer is using, and if I just pick a random port, LimeWire tells me I'm not connected to the internet. But then I discovered I can create "listening ports" in the Anonymizer program. When I did that, and then set all the appropriate settings (firewall & proxy) to that port, here is the error message I get from Anonymizer when Limewire tries to connect: "SSH Session: Server rejected our attempt to open a client-to-server forwarding channel - reason: SSH_OPEN_CONNECT_FAILED, description: Connection refused."

What this seems to say is that I figured out what I needed to do as far as settings go, but the Anonymizer is simply saying "Sorry, Charlie, but you can't do that." I have written to their tech support and will let you know what their reply is.

In the meantime, does anyone know of anyone who is using LimeWire through Anonymizer and how they're doing it? In fact, it does seem to make sense that it would not work: if you have to give up enough information about your identity for an outside server to be scanning your drive, you cannot possibly still be anonymous - and this is why Anonymizer refuses the connection. Does this sound wrong?