LimeWire: Network Bridge has a problem with NETBIOS name

[LaX]

Let me start from the beginning.

LimeWire has problems with Windows Firewall. To enable LimeWire, you have to
create ports for Gnutella.

Here is an overview from LimeWire's support site.

Now, here's the interesting problem. When you create the ports as
instructed, it works correctly. But if you use Network Bridge, it does not
work.

After you create Gnutella:6346 for TCP and UDP, it reverts the loopback IP
address from 127.0.0.1 to the NETBIOS name of the computer.

It seems to me that a limitation of the Network Bridge is keeping it from
using the localhost. Even if you type in "localhost" it changes the name
back as soon as you close the firewall app.

So here's the problem: I can't get LimeWire to work over Network Bridge, and
I would like it to. If there is a reason I cannot override the NETBIOS name,
how can I make the Gnutella entries work? This just doesn't seem right. So
far, I'm fairly unimpressed with Windows Firewall...but you get what you pay
for. It's quite annoying and unduly difficult to use. I'm afraid I am going
to have to switch back to ZoneAlarm. If I do that, I will need to know how
to make Windows XP shut up about the firewall.

 

[Ross Durie]

CLUE: The loopback address rule is simply a standard rule used on machines
without network cards.

Maybe you could now come up (HINT: switch your brain on) with another rule
to allow subnet traffic through port 6346.