diff --git a/README.html b/README.html index d12a729..23dacab 100644 --- a/README.html +++ b/README.html @@ -71,7 +71,7 @@

Note: uxplay is run from a terminal command line, and informational messages are written to the terminal.

1. uxplay starts, but stalls after “Initialized server socket(s)” appears, without any server name showing on the client.

Stalling this way, with no server name showing on the client as available, probably means that your network does not have a running Bonjour/zeroconf DNS-SD server. On Linux, make sure Avahi is installed, and start the avahi-daemon service on the system running uxplay (your distribution will document how to do this). Some systems may instead use the mdnsd daemon as an alternative to provide DNS-SD service. (FreeBSD offers both alternatives, but only Avahi was tested: one of the steps needed for getting Avahi running on a FreeBSD system is to edit /usr/local/etc/avahi/avahi-daemon.conf to uncomment a line for airplay support.)

-

Use the utility avahi-browse -a -t on the server to verify that the UxPlay AirTunes and AirPlay services are correctly registered (only the AirTunes service is used in the “Legacy” AirPlay Mirror mode used by UxPlay).

+

After starting uxplay, use the utility avahi-browse -a -t in a different terminal window on the server to verify that the UxPlay AirTunes and AirPlay services are correctly registered (only the AirTunes service is used in the “Legacy” AirPlay Mirror mode used by UxPlay).

2. uxplay starts, but stalls after “Initialized server socket(s)” appears, with the server name showing on the client (but the client fails to connect when the UxPlay server is selected).

This shows that a DNS-SD service is working, but a firewall on the server is probably blocking the connection request from the client. (One user who insisted that the firewall had been turned off turned out to have had two active firewalls (firewalld and ufw) both running on the server!) If possible, either turn off the firewall to see if that is the problem, or get three consecutive network ports, starting at port n, all three in the range 1024-65535, opened for both tcp and udp, and use “uxplay -p n” (or open UDP 6000, 6001, 6011 TCP 7000,7001,7100 and use “uxplay -p”).

3. Problems after the client-server connection has been made:

diff --git a/README.md b/README.md index fa3cdb7..56eeea7 100644 --- a/README.md +++ b/README.md @@ -326,7 +326,9 @@ _(FreeBSD offers both alternatives, but only Avahi was tested: one of the steps getting Avahi running on a FreeBSD system is to edit ```/usr/local/etc/avahi/avahi-daemon.conf``` to uncomment a line for airplay support._) -Use the utility ```avahi-browse -a -t``` on the server to verify that the UxPlay AirTunes and AirPlay services are correctly registered (only the AirTunes service is used in the "Legacy" AirPlay Mirror mode used by UxPlay). +After starting uxplay, use the utility ```avahi-browse -a -t``` in a different terminal window on the server to +verify that the UxPlay AirTunes and AirPlay services are correctly registered (only the AirTunes service is +used in the "Legacy" AirPlay Mirror mode used by UxPlay). ### 2. uxplay starts, but stalls after "Initialized server socket(s)" appears, *with the server name showing on the client* (but the client fails to connect when the UxPlay server is selected). diff --git a/README.txt b/README.txt index a4af5c7..1583048 100644 --- a/README.txt +++ b/README.txt @@ -411,8 +411,9 @@ one of the steps needed for getting Avahi running on a FreeBSD system is to edit `/usr/local/etc/avahi/avahi-daemon.conf` to uncomment a line for airplay support.*) -Use the utility `avahi-browse -a -t` on the server to verify that the -UxPlay AirTunes and AirPlay services are correctly registered (only the +After starting uxplay, use the utility `avahi-browse -a -t` in a +different terminal window on the server to verify that the UxPlay +AirTunes and AirPlay services are correctly registered (only the AirTunes service is used in the "Legacy" AirPlay Mirror mode used by UxPlay).