03-28-2015, 09:39 PM
So today I logged in again, found out that mach_kernel was visible and I was able to set it invisible. All cool.
to troubleshoot an issue with FaceTime, I asked him to plug in the external hard drive (one partition is time machine, the other partition is the clone of his internal drive). I rebooted from the clone. Dropbox didn't work (I heard that is normal). Teamviewer worked, but there were a couple of weir issues. One for example was that when I clicked on System Preferences in the dock, instead of System Preferences opening, like expected, Finder opened and took me to the System Preferences application, and I was able to open that by clicking on it, but I was not allowed to type anything. It turned out to be a glitch in Teamviewer, I quick team viewer on my side, made a new connection and then everything worked as expected, I was able to launch System Prefe straight from the dock, I was able to enter password, and reboot from his internal drive.
So far so good.
I rebooted, logged in again with TeamViewer, and called him on FaceTime. I also sent him a message. Both iMessages and FaceTime reacted to the incoming signals, but they asked him to type in the password. This never happened before.
I typed in the password in iMessages and then faceTime seemed OK, didn't keep asking for password. I was still not able to call him, but he can call me.
Now after a few back and forth calls, it was getting late over there (6 hours ahead of US), and I was also running late so I didn't have much time to troubleshoot. I called him from iPhone later on, his FaceTime didn't react. I sent him a messages, was delivered and read. He told me (via iMessages) that his FaceTime does not show anything when I call him. He was able to call me. So his faceTime is able to make calls, but does not receive calls.
I will try another remote session tomorrow (he has more issues with the printer) and I would like to understand why his FaceTime does not receive calls, as this is a mission critical application for us. I think I may need to log him out of his Apple account and log him in again. Or any other ideas what I can try?
Thanks
to troubleshoot an issue with FaceTime, I asked him to plug in the external hard drive (one partition is time machine, the other partition is the clone of his internal drive). I rebooted from the clone. Dropbox didn't work (I heard that is normal). Teamviewer worked, but there were a couple of weir issues. One for example was that when I clicked on System Preferences in the dock, instead of System Preferences opening, like expected, Finder opened and took me to the System Preferences application, and I was able to open that by clicking on it, but I was not allowed to type anything. It turned out to be a glitch in Teamviewer, I quick team viewer on my side, made a new connection and then everything worked as expected, I was able to launch System Prefe straight from the dock, I was able to enter password, and reboot from his internal drive.
So far so good.
I rebooted, logged in again with TeamViewer, and called him on FaceTime. I also sent him a message. Both iMessages and FaceTime reacted to the incoming signals, but they asked him to type in the password. This never happened before.
I typed in the password in iMessages and then faceTime seemed OK, didn't keep asking for password. I was still not able to call him, but he can call me.
Now after a few back and forth calls, it was getting late over there (6 hours ahead of US), and I was also running late so I didn't have much time to troubleshoot. I called him from iPhone later on, his FaceTime didn't react. I sent him a messages, was delivered and read. He told me (via iMessages) that his FaceTime does not show anything when I call him. He was able to call me. So his faceTime is able to make calls, but does not receive calls.
I will try another remote session tomorrow (he has more issues with the printer) and I would like to understand why his FaceTime does not receive calls, as this is a mission critical application for us. I think I may need to log him out of his Apple account and log him in again. Or any other ideas what I can try?
Thanks