I'm using a Netgear FA311 NIC.

From the "netstat -n -a -p UDP" command I get the following:

C:\tmp>netstat -n -a -p UDP

Active Connections

Proto Local Address Foreign Address State
UDP 0.0.0.0:135 *:*
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:1029 *:*
UDP 0.0.0.0:18678 *:*
UDP 0.0.0.0:21076 *:*
UDP 0.0.0.0:21077 *:*
UDP 0.0.0.0:21078 *:*
UDP 127.0.0.1:62515 *:*
UDP 127.0.0.1:62517 *:*
UDP 127.0.0.1:62519 *:*
UDP 127.0.0.1:62521 *:*
UDP 127.0.0.1:62523 *:*
UDP 127.0.0.1:62524 *:*
UDP 192.168.0.2:137 *:*
UDP 192.168.0.2:138 *:*
UDP 192.168.0.2:21075 *:*

C:\tmp>

As you can see it's close to what you've described as the expected result. The differences are that port 21078 is bound to 0.0.0.0 and port 21075 is bound to the IP of the NIC not vise versa as you've described.

I've also checked the registry as you've suggested and everything is exactly as you've described.

I've also tried the app you wrote. (The terms "above and beyond the call of duty" don't even come close to describing how much I appreciate that one)

When I run it on the Win2k box, I get a response from the Receiver manager with the IP of the NIC. So I know that within the context of the OS itself, the Receiver Manager is running properly. However, if I run it from another machine on my network, or a machine hooked up via cross over cable to the Win2k box, I get:

Looking for Rio Receiver NFS Servers...
Sending request to 255.255.255.255.......

until it times out.

I also have Win2k installed on my laptop (HP N5440). I installed the receiver manager and your app. When I run the receiver manager on the laptop and your app on my desktop, it connects just fine. However, with the receiver running on the desktop and your app on the laptop I get the timeout scenario I described above. The Win2k install as well as additional software are almost identical on the laptop and the desktop. I am looking through both now to try to find any differences.

I ran the netstat command you suggested on the laptop and the output is identical.

I also connected the receiver directly to the laptop via cross over cable. It conneced just fine.

It appears that the signals from the receiver & your app are somehow being blocked by the NIC on my Win2k desktop. I just can't figure out why. I had previously disabled Norton Firewall on the desktop. I have now gone so far as to uninstall it. There was stil no connection.

I've read on this board that ther's some sort of logging software for the for the receiver. Where can I get that? Is there similar logging software for the manager?

What next?