![]() I checked the eventviewer again on the client computer but i still get the bonjour service errors (ID 100) when i start Airplay. However i can't ping the device (logical because i unplugged the power cord) but it seems it stays visible on the network as a 'Ghost'.ĭisabling/enabling Bonjour Gateway resolved this. Tried disabling/enabling Wi-Fi on my iPad but the Apple TV stays in the Airplay list. I unplugged the power cord of the Apple TV and it's still showing up in the Airplay list on my iPad. I thought a Apple TV had something to do with it (seeing the log file), so we have one Apple TV in oure network, other computers are running Airserver. I use a Ruckus Zonedirector 3000 with firmware 9.7.1.0 build 17with enabled Bonjour gateway. ![]() ![]() Has the Ruckus Bonjour Gateway something to do with this or what can i do to prevent this errors from happening? When i Airplay (which works) i get another 10 of those Bonjour service errors. When doing a reboot i can ping this APIPA IP-address one time from a command prompt from the client computer running Airserver. However the client computer gets a IP from the DHCP server. The IP address 169.254.1.9 is the APIPA address from the computer running Airserver. TXT (Fwd by ruckus bonjour gateway)¦deviceid=00:19:D1:A4:B1:59¦features=0×100029ff¦model=AppleTV3,2¦pw=1¦rhd=1.9.7Įssentially, the cause appears to be at 169.254.1.9:5353, but the little bit of info that says “Fwd by ruckus bonjour gateway” suggests that the problem may lie there. From the information you have sent this is the most telling: If another reply is received then it will try again but use a number one larger than it previously did.Įssentially something on your network is telling the Bonjour service on the computer where this is happening that the name is in use. If anything on the network replies stating that it is in use then it will add a number wrapped in brackets to the end of the name and will try again. The (0), (1), (2) appearing behind the Bonjour name happens under the following circumstances: Apple’s Bonjour service sends a probe packet asking if a “name” is in use, to the network. ![]() I asked Airserver what this is al about and they come up with this answer: When the hostname shows up again it can occur it comes with (2), (3), (4), (5) (6) at the end (see picture fault_3.PNG and fault_4.PNG in attach). I also notice the hostname of the computer in the airplay list changes frequently. When i try to Airplay, it works great but i get the same errors in the eventviewer. MDNSCoreReceiveResponse: Reseting to Probing: 19 SRV 0 0 5000 AV-01.local. MDNSCoreReceiveResponse: Reseting to Probing: 19 AV-01\032(2)._airplay._tcp.local. When i click on the errors in the eventviewer i see the error is related to ‘mDNSCoreReceiveResponse’ When i launch Airserver my eventviewer gets tons of errors from the bonjour service. I’ve installed the latest Airserver version 1.9.7.1 圆4 on a Windows 7 圆4 SP1 computer with all the updates.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |