Quote - Hi Syrus_BD

Netbios is something different. Legacy ms windows protocol, principally.

What millighost was referring to was tcpip broadcast.

UDP broadcast, not tcpip.

I wouldn't normally write about this, but we have a user trying to figure out what settings to adjust and it's important that it be clear we're talking about UDP, not TCP. Both UDP and TCP go over IP (Internet Protocol). TCP is never broadcast and is used for point-to-point streams of communication. UDP is broadcast or unicast. Broadcast is often used for asking a question when you don't know who you're asking. In this case the question is "Who here is running Poser QM"? The answer would then be unicast.

Many routers route unicast UDP messages. (Unicast means addressed to a specific device, not a group of devices.) Most routers do not route broadcast (to everybody) or multicast (to a group) unless they are configured to do so.

Both UDP and TCP have two-level addressing. There is the IP address of the device, and there is the "port number". The port number usually (but not always) has to do with a specific well-known piece of software within a device. For example, TCP port 80 is almost always a web server. UDP port 137 and 138 are for the NETBIOS service. Enabling NETBIOS forwarding does not mean you have turned on all UDP broadcast forwarding. It only forwards if the port is 137 or 138.

---

Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)