Feb 9, 2016
Recorded "Live" on February 2, 2016
- Enjoy Command Control Power and want more
commercial free programs?
Please visit our Patreon Page where you can support Command Control Power and help us bring you more commercial free programming.
Thanks to all our Contributors.
- Joe and Jerry casually discuss the difficulties of converting a client from break fix to managed service.
- Jerry discusses a clients Macbook Pro black screen and restart
issue with no resolution:
Joe shares a similiar but different recurring problem
- Sam talks about the frustration of supportung clients running PC’s and providing support.
- Joe mentions a MacBook Pro 15-inch going unresponsive: black screen, not reachable by ARD, no response to keystrokes, close lid get steady white LED instead of sleep indicator, no response to command-control-power, must force power down and then power on. Seems to have been fixed by turning off automatic graphics switching.
-Jerry endorses the MacObserver's
MacGeekGab Podcast and shares a listener feedback
Record Your iOS Device Screen with QuickTime Playerhttp://www.techradar.com/us/how-to/computing/apple/easy-mac-hacks-record-your-ios-device-screen-with-quicktime-player-1305708
- Joe buys a static IP from Verizon Wireless and configures it in the Cradlepoint IBR350L-VZ router with built-in modem. A firmware update from Cradlepoint removed the IP Passthrough option, but the IBR650 has the option. Thanks to 3Gstore.com for the info!
- Jerry revisits his ongoing client SonicWall issue and finds a fix:
I am glad to hear that the issue looks to resolved. When we are connecting dumb switch between SonicWall and the upstream modem, it will help in the negotiation. The Ethernet Settings section allows you to manage the Ethernet settings of links connected to the SonicWALL. Auto Negotiate is selected by default as the Link Speed because the Ethernet links automatically negotiate the speed and duplex mode of the Ethernet connection Link Negotiation is basically forced by the ISP and when we select "Auto Negotiate" on X1 interface then the same speed is forced on the Sonicwall's X1 interface. Link Negotiation Could be basically "Full Duplex" and "Half Duplex" but whenever we setup a Sonicwall we recommend to the customer to select "Auto Negotiate" and not "Full Duplex" or "Half Duplex" because auto-negotiation is simply the method used by two devices to achieve the best rate possible of transmission. It allows them to discuss in a sense, the possible rates of transmission, then pick the best one that they both share. They do this by swapping advertisements of their own abilities using pulses called Fast Link Pulses (FLPs). The FLP lets one link partner know what the other is capable of. As they swap FLPs, the two stations detect the highest common denominator between them, according to the following: 1000BASE-T 100BASE-T2 Full Duplex 100BASE-TX Full Duplex 100BASE-T2 100BASE-T4 100BASE-TX 10BASE-T Full Duplex 10BASE-T
Switch works on full duplex. SonicWALL autonegotiates with Switch( Since switch is full duplex, so would be SonicWALL) . Now Switch tries to negotiate with the ISP connection( which may be set to autonegotiate (full or half duplex), so switch negotiates the connection with ISP side and sonicwall. From the IEEE standard: All 1000BASE-T PHYs shall provide support for Auto-Negotiation and shall be capable of operating as MASTER or SLAVE.Auto-Negotiation is performed as part of the initial set-up of the link, an allows the PHYs at each end to advertise their capabilities (speed, PHY type, half or full duplex) and to automatically select the operating mode for communication on the link. Auto-negotiation signaling is used for the following two primary purposes for 1000BASE-T: The SLAVE PHY uses loop timing where the clock is recovered from the received data stream. “The switch is configured to autodetect the speed and duplex settings on an interface. However, there are several things that can cause the autonegotiation process to fail, resulting in either speed or duplex mismatches (and performance issues). The rule of thumb for key infrastructure is to manually hard-code the speed and duplex on each interface so there is no chance for error. “
- Joe recounts an ongoing issue with a current Time Capsule losing broadband access.
- Joe discusses an issue with remote access to his Server and
missing certificates which led to his discovery of Apple plugging a
Apple removed Keychain First Aid in 10.11.2 to plug a security hole. Prior to that, Apple "disabled synthetic clicks for keychain access windows" to plug a security hole in to 10.11.1. Joe experiences some fallout: when you try to export a certificate from the keychain, upon entering the password for the login keychain and clicking "Allow" or "Always Allow", it doesn't work. The dialog box just stays on screen. The only way to dismiss it is "Deny" which of course prevents the successful export of the certificate in question. Same problem when trying to use Certificate Assistant in Server.app to Create a Certificate Identity, e.g. to create a new Self-Signed Certificate. Certificate Assistant completes, and the new certificate and private key are added to the user's login keychain, but Server.app fails to export the certificate to /etc/certificates. Solution: disconnect your ARD session and use a local display, keyboard, and mouse!
and last week's Command Control Power!
Geargrip Lite CPU Holder