Hi Don, That's what I'll do after I get the main problem solved. Another Win computer on the same LAN cannot connect to the Jamulus public server either through the local ip or the public ip. This is true with the Rpi out of the picture.
The Rpi private server works , so I'm going to forget about that server for now and just concentrate on getting the Win public server running. From the client computer, I can connect to the Rpi 2 ways (WAN and LAN) but cannot connect either way to the Win server which I tried making both private and public. I tried PF and still could not connect. What you implied that it's some Win-related anti malware or some other idiosyncrasy of win networking seems right. Now for some reason, the Public server...
I should have added port forwarding is only to the Pi . I assumed PF isn't needed for a public server.
Thank you for the response. Here's what I did to try your suggestions: Shut down Win server and pulled ethernet cable out of Pi. Verified no server is listed on Jamulus server list. Started up Win server. It is now listed on server list. (as "MadisonJazzJam" with OS Windows On another Win computer, it is not listed on the connection list. On the other computer, unsuccessfully tried connecting using the local IP address of the server computer. Plugged the Pi back in. Successfully connected to it using...
I'm running a private Jamulus server on a Raspberry Pi. Works fine. I set up a public server on a Windows machine. From another Windows computer on the same network, the client can connect to the private server by using the WAN IP. But I cannot see the public server in the connection list. Also on the registration list https://explorer.jamulus.io/ the public server name shows up but shows Linux, not Windows, for the OS.