Re: Screen Sharing/Firewall Catastrophe: HELP! New Status… All MIGHT be well!

Hendrik van Eeden hvaneeden at comcast.net
Wed Oct 30 11:36:21 EDT 2013


To be absolutely clear, I NEVER had any problems with any units or execution  of script in Xtension during this whole episode.  ONLY that the screen sharing did not work.  All of this after an electrical power glitch.

Henk



On Oct 30, 2013, at 11:28 AM, George Handley wrote:

> Dear Tom and James & Henk,
> 
> Thank you so much for pointing out I can ignore the Disk Utility warning about: "Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAgent” has been modified and will not be repaired."
> 
> I completely read both of the Apple Support Forum urls you both sent, and there is no question this is quite misleading, but again,,, to be ignored.
> 
> Further I read several times that if Disk Utility ends by saying "Permissions repair complete," all is really well? As stated in my original post. I have run DU several times, including this morning, and while I now know that I need to ignore the SUID warning, page after page scroll by stating that it found hundreds of other incorrect permissions, BUT NOW HAVE BEEN (Past tense) repaired.
> 
> I pasted a snippet of the very last of the DU Repair Permissions report this AM, and you can see that it is consistently telling me that the Permissions Repair was complete, Yet if I either run it again, or even reboot and run it again, it keeps finding all these same incorrect permissions that say it repaired the last time. Also note DU is NOT reporting a change in location of the permission, it's reporting that it found AND FIXED all the permissions.
> 
> Repaired “Applications/iTunes.app/Contents/Resources/zh_TW.lproj/UniversalAccess.nib”
> Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAgent” has been modified and will not be repaired.
> Permissions differ on “Applications/Safari.app/Contents/Resources/Dutch.lproj/BookmarkTitleChange.nib”; should be drwxr-xr-x ; they are -rwxr-xr-x .
> Repaired “Applications/Safari.app/Contents/Resources/Dutch.lproj/BookmarkTitleChange.nib”
> Permissions differ on “Applications/Safari.app/Contents/Resources/English.lproj/BookmarkTitleChange.nib”; should be drwxr-xr-x ; they are -rwxr-xr-x .
> Repaired “Applications/Safari.app/Contents/Resources/English.lproj/BookmarkTitleChange.nib”
> Permissions differ on “Applications/Safari.app/Contents/Resources/Japanese.lproj/BookmarkTitleChange.nib”; should be drwxr-xr-x ; they are -rwxr-xr-x .
> Repaired “Applications/Safari.app/Contents/Resources/Japanese.lproj/BookmarkTitleChange.nib”
> Permissions differ on “Applications/Safari.app/Contents/Resources/da.lproj/BookmarkTitleChange.nib”; should be drwxr-xr-x ; they are -rwxr-xr-x .
> Repaired “Applications/Safari.app/Contents/Resources/da.lproj/BookmarkTitleChange.nib”
> Permissions differ on “Applications/Safari.app/Contents/Resources/pt.lproj/BookmarkTitleChange.nib”; should be drwxr-xr-x ; they are -rwxr-xr-x .
> Repaired “Applications/Safari.app/Contents/Resources/pt.lproj/BookmarkTitleChange.nib”
> Permissions differ on “Applications/Safari.app/Contents/Resources/uk.lproj/BookmarkTitleChange.nib”; should be drwxr-xr-x ; they are -rwxr-xr-x .
> Repaired “Applications/Safari.app/Contents/Resources/uk.lproj/BookmarkTitleChange.nib”
> 
> Permissions repair complete
> 
> Now to James' questions.
> 
> First, everyone needs to know a new, an equally dumbfounding fact. After I gave up last night about 1 AM, and turned off my iMac, (Not the Mini running now only parts of the house) I finally went to bed around 2 AM, and discovered upon my entry into our master bath, and due to it's PIR that turns on three units all set to the same address, but both phases, all the lights worked!!!!!!!!!!!!!!!!!!!!!!!! I couldn't believe it.
> 
> I went back into the kitchen and tested all the other things included in scripts that I previously discovered last night didn't work, and they now did work again! I DIDN'T DO ANYTHING!
> 
> James, I only use a CM11A interface, but also have several Weeder and MaxSonar interfaces as you know. The non-working units in question, are not even on the same phase, but indeed on both phases, and all controlled by the CM11A X10 interface.
> 
> RE: "If you’re going to use a firewall then you need to specifically allow local connections to XTension on port 20300, or just clear the app for all ports." 
> 
> I am not using the Mini's ML firewall, but the discussion yesterday caused me to look at my own Mini, and like Henk, discovered it was off, which alarmed me. There is no specific provision to "clear all the ports." Specifically it states:
> 
> <For James.jpg>
> 
> RE: "If you turned on and off the firewall it’s possible that XTensions comm got blocked and hung itself up. Are those units that don’t respond on a specific interface separate from the others? Each interface makes it’s own internal connection and might have been dropped. But then after a restart that should all be back to normal. If the firewall rules have stuck even though you’ve turned it on then you may need to look up how to clear those rules manually."
> 
> All I can tell you so far is that I am only using one interface, the CM11A. I have about 170+ units that 86 of which are assigned the CM11A. Further, of the 7 specific units I identified not working last night, while they are on the same X10 CM11A interface, however they share electricity from both phases.
> 
> Now James and Michael, I have to further explain, that some of the seven units that failed last night, have given me trouble (Individually) before, and I've fought like hell to correct them inside of XTension, but this is a whole new ball game, when select units within XTension are flaky and most aren't, and I did NOTHING inside of XTension to cause this.
> 
> Just like Henk just reported, he doesn't know what caused this, OR HOW HE CORRECTED THIS, but his is fixed as well.
> 
> I don't know how many times in the past I have fought some of these specific units, and suspected it was something outside of XTension, but both you and Michael said that was impossible. Well, now I do know there IS a connection, and I, and I'm sure everyone else on this List, would love to understand this interaction to avoid wasting HOURS of fruitless time within XTension to try to correct this kind of phenomena.
> 
> Tis a true puzzlement!
> 
> Thanks,
> 
> George
> 
> 
> 
>  
> 
> _______________________________________________
> XTensionList mailing list
> XTensionList at shed.com
> http://shed.com/mailman/listinfo/xtensionlist

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shed.com/pipermail/xtensionlist/attachments/20131030/795577b4/attachment-0001.html>


More information about the XTensionList mailing list