ARD client disconnected from ARD under leopard after using curtain

I have just noticed a problem that occurs when I put a client under curtain mode under leopard....the client disconnects from the ARD console and remains in the locked state until I go over and manually restart the system...anyone else having this issue

Sorry, I hadn't noticed that someone replied...Geez you would think they would get this stuff corrected...Do you know if there is going to be an improved ARD in the future. I manage a lab and apple tools are better and more reliable but still have a long way to go....
Glen

Similar Messages

  • Client Disconnected From Database

    I'm running lookout 5.0 on one computer and logging its citadel to another machine. There is more than one lookout process on the PC that is actually running lookout itself. Different processes are logging to different designated database folders on the other computer. When you can actually get lookout to show the history info (i.e hypertrend data and such) on the computer it all works great. However if you ever restart the computer requiring to shutdown lookout, then the next time it boots up it is nearly impossible to get lookout to display the trend info again. You always get the "client disconnected from database" alarm. All the network paths and folder locations are correct. I am lost on this one.

    Did you get this error every time you reboot Lookout or sometimes ?
    If you get it sometimes:
    Simply delete the /database/ Folder in Lookout directory
    when you restart Lookout it will creat a new one.
    From experience when you get this message the database is realy damage
    i dont know why this happens.

  • How do i set up a new lion imac from a snow leopard imac using time machine?

    How do i set up a new lion imac from a snow leopard imac using time machine?

    Connect the two via Firewire cable - Transferring files between two computers using FireWire. Boot the old iMac into Target Disk Mode. Boot the new iMac normally.
    If you are starting the new iMac for the first time then do the above before you turn on the new iMac. After you turn on the new iMac you will begin in the Setup Assistant. When you complete the registration screens you will be offered an opportunity to migrate your data from another Mac. Follow the instructions to migrate your old Home folder, third-party applications and support files, and system preferences to the new iMac.
    If you have already gone through the Setup Assistant and created an initial admin user account, then you do the connection step but will use Migration Assistant in the Utilities folder of the new iMac.

  • [svn] 3687: Add some messaging tests for scenarios that involve subscribing to a destination , disconnecting from the channel currently being used and resubscribing to the destination .

    Revision: 3687
    Author: [email protected]
    Date: 2008-10-16 11:23:39 -0700 (Thu, 16 Oct 2008)
    Log Message:
    Add some messaging tests for scenarios that involve subscribing to a destination, disconnecting from the channel currently being used and resubscribing to the destination. There is an issue that is causing the streaming/multipleDisconnectsResubscribesTest.mxml test to fail that I will log a bug for.
    Added Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/disconnectResubscribeJMSTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/disconnectResubscribeTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/multipleDisconnectsResubscribesTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/disconnectResubscribeJMSTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/disconnectResubscribeTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/multipleDisconnectsResubscribesTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/disconnectResubscribeJMSTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/disconnectResubscribeTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/multipleDisconnectsResubscribesTest.mxml

    Revision: 3687
    Author: [email protected]
    Date: 2008-10-16 11:23:39 -0700 (Thu, 16 Oct 2008)
    Log Message:
    Add some messaging tests for scenarios that involve subscribing to a destination, disconnecting from the channel currently being used and resubscribing to the destination. There is an issue that is causing the streaming/multipleDisconnectsResubscribesTest.mxml test to fail that I will log a bug for.
    Added Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/disconnectResubscribeJMSTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/disconnectResubscribeTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/multipleDisconnectsResubscribesTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/disconnectResubscribeJMSTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/disconnectResubscribeTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/multipleDisconnectsResubscribesTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/disconnectResubscribeJMSTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/disconnectResubscribeTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/multipleDisconnectsResubscribesTest.mxml

  • Downgrade ARD client software from 3.4 to 2.2?

    Hi,
    I'm running Apple Remote Desktop 2.2, however the Mac Pros (running 10.5.8) which I want to control have ARD Client 3.4 installed.
    Is there any way to downgrade the client software so I can use ARD 2.2?
    At the moment, when I try to, for example, send a message using ARD 2.2 to a Mac Pro running ARD Client 3.4 I get an error message reading:
    "Failed on all. Status: Newer Client software (3.4)"
    Many thanks in advance for any assistance.

    ARD 2.2 is not supported on Leopard nor on Intel-based Macs. At least one user (raus), though, posted here that he got ARD 2.2 to work in Leopard, but there are no guarantees. From the finder, navigate to:
    /System/Library/CoreServices/RemoteMangement
    From the folder, delete (or move) the ARDAgent v3.X file. Reinstall the 2.2 update for ARD on the Apple site. (This may be optional; the original poster just reinstalled the update to be safe.) You can reportedly now run Remote Desktop 2.2 in 10.5. This works for PowerPC and Intel Mac.
    Note, though, that this is completely unsupported by Apple and may or may not work, or may cause issues. For proper support for Leopard, you need ARD 3.2 or later. Your best option is to upgrade your administration system to ARD 3.4, which is available through the Mac App Store for only $79.99 for the unlimited-client version.
    Good luck.

  • Client Upgraded from Tiger to Leopard Can No Longer Connect to Tiger Server

    I just finished upgrading a G5 2GHz DP Powermac from Tiger to Leopard. This was an Archive and Install upgrade with importing the old settings. After verifying the account migration, including .Mac connectivity, and fixing all 3rd party software compatibilities/upgrades, I tried to connect to our Tiger 4.11 server by clicking on the server's Icon in the Shared section of the Finder Sidebar. The finder then switches to browse the the server for shares: "Connecting..." is displayed under the tool bar, with a "Share Screen..." and "Connect As..." buttons to the right.
    At this point the "Connecting..." remains displayed with the spinning circle in the bottom right of the Finder window.... spinning. This situation continues for several minutes until is seems the system gives up.
    If I click on the Path button on the Tool Bar, and go up to the Shared level, ALL the Shares on the Network are displayed, including all the Tiger Client machine shares. I can click on the triangle beside the Tiger Client's icon, and all the drives and home directories on the Mac are listed. All the client shares can be accessed without any issues. NOTE: There are no other Leopard clients on the LAN.
    Prior to the Leopard upgrade, this client could connect to the Tiger server as well. All the other clients on the LAN can access the Tiger server also.
    On the Leopard client I have tried clicking and the "Connect As..." button and using the menu "Connect to Server" and specifying the server's IP, and I get the same "Connecting..." message with a "non-connecting" result.
    I can only assume that somehow the Account Name and password are not being passed correctly. But, using "Connect As..." should resolve that. However, "Connect As..." does not give me a user/password window!
    If I check the AFP Access log on the Server, the only messages displayed are "Mounted Volume..." No messages in the error log, and no messages in the "Connections" section.
    Can anyone help me figure out why the Leopard client can not connect to the Tiger Server?
    My apologies if the description of my problem is a bit disjointed. I have been thrown into server admin and am learning "Trial by Fire".
    Any help or suggestions on how to resolve this issue will be greatly appreciated.
    Thanks
    Gary
    Message was edited by: Gary Sumlak

    OK. A quick update.
    After waiting for about 10 minutes for the rotating circle in the bottom right corner to stop, I was able to click on the "Connect As..." button. It took another 10 minutes, but the Connect As window eventual popped up. I entered the Userid and Password (saving to Keychain) and was able to see all the sharepoints on the the server. I browsed all the connected drives and folders without issue.
    I then disconnected from the server. Reviewing the AFP logs on the server shows messages for the connection Login and Logout.
    I then tried to reconnect to the server, and again another 10 minutes wait, although this time the Leopard client eventually connected automatically with the proper User, as per the AFP logs confirms.
    Although, the client can now connect to the server, for it to take 10 minutes will be unacceptable to management, not to mention the end user. Tiger clients can connect in a couple seconds!
    Is there a way to reduce the Leopard login time to, say, a couple seconds, like it does with the Tiger clients?
    Again, any help or suggestions would be greatly appreciated.
    Thanks
    Gary

  • Clients disconnected from WLC randomly

    Hi,
    I'm doing some tests with clients to see how much time they are kept registered in the controller while they are disconnected. I've set session timeout to 0 (infinite) and user idle timeout to 12 hours. 
    The problem is that sometimes the clients are disconnected from the controller before the user idle timeout expires:
    apfMsDeleteByMscb Scheduling mobile for deletion with deleteReason 6, reasonCode 1
    Other times they are expired normally by the user idle timeout (deleteReason4,reasonCode4).
    If I am not wrong deleteReason 6 corresponds to manual deletion of the client, but there is no manual interventention when this happen, is the controller who deletes it.
    Can anybody explain why this happens randomly?
    WLC version 6.0.196
    Thanks.

    Refer the 2 Bugs :
    Unified APs removing clients on maximum retries.
    CSCti91944
    Description
    Symptom:
    A wireless client might be removed from the mobility database before the user idle timeout. When this happens, if "debug client MAC" is in effect, messages similar to the following are seen on the WLC:
    *spamApTask3: clientmacaddrXYZ Received Idle-Timeout from
    AP macADDR-abc slot 0 for STA XYZ Client MAC ADDR
    *spamApTask3: apfMsDeleteByMscb Scheduling mobile for deletion with
    deleteReason 4, reasonCode 4
    The symptoms, as experienced by the user, depends on the behavior of the client device and on the WLAN configuration as follows:
    - If the WLAN is configured for web-auth, the client is forced to reauthenticate through the web.
    - If the WLAN is configured for L3 mobility and if the client performs an L3 roam at the time of the removal, the client's old IP address in the old subnet is no longer valid, and the client is forced to re-DHCP in the new subnet. Any existing TCP connections fail to work expected. If the client is a 792x wireless phone on a call, the talk path is lost for the remainder of the call.
    - If the WLAN is configured for L2 mobility, then the client is forced to perform a full EAP authentication (if EAP is configured) and to re-DHCP (if DHCP required is configured). In most cases, this does not cause a perceptible service interruption, unless the client's IP address changes.
    Conditions:
    This occurs when an access point fails to transmit 250 consecutive packets to the client (if there are 64 failed retransmits per packet, which means 4 consecutive dropped packets, it triggers the deauth).
    Examples:
    - Client radio is temporarily disabled.
    - Client has gone into hibernation/standby.
    - For a voice client, if the client is in a call and is unable to receive audio packets for a fraction of a second.
    Workaround:
    None; however, reconfiguring the WLAN for layer 2 rather than layer 3 mobility can mitigate the effect.
    Known Affected Releases:
    (3)
    7.0(98.0)
    6.0(199.0)
    6.0(199.4)
    Clients hit Idle timeout after successful authentication
    CSCue34763
    Description
    Symptom:
    A wireless client, while associated/authenticated (in RUN state), will be
    prematurely idle timed out by an AP. With "debug client" in effect on the
    WLC, messages similar to the following are seen:
    *spamApTask2: Jan 30 17:10:17.258: 00:11:22:33:44:55 Received Idle-Timeout from
    AP 84:78:ac:00:11:22, slot 1 for STA 00:11:22:33:44:558
    *spamApTask2: Jan 30 17:10:17.258: 00:11:22:33:44:55 apfMsDeleteByMscb
    Scheduling mobile for deletion with deleteReason 4, reasonCode 4
    The idle timeout event occurs while the client is not idle, and more rapidly,
    after the client's last reassociation, than the configured user idle timeout
    value.
    Conditions:
    Flexconnect (H-REAP) local switching is configured, with DHCP Required.
    Workaround:
    Clients hit Idle timeout after successful authentication
    CSCue34763
    Description
    Symptom:
    A wireless client, while associated/authenticated (in RUN state), will be
    prematurely idle timed out by an AP. With "debug client" in effect on the
    WLC, messages similar to the following are seen:
    *spamApTask2: Jan 30 17:10:17.258: 00:11:22:33:44:55 Received Idle-Timeout from
    AP 84:78:ac:00:11:22, slot 1 for STA 00:11:22:33:44:558
    *spamApTask2: Jan 30 17:10:17.258: 00:11:22:33:44:55 apfMsDeleteByMscb
    Scheduling mobile for deletion with deleteReason 4, reasonCode 4
    The idle timeout event occurs while the client is not idle, and more rapidly,
    after the client's last reassociation, than the configured user idle timeout
    value.
    Conditions:
    Flexconnect (H-REAP) local switching is configured, with DHCP Required.
    Workaround:
    Disable DHCP required.
    Disable DHCP required.

  • VPN Client disconnection from command line

    Hi,
    I want to connect to IPsec VPN on ISA500 by VPN Client (v 5.0.07.0440, the last version, I think), using command line parameters.
    I can connect with the command:
    "%programfiles%\Cisco Systems\VPN Client\ipsecdialer.exe" -c -user myUser -pwd myPassword "MyConnectionEntry"
    but i don't know the command to disconnect from command lines.
    If I do
    "%programfiles%\Cisco Systems\VPN Client\ipsecdialer.exe" -?
    I obtain the list of parameters
    vpngui [-c | -sc [sd] [-user <username>] [-pwd <password> ! -eraseuserpwd]] <connection entry>
    but I don't unterstand what I have to do... I try every combination using -sd parameter (I think means for silent disconnect), but in every case I can only to show VPN interface  without disconnect anything...
    Can anyone help me?
    Thanks

    Prasath,
    This appears to be a data flow issue.  You need to look in the dataflow log file.  Your information indicates the project name is SAMPLES.xml, and the data flow ID is D20091213_014350765.  Look at the data flow log file in
    C:\dqxi\11_7\repository\configuration_rules\runtme_metadata\project_SAMPLES\D20091213_014350765
    Alternatively, you can temporarily replace the transactional reader and writter transforms with their corresonding batch transforms, and run the job from the Project Architect.  Any errors will be displayed in the Running window.
    Paul

  • WebStart Fails to load cached app when disconnected from internet under Apple OS-X

    Java WebStart broken under OS-X
    Our Java WebStart application fails to re-launch when disconnected from the internet.
    Instructions:
    Running OS-X 10.8 or 10.9 with internet connected.
    Launch a WebStart application (e.g.. from http://www.dsuk.biz/Downloads/SmartType/SmartType2.0.19/APPLICATION.JNLP)
    Disconnect from internet.
    Relaunch the application either with the downloaded JNLP file or the installed desktop shortcut.
    I get "Unable to launch application" error with following exception:
    java.net.UnknownHostException: www.dsuk.biz
      at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
      at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
      at java.net.Socket.connect(Socket.java:589)
      at java.net.Socket.connect(Socket.java:538)
      at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
      at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
      at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
      at sun.net.www.http.HttpClient.<init>(HttpClient.java:211)
      at sun.net.www.http.HttpClient.New(HttpClient.java:308)
      at sun.net.www.http.HttpClient.New(HttpClient.java:326)
      at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1167)
      at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1103)
      at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:997)
      at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:931)
      at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1511)
      at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1439)
      at com.sun.deploy.net.HttpUtils.followRedirects(Unknown Source)
      at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source)
      at com.sun.deploy.net.BasicHttpRequest.doGetRequestEX(Unknown Source)
      at com.sun.deploy.cache.ResourceProviderImpl.checkUpdateAvailable(Unknown Source)
      at com.sun.deploy.cache.ResourceProviderImpl.isUpdateAvailable(Unknown Source)
      at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
      at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
      at com.sun.javaws.Launcher.updateFinalLaunchDesc(Unknown Source)
      at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
      at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
      at com.sun.javaws.Launcher.launch(Unknown Source)
      at com.sun.javaws.Main.launchApp(Unknown Source)
      at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
      at com.sun.javaws.Main.access$000(Unknown Source)
      at com.sun.javaws.Main$1.run(Unknown Source)
      at java.lang.Thread.run(Thread.java:744)
    I have reproduced with Java build 1.8.0-b132 and 1.7.0_51
    Java Web Start 11.0.2.132
    Using JRE version 1.8.0-b132 Java HotSpot(TM) 64-Bit Server VM
    Re launching the application under Windows 7 when disconnected from the internet seems to work fine (tested in virtual Windows 7 64 bit VM under Parallels). It used to work fine on OS-X!
    RANT/QUESTION
    WebStart over the last two years has given me no end of headaches with deployed applications mysteriously breaking when either Oracle or Apple have made changes. So far WebStart just has not been a reliable and robust means of deployment.
    Is WebStart to be taken seriously as a deployment vehicle for a commercial application or should I be looking at other solutions?
    Also: How do I report bug to Oracle? Do you have to pay for support in order to report bugs?

    Java WebStart broken under OS-X
    Our Java WebStart application fails to re-launch when disconnected from the internet.
    Instructions:
    Running OS-X 10.8 or 10.9 with internet connected.
    Launch a WebStart application (e.g.. from http://www.dsuk.biz/Downloads/SmartType/SmartType2.0.19/APPLICATION.JNLP)
    Disconnect from internet.
    Relaunch the application either with the downloaded JNLP file or the installed desktop shortcut.
    I get "Unable to launch application" error with following exception:
    java.net.UnknownHostException: www.dsuk.biz
      at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
      at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
      at java.net.Socket.connect(Socket.java:589)
      at java.net.Socket.connect(Socket.java:538)
      at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
      at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
      at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
      at sun.net.www.http.HttpClient.<init>(HttpClient.java:211)
      at sun.net.www.http.HttpClient.New(HttpClient.java:308)
      at sun.net.www.http.HttpClient.New(HttpClient.java:326)
      at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1167)
      at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1103)
      at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:997)
      at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:931)
      at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1511)
      at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1439)
      at com.sun.deploy.net.HttpUtils.followRedirects(Unknown Source)
      at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source)
      at com.sun.deploy.net.BasicHttpRequest.doGetRequestEX(Unknown Source)
      at com.sun.deploy.cache.ResourceProviderImpl.checkUpdateAvailable(Unknown Source)
      at com.sun.deploy.cache.ResourceProviderImpl.isUpdateAvailable(Unknown Source)
      at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
      at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
      at com.sun.javaws.Launcher.updateFinalLaunchDesc(Unknown Source)
      at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
      at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
      at com.sun.javaws.Launcher.launch(Unknown Source)
      at com.sun.javaws.Main.launchApp(Unknown Source)
      at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
      at com.sun.javaws.Main.access$000(Unknown Source)
      at com.sun.javaws.Main$1.run(Unknown Source)
      at java.lang.Thread.run(Thread.java:744)
    I have reproduced with Java build 1.8.0-b132 and 1.7.0_51
    Java Web Start 11.0.2.132
    Using JRE version 1.8.0-b132 Java HotSpot(TM) 64-Bit Server VM
    Re launching the application under Windows 7 when disconnected from the internet seems to work fine (tested in virtual Windows 7 64 bit VM under Parallels). It used to work fine on OS-X!
    RANT/QUESTION
    WebStart over the last two years has given me no end of headaches with deployed applications mysteriously breaking when either Oracle or Apple have made changes. So far WebStart just has not been a reliable and robust means of deployment.
    Is WebStart to be taken seriously as a deployment vehicle for a commercial application or should I be looking at other solutions?
    Also: How do I report bug to Oracle? Do you have to pay for support in order to report bugs?

  • No more SMS from Adressbook under Leopard?

    I liked to use the right click option on a phonenumber to send an sms to someone through my mobile which is connected via bluetooth. It seems that this feature was stripped under Leopard. Why? I really liked it. I hope Apple isn't stripping functionality to favor the iPhone-functionality!

    Yes, Apple has removed this feature.
    See here:
    http://discussions.apple.com/search.jspa?threadID=&q=sms&objID=f1223&dateRange=l ast90days&userID=&numResults=15&rankBy=10001

  • Clients disconnecting from WiFi

    symptoms:
    Client shows associated but client does not connect.
    Also, network will show up in "Available Networks" and then disappears.
    Only affecting some computers. All same make and model.
    Controller did show a reboot yesterday at 9:00am for no apparerent reason.
    Config was not lost so, MACs are still entered.
    Connecting clients can disconnect and reconnect - ruling out DHCP.

    Patrick if you are having WLC reboots it is a good idea to open a tac case here so we can check for any crash files.
    with regards to the client not connecting / debug client from the wlc cli will help out to isolate what is going on.
    ssh / telnet to wlc
    debug client xx:xx:xx:xx:xx:xx
    log to a text file
    reproduce the problem
    and paste
    thanks
    Serge

  • Clients disconnected from AP, Sending station has left the BSS

    Issue Experienced
    Clients randomly disconnects average time before disconnect is 15 minutes
    Current AP running config
    Current configuration : 2449 bytes
    ! Last configuration change at 16:49:26 UTC Mon Feb 24 2014
    version 15.2
    no service pad
    service timestamps debug datetime msec
    service timestamps log datetime msec
    service password-encryption
    hostname BE-AP4
    logging rate-limit console 9
    enable secret 5 secret
    no aaa new-model
    no ip cef
    dot11 syslog
    dot11 vlan-name Manufacturing vlan 15
    dot11 ssid BE-WAP1
       vlan 15
       authentication open
       authentication key-management wpa
       guest-mode
       wpa-psk ascii 7 password
    dot11 guest
    power inline negotiation injector override
    username admin privilege 15 password 7
    bridge irb
    interface Dot11Radio0
     no ip address
     no ip route-cache
     encryption mode ciphers tkip
     encryption vlan 15 mode ciphers tkip
     ssid BE-WAP1
     antenna gain 0
     antenna ab-antenna
     stbc
     speed  basic-1.0 basic-2.0 basic-5.5 basic-11.0 basic-6.0 basic-9.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0 m0. m1. m2. m3. m4. m5. m6. m7. m8. m9. m10. m11. m12. m13. m14. m15. m16. m17. m18. m19. m20. m21. m22. m23.
     channel 2442
     station-role root
    interface Dot11Radio0.15
     encapsulation dot1Q 15 native
     no ip route-cache
     bridge-group 1
     bridge-group 1 subscriber-loop-control
     bridge-group 1 spanning-disabled
     bridge-group 1 block-unknown-source
     no bridge-group 1 source-learning
     no bridge-group 1 unicast-flooding
    interface Dot11Radio1
     no ip address
     no ip route-cache
     shutdown
     antenna gain 0
     peakdetect
     dfs band 3 block
     channel dfs
     station-role root
     bridge-group 1
     bridge-group 1 subscriber-loop-control
     bridge-group 1 spanning-disabled
     bridge-group 1 block-unknown-source
     no bridge-group 1 source-learning
     no bridge-group 1 unicast-flooding
    interface GigabitEthernet0
     no ip address
     no ip route-cache
     duplex auto
     speed auto
    interface GigabitEthernet0.15
     encapsulation dot1Q 15 native
     no ip route-cache
     bridge-group 1
     bridge-group 1 spanning-disabled
     no bridge-group 1 source-learning
    interface BVI1
     ip address 192.168.15.68 255.255.255.0
     no ip route-cache
    ip default-gateway 192.168.15.254
    ip forward-protocol nd
    ip http server
    no ip http secure-server
    ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
    Log Output
    *Feb 24 15:39:30.226: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b464 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:39:44.446: %DOT11-6-ROAMED: Station 0017.23a9.b464 Roamed to 544a.00e1.e5c0
    *Feb 24 15:39:44.446: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b464 Reason: Sending station has left the BSS
    *Feb 24 15:39:53.154: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b474 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:39:57.670: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b464 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:40:08.602: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230b.9bdf Associated KEY_MGMT[WPA PSK]
    *Feb 24 15:40:49.662: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee2e Associated KEY_MGMT[WPA PSK]
    *Feb 24 15:41:19.318: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee16 Associated KEY_MGMT[WPA PSK]
    *Feb 24 15:43:31.622: %SYS-5-CONFIG_I: Configured from http by  on 192.168.1.97
    *Feb 24 15:43:31.622: %SYS-5-CONFIG_I: Configured from http by  on 192.168.1.97
    *Feb 24 15:43:31.622: %SYS-5-CONFIG_I: Configured from http by  on 192.168.1.97
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230a.ee16 
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230a.ee2e 
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230b.9bdf 
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b464 
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b474 
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b461 
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b470 
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.c1e8 
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 843a.4b55.1136 
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 843a.4b5e.cd44 
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 843a.4b55.12ec 
    *Feb 24 15:43:31.642: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
    *Feb 24 15:43:31.654: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Feb 24 15:43:32.642: %DOT11-4-DIVER2_USED: Interface Dot11Radio0, Mcs rates 16-23 disabled due to only two transmit or receive antennas enabled
    *Feb 24 15:43:32.654: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Feb 24 15:43:32.682: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
    *Feb 24 15:43:32.690: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
    *Feb 24 15:43:32.698: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Feb 24 15:43:33.726: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
    *Feb 24 15:43:33.746: %DOT11-4-MAXRETRIES: Packet to client 843a.4b5e.cd44 reached max retries, removing the client
    *Feb 24 15:43:33.766: %DOT11-4-MAXRETRIES: Packet to client 843a.4b55.12ec reached max retries, removing the client
    *Feb 24 15:43:34.726: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Feb 24 15:43:36.210: %SYS-5-CONFIG_I: Configured from http by  on 192.168.1.97
    *Feb 24 15:44:09.450: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 6c88.145d.0db8 Associated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:27.522: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 843a.4b5e.cd44 Associated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:27.526: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 843a.4b55.12ec Associated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:27.890: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230b.9bdf Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:28.614: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee16 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:28.842: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee6b Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:28.850: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.c1e8 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:28.862: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b470 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:28.866: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b461 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:29.102: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b464 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:29.110: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b474 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:29.350: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee2e Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:47:17.174: %DOT11-7-AUTH_FAILED: Station cc3a.6194.ec3c Authentication failed
    *Feb 24 15:48:32.938: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 15:48:38.150: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 15:49:11.446: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 15:49:23.094: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 15:49:56.018: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 843a.4b55.1136 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:50:44.850: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 15:50:52.198: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 15:50:58.106: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 15:51:44.738: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 15:51:50.150: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 15:51:58.738: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 15:55:27.622: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 843a.4b55.12ec Reason: Sending station has left the BSS
    *Feb 24 15:55:27.650: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 843a.4b55.12ec Associated KEY_MGMT[WPA PSK]
    *Feb 24 16:01:57.442: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b470 Reason: Sending station has left the BSS
    *Feb 24 16:05:48.854: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b461 Reason: Sending station has left the BSS
    *Feb 24 16:06:28.310: %DOT11-6-ASSOC: Interface Dot11Radio0, Station  f409.d8b0.313d Associated KEY_MGMT[WPA PSK]
    *Feb 24 16:06:50.414: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b464 Reason: Sending station has left the BSS
    *Feb 24 16:06:56.102: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b474 Reason: Sending station has left the BSS
    *Feb 24 16:08:13.282: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b461 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:08:13.914: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b474 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:08:15.870: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b464 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:08:28.066: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.c1e8 Reason: Sending station has left the BSS
    *Feb 24 16:08:34.610: %DOT11-6-ROAMED: Station 0017.230b.9bdf Roamed to 544a.00e1.ef70
    *Feb 24 16:08:34.610: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230b.9bdf Reason: Sending station has left the BSS
    *Feb 24 16:08:34.622: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b461 Reason: Sending station has left the BSS
    *Feb 24 16:08:34.934: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b474 Reason: Sending station has left the BSS
    *Feb 24 16:08:35.846: %DOT11-6-ROAMED: Station 0017.230a.ee6b Roamed to 00e1.6d4f.6090
    *Feb 24 16:08:35.846: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230a.ee6b Reason: Sending station has left the BSS
    *Feb 24 16:08:36.394: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b464 Reason: Sending station has left the BSS
    *Feb 24 16:08:36.398: %DOT11-4-MAXRETRIES: Packet to client 0017.23a9.b464 reached max retries, removing the client
    *Feb 24 16:08:37.426: %DOT11-6-ROAMED: Station 0017.230a.ee2e Roamed to 00e1.6d4f.6090
    *Feb 24 16:08:37.426: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230a.ee2e Reason: Sending station has left the BSS
    *Feb 24 16:08:57.994: %DOT11-6-ROAMED: Station 0017.230a.ee16 Roamed to 544a.00e1.e5c0
    *Feb 24 16:08:57.994: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230a.ee16 Reason: Sending station has left the BSS
    *Feb 24 16:10:00.562: %DOT11-7-AUTH_FAILED: Station cc3a.6194.ec3c Authentication failed
    *Feb 24 16:10:00.562: %DOT11-4-MAXRETRIES: Packet to client cc3a.6194.ec3c reached max retries, removing the client
    *Feb 24 16:12:41.694: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station f409.d8b0.313d Reason: Sending station has left the BSS
    *Feb 24 16:13:06.994: %DOT11-7-AUTH_FAILED: Station cc3a.6194.ec3c Authentication failed
    *Feb 24 16:13:47.870: %DOT11-6-ASSOC: Interface Dot11Radio0, Station  f409.d8b0.313d Associated KEY_MGMT[WPA PSK]
    *Feb 24 16:16:24.822: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 16:16:32.262: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 16:16:46.838: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 16:16:56.050: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 16:17:16.262: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 16:20:37.806: %DOT11-4-MAXRETRIES: Packet to client f409.d8b0.313d reached max retries, removing the client
    *Feb 24 16:20:37.806: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station f409.d8b0.313d Reason: Previous authentication no longer valid
    *Feb 24 16:20:37.810: %DOT11-4-MAXRETRIES: Packet to client f409.d8b0.313d reached max retries, removing the client
    *Feb 24 16:20:39.142: %DOT11-6-ASSOC: Interface Dot11Radio0, Station  f409.d8b0.313d Associated KEY_MGMT[WPA PSK]
    *Feb 24 16:21:40.406: %DOT11-6-ROAMED: Station f409.d8b0.313d Roamed to 544a.00e1.ef70
    *Feb 24 16:21:40.406: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station f409.d8b0.313d Reason: Sending station has left the BSS
    *Feb 24 16:25:45.006: %DOT11-7-AUTH_FAILED: Station f409.d8b0.313d Authentication failed
    *Feb 24 16:25:45.010: %DOT11-4-MAXRETRIES: Packet to client f409.d8b0.313d reached max retries, removing the client
    *Feb 24 16:31:32.954: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b474 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:31:33.654: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.c1e8 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:31:36.866: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee6b Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:31:38.538: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee2e Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:31:38.666: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b470 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:31:40.526: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee16 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:31:42.414: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230b.9bdf Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:31:51.362: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b461 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:31:53.554: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b464 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:44:45.258: %DOT11-6-ASSOC: Interface Dot11Radio0, Station  f409.d8b0.313d Associated KEY_MGMT[WPA PSK]
    *Feb 24 16:47:39.350: %DOT11-6-ROAMED: Station 6c88.145d.0db8 Roamed to 544a.00e1.ef70
    *Feb 24 16:47:39.350: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 6c88.145d.0db8 Reason: Sending station has left the BSS
    *Feb 24 16:49:26.394: %SYS-5-CONFIG_I: Configured from http by  on 192.168.1.97
    *Feb 24 16:49:26.394: %SYS-5-CONFIG_I: Configured from http by  on 192.168.1.97
    *Feb 24 16:49:26.398: %SYS-5-CONFIG_I: Configured from http by  on 192.168.1.97
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station f409.d8b0.313d 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b464 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b461 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230b.9bdf 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230a.ee16 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b470 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230a.ee2e 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230a.ee6b 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.c1e8 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b474 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 843a.4b55.12ec 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 843a.4b55.1136 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 843a.4b5e.cd44 
    *Feb 24 16:49:26.410: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
    *Feb 24 16:49:26.422: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Feb 24 16:49:27.414: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Feb 24 16:49:27.442: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
    *Feb 24 16:49:27.450: %DOT11-4-MAXRETRIES: Packet to client 843a.4b55.12ec reached max retries, removing the client
    *Feb 24 16:49:27.502: %DOT11-4-MAXRETRIES: Packet to client 0017.23a9.b464 reached max retries, removing the client
    *Feb 24 16:49:27.510: %DOT11-4-MAXRETRIES: Packet to client 0017.23a9.b470 reached max retries, removing the client
    *Feb 24 16:49:27.522: %DOT11-4-MAXRETRIES: Packet to client 0017.23a9.c1e8 reached max retries, removing the client
    *Feb 24 16:49:27.530: %DOT11-4-MAXRETRIES: Packet to client 0017.23a9.b461 reached max retries, removing the client
    *Feb 24 16:49:27.530: %DOT11-4-MAXRETRIES: Packet to client 0017.23a9.b474 reached max retries, removing the client
    *Feb 24 16:49:27.594: %DOT11-4-MAXRETRIES: Packet to client 0017.230a.ee2e reached max retries, removing the client
    *Feb 24 16:49:28.134: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230b.9bdf Associated KEY_MGMT[WPA PSK]
    *Feb 24 16:49:28.442: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Feb 24 16:49:29.806: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee2e Associated KEY_MGMT[WPA PSK]
    *Feb 24 16:49:35.038: %DOT11-6-ASSOC: Interface Dot11Radio0, Station  f409.d8b0.313d Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:49:37.294: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee16 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:49:37.418: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee6b Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:49:41.622: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.c1e8 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:49:41.642: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b474 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:49:41.726: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b461 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:49:42.522: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b470 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:49:42.886: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b464 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:49:57.310: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 6c88.145d.0db8 Associated KEY_MGMT[WPA PSK]
    *Feb 24 16:50:02.818: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station f409.d8b0.313d Reason: Sending station has left the BSS
    *Feb 24 16:50:06.014: %DOT11-6-ASSOC: Interface Dot11Radio0, Station  f409.d8b0.313d Associated KEY_MGMT[WPA PSK]
    *Feb 24 16:52:37.670: %DOT11-7-AUTH_FAILED: Station 9018.7cb5.01f5 Authentication failed
    *Feb 24 16:57:13.026: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b474 Reason: Sending station has left the BSS
    *Feb 24 16:57:13.034: %DOT11-4-MAXRETRIES: Packet to client 0017.23a9.b474 reached max retries, removing the client
    *Feb 24 16:58:37.262: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b464 Reason: Sending station has left the BSS
    *Feb 24 16:58:43.302: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b461 Reason: Sending station has left the BSS
    *Feb 24 16:58:46.710: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.c1e8 Reason: Sending station has left the BSS
    *Feb 24 16:58:48.338: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b470 Reason: Sending station has left the BSS
    *Feb 24 17:02:27.078: %DOT11-7-AUTH_FAILED: Station 9018.7cb5.01f5 Authentication failed
    *Feb 24 17:04:45.486: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 843a.4b55.12ec Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 17:04:46.514: %DOT11-7-AUTH_FAILED: Station 9018.7cb5.01f5 Authentication failed
    *Feb 24 17:19:47.858: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 6c88.145d.0db8 Reason: Sending station has left the BSS
    *Feb 24 17:19:59.694: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.c1e8 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 17:25:36.682: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b470 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 17:26:40.910: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b470 Reason: Sending station has left the BSS
    *Feb 24 17:27:01.002: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b470 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 17:27:27.390: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b470 Reason: Sending station has left the BSS
    *Feb 24 17:27:47.626: %DOT11-4-MAXRETRIES: Packet to client f409.d8b0.313d reached max retries, removing the client
    *Feb 24 17:27:47.626: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station f409.d8b0.313d Reason: Previous authentication no longer valid
    *Feb 24 17:27:47.630: %DOT11-4-MAXRETRIES: Packet to client f409.d8b0.313d reached max retries, removing the client
    *Feb 24 17:31:49.458: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.c1e8 Reason: Sending station has left the BSS
    *Feb 24 17:32:53.530: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 843a.4b55.12ec Reason: Sending station has left the BSS
    *Feb 24 17:40:59.858: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.c1e8 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 18:08:22.578: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.c1e8 Reason: Sending station has left the BSS
    *Feb 24 18:36:31.482: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230b.9bdf Reason: Previous authentication no longer valid
    *Feb 24 18:57:16.774: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b470 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 18:57:25.642: %DOT11-7-AUTH_FAILED: Station f409.d8b0.313d Authentication failed
    *Feb 24 18:57:38.958: %DOT11-6-ASSOC: Interface Dot11Radio0, Station  f409.d8b0.313d Associated KEY_MGMT[WPA PSK]
    *Feb 24 18:59:28.442: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 6c88.145d.0db8 Associated KEY_MGMT[WPA PSK]
    *Feb 24 19:23:40.450: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b470 Reason: Sending station has left the BSS
    *Feb 24 19:40:30.433: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 6c88.145d.0db8 Reason: Sending station has left the BSS
    *Feb 24 19:40:30.449: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 6c88.145d.0db8 Associated KEY_MGMT[WPA PSK]
    *Feb 24 19:45:30.009: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 6c88.145d.0db8 Reason: Sending station has left the BSS
    *Feb 24 19:45:38.109: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 6c88.145d.0db8 Associated KEY_MGMT[WPA PSK]
    *Feb 24 19:48:41.953: %DOT11-4-MAXRETRIES: Packet to client 6c88.145d.0db8 reached max retries, removing the client
    *Feb 24 19:48:41.953: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 6c88.145d.0db8 Reason: Previous authentication no longer valid
    *Feb 24 19:48:42.029: %DOT11-4-MAXRETRIES: Packet to client 6c88.145d.0db8 reached max retries, removing the client
    *Feb 24 19:48:45.305: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 6c88.145d.0db8 Associated KEY_MGMT[WPA PSK]
    *Feb 24 19:52:20.877: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
    *Feb 24 19:52:21.877: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
    *Feb 24 19:52:30.957: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
    *Feb 24 19:52:31.957: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
    *Feb 24 19:57:43.173: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 6c88.145d.0db8 Reason: Sending station has left the BSS
    *Feb 24 20:00:09.885: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b433 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:01:08.445: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b465 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:01:25.453: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b453 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:01:47.549: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b449 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:02:07.469: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b456 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:02:23.713: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b5da Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:02:45.761: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b466 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:02:53.133: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b449 Reason: Sending station has left the BSS
    *Feb 24 20:02:57.913: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b456 Reason: Sending station has left the BSS
    *Feb 24 20:03:14.521: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b5db Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:03:24.673: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b466 Reason: Sending station has left the BSS
    *Feb 24 20:03:29.653: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b453 Reason: Sending station has left the BSS
    *Feb 24 20:03:39.125: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b458 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:03:49.093: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b5da Reason: Sending station has left the BSS
    *Feb 24 20:03:51.113: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b5d7 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:03:52.549: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b5da Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:03:54.905: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b433 Reason: Sending station has left the BSS
    *Feb 24 20:04:12.565: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b458 Reason: Sending station has left the BSS
    *Feb 24 20:04:19.213: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b5db Reason: Sending station has left the BSS
    *Feb 24 20:04:22.865: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b465 Reason: Sending station has left the BSS
    *Feb 24 20:04:24.965: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b465 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:04:26.341: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b433 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:04:27.089: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b5d7 Reason: Sending station has left the BSS
    *Feb 24 20:05:29.437: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b5d7 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:06:46.761: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b470 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:06:50.233: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b474 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:07:03.725: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b461 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:07:52.513: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230a.ee16 Reason: Previous authentication no longer valid
    *Feb 24 20:08:09.513: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230a.ee6b Reason: Previous authentication no longer valid
    *Feb 24 20:08:40.685: %DOT11-6-ROAMED: Station f409.d8b0.313d Roamed to 2c3e.cf54.f590
    *Feb 24 20:08:40.685: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station f409.d8b0.313d Reason: Sending station has left the BSS
    *Feb 24 20:09:40.053: %DOT11-7-AUTH_FAILED: Station f409.d8b0.313d Authentication failed
    *Feb 24 20:31:25.833: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b433 Reason: Sending station has left the BSS
    *Feb 24 20:31:29.373: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b5d7 Reason: Sending station has left the BSS
    *Feb 24 20:31:52.053: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b5da Reason: Sending station has left the BSS
    *Feb 24 20:32:29.245: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b465 Reason: Sending station has left the BSS
    *Feb 24 20:33:46.221: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b470 Reason: Sending station has left the BSS
    *Feb 24 20:33:49.717: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b474 Reason: Sending station has left the BSS
    *Feb 24 20:34:03.213: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b461 Reason: Sending station has left the BSS

    Hi
    if you want to get any higher data rates (802.11n) you have to configure WPA2/AES & not TKIP
    dot11 ssid BE-WAP1
       vlan 15
       authentication open
       authentication key-management wpa version 2
       guest-mode
       wpa-psk ascii 7 password
    interface Dot11Radio0
     encryption vlan 15 mode ciphers aes-ccm
     no encryption vlan 15 mode ciphers tkip
     ssid BE-WAP1
    Also enable 5GHz band as well. Then see if the problem occurs for both bands
    interface Dot11Radio1
     encryption vlan 15 mode ciphers aes-ccm
     ssid BE-WAP1
     channel width 40-above
     no shut
    interface Dot11Radio0.15
     encapsulation dot1Q 15 native
     bridge-group 1
    HTH
    Rasika
    **** Pls rate all useful responses ****

  • 'Unknown Error' when trying to save files from CS under Leopard

    We recently upgraded to Leopard, and reinstalled our CS apps. Photoshop and InDesign work fine. Illustrator, however gives us an 'An Unknown Error has Occurred' when trying to save any file. After dismissing the alert, a window pops up, informing us that, 'Can't save preview, but all other information was saved successfully. The file couldn't be found. ID=-43.' This happens when trying to save a new file, or an existing file, when saving with PDF preview is checked, or unchecked. Does anyone know how to fix this?

    I deleted preferences on both machines. The Intel seems to be cured. All file formats save, printing, and importing are functioning normally.
    The G5 however is only modestly improved. I can now at least create and save files. Printing also functions. However if I attempt to use the template dialog box or to import (place) a file the dialogs crash the application.
    My suspect is a corrupt font, but until I have time to track down which one it is, I'll have to limp along as is...

  • How can I recover my Notes from mail in Leopard after updating to Mountain Lion?

    I had Snow Leoppard and I used to save so many notes in "mail". When I switched to Mountain Lion, it seems all notes are disappeared. I can get the notes from my iphone and ipad, but not the ones in my "mail". I appreciate if you help me, since those notes were crucial for me.
    Best,
    P.S.

    Hi,
    See this Excellent Link by Pondini on TM:
    http://web.me.com/pondini/AppleTips/Index.html
    May be Helpful...

  • How can I exclude client IP address from access log using WebServer 6.0? WebServer 3.x has Do not log client accesses from: option under Log Preferences". But I cant find it when we upgrade to 6.0

     

    Hi,
    Please go through the below link.
    http://docs.iplanet.com/docs/manuals/enterprise/60sp1/ag/esmonsvr.htm#18110
    I hope this helps. If you need any help let me know.
    Regards,
    Dakshin.
    Developer Technical Support
    Sun Microsystems
    http://www.sun.com/developers/support.

Maybe you are looking for