Extend multicast (bonjour, mDNS, 224.0.0.251) over network borders

Hi,
I try to get Bonjour (mDNS, iChat, multicast and so on) running across network borders. Where 'running across network borders' means, that the multicast traffic travels from one layer 2 domain / ip network (over a router) to another.
Is this possible?
While playing around with a Cisco Catalyst 3560 as Router and trying to get multicast routing to work, I saw that the TTL of the multicast traffic (desination 224.0.0.251 udp 5353) is 1. And as far as I know a router would decrement the TTL by (at least) 1, so it becomes 0 and the packet would be discarded.
Is it possible to change the TTL value to something greater than 1?
It would be kind if here is someone out there who could give me some hints on this.
Thanks in advance
regards
Mark
Mac OS X (10.4.10)

Sonic,
The Multicast address you are referencing 224.0.0.251 is part of Bonjour. Bonjour is a Multicast DNS protocol for service discovery and advertisement and is a perfectly normal process. Apple's implementation of Bonjour assumes a link-local multicast address (224.0.0.*) that is not suppose to traverse a router but will still be heard on interfaces that process multicast packets.
Search for multicast DNS or Bonjour on wikipedia to learn more about how these protocols work.
While you may have had Bonjour disabled in prior versions of MacOS, it was likely re-enabled to support the Apple Wireless Direct Link (a wireless adapter sub-interface) which requires the Bonjour protocol to advertise services such as AirDrop and AirPlay.
Since you are receiving Teardrop attack notifications on your router, it is safe to assume that internal interfaces are being monitored. I would suggest disabling the deep packet security inspection for internal ethernet and wireless interfaces (or if possible dismiss or disable just the offending signature for your trusted hosts).
Best Regards

Similar Messages

Computer on 224.0.0.251 trying to access /usr/libexec/discoveryd

Ever since upgrading to Yosemite, my Norton firewall tells me that a computer with this IP is trying to run discoveryd on UDP port 5353 (bonjour). Is this something that Yosemite needs that I need to unblock?

From Wikipedia…
Local subnetwork
Addresses in the range of 224.0.0.0 to 224.0.0.255 are individually assigned by IANA and designated for multicasting on the local subnetwork only. For example, the Routing Information Protocol (RIPv2) uses 224.0.0.9, Open Shortest Path First (OSPF) uses 224.0.0.5 and 224.0.0.6, and Zeroconf mDNS uses 224.0.0.251. Routers must not forward these messages outside the subnet in which they originate.
https://en.wikipedia.org/wiki/Multicast_address
In short 224.0.0.251 is something on your local network attempting to 'discover' the locally available services via mDNS. If you use Norton or any other firewall to block it the services on that machine won't be discovered & you will need to manually configure them, then you will also need to ensure the ports in question are not blocked for the specific services.

WLC 7.5 Bonjour/mDNS at multiple sites

Hi all,
After reviewing the mDNS/Bonjour features of WLC software 7.5 (although most applies for 7.4 as well), I am left somewhat confused. It seems that once services are discovered, there is no way to filter them to be advertised only to the site they were discovered at.
To simplify our environment, consider the following scenario:
A single WISM2 controller
A single SSID using dynamic VLANs deployed across diverse locations, with Wi-Fi mDNS discoveryeg. Site A has VLANs 11, 12, 13, Site B has VLANs 21, 22, 23
Wired mDNS discovery at both siteseg. Site A has VLANs 101, 102, 103, Site B has VLANs 201, 202, 203
In the instance, let's say a printer, is discovered on wired VLAN 101, and I only want to advertise it to the Site A Wi-Fi VLANs, it seems that I can't. All VLANs that are configured to advertise the printer mDNS service records receive it, which means Site B sees the printer at Site A.
Is there any way to achieve what I want here? It seems a crazy limitation that I can't filter the VLANs to what advertisements they receive, considering the service provider database has the learnt VLAN information in it.
Alex

Scott,
     LSS doesn't support mDNS-AP, it only applies over the wireless: http://www.cisco.com/en/US/docs/wireless/controller/7.5/config_guide/b_cg75_chapter_01011.html – about halfway down under Configuring Multicast Domain Name System, it states that there is no location awareness for wired service provider devices (Apple TVs). It also states that mDNS-AP devices are considered wired – even though these devices were discovered by the APs, they don’t get filtered by LSS.
     If the Service provider is in the same wireless SSID/VLAN, you wouldn't need Bonjour Gateway. If it's in a different wireless SSID/VLAN, but on the same AP, you'd be hairpinning traffic and doubling up wireless airtime. LSS doesn't make much sense to me, unless I'm missing something.
     Our solution so far is to extend the wireless VLAN out to a single port on the wired network, but the AppleTV can only be plugged into that port. It limits our user's mobility with the devices.
     I've sent this on to our Cisco reps, and they are pushing it up the chain for a feature request.
Mark

Why are my Macs triggering TEARDROP OR DERIVATIVE attacks to 224.0.0.251?

Since updating to Yosemite my router is sending security emails every couple of hours saying that "teardrop or derivative DETECTED" from one of our local Macs running Yosemite, targeting multicast address 224.0.0.251, port 5353.
Even when I disable port filtering on my router, I still get these messages. I think my router is factory set to block these types of messages.
The effective result is that my Internet access slows to a halt until I reboot the router.
I read somewhere that this multicast address 224.0.0.251 and port 5353 are related to Bonjour services/iTunes. I wouldn't doubt it if it's also a significant part of the background services to enable handoff.
*note: I'm not a network guy, so I'm just guessing as to the cause. I saw these teardrop messages before Yosemite but not as frequently. I dug deeper only because I'm getting several a day. Thanks if you can offer any solutions for stopping the messages.*

Sonic,
The Multicast address you are referencing 224.0.0.251 is part of Bonjour. Bonjour is a Multicast DNS protocol for service discovery and advertisement and is a perfectly normal process. Apple's implementation of Bonjour assumes a link-local multicast address (224.0.0.*) that is not suppose to traverse a router but will still be heard on interfaces that process multicast packets.
Search for multicast DNS or Bonjour on wikipedia to learn more about how these protocols work.
While you may have had Bonjour disabled in prior versions of MacOS, it was likely re-enabled to support the Apple Wireless Direct Link (a wireless adapter sub-interface) which requires the Bonjour protocol to advertise services such as AirDrop and AirPlay.
Since you are receiving Teardrop attack notifications on your router, it is safe to assume that internal interfaces are being monitored. I would suggest disabling the deep packet security inspection for internal ethernet and wireless interfaces (or if possible dismiss or disable just the offending signature for your trusted hosts).
Best Regards

Bonjour mDNS Vista client problem

Hi all, in my home network I have several machines with different OS'es; XP, Vista, Ubuntu. Recently I have installed Avahi in Ubuntu machines, and Bonjour in Windows machines. The main goal is to have mDNS (.local resolving) working throughout the network. Avahi seems to work ok, as does Bonjour in XP machine. Those machines are able to resolve other's .local names to IP address, and they also answer correctly to mDNS queries.
The problem is the Vista machine. It does answer correctly to mDNS queries, so other machines are able to resolve it's .local name to IP address. But Vista machine is not able to resolve other machines' IP addresses as it should. For ping, the resolving seems to work, but it is slow; it takes 2-3 seconds before ping actually starts, as resolving the .local name to IP address takes so long. Mapping a network drive using .local mDNS name does not work at all. Putty is not able to connect to other machines using .local name.
Is there some known issues in Vista's Bonjour mDNS client which could cause this kind of behavior (e.g. slowness in resolve process, and some programs able to resolve the names and some not)? Any proposals how to debug this further?
I have Vista Ultimate, and I have tried with both 32-b bit and 64-bit versions.

"I can see no real need to install Bonjour on a Windows machine"?
I just explained that the need is to have .local names resolved throughout my home network. AFAIK, there is no support for this in native Windows, but Bonjour should be able to provide that support. So uninstalling Bonjour is not an answer to my needs.

Bonjour (mDNS) not broadcasting shared printers

I have a shared USB printer connected to my G4 running 10.5.3. The printer shows up as shared and worked fine in my Airport connected G4 iBook running 10.3.9. After upgrading the iBook to 10.5.5 I could no longer see the shared printer. Noting other posts that cite:
http://docs.info.apple.com/article.html?artnum=306984 (I am not sure how to make this a link)
which addresses the problem of OLDER (10.3) systems not recognizing shared printers from a 10.5 machine because 10.5 uses Bonjour (mDNS) to broadcast shared printers and 10.3 uses "cups". In my case I am sharing from 10.5 to 10.5 so that should not be an issue, but I turned on the cups protocol I per the article, in the iBook anyway (cupsctl BrowseProtocols='"cups dnssd"') - and it worked.
Looking at the ethernet protocol using "wireshark" on the G4 running. 10.5.3 is broadcasting the shared printer using CUPS protocol and not nDNS protocol. I updated the G4 to 10.5.5 and got the same results.
The question is, why is my G4 now on 10.5.5, using the old cups protocol and not the new Bonjour protocol to broadcast the shared printer?

Never mind - I solved the problem.
It seems that when upgrading, the installer does not replace the existing /etc/cups/cupsd.conf with a later version but leaves the new file ether as cupsd.conv.default or cupsd.conf.system.default. Both of my G4 computers were using the outdated file that specified the cups protocol. After changing them the the latest version everything worked.

Bonjour/mDNS over IPSEC/L2TP?

Hi there,
has anyone managed to get Bonjour / mDNS sharing working over Ipsec / L2tp Links? Can this be configured somehow? As far as I see it, ipsec / l2tp links appear as point-to-point devices which the mDNSresponder doesn't pick up for broadcasts - can this be enabled somehow?
Best regards,
abrax5

This makes no sense to me. I have been researching this topic for a while, and the general consensus seems to be that Bonjour simply is not available over a VPN connection. Isn't the purpose of a VPN to join a computer securely to a remote network? The remote computer is connected to the corporate network via a VPN, is on the *same subnet* as the corporate network, and responds to broadcast PINGs sent to the broadcast address -- indicating to me, at least, that broadcast capability is present. Why, then, can't Bonjour broadcasts be sent to the remote computer?
I have seen "solutions" detailing the use of Wide-Area Bonjour in other posts (see here: http://discussions.apple.com/thread.jspa?messageID=6917732), but this is unnecessary when the simple solution should be to forward Bonjour broadcasts to VPN-connected computers on the same subnet. I would really like to see this resolved.

How do I setup my Airport Extreme so that I can extend the coverage of my existing AT&T wifi network?

How do I setup my Airport Extreme so that I can extend the coverage of my existing AT&T wifi network?

Start by establishing a permanent fixed Ethernet cable connection from one of the available LAN <-> ports on the ATT modem/router to the WAN "O" port on the AirPort Extreme.
Ethernet cabling can be run up to 300+ feet or 100 meters, so you should be able to locate the AirPort Extreme exactly where it will be needed to provide more wireless signal coverage.
Configure the AirPort Extreme to "create" a wireless network using exactly the same wireless network name, same wireless security setting, and same wireless network password that the ATT wireless is using.
The final step is to insure that the AirPort Extreme is configured to operate in Bridge Mode, so it will work correctly with the ATT modem/router.
If you need more specific steps, we need to know what operating system you are using on your Mac or PC. If you have a Mac and do not know which operating system it is using.....click the Apple icon in the upper left corner of the screen and then click About This Mac, and post back with the OS X version number that you see there.

Can I extend both a 2.4Ghz and a 5Ghz wireless network at the same time with a second Timecapsule / Extreme ?

Can I extend both a 2.4Ghz and a 5Ghz wireless network coming from a Timecapsule with a second Timecapsule / Extreme at the same time?

I am currently extending my 5Ghz network via an Express without any problems, but the Express can only extend either / or. I just want full coverage for both networks in the whole house.
If you can extend 5 GHz now with an AirPort Express and get satisfactory results, then the AirPort Extreme will work to extend both the 2.4 GHz and 5 GHz bands in the same location.
However, your computer is going to connect to the band with the strongest signal, so it may....or may not....connect to 5 GHz given a choice of two signals.

WLC - AP Groups - Multicast - Bonjour - Apple TVv3

Good Morning
first off - Should start off by saying I have followed the Apple Bonjour deployment guide [except for interface group] portion
I have searched high and low, here and there to no avail.
http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_tech_note09186a0080bb1d7c.shtml
I am aware that the bonjour gateway IOS may or may not come out in Oct/Nov 2012, which maybe my only option at this point.
Is this not working because of my AP groups setup or have I misssed something
I can only get bonjour to work if multicast - unicast mode is selected, but our network slowly grinds to a halt, so it is not an option
when I first connect to the wireless I see 1 bonjour device for about 3 minutes and then disappears.
I can not see the appletv at all with an ipad, airplay does not appear at all.
We have the following setup.
2 campuses - Campus 2 is simular setup, but WLCs higher model and ios 7.2 and clients and subnets are double
Campus 1
2 WLC 4404 ios 7.0.230.0
30 AP groups mapped to 30 Interfaces using subnets with /23 bit subnetmasks
multicast - multicast is set with multicast addresses of
controller 1 239.239.5.1 and
controller 2 239.239.5.2
multicast is enabled
IGMPsnooping as well
On Switch multicast routing is enabled
all AP group subnets and Mgmt vlans are PIM enabled dense mode
set up a trunk to ubuntu server to act as a bonjour gateway, installed avahi and vlan
mapped all AP and mgmt vlans to Ubuntu server.
avahi see the following + more
+ eth0.136 IPv6 Apple TV                                      _airplay._tcp        local
+ eth0.136 IPv4 Apple TV                                      _airplay._tcp        local
+ eth0.134 IPv6 Apple TV                                      _airplay._tcp        local
+ eth0.134 IPv4 Apple TV                                      _airplay._tcp        local
+ eth0.132 IPv6 Apple TV                                      _airplay._tcp        local
+ eth0.132 IPv4 Apple TV                                      _airplay._tcp        local
+ eth0.130 IPv6 Apple TV                                      _airplay._tcp        local
more goes on forever
+ eth0.136 IPv4 xyz Library                             Apple Home Sharing   local
show ip multicast
Multicast Routing: enabled
Multicast Multipath: disabled
Multicast Route limit: No limit
Multicast Triggered RPF check: enabled
Multicast Fallback group mode: Dense
show ip multicast interface vlan 128
Vlan128 is up, line protocol is up
Internet address is x.x.128.1/23
Multicast routing: enabled
Multicast switching: fast
Multicast packets in/out: 14671352/276693
Multicast boundary: not set
Multicast TTL threshold: 0
Multicast Tagswitching: disabled
Where do I go from here?

Thanks Yahya and Stephen
I have tried to simplify my config as much as possible.
wlc 4404
Ethernet Multicast Forwarding............... Enable
Ethernet Broadcast Forwarding............... Enable
AP Multicast/Broadcast Mode................. Multicast   Address : 239.239.5.1
IGMP snooping............................... Enabled
IGMP timeout................................ 60 seconds
IGMP Query Interval......................... 20 seconds
I have an interface created 10.x.x.x/23
I have created a new SSID APPLETV - assigned Interface
I have added the SSID to just 1 AP Group
show network multicast mgid summary
Layer2 MGID Mapping:
InterfaceName                    vlanId   MGID
2upadhoc                         136      27
Layer3 MGID Mapping:
Number of Layer3 MGIDs........................... 11
My vlan does not show up here.
I only have 2 devices in this vlan the AppleTV and IPAD
checking the switch for all required vlans
show ip multicast
Multicast Routing: enabled
Multicast Multipath: disabled
Multicast Route limit: No limit
Multicast Triggered RPF check: enabled
Multicast Fallback group mode: Dense
admin interface
Management, AP-Manger
Vlan12 is up, line protocol is up
Internet address is x.x.x.1/24
Multicast routing: enabled
Multicast switching: fast
Multicast packets in/out: 238489978/724352
Multicast boundary: not set
Multicast TTL threshold: 0
Multicast Tagswitching: disabled
AP vlan
Vlan222 is up, line protocol is up
Internet address is x.y.z.1/24
Multicast routing: enabled
Multicast switching: fast
Multicast packets in/out: 11423/238338583
Multicast boundary: not set
Multicast TTL threshold: 0
Multicast Tagswitching: disabled
The test Apple TV Vlan
Vlan136 is up, line protocol is up
Internet address is x.xx.1/23
Multicast routing: enabled
Multicast switching: fast
Multicast packets in/out: 156740/0
Multicast boundary: not set
Multicast TTL threshold: 0
Multicast Tagswitching: disabled
interface Vlan12
ip pim dense-mode
interface Vlan222
ip pim dense-mode
interface Vlan136
ip pim dense-mode
Show ip igmp groups
Group Address    Interface                Uptime    Expires   Last Reporter
224.0.1.39       Vlan136                  2d00h     00:02:35 x.x.x.1
So just to recap
Same subnet in a AP Group
New SSID
multicast enabled on WLC - using multicast multicast mode
Broadcast forward enable
Switch -Multicast routing enabled
all vlans enabled for PIM
2 devices - added Imac to see if I could home share through Itunes.
end result
no bonjour clients, no apple tv, no airplay
Bonjour Gateway device - although same subnet it shouldn't be needed
eth0.12   Link encap:Ethernet HWaddr bc:30:5b:x:x:x
          inet addr:x.x.x.244 Bcast:x.x.x.255 Mask:255.255.255.0
          inet6 addr: fe80::be30:5bff:fed6:a178/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:55005 errors:0 dropped:115 overruns:0 frame:0
          TX packets:23003 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2776156 (2.7 MB) TX bytes:11285256 (11.2 MB)
eth0.136 Link encap:Ethernet HWaddr bc:30:5b:x:x:x
          inet addr:x.x.x.9 Bcast:x.x.x.255 Mask:255.255.254.0
          inet6 addr: fe80::be30:5bff:fed6:a178/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:42167 errors:0 dropped:115 overruns:0 frame:0
          TX packets:22340 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3251242 (3.2 MB) TX bytes:10373581 (10.3 MB)
eth0.222 Link encap:Ethernet HWaddr bc:30:5b:xx:xx:xx
          inet addr:x.x.x.9 Bcast:x.x.x.255 Mask:255.255.255.0
          inet6 addr: fe80::be30:5bff:fed6:a178/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:152397 errors:0 dropped:115 overruns:0 frame:0
          TX packets:23768 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:12795709 (12.7 MB) TX bytes:11318103 (11.3 MB)
+ eth0.222 IPv6 67665ACD317A45B0                              _appletv-v2._tcp     local
+ eth0.222 IPv4 67665ACD317A45B0                              _appletv-v2._tcp     local
+ eth0.136 IPv6 67665ACD317A45B0                              _appletv-v2._tcp     local
+ eth0.136 IPv4 67665ACD317A45B0                              _appletv-v2._tcp     local
+ eth0.12 IPv6 67665ACD317A45B0                              _appletv-v2._tcp     local
+ eth0.12 IPv4 67665ACD317A45B0                              _appletv-v2._tcp     local
Should Bonjour work same subnet with these settings?
I am going to have read more about the Interface groups and the Multicast vlan.

Airprint/Bonjour with mDNS gateway does not work over anchor

Dears
We have one WLAN where I try to use Airprint on a wireless HP printer using Bonjour. Both client and printer are on the same WLAN which anchor with another contoller for accessing internet. On WLAN we have enabled WPA PSK with MAC filtering.
Both internal and DMZ (anchored) controllers run 7.4.100 and I have enable Bonjour on DMZ controller. Using the default "default-mdns-profile"
mDNS profile I can see the printer registering but I still can not print. Bonjour is only enabled on DMZ controller but I have try both on internal without any different. Multicast is disabled globally on both controllers.
Attached the Bonjour debug during problem
Thank you in advance for your assistant.

In 7.4
For guest anchoring, the guest WLAN is able to see Bonjour services advertised to the anchor controller.
check the following link :
http://www.cisco.com/en/US/docs/wireless/technology/bonjour/Bonjour_DG_Guide.pdf
Please Don't forget to rate correct answers and flag as answered if your issue is resolved

Wlc 5508 multicast/bonjour

hello,
i have a wlc 5508 with code 7.0.220, with multicast enabled in it and on the lan too.I am having a bit of confusion getting bonjour to work on the wireless side. Looking at some of the cisco docs, i still have some questions on how to get it working in my specific enviroment.
I have the wlc conected to the lan via a port-channel. 2 wlan (ssid1 and ssid2) each wlan maps to a specific vlan (dynamic int), the management int (also used for dynamic ap-manager) on a third vlan (vlan x).
The requirement:
I need to get Bonjour working between ssid1 and vlan-x, so my wireless clients (in ssid1 can use bonjour with their laptops) can synch between wireless and wired. I know that you can do this within the same wlan (ssid) but in this case, when a user has a laptop wired into the network he cant comunicate to the wireless device. I read about Vlan Select and Multicast Optimization however, from what i understand i need to setup an interface group and just assign my wlan1 and management int to it, correct?
Is there anyone that has this type of setup working? Can you provide some configs/print screens.
Another scenario that may come into play would also be when or if i need a different segment (vlan y) in my lan to also "bonjour" with ssid1? For this i assume i would need to create a dynamic interface on the wlc using the same IP segment and do the a new interface group?
thanks in advance

Cisco answers user questions about upcoming Apple Bonjour Gateway
How specific can you be about the beta release of the Gateway?
Beta for the v7.4 release will be in Oct/Nov of this year [2012].
[RECORDING]Better Application Device Visibility With Cisco’s Bonjour Gateway-20120724 1704-1

5580 & multicast (bonjour)

I have just completed an 18AP install at my place of employment and we have run into a slight problem.
The Apple clients on our wireless LAN cannot discover printers through the bonjour protocol.
Am I correct in saying this would be related to either a unicast or multicast issue?
Can someone point me in the correct direction on how to begin configuring either unicast or multicast between the 5508's and other switching devices.
Currently I have the 2 5508's patched into a 3750 (which provides routing) and from that switch on, the other AP's connect from the network.
Thanks

Enable Multicast Globally on the WLC..
WLC GUI >> Controller >> Multicast >> Enable Global Multicast >> Enable Snooping >> Let the timeout be in defaults (60 seconds)..
and follow the below link..
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00807cc10d.shtml
lemme know if this helps and please dont forget to rate hte usefull posts!!
Regards
Surendra

CSCuh52683 - Bonjour mDNS proxy print servers not supported on mDNS Bonjour Gateway

Since 3rd party print servers are not supported. The question becomes what print servers do you recommend and are supported?

I moved this to the more appropriate "Mac OS X Technologies > Networking and the Web" forum, since it's become apparent that it involves more than Time Capsules.

Deploying Adobe Photoshop CS4 Extended over Network - issue

Hi all,
I'm hoping anyone can help me with this issue that has plagued me for a few weeks! First of all, here's the details I have:
* Adobe Photoshop CS4 Extended - downloaded media from Adobe website
* Creative Suite Deployment Toolkit - again, downloaded from Adobe website
* Installing to Windows XP with SP3
I ran Creative Suite Deployment Toolkit and set it up including our Volume Licensing key and it output some files including the XML files. I double clicked the AdobeUberInstaller.exe file and it got installed without any issue.
However, when I ran it as silent install via our SMS, it always get stuck at Adobe AIR install with the install log from
C:\Program Files\Common Files\Adobe\Installers\Adobe Photoshop CS4 11.0 09-02-2009.log
with this at the end of the log file:
[     320] Wed Sep 02 14:12:09 2009 INFO
Checking bootstrapper progress
[     320] Wed Sep 02 14:12:11 2009 INFO
Checking bootstrapper progress
[     320] Wed Sep 02 14:12:13 2009 INFO
Checking bootstrapper progress
[     320] Wed Sep 02 14:12:15 2009 INFO
Checking bootstrapper progress
[     320] Wed Sep 02 14:12:17 2009 INFO
Checking bootstrapper progress
[     320] Wed Sep 02 14:12:19 2009 INFO
Checking bootstrapper progress
and so on, with no end in sight.
I have left it more than hour. I also have left it all day, the log file is always full of it. I even "told" Creative Suite Deployment Toolkit not to install Adobe AIR and it still tries to install it anyway. I checked the AdobeUberInstaller.xml file and it has <Action>donotinstall</Action> marked for Adobe AIR. So I'm not even sure why it's trying to install it.
This happens on a PC that has Adobe AIR installed. I tried on another PC where it doesn't have Adobe AIR installed and I still get the same thing.
I'm running out of ideas how to get this to work and this is why I'm here to seek further help from you... help?
Has anyone seen this issue before and if so, what was the fix to get it to work?
Many thanks,
Tony Sutton

Hi all,
I received this e-mail from Adobe, so I thought I'd share this with you all for future ref.
Air needs to contact Adobe to get a certificate.   I would recommend not installing this as part of the suite and push out seperately. At any rate, if you AIR remotely, you will need to set the proxy to allow for the certification process. The other option might to create a snapshot of Air with the certificate already in place.
Here is KB article on it   http://kb2.adobe.com/cps/408/kb408168.html
Thanks all.

Extend multicast (bonjour, mDNS, 224.0.0.251) over network borders

Similar Messages

Maybe you are looking for