Screen Sharing - Can't Authenticate

Hi everyone,
I have screen sharing enabled on both my machines. My Macbook Pro is able to view my iMac screen but when I try to access my MacBook it prompts me for username and password and no matter what I put in, it says it cannot authenticate.
I created a user solely to test this feature and still says it can't authenticate - any suggestions?

I was able to fix this by reformatting my MBP and starting from scratch. Not sure what was causing this but that fixed it.

Similar Messages

Screen sharing can't connect

My husband and I both have mac books and are trying to use screen sharing on ichat. Audio chat works fine as well as video chat. But when we try to use screen sharing, it connects for about 2 seconds, you can hear the audio and then it disconnects with the error of: disconnected from screen sharing because: screen sharing could not be established. I don't understand why the others work fine, but screen sharing won't. Please help!

Hi,
Welcome to the  Discussions
You have posted in iChat 2's forum.
I have asked the Hosts to move it to Leopard > iChat and Screen Sharing.
iChat Screen Sharing tends to need your Router or Modem if it routes to use UPnP to open the ports.
This is because the Screen Sharing part happens on a random ports and not one of those listed in the two apple Articles on the Ports of iChat.
11:11 PM Thursday; February 26, 2009

Screen sharing: can't access after update to SL

I have a set-up with a new mini server running SL Server 10.6.2. A Macbook Pro and iMac are on the network, they were both running 10.5.8. I manage my mini server with one of these computers through screen sharing.
I updated my Macbook Pro last week to SL 10.6.2.
I updated my iMac this week to SL 10.6.2.
I can't log in to my mini server from these 2 machines since the update. I get a message "Authentication failed, please verify user name and password".
I have restarted my imac under 10.5.8, and I can use screen sharing again to manage my server.
I am at a loss to figure why the update to SL on my clients has killed may screen sharing access to the server.
Any hints would be appreciated.
Thansk

1. Startup in Safe Mode
    http://support.apple.com/kb/PH14204
2. Repair Disk
    Steps 1 through 7
    http://support.apple.com/kb/PH5836
Best.

Chicken of the VNC connects to my PC running RealVNC, Screen Sharing can't?

Hi,
One of the big features I was looking forward in to Leopard was being able to connect to VNC servers using the OS instead of a dedicated app, but when I try to use Screen Sharing to connect to my PC which is running a VNC server, I get the error:
"Connection Failed .... Please make sure that Screen Sharing (in the Sharing section of System Preferences) is enabled on the computer you're attempting to connect to. Also make sure your network connection is working properly."
This also happens if I try to make the connection via directly launching Screen Sharing or from the side panel of a Finder window or by doing command-K.
The weird thing is that Chicken of the VNC connects to the server without a hitch. Anyone know what might be wrong here? The PC is running RealVNC Personal Edition and has Bonjour for Windows installed. The Mac and the PC are on the same subnet.
Thanks in advance for any assistance!

Halle Winkler wrote:
....I still have to use command-k in order to connect because the finder doesn't auto-detect the VNC server....
The weird thing is that Chicken of the VNC connects to the server without a hitch. Anyone know what might be wrong here? The PC is running RealVNC Personal Edition and has Bonjour for Windows installed. The Mac and the PC are on the same subnet.
Finder probably isn't auto-detecting the VNC server because it likely isn't being advertised via Bonjour. I don't think Bonjour for Windows does much aside from give a Windows box the ability to listen for Bonjour printers and see Bonjour HTTP bookmarks. I'm unaware of it performing any sort of advertising of the services on a Windows box.
For Finder to do the auto biz, you will likely need some other sort of Bonjour advertiser, like Rendezvous Proxy or a mdns DNS server sending out an appropriate rfb.tcp service advertisement.

Video/Screen Sharing via 3G connection not possible - port restrictions?

I'm running Jabber-based iChat AV 5.0.3 sessions from my MBP connected to the Internet via a wireless USB modem 3G/UMTS (German Telekom D1 network). My buddies are connected to the Internet via regular broadband connections (DSL). I have set up a hosted Jabber server via Dreamhost (without SSL, port 5222 used).
Status Quo:
- Contact status of remote Jabber users shows up properly. All buttons (text chat, screen sharing, video) are available (not greyed out) on both sides.
- Text chat works fine.
- Video chat and screen sharing can be invoked from both sides (confirmation window shows up), but after confirmation the initiation process doesn't finish successfully. The video/screen sharing session doesn't run. *iChat AV shows a message indicating that it doesn't receive an answer from the remote user device.* If the iChat session is initiated from a buddy's computer, the buddy gets the same message respectively.
- For testing purposes, I changed the internet connection on my MBP from the mobile 3G USB modem to a regular *DSL broadband connection (same ISP, German Telekom). In this scenario, video/audio calls and screen sharing work flawlessly!* Therefore, I assume that the problems in 3G connection mode is caused by the ISP (German Telekom) blocking/restricting ports required by iChat AV for initiating the video call and streaming the data on their 3G network.
Is there any way to bypass ISP restrictions, by either changing specific iChat AV port settings on both ends (client devices) or by port forwarding? If yes, which settings should I change? Unfortunately, it's couldn't find any document indicating which ports are opened/allowed by German Telekom's 2G/3G (GSM/UMTS) network.
Below is an excerpt of the error message produced by iChat AV:
iChat Connection Log:
2010-11-09 21:18:19 +0100: AVChat started with ID 494414145.
2010-11-09 21:18:19 +0100: [email protected]: State change from AVChatNoState to AVChatStateWaiting.
2010-11-09 21:18:19 +0100: 0x1a8bf8b0: State change from AVChatNoState to AVChatStateInvited.
2010-11-09 21:18:28 +0100: 0x1a8bf8b0: State change from AVChatStateInvited to AVChatStateConnecting.
2010-11-09 21:18:28 +0100: [email protected]: State change from AVChatStateWaiting to AVChatStateConnecting.
2010-11-09 21:18:48 +0100: 0x1a8bf8b0: State change from AVChatStateConnecting to AVChatStateEnded.
2010-11-09 21:18:48 +0100: 0x1a8bf8b0: Error -8 (Did not receive a response from 0x1a8bf8b0.)
2010-11-09 21:18:48 +0100: [email protected]: State change from AVChatStateConnecting to AVChatStateEnded.
2010-11-09 21:18:48 +0100: [email protected]: Error -8 (Did not receive a response from 0x1a8bf8b0.)
Video Conference Error Report:
0.000000 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/DotMacConfiguration.m:1039 type=4 (FFFFFFFF/2)
[HTTP GET failed (0)]
0.000627 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/DotMacConfiguration.m:758 type=4 (FFFFFFFF/0)
[HTTP GET failed (0)]
0.346813 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/DotMacConfiguration.m:758 type=4 (FFFFFFFF/0)
[HTTP GET failed (0)]
1331.086051 @/SourceCache/VideoConference/VideoConference-415.22/SIP/SIP.c:2917 type=4 (900A0015/0)
[SIPConnectIPPort failed]
1333.086142 @/SourceCache/VideoConference/VideoConference-415.22/SIP/SIP.c:2917 type=4 (900A0015/0)
[SIPConnectIPPort failed]
1335.086270 @/SourceCache/VideoConference/VideoConference-415.22/SIP/SIP.c:2917 type=4 (900A0015/0)
[SIPConnectIPPort failed]
1337.086603 @/SourceCache/VideoConference/VideoConference-415.22/SIP/SIP.c:2917 type=4 (900A0015/0)
[SIPConnectIPPort failed]
1339.087985 @/SourceCache/VideoConference/VideoConference-415.22/SIP/SIP.c:2917 type=4 (900A0015/0)
[SIPConnectIPPort failed]
1341.088212 @/SourceCache/VideoConference/VideoConference-415.22/SIP/SIP.c:2917 type=4 (900A0015/0)
[SIPConnectIPPort failed]
1343.088361 @/SourceCache/VideoConference/VideoConference-415.22/SIP/SIP.c:2917 type=4 (900A0015/0)
[SIPConnectIPPort failed]
Video Conference Support Report:
929.446913 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2059 type=2 (00000000/0)
[Connection Data for call id: 1 returns 1
934.996640 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2074 type=2 (00000000/0)
[Prepare Connection With Remote Data - remote VCConnectionData: 1, local VCConnectionData: 1
935.002114 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2266 type=2 (00000000/0)
[Initiate Conference To User: u0 with Remote VCConnectionData: 1 with Local Connection Data: 1 conferenceSettings: 1]
935.467624 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
[INVITE sip:user@rip:16402 SIP/2.0
Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK0fdd30e326aa779b
Max-Forwards: 70
To: "u0" <sip:user@rip:16402>
From: "0" <sip:user@lip:16402>;tag=544473054
Call-ID: 9c7ecf46-ec3d-11df-8530-f81eeb5f4012@lip
CSeq: 1 INVITE
Contact: <sip:user@lip:16402>;isfocus
User-Agent: Viceroy 1.4
Content-Type: application/sdp
Content-Length: 708
Video Conference User Report:
928.427249 @:0 type=5 (00000000/16402)
[Local SIP port]
934.996832 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2171 type=5 (00000000/0)
*[Remote Router]*
*[PORT RESTRICTED]*
934.996842 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2173 type=5 (00000000/0)
[Remote CommNAT Result: 0x000000d0
936.003962 @:0 type=5 (00000000/60)
[Detected bandwidth (kbits/s): 2627 up, 2627 down. (00000000)
936.033015 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VideoConferenceMultiController.m:2423 type=5 (00000000/0)
[Start Conference With UserID: u0]
978.787787 @:0 type=5 (00000000/16402)
[Local SIP port]
1014.011790 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2171 type=5 (00000000/0)
[Remote Router]
[PORT RESTRICTED]
1014.011800 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2173 type=5 (00000000/0)
[Remote CommNAT Result: 0x000000d0
1015.024555 @:0 type=5 (00000000/60)
[Detected bandwidth (kbits/s): 2627 up, 2627 down. (00000000)
1015.031800 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VideoConferenceMultiController.m:2423 type=5 (00000000/0)
[Start Conference With UserID: u0]
1323.083386 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2171 type=5 (00000000/0)
[Remote Router]
[PORT RESTRICTED]
1323.083396 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2173 type=5 (00000000/0)
[Remote CommNAT Result: 0x000000d0
(…)

Hi,
Does this 3G device have any set up functions that are on your Mac ?
If it does not it is likely that it is wide open to all Port (65535 of them).
I presume that in System Preferences > Network you see a Public IP when using this device ?
Again this would tend to pint to all the ports being open.
Is there anything on the ISP's web site that suggests this device is unsuitable to be used with VoIP or SIP connections ?
VoIP (Voice over the Internet) uses the SIP connection process the way iChat does.
Most likely the issues is the way packets are sent.
When you do a download, for instance, do you find the speed increases in the first few minutes ?
When some data packets are sent over the Internet the next one is not sent until confirmation that the first has arrived.
This Latency effects Point to Point WiFi (antenna to Dish on House) and satellite connections mostly particularly when it is a two way thing.
It can effect Mobile/Cell phone type connections.
What sort of Speeds are you getting on the 3G device ?
http://www.speedtest.net/
Do these seem to get faster as the time proceeds ? (this can be difficult to spot).
The Log mentions one end being at just over 2Gbps although it does not make it clear which end.
As the Remote end is the end that reports "Router: Port Restricted" and it works over standard DSL we have to presume they have the ports open.
You could try restricting iChat 's Bandwidth in iChat menu > Preferences > Video Section to 500kbps (try it at both ends)
If that does not work try 200kbps
This may stop iChat from trying to send data too Fast for the Network Connections.
Realistically there are a few too many variables here.
It could be Speed of data throughout at the Initiation point. (Slow Start up of data transfer)
It could be an Internal setting preventing SIP.
It could be that the 3G network sends and receives data by different routes.
(I have seen this once when a ISP was repairing some Cabling. To maintain end user speeds they managed their own network to split Incoming and outgoing data to the end point.)
iChat does not like this as it checks the IPs and the Hops (number of intermediate stages/servers) and if the data is different it will not connect (Man in the Middle attack protection).
I can't remember the last time I knew of someone being successful with either an 3G USB dongle or a 3G phone as Modem (internet Sharing).
Despite my ideas I think you will be unlucky and this will not work.
10:31 PM Saturday; November 13, 2010
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

Screen Sharing Impossible!

hello guys, i've tried almost everything to get my ichat screen sharing working but unfortunately it's impossible..
I've already read thousands of topics talking about this issue and no one was able to help me. so i've decided to create my own topic.
I've tried:
ichat preferences, since Bandwidth Limit from None to 2 Mbps
Quicktime Streaming Preferences from Automatic to 1.5 MBPs
System Preferences > Sharing:
1) Screen Sharing enabled (only option selected at the time)
2) Internet Sharing disabled
Both Macs Running Leopard 10.5.7. I live in Italy and my mom and friends in Brazil.
My internet is 6035(Kbps) / 509(Kbps)
My modem is a D-link DSL-2640B with UPnP enabled. (I've also tried forwarding ports 5060, 5190, 5220, 5222, 5297, 5298, 5353, 5678, 5900 and 16384 through 16403)
My mother's internet is 1005(Kbps) / 300(Kbps)
My friend's internet is 13000(Kbps) / 1000(Kbps)
My mother was using a modem Parks Altavia 670R. This modem is quite old, and has no UPnP so, i thought it would be the problem and bought another modem.
So, now my friend and my mother are using a Thomson/Alcatel SpeedTouch 510 (V6) also with UPnP and they've also tried port forwarding as well as I mentioned before.
My friend is able to share his screen with his other friends and so am i with my other friends..
We've also tried:
Trash QuickTime preferences
Trash all iChat preferences
Change iChat's port to 443 and turn on SSL
Turn on All in Security System Preference
Set access for specific services and applications and select ichat.
Our macs are all intel macs and completely updated.
Don't know what else to do.
Please, someone hive me a hand!

Ok,
For a Long time (Since at least their Version 3 firmware) Thomson-Alcatel have done what is called SIP Binding.
This forces all SIP data to use port 5060 whether that is the port is using that one or not.
(There was an International Standard at one point that SIP would be on Ports 5060-5063 - one at a time if one was bus)
SIP (Session Initiation Protocol) is uses by VoIP phones and apps.
Apple decided iChat was a VoIP app and included SIP as the Connection Method behind the scenes.
Up to Version 4.2.7 of the Thomson-Alcatel firmware you could fully "unbind" the SIP from port 5060 as in practice the modems thought it should go to a Phone and not pass it to the computer.
The symptoms were intermittent success in Audio Only and Video Chats.
Out of 50 Buddies 10 would be successful all the time.
10 Buddies now and then Success
30 Buddies would be unsuccessful
In version 5, 6 and 7 of their Firmware the SIP Binding can only be partially Undone.
It moves the Split to 15:10:25 (a change from 1 in 5 to about 1 in 3 only)
More here
Having said all that the Screen Sharing can be a bit of a different problem aside from the Audio Only chat that goes with the Screen Share that could suffer form the above issue.
The ports in iChat 4 that the Screen Share actually happens on is a random port.
Consider it as two connections that happen at the same time.
The Screen Share and the Audio Chat
The Audio Chat remains on port 16402
If you can Video or Audio Only chat with this Buddy that is not where the Problem is.
The Screen Share part is on a random port. A range is not even listed By Apple in the Article. (This one does not even list the Jabber and Bonjour ports)
This means that you either have to start opening ranges of Ports in Port Forwarding or use UPnP which will open the ports from the application side (the application has control over what ports are opened)
Some D-Links do not have UPnP.
Those that do hide it away in the Set up pages in Tools in the top Menu and Misc in the side menu when Tools is opened.
It is Not On by default.
It should not be used with Port Forwarding (Virtual Server) or Port Triggering (Applications) as clashes can occur.
If you can not screen share with other people it is more likely to be your end - IF you can Audio chat to this Buddy.
7:24 PM Tuesday; July 7, 2009
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

Can connect with Server Admin and Server Prefs, not Screen Sharing or ARD

Just set up 10.5 server on my G5, and trying to connect from 10.5 on my iMac. I have tried both with the server System Preferences set to allow Screen Sharing via VNC, and with Remote Management enabled for ARD. In both cases, I get authentication errors when trying to connect from home. I have tried with both the full username, and with the short name of the only account on the server. My assumption is that, since this is the administrator account, I don't need to setup explicit privs for it on the server.
I can authenticate without any trouble with both Server Admin and Server Preferences.
The Firewall is not enabled on either machine, although I am behind a NAT router at home -- is it necessary to open any special ports to enable screen sharing? Is it possible that having these ports closed would produce an authentication error?
Thanks for any help.

Hi
I'm going to assume you configured your Server in Standard Configuration and not Workgroup or Advanced?
When using Standard in setting up the server DNS is automatically configured for as well as the Server taking an Open Directory Master Role. The admin account created at the beginning is for administering the Open Directory. Unknown to you and not documented at all - as far as I can see - is the 'Local Administrator' (localadmin) account.
You only become aware of this account if for some reason you have a problem with the Server which involves demoting to Standalone (ie not an Open Directory Master) once this happens you find you can't log on to the Server anymore or communicate with any of the Server applications because it won't accept any username or password other than root and localadmin for the name and the password defined for the original admin account you created right at the beginning.
Sometimes it does not even take demotion to find yourself locked out of the Server. Some have experienced this problem when running the Security Update or when some other problem has occured.
Part of the process of creating an Open Directory Master involves the creation of a 'special' directory administrator account. This account is used for administering the LDAP node. If demotion takes place this account gets blown away along with all users and group accounts that exist in the LDAP node, in fact everything to do with Open Directory is destroyed apart from Users' home folders.
Why demote if this happens? Sometimes the LDAP database gets damaged/corrupted beyond a point where normal troubleshooting methods fail. This can happen for a whole variety of reasons but more often than not is due to a poorly configured DNS Service. You basically only have two options once you reach that stage. A server reinstall involving a format and rebuild or a demotion to Standalone. Which option would you choose? Prior to demotion you can (if you have the chance) export users and groups or even archive the LDAP database itself for restoration later on. This is a useful option as everything to do with the LDAP Server is retained - passwords, users, groups etc. The other method of saving users etc does not retain passwords.
As time goes on and you become more familiar with your server you will find more and more of this information out for yourself. Hopefully the simple advice I've given helps you understand Open Directory a little better.
Hope this helps, Tony

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.

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

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

Why can't I connect to my Mac Mini via Finder (but I CAN via screen sharing)?

My problem concerns a quad-core 2.0 GHz Mac Mini Server (mid 2011, I think) with SSD and 3 external hard drives. It's (a) my desktop workstation (b) our Time Machine backup repository (c) iTunes server and (d) Printopia server for our iDevices. That's it. The only thing I use the server app for, really, is Time Machine.
So recently we lost power a couple of times. As always, I ran Disk Utility, repaired permissions and verified the main disk. All appeared well.
But all is assuredly not well. Now, none of my other Macs can (a) find the Time Machine backup volume or (b) connect to the server at all. Whenever I try either thing, I receive the message below:
The network is in flawless shape otherwise. My router is the latest generation Airport Extreme Base Station. The server has a static IP, and I CAN connect to it from my other Macs by clicking Finder, then Go, then entering the IP address -- but ONLY if I use an smb:// prefix!
Moreover, even when I'm connected in this way, I STILL get the message whenever I try to connect by merely clicking the name on the finder sidebar -- or whenever I try to access the machine using Time Machine preferences. Weirder still, I CANNOT connect to the ip address via afp.
Final piece of weirdness: I can also connect to this machine from any other Mac via screen sharing. So please....
WHAT'S MY PROBLEM AND HOW CAN I FIX IT? I've wracked my brains, combed through forums and can find nobody else with this problem, let alone a solution.The problem persists when I shut down the server app.
I'm assuming that either something is corrupted or some setting is afoul, but can't figure out what it might me,
I'm just about at the point of reformatting my main drive and reinstalling Mountain Lion, but am hoping someone can spare me that pain.
THANK YOU so much!
Arthur P. Johnson
P.S. I have no problem at all with outbound connections from this bewitched Mini. Just inbound.
P.P.S I will, of course, be happy to provide shots of any other settings you may desire,

For some reason, the error box photo didn't appear in my post. Here it is:

Upgraded to Yosemite and can no longer remote into my work iMac through screen sharing- it is turned on in settings?

My screen sharing functionality did not show up in the dock with an updated icon. It had a question mark- shows my connections but nothing works, I did make sure screen sharing is on and also connected to VPN. Once I tried to launch screen sharing nothing happens. Such an elegant solution in Mavericks not does not work. Ugh. Help!

This is the post that got me set up- I too am running an older version at work vs. Yosemite. As soon as I followed is advice everything worked.
Upgraded to Yosemite and can no longer remote into my work iMac through screen sharing- it is turned on in settings?
I believe the location of the "Screen Sharing" app has changed, which explains why if you had it in the dock it has been replaced by a ?
Don't forget you can launch screen sharing (once your VPN connection is up) by typing in the Safari destination slot vnc://remotemachinename:portnumber (omit the :port number if you are using the default VNC port, 5900). This should launch Screen Sharing and put its icon in the dock. You can drag the Screen Sharing icon to the left of your dock and it will hopefully remain there after you exit Screen Sharing, or you can right-click on the icon when it's running and select Options->Show in Finder to find out its new location and drag its icon to the permanent entries in your dock.
Hope this helps; worked for me.

Can't access iTunes and Screen Sharing sharing services on my mac Mini

Since several weeks now I face a networking issue of the stranger kind.
Currently I've got my Mac mini acting as the central server for music, photos and files in my home. Central Network Mgmt device is a Wireless Lan router.
In the past I was accessing the Mac Mini from my MacBook via Screen Sharing this doesn't work anymore. When requesting the service the connection effort just runs idle. In iTunes on my MacBook I can see the Libary of my Mac Mini iTunes but clicking on it brings the rotateing ball and after a certain while the message that the iTunes Libary is not responding and that I should check my Firewall settings. Which I did on both computers and they are wide open. 'Ipfw show' in Terminal brings back the message 'Open for any to any communication' also on both computers.
Makeing use of the File sharing service from the MacBook to the MacMini works but it takes a extreme long while until the shared folder appears on the MacBook.
Trying to access from the Mac Mini my MacBook for all these services is no problem.
One more thing is that my Mac Mini cannot access the Wireless Lan router anymore thru the Web Browser or thru a Ping. Here I get the message 'Ping Send to: permission denied'. I changed the Router still the same message. Internet traffic is only possible after I manually applied a DNS Server with its IP number.
Anyone out there who could help? I'm close to completely reinstall my Mac Mini but would naturally love to avoid this.

wireduck,
Highlight the music folder and on the keyboard type (Command) + i: on the window that opens scroll down if need and click on the lock on the bottom right. Type in an Admin User name and password. Then under the (Sharing & Permissions:) make sure the users you want to open the folder are listed and that there (Privilege) is set to @ least Read. If not hit the ( + ) sign and add them. After you have that all set up click on the little gear next to the ( - )s sign and (Apply to a enclosed items). that way each user can read the files. After that the little ( - ) sign should be gone on the folders.
Hope that helps.

10.6.8 MBPro Screen Sharing suddenly can not connect to our other Macs.

We've used Screen Sharing from our MBPros for the past few years to manage our Mac file & media servers. Last year we replaced our G5 file server with a Mac Mini with Lion server. No problems - we could still use Screen Sharing to manage both this Lion file server and the Snow Leopard MacPro that's hooked up to our TV (among other things).
Friday morning my MBP could not see or connect to the Lion file server - the MBPs have the Lion server's data drives in Login Items so they mount when we log in. I also cound not Screen Share to either the Lion server or the SL MacPro. I checked the MBP's ethernet connection and could get to our router and the internet. When I tried to connect via Screen Sharing (by using the Share Screen... button in a Finder window, by using the Connect to Server command with vnc:// protocol, or by using the ScreenSharing menulet) I would get the "Connecting to Lion server" alert but nothing further. I left it for 10 minutes or so and it eventually disappeared but the connection never opened.
I checked the two servers and both were up and running. From the SL MacPro I could use Screen Sharing to get to the Lion server - and my MBPro too. From the Lion server I could Screen Share to the MacPro and my MBPro also.
The problem appeared to be with my MBPro. I switched to an unprivledged user account on it and found I could then get to both servers using Screen Sharing. So it was just my account on the MBPro. Rebooting did not help. Turning on AirPort, connecting to our home AirPort Extreme and unplugging the ethernet cable did not change anything with my account connecting to the servers.
I figured something somehow got pranged in my account's credentials. I used Keychain Access to delete all keychains containing the servers' names, IP addresses or sharing. I was asked for my credentials when I mounted the server's shared drives, but not when I tried Screen Sharing - got the same "Connecting to Lion server" or "Connecting to media server" dialogues and was never asked for username or password, but never connected either.
I cleared all caches using the utility Maintenance in case my MBPro was using invalid cached info. No improvement.
Saturday morning I shut down everything on our entire network - FiOS "modem"/router, Netgear gigabit switch, AirPort Snow, AirPort Extreme, MacPro, MacMini, both MacBookPros... even the FiOS cable box. Still no improvement.
IPv6 is disabled on the Lion server. All the Macs have all curent updates applied.
I've spent most of today Googling for solutions and trying them out. None have worked - though I see several very recent reports in these Apple Communities about Screen Sharing suddenly not working.
I really do not want to have to move to a new account on my MBP - and what's to say it won't happen again? Anyone have other suggestions?

sunnovagun!
Hitting the Log Out button in the MobileMe panel worked. I can now connect to both the SnowLeopard and Lion servers just like I used to.
My condition appears to have been slightly different from yours, gmia - the MobileMe on my MBP had the correct info, but hose are not the credentials i use to remote to the two servers. I'm guessing that for some reason ScreenSharing began using my MobileMe credentials instead of what I had saved in the keychains.
Wonder if it had anything to do with the shutdown of the MM servers. That would be odd as using ones apple ID to log into a Mac remotely was new with Lion, and I had the same problem with our SnowLeopard server - which I remote into much more frequently.
Probably didn't hurt though to reboot the entire network...

Display is not working But Through Screen Sharing I can Access my computer

Ok. After turning my computer off and then turning it back on a couple hours later the screen would not turn on. Im still able to log in. With screen Sharing I can acces my computer and system profiler shows that my RAM cards are OK. However when I click on Graphics/Display it unexpectedly quits.
What could the problem be? Any help is greatly appreciated : )
Ps. I wrote this through screen sharing out of my account on the display-less computer.

Welcome to Apple Discussions!
I wonder if you could have the NVIDIA chip problem?
http://support.apple.com/kb/TS2377
Is the display totally dead, or can you see your desktop if you shine a strong light through the apple on the back of the display? If so, you may have a different issue with just the internal display. A good test would be to see what happens with an external display connected directly to the MBP.
Good luck!

Screen Sharing - Can't Authenticate

Similar Messages

Maybe you are looking for