Screen Sharing debug

I was wondering if there is a log file for screen sharing, or how I can enable debugging?
I am trying to connect using a VNC client, this works on my internal netowrk but I cannot get access from outside despite adding the correct port forwarding rules. I have tested this with a Windows based VNC server on my network so can confirm it is not an issue with the router.
When I connect from outside I get the password prompt, enter tha password, the connection starts to negotiate (momentary blue VNC display) and then the connection drops. Being able to enable logging would probable help me resolve this in a matter of minutes.
I could just install a clean VNC server on the Mac but don't really want to do that seeing as there is already one built-in.
Thanks,

I too am having this problem recently... I switched from Static IPs to DHCP at the house... I noticed it starting then, but we also had a bunch of machines move, and added machines to the network, AND upgraded some machines to newer operating systems... so... I'm having trouble isolating the issue.
I get the EXACT same bug as you! But I also got this:
4/16/10 11:09:48 AM [0x0-0x2f02f].com.apple.ScreenSharing[383] Screen Sharing: OpenScripting.framework - scripting addition "/Library/ScriptingAdditions/Adobe Unit Types.osax" declares no loadable handlers.
So I moved both of those files mentioned above... and it still didn't work...
I am also at a loss.

Similar Messages

Screen Sharing and ARD broken

Hi,
I have 10.9.4. I had remote management switched on and it was working fine.
I installed ARD 3.7 and started it up fine and it was running fine allowing me to do all what I needed.
I also need to remote to this Mac and so set the preference in ARD to allow control whilst the app was running. Thats when it went pear shaped.
It suddenly stopped allowing remote access to the machine.
I now have to be physically at the unit. I have removed ARD and all the files it has added and switched off all screen sharing and Remote Management in Sys Pref. Restarted and switched on Remote Management again.
I can still not access the machine remotely (i.e. screen sharing).
When trying to use screen sharing on the Mac itself to remote onto another machine I get the following in Console.
20/08/2014 15:08:23.459 Screen Sharing[1422]: unable to get server port
20/08/2014 15:08:23.459 Screen Sharing[1422]: *** -[__NSSetM addObject:]: object cannot be nil
20/08/2014 15:08:23.537 Screen Sharing[1422]: (
0   CoreFoundation                      0x00007fff93cd525c __exceptionPreprocess + 172
1   libobjc.A.dylib                     0x00007fff94276e75 objc_exception_throw + 43
2   CoreFoundation                      0x00007fff93bf4966 -[__NSSetM addObject:] + 790
3   ScreenSharing                       0x00007fff91f3a0e2 -[SSInputEventSourceCoordinator addSource:] + 69
4   CoreFoundation                      0x00007fff93ca3e0c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
5   CoreFoundation                      0x00007fff93b9782d _CFXNotificationPost + 2893
6   Foundation                          0x00007fff905277ba -[NSNotificationCenter postNotificationName:object:userInfo:] + 68
7   AppKit                              0x00007fff96fb1cde -[NSApplication finishLaunching] + 440
8   AppKit                              0x00007fff96fb17f3 -[NSApplication run] + 128
9   AppKit                              0x00007fff96f9c783 NSApplicationMain + 940
10 libdyld.dylib                       0x00007fff8f5b55fd start + 1
20/08/2014 15:08:23.622 Screen Sharing[1422]: *** -[NSLock lock]: deadlock (<NSLock: 0x6000000ca330> '(null)')
20/08/2014 15:08:23.622 Screen Sharing[1422]: *** Break on _NSLockError() to debug.
I can ssh to the machine fine, just not screen share (VNC).
Any help to fix allowing VNC to the machine would be greatly appreciated.
Regards
Keith

Further,
I have run a port scan and confirmed that port 5900 is open.
When using COTVNC it sort of sits there trying to connect but doesn't show the screen. If whilst it is trying I switch off Remote Management then COTVNC instantly throws up the error that screen sharing is not enabled.
Thus I am deducing that the actual VNC server of the os is goosed.

Screen Sharing / vnc with OS X 10.5.6 fails

I can not get the Screen Sharing that comes with OS X 10.5.6 to work with any vnc client. The server is my laptop, an MBP 2.4 GHz Intel running OS X 10.5.6.
*I enable Screen Sharing by doing the following:*
1) +System Preferences > Sharing > Screen Sharing+ is checked
2) +System Preferences > Sharing > Screen Sharing > Computer Settings > Anyone may request permission to control screen+ is checked
3) +System Preferences > Sharing > Screen Sharing > Computer Settings > VNC viewers may control screen with password+ is checked and I've entered a password
4) I also have Remote Login enabled for SSH access, but no other services are enabled.
*I see two different behaviors depending on one of two clients that I try using:*
1) +Chicken of the VNC v2.0b4+ running on same machine- Always says "Connection Terminated / Authentication Failed" without ever asking for a password. Logs the following in system.log (dates, hostnames and pids removed):
Chicken of the VNC: Server reports Version RFB 003.889
Chicken of the VNC: Bogus RFB Protocol Version Number from AppleRemoteDesktop, switching to protocol 003.007
I believe that the information in system.log is OK, and is just warning me that Chicken of the VNC is working around Apple's strange protocol version.
2) +TightVNC 1.3.9 on Windows XP sp2+- Says "Security type requested", then asks for a password. I enter it, click OK and tightvnc simply waits endlessly.
*Other Notes:*
1) I have tried configuring and starting the server using kickstart from the command line as suggested at http://support.apple.com/kb/HT2370 (+sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/k ickstart -activate -configure -access -on -restart -agent -privs -all+)
2) I have tried unchecking +VNC viewers may control screen with password+, but in this case Chicken of the VNC says "Please configure Apple Remote Desktop to allow VNC Viewers to control the screen. Unknown authType 30,31,32" and TightVNC says "Server did not offer supported security type!"
3) If I disable the Screen Sharing feature that comes out of the box with OS X, I CAN install and successfully run the OSXVnc server available at http://sourceforge.net/projects/osxvnc/. In this case, both Chicken of the VNC and TightVNC are able to connect.
*So Apple's Screen Sharing does not work. Does anyone know what the problem is? Are there any log files I can look at, or is there another way I can debug this? I'm not impressed. :)*

Thanks for the suggestion. It was possible that one of these files had become corrupted, so I tried moving each of these files to another directory but unfortunately I'm still seeing the same behavior.
Here's what happens with each of these files individually after they're moved:
1) When I set the VNC password in the system prefs, com.apple.VNCSettings.txt gets re-created (with the same contents as the original unless I change the password, so that just looks like a hash of the password).
2) com.apple.RemoteManagement.plist also gets recreated when I change the system prefs. If I use "sudo plutil -convert xml1 com.apple.RemoteManagement.plist" I get the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>ARD_AllLocalUsers</key>
<true/>
<key>ARD_AllLocalUsersPrivs</key>
<integer>2</integer>
<key>ScreenSharingReqPermEnabled</key>
<true/>
<key>VNCLegacyConnectionsEnabled</key>
<true/>
</dict>
</plist>
3) For me, com.apple.RemoteDesktop.plist does not exist.
4) Interestingly, com.apple.ARDAgent.plist does not get created until I run "sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/k ickstart -activate -configure -access -on -restart -agent -privs -all". Its XML contents are as follows:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>AdminConnectInfoList</key>
<dict/>
<key>AgentLogLevel</key>
<integer>3</integer>
<key>ServerConnectInfoList</key>
<dict/>
<key>Version</key>
<real>3</real>
</dict>
</plist>
Looking at this, I tried setting ScreenSharingReqPermEnabled to false, but that didn't help. Then I increased AgentLogLevel to 100 and got a lot of output in system.log (12:28:45 is when I restart the server and 12:29:34 is when I try to connect):
Feb 24 12:28:45 ARDAgent [749]: ******ARDAgent Launched******
Feb 24 12:28:45 ARDAgent [749]: got a sessionDict, onConsoleRef is 0xa04cd400
Feb 24 12:28:45 ARDAgent [749]: grUserOnConsole is 1
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 122
Feb 24 12:28:45 ARDAgent [749]: LoadMenuExtra: Attempting to unload menu extra
Feb 24 12:28:45 ARDAgent [749]: PostNotificationForced: Going to send notifation value 9
Feb 24 12:28:45 ARDAgent [749]: UpdatePrefs: versionFlt : 0.000000 kCurrentPrefsVersion : 3.000000
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 44
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 22
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 100
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 94
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 96
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 18
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 106
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 74
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 130
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 60
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 45
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 65
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 66
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 105
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 115
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 38
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 12
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 61
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 20
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 62
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 39
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 30
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 101
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 53
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 103
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 107
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 109
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 135
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 41
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 110
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 111
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 28
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 36
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 48
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 59
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 57
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 116
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 58
Feb 24 12:28:45 ARDAgent [749]: InitAppUsageHandlers: Called gTrackingDays is set to 0
Feb 24 12:28:45 ARDAgent [749]: CheckRFBServerPIDFile: return 679
Feb 24 12:28:45 ARDAgent [749]: RemoteCommandListenerThread init communications
Feb 24 12:28:45 ARDAgent [749]: RFBServerStart - did not kill 679
Feb 24 12:28:45 ARDAgent [749]: DOCStartDOC: No serial number. Task Server not started.
Feb 24 12:28:45 ARDAgent [749]: DT_InitLocalProcessing: Loading existing tasks from disk.
Feb 24 12:28:45 ARDAgent [749]: DT_InitLocalProcessing: Found 0 tasks
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 158
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 117
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 118
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 162
Feb 24 12:28:45 ARDAgent [749]: ARD Agent: RFB Server exited quickly after starting - probable failure.
Feb 24 12:28:45 ARDAgent [749]: PostNotificationForced: Going to send notifation value 6
Feb 24 12:28:45 ARDAgent [749]: PostNotificationForced: Setting lastNotification to value 6
Feb 24 12:28:45 ARDAgent [749]: ******ARDAgent Ready******
Feb 24 12:29:34 Chicken of the VNC[693]: Server reports Version RFB 003.889
Feb 24 12:29:34 Chicken of the VNC[693]: Bogus RFB Protocol Version Number from AppleRemoteDesktop, switching to protocol 003.007
Feb 24 12:29:36 ARDAgent [749]: PostNotificationForced: Going to send notifation value 1
Feb 24 12:29:36 ARDAgent [749]: PostNotificationForced: Got request for kCurrentStateNotification. Sending value 6
Interesting that it says "ARD Agent: RFB Server exited quickly after starting - probable failure." That doesn't sound too good.
I will try to watch fs_usage more closely to see what else gets modified and accessed, but I'm increasingly suspicious that there's simply a bug which is showing up under whatever specific conditions I have on my machine. Perhaps the included log info will trigger an idea for someone.

Screen sharing works from home to work but can't type shifted characters

hi
i can successfully connect to from my home (using macbook or macmini) to my work mac using screen sharing but it seems that i can't type shifted characters like
@ or _
i can type these characters using screen sharing within the network at work so. any reason why this might be?
best wishes
max

I'm having exactly the same keyboard issue. Certainly nothing has ever enhanced my concentration while coding like suddenly becoming unable to type.
I'm seeing a great many devicemgr and rake errors in my system log. I don't know if they're related. How 'bout you?
If you're unfamiliar with the system log…
Open /Applications/Utilities/Console.
If necessary, choose View > Show Log List.
system.log is at the top of the FILES section.
Try searching it for hot words like DEBUG, FATAL, and aborted.
I've found some discussions that would tend to indicate my errors are postGres related – I'm running OS X server.
-Bryan

Screen Sharing hangs after a few minutes idle

I've enabled Screen Sharing on my Mac and am connecting from a Windows machine. I've tried connecting with TigerVNC, TightVNC, and TurboVNC clients but after about 10 minutes of no activity on the screen hangs. I'm able to move the mouse pointer, but no screen updates are sent over to the client. Reconnecting works, but it's a nuisance to have to connect every ten minutes
Any help on how to debug this would be appreciated. I bought my machine a month ago and I have the latest updates installed. Both the Mac and the VNC client are on the same LAN switch.
Thanks.
- Amir

You could try the Vine Server (a different VNC server).
Vine Server (aka OSXvnc)
<http://www.versiontracker.com/dyn/moreinfo/macosx/16699>
Just make sure you either give the Vine Server a different port number (for example port 5901), or you turn off the Mac OS X Screen Sharing VNC server.

Screen Sharing Broken for Network Account Admins Mac OS X Server

Re: OS X 10.8.4, Server.app 2.2.1
After replacing a failed Airport Extreme -- and the resulting changes in server IP address -- Screen sharing is now broken for "Network" account administrators. "Local" adminstrators can screen share successfully.
When logging in as a Local Admin, the System Log contains a single entry:
Authentication: SUCCEEDED :: User Name: localadmin :: Viewer Address: 10.0.1.6 :: Type: DH
When logging as a Network Admin, a similar line appears:
Authentication: SUCCEEDED :: User Name: testnetwork :: Viewer Address: 10.0.1.6 :: Type: DH
followed by screen-fulls of other log messages, eventually ending -- a minute or two later -- with:
screensharingd[77693]: uid 1034 not found
screensharingd[77693]: unable to get width and height of display.
at which point the client sees a "Error: Network connection lost." alert. 1034 is the UID of "testnetwork", as seen in
dscl /LDAPv3/127.0.0.1 -list /Users UniqueID
So apparently, Network users are authenticated, but screensharingd cannot find the user.
changeip -checkhostname returns "success". Just to be sure, I "Updated the Host Name" as suggested by the "Network Configuration Has Changed" alert in Server.app -- problem remains.
How does one debug this? Are there more comprehensive debug logging options available for screensharingd or login window? Anyone else seen this problem?

Linc: thanks for your inquiry.
Here are more steps I've taken to solve this problem:
1) From a Time Machine backup to a test partition, I restored the server from before the failure of the base station and found that the login problems were present then.
2) On yet another test partition, I created from scratch a new OS X Server. Added a local administrator, and a network admistrator and discovered the same problem: network administrators cannot screen share, although in this case, they are simply unauthorized.
Using dscl, things look OK: there is a /Local/Default/Groups/com.apple.access_screensharing that lists only the admin group, and the admin group contains networkAdmin.
Furthermore, I can log in as the networkadmin from the login window, as "Other".
Furthermore, I can ssh into the server using the networkadmin credential.
I used odutil to boost the logging OpenDirectory log level. The logs are very verbose, but to my eyes, it looks like OD recognizes the networkUser, but screensharingd fails to authorize. See logs below.
Can someone confirm that screen sharing from network admin accounts works at all? Is there a way to elevate screensharingd logging to find out more about why it rejects network admins?
TIA
/var/log/opendirectoryd.log
4643.65273.65277, Module: search - ODQueryCreateWithNode request, NodeID: 3D4241C6-FAFF-4816-8F7C-B3E0ED6F56A6, RecordType(s): dsRecTypeStandard:Users, Attribute: dsAttrTypeStandard:RecordName, MatchType: EqualTo, Equality: CaseIgnore, Value(s): networkadmin, Requested Attributes: dsAttributesStandardAll, Max Results: 1
4643.65273.65277, Node: /LDAPv3/127.0.0.1, Module: search - queuing request to connection - '/LDAPv3/127.0.0.1:ldap:406935A6-9ADB-413A-A82B-7F30F4E9E5A1'
4643.65273.65277, Node: /LDAPv3/127.0.0.1, Module: ldap - adding 'dsAttrTypeStandard:RecordName' for ambiguous name query
4643.65273.65277, Node: /LDAPv3/127.0.0.1, Module: ldap - adding 'dsAttrTypeStandard:RealName' for ambiguous name query
4643.65273.65277, Node: /LDAPv3/127.0.0.1, Module: ldap - query with filter - '(&(&(objectClass=inetOrgPerson)(objectClass=posixAccount)(objectClass=shadowAc count)(objectClass=apple-user)(objectClass=extensibleObject))(|(uid=networkadmin )(cn=networkadmin)))', baseDN - 'cn=users, dc=testserver,dc=local'
4643.65273.65277, Node: /LDAPv3/127.0.0.1, Module: ldap - found result - 'uid=networkadmin,cn=users,dc=testserver,dc=local'
4643.65273.65277, Node: /LDAPv3/127.0.0.1, Module: ldap - ODQueryCreateWithNode completed, delivered 1 result
4643.65273, Node: /Search, Module: search - ODQueryCreateWithNode completed, delivered 1 result
4643.65278 - Client: screensharingd, UID: 0, EUID: 0, GID: 0, EGID: 0
4643.65278 - ODNodeRelease request, NodeID: 184CFA31-1EB8-4384-B9CA-D04A93736CB1
4643.65278, Node: /Search - ODNodeRelease completed
clearing all node authentication connections
/var/log/system.log:
screensharingd[4665]: Authentication: FAILED :: User Name: networkadmin :: Viewer Address: 10.0.1.6 :: Type: DH

Screen sharing and multiple users

I have an iMac at home that is used by multiple family members. I have multiple logins enable so it is common to have 2-3 accounts logged in at once. I would like to use screen sharing to connect to my account even when one of the kids is logged into their account.
I started by looking at the vnc processes. There is one process that run as root:
root 21792 0.0 0.0 2437128 1736 ?? Ss 12:25PM 0:00.02 /System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/RFBRegisterMDNS
Then there is another process for each person logged in:
username 22006 0.0 0.3 2734876 13964 ?? S 12:33PM 0:00.29 /System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Ma cOS/AppleVNCServer
So I have two questions. One is how can there be three processes running that listen on the same 5900 port at the same time and how does it decide which one to connect a vnc client to? My second question is how can I prevent the AppleVNCServer process from starting for each user. I've tried killing those processes but they respawn immediately.

Hi
Thank you for your answer. Sorry to have been unclear - I'll give it another go :o)
Here is what I am trying to do:
I have 2 users (Plex and Ursus) that I want to have logged on at the same time. Plex will be "in the front" i.e. that is the screen that is seen if you are at the mini. Ursus is a user that is logged on but you cannot currently see (i.e. in the back as it where). I would like to work using the user Ursus (to, for example, rip a movie from a DVD (that I own of course :o).
Using file sharing would mean that I have 2 machines running and that I need to copy all the files from the one machine to the other, not exactly what I want but manageable.
I have managed to get this "partly" working - I am using Vine Server for Mac (http://www.testplant.com/products/vineserver/OSX) which allows me to start a VNC server on e.g. port 5901 and then screen share to that session. If I setup the second user (Ursus in this case) to use this server then I can connect to the "back" user. The only problem being that Vine Server seems to crash with Plex - as soon as I start it Plex just hangs and randomly crashes!
Was that clearer?
Thanks again
Ursus

Airport Extreme is allowing access to screen sharing, file sharing from external IP addresses (some from China, Canada etc)

How to get control over the ports/port forwarding etc in Airport Extreme?
How to make AE drop packets to certain ports from external ports. Or create whitelist/blacklists?
I figured out where the MAC filtering is! (It is inside the Timed Access Control). I wish it had a list of connected device and allowed me to select, name and add them.
I am getting requests from Chinese IP to the screen sharing ports forwarded to my iMac. Had requests to other ports as well. There was one IP address from CANADA too.
I want to open file sharing for local use only.

Why is Airport Extreme forwarding requests for screen sharing from external ip addresses to my imac? I don't have a public address, nor use dynamic dns service, and I have removed the server app (at least I think I have, but Apple Store doesn't think so).

Can I display EyeTV's live TV over HDMI-out and be able to see my desktop using screen-sharing on a headless mac-mini used as a media-box?

Hi,
I'm thinking of buying a new mac-mini to replace my current one which acts as an iTunes server and records TV programs using eyeTV. I connect using screen-sharing/VNC to be able to do stuff on it (like handbrake etc.)
I have eyeTV with a satelite receiver and I want to change the setup so that:
- the new mac-mini continues to work as an iTunes server (and handbrake workhorse)
- I can use the HDMI output (inc. audio) to show eyeTV's live TV full-screen app
- I can connect using screen-sharing/VNC to the mac-mini and see my normal desktop to be able to maintain it etc. but this is a headless display (no screen is connected to the display-port).
- recorded media I'd play through the appleTV2 still + rentals etc. unless anyone knows if eyeTV software can offer up iTunes content? I don't like the eyeTV recordings in general as it seems very slow to me for access when there are lots of recordings and wouldn't be available in other apleTVs in the house AFAIK.
The main benefit that this gives me is that I'd no longer need a seperate satelite box to watch live TV and can add more eyeTV hardware to get additional TV channels all through the same HUD on the TV for ease of access.
Does this seem possible in theory & practice (ie are there any gotcha's to consider?)
- can I force the HDMI output resolution to 1080i as I go via an amp to the TV and the appleTV2 drops to low-res in this configuration so I have had to find a workaround for that.
- does the mac-mini have IR input that can be programmed?
- Does eyeTV software remain stable for long periods?
- Does the HDMI out have any handshake issues that would need a reset of the display (somehow)?
thanks in advance for any thoughts/contributions
Lee

I think the easiest way to do this is to have the EyeTV app running in one user account and sent via HDMI to the TV, and use a separate user account for Screen Sharing. Both logins can be active at the same time and with Lion you can connect via screen sharing to which ever login you need.
With regards to the Mac video resolution changing, when it is not the current input on your AV receiver. This is 'normal', if the Mac sees no signal it drops down the a lower level. What you need is to buy a HDMI Detective Plus which tricks the Mac in to always seeing a signal and hence it will not drop down the resolution. See http://www.gefen.com/kvm/dproduct.jsp?prod_id=8005
The Mac mini does have an IR receiver. This can be used with the EyeTV app, iTunes, and similar. Yes I believe EyeTV would run for prolonged periods quite happily, it is has been around for a long time and had most of the rough edges polished off. However one issue you will have to deal with is that it does not automatically update its program guide data. For this you might have to write or modify an AppleScript. Elgato support or their user forums will be a lot of help.
You can set EyeTV to convert recordings to an iTunes (Apple TV) compatible format and then delete them from EyeTV.
The HDMI Detective should solve your handshaking problems.

Screen-Sharing and Internet-Sharing via same network connection

Hello out there,
I'm using a TiBook (G4 867MHz) and a MacBook Pro 17". They are connected via a WLAN-router. Additionally the MBP is connected to the internet via an UMTS-connection established with a Merlin 870XU type PC-card.
Network is working fine, including screen-sharing. Also the internet connection on MBP works without error. But if I activate Internet-Sharing via WLAN to get my TiBook connected to the internet, the MBP connection to the WLAN is cut off.
Can somebody tell me what's going wrong and how to solve it?
Greetings from good old Germany
Ansgar

Hello out there,
I'm using a TiBook (G4 867MHz) and a MacBook Pro 17". They are connected via a WLAN-router. Additionally the MBP is connected to the internet via an UMTS-connection established with a Merlin 870XU type PC-card.
Network is working fine, including screen-sharing. Also the internet connection on MBP works without error. But if I activate Internet-Sharing via WLAN to get my TiBook connected to the internet, the MBP connection to the WLAN is cut off.
Can somebody tell me what's going wrong and how to solve it?
Greetings from good old Germany
Ansgar

How do I speed up my Screen Sharing experience?

Hi. Apologies if this has already been answered, but I couldn't find post that matched. Anyway, I have set up Screen Sharing on my iMac so I can run it with my eMac (running Tiger 10.4.11). It all works fine except the response is a bit slow - that is to say the refresh rate doesn't make it workable if I'm working in image editing or whatever, in fact even just moving open windows around there's a noticeable lag in response time.
I think I should mention that both computers are networked via ethernet cables - not wirelessly - so the response is as good as I can get it at the moment.
I did hear somewhere that if I had an 'N' speed Router (as opposed to the standard 'G' speed) then this would improve the speed noticeably. Is that right? Also, my iMac is equipped with a 10/100/1000 Base T ethernet port, whereas my eMac is only the 10/100 variety. Will this make an 'N' speed router pointless. I just want to know before I waste money on something that'll make no difference really.
Thanks
Simon
Message was edited by: Simon Bramley

If you are using ethernet to ethernet connection, then 802.11g vs 802.11n WiFi does not matter.
The slowest ethernet connection will be the limiting factor, so the eMac's ethernet port is the controlling factor for transfer speeds.
If you want to experiment with a different VNC client and server, you might try installing Vine Server (aka OSXvnc) on the Mac to be controlled, and then use Chicken of the VNC as the client on the Mac you are sitting at. This pair of VNC client and server are very good at compressing the screen data to maximize network bandwidth.
The next trick you could try is to tell Chicken of the VNC to use less colors. CofVNC -> Connection -> Connection Profiles -> Default Profile -> Color. Try "Thousands of Colors" first, then maybe "256 Colors" although 256 is going to look very Andy Wohl'ish

Screen Sharing/network problem seems confined to 1 volume. What's the fix?

I am having a networking problem on one of the volumes of my multi-volumed, three-Mac local area network, and I need a networking guru to identify the specific software file(s), application(s), or system configuration that is the cause of the problem. I have already spent several hours checking and re-checking the various hardware and system preference settings involved, and I have narrowed the problem down to a software corruption issue and/or system configuration issue on one volume.
I now need someone to identify specifically what the nature of the problem is, and how to eliminate it. I am not looking for a sledgehammer solution that says I should re-install all of the Mac OS X software on the problem volume. That may be held in reserve as a last resort. I'm looking for a more elegant approach, one that points out the specific corrupt files to remove without disturbing everything else.
Here's some background to set the context. I have a MacBook Pro laptop; a PowerMac iMac G5; and a PowerMac G4 hooked up in a network. All are running Leopard 10.5.8. All have file sharing and screen sharing enabled. Besides being able to connect to each other using registered users, my goal here is for each of the Macs to be able to share the screen of the others upon my demand. Since each of the 3 Macs can theoretically share the screens of the other 2, that makes a total of six possible connections. Five succeed; one does not. That's the problem. I am trying to determine why the iMac G5 cannot share the screen of the MacBook Pro.
The iMac G5 has no problem sharing the screen of the PowerMac G4. That connection is fast and immediate. But, every time that I hit the Share Screen button on the iMac G5 to try to connect to the MacBook Pro, I get a window with the blue barber pole spinning for two or three minutes as it is allegedly "Connecting to Mac Book Pro," followed by a window with a headline telling me that "Connection Failed to MacBook Pro." The text within that window goes on to say: "Please make sure that Screen Sharing (in the Sharing section of System Preferences) is enabled on the computer to which you are attempting to connect. Also make sure that your network connection is working properly."
Well, as I indicated, the PowerMac G4 has no problem sharing the screen of the MacBook Pro, so the Screen Sharing settings on the laptop are correct; and the iMac G5 can share the screen of the PowerMac G4, so its network connection is working properly in that regard. It is only in regards to sharing the screen of the MacBook Pro that the iMac G5 is not working properly.
The reason why I say that the issue must be unique to the one volume in question, let's call it "iMacG5 Music," is that another Leopard volume on the same computer has no problem whatsoever in sharing the screen of the MacBook Pro. Whenever I boot up in that volume, let's call it "iMacG5 JMB," it makes a network connection with a registered user name immediately, and it is able to share the screen of the MacBook Pro within a second of my issuing the command. In sharp contrast to the success of the iMacG5 JMB volume, the iMacG5 Music is unacceptably slow (several minutes slow!) in making a network connection with the MacBook Pro, and it always fails to share the screen of the MacBook Pro, preferring instead to take about three minutes to attempt the connection, before announcing its failure.
Since the iMacG5 Music volume makes an immediate network connection to the PowerMac G4, as well as sharing the screen of the PowerMac G4 the moment I ask it to, I have concluded that the hardware of the iMac G5 is just fine. The problem seems confined to the system software and/or associated networking files that are unique to the iMacG5 Music volume. I just don't know what those files could be, or where the problem lies, so I've issued this call for help.
Let me add one more little twist to this puzzle which baffles me even more. I use external LaCie Firewire drives as clone backups of my Macs. As part of my trouble-shooting process, I booted up from the cloned versions of the iMacG5 JMB volume and the iMacG5 Music volume. What I learned surprised me!
The iMacG5 JMB clone worked just fine in making a fast network connection to the MacBook Pro, as well as sharing the screen of the MacBook Pro. I expected that. What I did not expect was that the iMacG5 Music clone was also able to make a fast network to the MacBook Pro, as well as share its screen!
Yes, that's right. It's weird! Screen sharing works OK when I start-up from the clone of the iMacG5 Music volume, but it does not succeed when I boot up on the source itself! I was surprised to find that out, but I'm glad I did.
(Over the past few days since I executed the last clone, I did use Drive Genius to de-frag the source volume, and maybe that has contributed to the problem I am now encountering. But it's hard to say, since nothing else seems to be amiss.)
One solution, I suppose, would be to sync the clone back to the source. But, before I do that, I'm just wondering if anyone has a clue as to the nature of this problem on the source volume and what I might do to remedy it—short of re-installing the system software or restoring from the clone. Anyone have any insight to this problem?

CORRECTION #2:
Ignore the previous "CORRECTION" post.
Oops, excuse me, I wrote that sentence correctly the first time.
I was trying to point out that the ability of the iMac G5 computer to connect quickly and effectively to the PowerMac G4 when booted up into the iMacG5 Music volume was an indication (to me, anyway) that there is nothing wrong with the computer's hardware, nor its network connection ability, but that the problem lay somewhere in the files/settings used to connect to the MacBook Pro, which it cannot accomplish.
This is what happens when I get engrossed in one of these technical morasses and it ***** me into its vortex all through the night... time for bed.

Can you use screen sharing outside of your local network?

I've been poking around with the "screen sharing" in osx Lion. I have a few questions about it.
Firstly, is the built-in screen sharing only accessible through the finder?
Also, is it only available on local networks? I've gotten it to work on two computers on the same network. But, can I use in the built-in screen sharing to look at my work iMac while I'm at home on my Macbook? Or would I need a full VPN client to do this? (Although isn't there built-in VPN compatibility in Lion?)
Thanks!

Go here..
https://discussions.apple.com/message/16439571#16439571
... and read my post explaining the different ways to share your screen. Things should be a little clearer for you, I hope.
Bob

Is it possible for multiple users to use a "generic" account simultaneously without screen sharing?

Hey and thanks for checking out the thread.
I am wondering if it is possible to have users use a generic account at the same time without any sort of screen sharing.
I have set up a generic user account (for example useraccount, password 1234) for users to use in the time before I can set up a custom user name for them. However, I have run into some issues with this.
When multiple users log on using this generic account, their applications seem to be shared on each screen. In the room with multiple Mac workstations, if someone starts working on Photoshop, Photoshop will open on every one elses screen who is logged on under that generic account.
Is it possible for users to log on using a generic network account and have their own isolated work environment or is this sort of sharing a feature? I am new to Mac servers and am not sure.
Thanks for reading the thread.

That shared-account approach seems impractical for the various reasons you've identified, as well as the inevitable issue of cleaning up the detritus that'll inevitably build up in a shared account, and for the lack of accountability for activities occuring under the shared account for both auditing and security, and sharing directories would tend to introduce obscure conflicts around which-file-version-wins file updates when the same file is used in several places, and would probably be contrary to any per-user application software licensing agreements that might be involved.
Put another way, get unique accounts created for folks, and work toward the ability to create accounts for arriving folks, and — if it's applicable here — talk to management about getting any per-user software licensing issues sorted out, whether that's having spare copies purchased and ahead or some advanced notice on accounts, or establishing group software licensing where that's available.
AFAIK, there are tools around which can automate account creation, too. Either generic, a tool such as Passenger, or it's certainly feasible to script the account creation sequence.
Trying this shared-access generic-account approach just looks like it can create more work and more hassles and more effort to me...

How can I set up a screen screen sharing VNC at a resolution higher than display?

I have a mid 2010 MacBook Pro 13in, and i have set up screen sharing to access over VNC. I want to view my mac on my 1920x1080 display hooked up to my PC. But when i do it is not full screen, it is the same resolution as my MBP. how can i run it at a higher resolution only over VNC?

As Cvid suggests, I create my "frames" in Photoshop. Not sure about all versions, but my PS has several Actions, just for frames, and I have made a few more, with a different "look."
I Save_As PSD, and just Import those as Footage (I do not need the capability to work with the individual Layers).
Good luck,
Hunt

Screen Sharing debug

Similar Messages

Maybe you are looking for