Cisco AP 1142 not discovered in WLC

After AP is booted it shows the following message and cannot able to join in WLC:
*Mar 1 07:13:37.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.71.16 peer_port: 5246
*Mar 1 07:13:37.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Mar 1 07:13:37.785: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.71.16 peer_port: 5246
*Mar 1 07:13:37.786: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.71.16
*Mar 1 07:13:37.786: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Mar 1 07:13:37.911: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Mar 1 07:13:37.916: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.71.16
*Mar 1 07:13:37.916: %DTLS-5-PEER_DISCONNECT: Peer 192.168.71.16 has closed connection.
*Mar 1 07:13:37.916: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.71.16:5246
*Mar 1 07:13:37.954: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Mar 1 07:13:37.954: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Mar 1 07:13:38.028: status of voice_diag_test from WLC is false
How can i solved this problem?

I guess there is problem of Regualatory Domain mismatch, My WLC is configure in Ameican domain (-A) and Now my new AP is in European domain (-E)... and which caused the AP unable to discover in WLC.
These are the logs which i got in WLC:
*spamReceiveTask: Mar 01 02:53:23.334: 20:3a:07:33:8c:80 Failed to parse CAPWAP packet from 192.168.71.20:1231
*spamReceiveTask: Mar 01 02:53:23.337: 20:3a:07:33:8c:80 Discarding non-ClientHello Handshake OR DTLS encrypted packet from 192.168.71.20:1231)since DTLS session is not established
*spamReceiveTask: Mar 01 02:53:34.368: 20:3a:07:33:8c:80 AP 20:3a:07:33:8c:80: Invalid country code ().
*spamReceiveTask: Mar 01 02:53:34.368: 20:3a:07:33:8c:80 PHY_TX_POWER_PAYLOAD: Invalid Tx Power Level 0
*spamReceiveTask: Mar 01 02:53:34.368: 20:3a:07:33:8c:80 AP 20:3a:07:33:8c:80: Invalid country code ().
*spamReceiveTask: Mar 01 02:53:34.368: 20:3a:07:33:8c:80 PHY_TX_POWER_PAYLOAD: Invalid Tx Power Level 0
*spamReceiveTask: Mar 01 02:53:34.370: 20:3a:07:33:8c:80 AP 20:3a:07:33:8c:80: Invalid country code ().
*spamReceiveTask: Mar 01 02:53:34.370: 20:3a:07:33:8c:80 Regulatory Domain Mismatch: AP 20:3a:07:33:8c:80 not allowed to join. Regulatory Domain check failed.
Allow
*spamReceiveTask: Mar 01 02:53:34.372: 20:3a:07:33:8c:80 Failed post decode processing of config status from 192.168.71.20:1230
*spamReceiveTask: Mar 01 02:53:34.372: 20:3a:07:33:8c:80 State machine handler: Failed to process msg type = 5 state = 5 from 192.168.71.20:1230
*spamReceiveTask: Mar 01 02:53:34.372: 20:3a:07:33:8c:80 Failed to parse CAPWAP packet from 192.168.71.20:1230
*spamReceiveTask: Mar 01 02:53:34.375: 20:3a:07:33:8c:80 Discarding non-ClientHello Handshake OR DTLS encrypted packet from 192.168.71.20:1230)since DTLS session is not established
*spamReceiveTask: Mar 01 02:53:46.312: 20:3a:07:33:8c:80 AP 20:3a:07:33:8c:80: Invalid country code ().
*spamReceiveTask: Mar 01 02:53:46.312: 20:3a:07:33:8c:80 PHY_TX_POWER_PAYLOAD: Invalid Tx Power Level 0
*spamReceiveTask: Mar 01 02:53:46.312: 20:3a:07:33:8c:80 AP 20:3a:07:33:8c:80: Invalid country code ().
*spamReceiveTask: Mar 01 02:53:46.313: 20:3a:07:33:8c:80 PHY_TX_POWER_PAYLOAD: Invalid Tx Power Level 0
*spamReceiveTask: Mar 01 02:53:46.313: 20:3a:07:33:8c:80 AP 20:3a:07:33:8c:80: Invalid country code ().
*spamReceiveTask: Mar 01 02:53:46.313: 20:3a:07:33:8c:80 Regulatory Domain Mismatch: AP 20:3a:07:33:8c:80 not allowed to join. Regulatory Domain check failed.

Similar Messages

Cisco CAP 3702I not registered with WLC 5508.

I Have WLC 5508 in my network. Now i need to add another 2 no of cisco CAP 3702I in to my network. But we got the following errors
*Mar 1 01:27:06.359: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'WLC'runn
ing version 7.3.101.0 is rejected.
*Mar 1 01:27:06.359: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.
*Mar 1 01:27:06.359: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process m
essage type 2 state 2.
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 1 01:27:25.359: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROL
LER
*Mar 1 01:27:25.363: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'WLC'runn
ing version 7.3.101.0 is rejected.
*Mar 1 01:27:25.363: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.
*Mar 1 01:27:25.363: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process m
essage type 2 state 2.
*Mar 1 01:27:25.363: %CAPWAP-3-ERRORLOG: Failed to handle capwap control messag
e from controller
*Mar 1 01:27:25.363: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap p
acket from 10.56.200.201
*Mar 1 01:27:25.363: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'WLC'runn
ing version 7.3.101.0 is rejected.
*Mar 1 01:27:25.363: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.
*Mar 1 01:27:25.363: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process m
essage type 2 state 2.
*Mar 1 01:27:06.359: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'WLC'runn
ing version 7.3.101.0 is rejected.
*Mar 1 01:27:06.359: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.
*Mar 1 01:27:06.359: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process m
essage type 2 state 2.
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 1 01:27:25.359: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROL
LER
*Mar 1 01:27:25.363: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'WLC'runn
ing version 7.3.101.0 is rejected.
*Mar 1 01:27:25.363: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.
*Mar 1 01:27:25.363: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process m
essage type 2 state 2.
*Mar 1 01:27:25.363: %CAPWAP-3-ERRORLOG: Failed to handle capwap control messag
e from controller
*Mar 1 01:27:25.363: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap p
acket from 10.56.200.201
*Mar 1 01:27:25.363: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'WLC'runn
ing version 7.3.101.0 is rejected.
*Mar 1 01:27:25.363: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.
*Mar 1 01:27:25.363: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process m
essage type 2 state 2.

Your WLC seems to be running version 7.3 which is not supported with 37xx AP platform.
You need to run WLC with version 7.6.100.0 onwards to support these new AP's.
For more details check the Wireless Software Compatibility Matrix.
-Thanks
Vinod
**Encourage Contributors. RATE Them.**

Cisco UCS Manager not discovering C240 server

Hello, Cisco community!
Currenlty UCS manager shows two Fabric Interconnects, and two Fabric Extenders, but for some reason my server isn't showing up
Here is the birds eye view:
I have my C240 connected with two 10GbE twinax cables, each going to one fabric extender. (2 FEX total)
I have two 10GbE twinax cables connected from the fiber module of each FEX to each Fabric interconnects. (2 FI total)
The fabric interconnect ports L1 and L2 ports are connected to their corresponding ports. So their connected to each other.
I run 'show cluster extended-state' on the primary FI and this is what i get:
FI-A# show cluster extended-state
Cluster Id: 0xebaad0e28ded11e3-0x86d4002a6a153d84
Start time: Wed Feb 5 16:07:44 2014
Last election time: Wed Feb 5 16:23:26 2014
A: UP, PRIMARY
B: UP, SUBORDINATE
A: memb state UP, lead state PRIMARY, mgmt services state: UP
B: memb state UP, lead state SUBORDINATE, mgmt services state: UP
heartbeat state PRIMARY_OK
INTERNAL NETWORK INTERFACES:
eth1, UP
eth2, UP
HA NOT READY
No device connected to this Fabric Interconnect
After configuring the server-side ports on each FI, the server still doesn't show up
Any idea are highly appreciated!!
-Alex

It's good to know that the Fabric Interconnects don't need upstream connectivity, so we can scratch that from our list of possible issues.
For clarity, here are the important firware versions:
CMIC - 1.5(3), cisco recommends a minimum of 1.4(6)
BIOS - 1.5.1c, cisco recommends a minumum of 1.4.7a
vNIC - 2.1(1c), cisco recommends a minumum of 2.1(0.367e)
So, we can cross out firware mis-matches from the list.
wdey,
I tried going trough UCS Manager and looking where i could configure the out-of-band IP management pool, but I can't find the right place to do that. Here is a screen shot of the VLAN tab of my UCS Manager.
Could you eleborate more on the process of how to do this? This might fix the issue.
Also, I noticed that in the BIOs setting screen, under Advanced -> LOM and PCIe Slots configuration -> PCIe Slot ID: 2(VIC 1225) it says Option ROM Status Not Loaded. Do you think this might have something to do with server discovery?
Thanks alot for the help guys It's really much apprecaited.
-Alex

Cisco 3502i will not upgrade to 7.4.121.0 from 7.2.111.3 2504 WLC "Downloading"

Cisco 3502i will not upgrade to 7.4.121.0 from 7.2.111.3. 2504. Wireless tab continues to say "downloading" state on all APs. Temporary fix is to set WLC back to 7.2.11.3.
This is only happening on a few stores that are on one particular Prime Infrastructure box. Other stores on other Prime boxes not having this issue as well as most stores on the same box also not having this issue.
Anyone run into this and was able to resolve?

Scott, I have a few 2504 having this issue. Some having this issue if the site recovered from a power outage.
I can upload the image to other WLCs without issue. Its just these few on one particular PI, leading me to think that some of the WLC have corrupt images.
Yes, TAC told me the issue with 7.4 in the "downloading" state was that there was a communication issue between the AP and WLC and that I would need to get into the AP which I can not do, being it a remote site and FW security disabled this ability.
Some of TAC comments attached.

AP not joining to WLC

Hi,
After a wireless network interruption, one of MAP 1522 it's not joining to WLC .
What should I do to solve this problem?
Thanks.
(Cisco Controller) >show ap join stats detailed 00:08:30:bb:53:20
Discovery phase statistics
- Discovery requests received.............................. 7
- Successful discovery responses sent...................... 5
- Unsuccessful discovery request processing................ 0
- Reason for last unsuccessful discovery attempt........... Not applicable
- Time at last successful discovery attempt................ Feb 23 11:25:16.137
- Time at last unsuccessful discovery attempt.............. Not applicable
Join phase statistics
- Join requests received................................... 2
- Successful join responses sent........................... 2
- Unsuccessful join request processing..................... 2
- Reason for last unsuccessful join attempt................ RADIUS authorization is pending for the AP
- Time at last successful join attempt..................... Feb 23 11:25:28.385
- Time at last unsuccessful join attempt................... Feb 23 11:25:28.386
Configuration phase statistics
- Configuration requests received.......................... 3
- Successful configuration responses sent.................. 1
- Unsuccessful configuration request processing............ 0
- Reason for last unsuccessful configuration attempt....... Not applicable
- Time at last successful configuration attempt............ Feb 23 11:25:28.581
--More-- or (q)uit
- Time at last unsuccessful configuration attempt.......... Not applicable
Last AP message decryption failure details
- Reason for last message decryption failure............... Not applicable
Last AP disconnect details
- Reason for last AP connection failure.................... Timed out while waiting for ECHO repsonse from the AP
- Last AP disconnect reason................................ AP's capwap state machine restarted
Last join error summary
- Type of error that occurred last......................... AP got or has been disconnected
- Reason for error that occurred last...................... Timed out while waiting for ECHO repsonse from the AP
- Time at which the last join error occurred............... Mar 18 19:07:28.864
AP disconnect details
- Reason for last AP connection failure.................... Timed out while waiting for ECHO repsonse from the AP

Ioan,
as you see here:
Reason for last unsuccessful join attempt................ RADIUS authorization is pending for the AP
It seems you need to add a mac filter for this AP on you WLC so it joins.
Or, if you are using external radius for authorization, you need to add an entery for this AP on the radius server.
Here are some links that may help:
http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00808f8599.shtml#p5
http://www.cisco.com/en/US/products/ps6366/products_configuration_example09186a00808c7234.shtml
Don't please forget to rate the reply if it is useful.
Cheers,
Amjad

WLAN override option not available for WLC 4402 - 6.0.196.

Hi All,
Its kind of weird BUT it seems that the option for WLAN override is missing.u.
I could find it on the lower version BUT not on the 6.0.196.
Please help.
Does this mean I could only set it up via the WCS and not the WLC directly.
Thank you.
Warmest Regards,
Azzafir Ariff Patel.

Hi Scott,
Thank you so much for the clarification.
Thanks again.
Quoting fella5 :
azzafir,
>
A new message was posted in the Discussion thread "WLAN override
option not available for WLC 4402 - 6.0.196.":
>
https://supportforums.cisco.com/message/3042635#3042635
>
Author : Scott Fella
Email : [email protected]
Profile : https://supportforums.cisco.com/people/fella5
>
Message:

Cisco Prime does not update devices in "Device Work Center"

Hi everyone.
I have a problem that is bugging me a lot.
I'm working in Cisco Prime 2.0 and we have a big problem.
If I run a discovery and find all a lot of switches, the switches is discovered and are fully managed via SSH and SNMP.
We are using both 2960S, 2960x and a lot of old 2950:s.
We are replacing all 2950:s to some new 2960 model.
The big problem is that when we replace the old 2950:s we reuse the same IP-address (so our customly built programs can find them again), Cisco Prime DOES NOT update the model of the switches. The switches are still in the Device Work Center and are still in recognized as a 2950.
If I mark the switch to view more info in Device Work Center the Unique Device Identifier says that it is a new 2960s/x but the model is still recognized as a 2950 so Prime can obviously find a manage the switch and update "some" info, but not the device itself.
Does someone have the same problem or do I need to delete all 2950:s and do a new discovery so Prime understand?
EDIT
I have now an example.
Please look at the image.

Hi,
I ran into same issue,Yes this is known issue,there is a open defect id and is fixed in upcoming releases.
I deleted existing devices and rediscovered,but note you will loose all your configurations related to existing deive model.
Regards

CCP IS NOT DISCOVERING DEVICE

Dear all,
I could not Discover my cme router in CCP software.When I try to Discover It showing discovery Failed
Discovery details shows password error.But I can login to router using CLI,telnet and Via Web interface(GUI).
my configuration detailsa are
ip http server
ip http authentication local
ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
ip http path flash:/GUI
Could you Please help me
Thanks and Regards
Ajay Jose K

HI Ajay.
If you are using simple password such as "cisco", try to change it with something more complex.
Let me know
Regards
Carlo

CER 2.0 Switch not discovered

I have a 3560 switch that has been defined under Phone Tracking>LAN Switch Details section of CER. I had a bad DNS entry pointing two different switch hostnames to the same IP address. I made the correction in DNS to point to the correct switch. CER will not discover the switch. I have removed and re-added the switch as well. It is not getting any SNMP read errors like when the RO community string doesn't match. I don't find any relevant entries in the event logs. I have restarted several services and waited ample time for DNS to refresh. Another note - I have 70 more 3560 switches working ok on the same IOS version. Does CER cache DNS entries? Any guidance is much appreciated.

Check that all Cisco CallManagers are SNMP-reachable and that the SNMP settings are correct. Verify that the community string setting is read-only on all the Cisco CallManagers in the cluster.

Thunderbolt display: devices not discovered after using Mini DisplayPort–to–VGA adapter

I have an interested problem related to using my MacBook Air in clamshell (closed) mode, connected to a Thunderbolt display. The problem appears to be related to moving my MacBook air between my office and my home.
At the office, I use the MacBook Air with an external VGA display, connected via the Mini DisplayPort–to–VGA adapter. At home, I use the MacBook Air together with a Thunderbolt display. An Apple USB keyboard is also connected to the display.
Mini DisplayPort–to–VGA adapter implicated
The following sequence of events causes the problem to occur:
Use the MacBook air (open) together with a VGA display, connected via a Mini DisplayPort–to–VGA adapter (depicted at right);
Put the MacBook Air to sleep by closing the lid, and disconnect the Mini DisplayPort–to–VGA adapter (I am not sure if the order of these two steps is significant—I usually perform them almost simultaneously when packing up my MacBook Air and getting ready to leave the office); and
With the MacBook Air still closed, connect it to a Thunderbolt display with a connected USB keyboard.
At this point, I would expect to be able to wake up the MacBook Air by tapping on the space bar of the keyboard. However, what I have observed is that this does not wake the MacBook Air.
I can wake the MacBook however by moving or clicking a Bluetooth mouse that is paired with the MacBook Air.
At this point, although the MacBook Air is awake, and the display is working, the USB keyboard connected to the display still does not work. This is the problem, in a nutshell.
Unplugging the USB keyboard from the display, and plugging it back in causes the MacBook Air properly to identify the keyboard.
I used Apple System Profiler to save a list of identified devices at two points in time:
Immediately after waking the MacBook Air by moving the Bluetooth mouse (at which point the USB keyboard was not working); and
After unplugging and plugging in again the USB keyboard (at which point the USB keyboard worked fine).
Many devices are enumerated in the second list that are missing from the first. For example:
Keyboard Hub@fe110000 <class IOUSBHubDevice, id 0x1000378ef, !registered, !matched, inactive, busy 3 (37993 ms), retain 6>
AppleUSBHub <class AppleUSBHub, id 0x1000378f2, !registered, !matched, inactive, busy 1 (37987 ms), retain 6>
IOUSBInterface@0 <class IOUSBInterface, id 0x1000378f4, !registered, !matched, inactive, busy 1 (37986 ms), retain 6>
Keyboard Hub@fe110000 <class IOUSBHubDevice, id 0x1000378f6, registered, matched, active, busy 0 (7 ms), retain 10>
AppleUSBHub <class AppleUSBHub, id 0x1000378f9, registered, matched, active, busy 0 (1 ms), retain 9>
IOUSBInterface@0 <class IOUSBInterface, id 0x1000378fb, !registered, !matched, active, busy 0, retain 7>
Apple Keyboard@fe112000 <class IOUSBDevice, id 0x1000378fd, registered, matched, active, busy 0 (112 ms), retain 11>
and many child devices…
Using the Mini DisplayPort–to–VGA adapter appears to be a necessary step to causing this problem to occur. If I merely disconnect the MacBook Air from the display, let it go to sleep, and then reconnect it again, the USB keyboard will work immediately and can be used to wake the computer from sleep.
Some devices are discovered even when the computer is in sleep mode. This is how it should work.
The problem appears to be that when a Mini DisplayPort–to–VGA adapter has been used since the last time the computer was connected to a Thunderbolt display, the MacBook air does not discover devices completely when it is again connected to the Thunderbolt display while in sleep mode.
Can anyone else reproduce this problem?

Hi glraczon.support,
It sounds like the external display you are using (projector) operates at a smaller resolution than your MacBook Pro. You may want to configure the display preferences in System Preferences for the external projector.
Here is an article that may help you with that process:
OS X Mountain Lion: About the Display pane of System Preferences
http://support.apple.com/kb/HT5369
Thanks,
Matt M.

2014 Macbook Pro 10.9.5 not discovering my iPhone 5s iOS8

Why is Airdrop on my new Macbook Pro 10.9.5 not discovering my iPhone 5s iOS8.0.2
Bluetooth on.
On same wireless home network.
Selected Airdrop to everyone on my iPhone 5s.
Macbook Pro was bought in August still not discovering my iphone. Airdrop icon in Finder just keeps spinning.
I'm signed into my Apple ID on the both devices. My admin login account for my Macbook is also connected to my Apple ID.
If only i could transfer selected photos to my Macbook!
Help!

Hi there Musicoshi,
It looks like this feature will be avlaible in OS X Yosemite later this fall. Take a look at the page below for more information.
Apple - OS X Yosemite - Apps
With AirDrop, sharing ﬁles has never been easier.
AirDrop makes sharing your files between Mac computers simple. And now it works between Mac and iOS, too. So with just a few clicks on your Mac, you can take a file from any folder and use AirDrop to send it to a nearby Mac or iOS device. It’s perfect for, say, sharing a document with a coworker in the next room or sending a presentation to a client across the table.
-Griff W.

My iphone 5 is not discovered ssid wifi

my iphone 5 is not discovered ssid wifi in near of ap, but most very near of ap why ???? my ios v 6.0.2 but not currect work

Try restarting the iPhone and power cycling the router.
Is the network broadcasting the Wi-Fi address? Do you see any errors when trying to join the network?
Also, take a look at this Apple doc -> iOS: Troubleshooting Wi-Fi networks and connections

Mine is not a question but I received the solution to the iphone 4s not discovering bluetooth, you hold the top button and the home button until the apple logo comes up and then let it reboot, put your bluetooth in pairing mode, and then turn on bluetooth

My new iphone 4s would not discover bluetooth. I called apple, and the guy was great!!! He told me to hold the top button and the home button together and do not let go until the apple logo came up, this would do a hard reset. Then when it reboots, you turn on your bluetooth in paring mode, and then turn on the bluetooth on your iphone 4s and it will find your bluetooth device. Simple, yet it works!!! Hope this helps those of you having the same problem I was having trying to connect your bluetooth.

My new iphone 4s would not discover bluetooth. I called apple, and the guy was great!!! He told me to hold the top button and the home button together and do not let go until the apple logo came up, this would do a hard reset. Then when it reboots, you turn on your bluetooth in paring mode, and then turn on the bluetooth on your iphone 4s and it will find your bluetooth device. Simple, yet it works!!! Hope this helps those of you having the same problem I was having trying to connect your bluetooth.

SQL Server 2012 Express Instance is Not Discovered

I have a single SQL Server 2012 Express instance that is the backend database for a small door security application. I just noticed after having deployed the OpsMgr agent months ago that it never discovered the SQL instance. The SQL instance
is, as stated, Express, and it's the only Express instance I have. Is that why it is not discovered? All the documentation I found seems to indicate the opposite -- that Express is discovered and there are steps you can take to exclude Express
instances. I have no overrides set to exclude any instance or any database.
- System Center Operations Manager 2012 RTM (no SP1, no R2)
- SQL Server 2012 MP version 6.3.173.1
- SQL Server is Windows Server 2012
- SQL Server 2012 Express running on a Hyper-V VM. Instance is named DOORSERVER\Eclipse
- Agent is installed and other discoveries seem to be working fine
- No discovery errors in the event log related to SQL, although there is one about the Windows Server 2008 discovery not being able to start, but I'm on Windows Server 2012, so I am guessing that's okay?
- No overrides are set on the discovery
- Discovery has found every other SQL Server 2012 instance (standard and enterprise editions)

Well, just realized I didn't have the latest MP. Upgrading to 6.4.1.0 version of the SQL MP fixed the discovery issue.

My apple TV is not discovering my devices. what do i do?

my apple TV is not discovering my devices. what do i do?

If you are referring to airplay
http://support.apple.com/kb/TS4215?viewlocale=en_US&locale=en_US

Cisco AP 1142 not discovered in WLC

Similar Messages

Maybe you are looking for