Can't screen share on local network

Hi folks,
Seems like lots of problems are to be had with the iChat screen sharing. I've been looking through here and tried several options, but I don't seem to be able to get this working.
My MacPro 2x2.66 is sitting in the DMZ of my DSL Router and a brand new iMac is sitting behind the router's firewall, but on the same network. Both are running updated versions of Leopard. I've followed the instructions for NAT port forwarding on the router found here:
http://web.mac.com/valsjo/personal/Start/Entries/2007/12/8iChat_screen_sharing_problemsolved.html
and also made the necessary changes to the Apple firewall (although I actually just have "accept all incoming connections" checked rather than listing iChat and my many other apps individually).
These two computers can't seem to screen share, however, with the dreaded "Screen sharing could not be established" error. Why is this happening when I'm on the same LAN?
Video chat appears to have similar problems.
Thanks for your input,
Aaron Genest

Have you tried Bonjour for screen sharing on your local network?
It works without problems on my local network, these are the settings that work for me:
Enable Bonjour messaging in iChat preferences>select use Bonjour instant messaging.
With iChat open select "enable screen sharing" from the top menu>video
In order to get it to work on my local network I had to disable screen sharing in Apple menu>System preferences>sharing.
The firewall settings are set to specifically allow the iChat application.
These settings should be set on all Mac's on your local network you wish to use iChat screen sharing with.
It might not work with a mac that has the file vault feature enabled.
My router settings are in default.

Similar Messages

Can I set up a local network without being connected to internet?

Can I set up a local network with Airport without being connected to internet?

Yes. Your AirPort Express router, by default, will create an unsecured wireless network and does not need to be connected to the Internet to do so. Local clients can then connect to this wireless network and be able to "see" each other.

G5 to MacBook Pro Can't Screen Share But Can MacBook Pro to G5 ?

Hi
I am using the Screen Sharing app built into Leopard and I can see the G5 screen from the MacBook Pro but not the other way round as it will just not connect whatever I try. I can file share no problem. I have checked the system preferences and they are identical as far as the Sharing and Security options are concerned. I have tried over ethernet and wireless but no luck. They are on the same local network and both running 10.5.2.
Anyone any idea or experienced the same problem?

Hey,
I have about the same thing going on. With my MBP, I can login and share HD, Screen, etc of the G5. Using my G5, I cannot login and share anything on the MBP. Get a connection timed out message, even though the MBP does show up in the sidebar. I tried to log on to the MBP with a G4, and that also wouldn't work. They are all on the same local network.

Asa 5505 Remote VPN Can't access with my local network

Hello Guys ,, i have a problem with my asa 5505 Remote VPN Connection with local network access , the VPn is working fine and connected , but the problem is i can't reach my inside network connection of 192.168.30.x , here is my configuration , please can you help me
ASA Version 8.2(1)
interface Vlan1
nameif inside
security-level 100
ip address 192.168.30.1 255.255.255.0
interface Vlan2
nameif outside
security-level 0
ip address 155.155.155.10 255.255.255.0
interface Vlan5
no nameif
no security-level
no ip address
interface Ethernet0/0
switchport access vlan 2
interface Ethernet0/1
interface Ethernet0/2
interface Ethernet0/3
interface Ethernet0/4
interface Ethernet0/5
interface Ethernet0/6
interface Ethernet0/7
ftp mode passive
access-list inside_nat0_outbound extended permit ip any 192.168.100.0 255.255.255.240
pager lines 24
logging asdm informational
mtu inside 1500
mtu outside 1500
ip local pool vpn-Pool 192.168.100.1-192.168.100.10 mask 255.255.255.0
icmp unreachable rate-limit 1 burst-size 1
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list inside_nat0_outbound
nat (inside) 1 0.0.0.0 0.0.0.0
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
dynamic-access-policy-record DfltAccessPolicy
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
crypto ipsec transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac
crypto ipsec transform-set ESP-DES-SHA esp-des esp-sha-hmac
crypto ipsec transform-set ESP-DES-MD5 esp-des esp-md5-hmac
crypto ipsec transform-set ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto ipsec transform-set ESP-AES-256-SHA esp-aes-256 esp-sha-hmac
crypto ipsec transform-set ESP-AES-128-SHA esp-aes esp-sha-hmac
crypto ipsec transform-set ESP-AES-192-SHA esp-aes-192 esp-sha-hmac
crypto ipsec transform-set ESP-AES-128-MD5 esp-aes esp-md5-hmac
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set pfs group1
crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA ESP-3DES-MD5 ESP-DES-SHA ESP-DES-MD5
crypto map outside_map 65535 ipsec-isakmp dynamic SYSTEM_DEFAULT_CRYPTO_MAP
crypto map outside_map interface outside
crypto isakmp enable outside
crypto isakmp policy 10
authentication pre-share
encryption 3des
hash sha
group 2
lifetime 86400
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd auto_config outside
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
webvpn
group-policy mull internal
group-policy mull attributes
vpn-tunnel-protocol IPSec
username xxx password eKJj9owsQwAIk6Cw encrypted privilege 0
vpn-group-policy Mull
tunnel-group mull type remote-access
tunnel-group mull general-attributes
address-pool vpn-Pool
default-group-policy mull
tunnel-group mull ipsec-attributes
pre-shared-key *
class-map inspection_default
match default-inspection-traffic
policy-map type inspect dns preset_dns_map
parameters
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect esmtp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect xdmcp
inspect sip
inspect netbios
inspect tftp
service-policy global_policy global
prompt hostname context

Hey Jennifer i did every thing you mention it , but still i can't reach my inside network (LOCAL network) iam using Shrew Soft VPN Access Manager for my vpn connection
here is my cry ipsec sa
interface: outside
    Crypto map tag: SYSTEM_DEFAULT_CRYPTO_MAP, seq num: 65535, local addr: 155.155.155.1
      local ident (addr/mask/prot/port): (0.0.0.0/0.0.0.0/0/0)
      remote ident (addr/mask/prot/port): (192.168.100.1/255.255.255.255/0/0)
      current_peer:155.155.155.1, username: Thomas
      dynamic allocated peer ip: 192.168.100.1
      #pkts encaps: 0, #pkts encrypt: 0, #pkts digest: 0
      #pkts decaps: 0, #pkts decrypt: 0, #pkts verify: 0
      #pkts compressed: 0, #pkts decompressed: 0
      #pkts not compressed: 0, #pkts comp failed: 0, #pkts decomp failed: 0
      #pre-frag successes: 0, #pre-frag failures: 0, #fragments created: 0
      #PMTUs sent: 0, #PMTUs rcvd: 0, #decapsulated frgs needing reassembly: 0
      #send errors: 0, #recv errors: 0
      local crypto endpt.: 155.155.155.1/4500, remote crypto endpt.: 155.155.155.20/4500
      path mtu 1500, ipsec overhead 82, media mtu 1500
      current outbound spi: 73FFAB96
    inbound esp sas:
      spi: 0x1B5FFBF1 (459275249)
         transform: esp-aes esp-sha-hmac no compression
         in use settings ={RA, Tunnel, NAT-T-Encaps, }
         slot: 0, conn_id: 12288, crypto-map: SYSTEM_DEFAULT_CRYPTO_MAP
         sa timing: remaining key lifetime (sec): 2894
         IV size: 16 bytes
         replay detection support: Y
         Anti replay bitmap:
          0x00000000 0x00000001
    outbound esp sas:
      spi: 0x73FFAB96 (1946135446)
         transform: esp-aes esp-sha-hmac no compression
         in use settings ={RA, Tunnel, NAT-T-Encaps, }
         slot: 0, conn_id: 12288, crypto-map: SYSTEM_DEFAULT_CRYPTO_MAP
         sa timing: remaining key lifetime (sec): 2873
         IV size: 16 bytes
         replay detection support: Y
         Anti replay bitmap:
          0x00000000 0x00000001

Can't screen share on one computer on LAN; strange vnc settings?

While troubleshooting problems using FaceTime on Mac on one of four computers on my LAN, I discovered several strange things about the Mac in question.
Though the Mac's name shows up on all the other computers on the LAN under the "Shared" area of the finder window, none of the computers can connect for file sharing or screen sharing even though these are turned on in the system prefs.
Even seemingly stranger, it is impossible to connect to this computer using VNC. Under the Screen Sharing section of "Sharing" it states, "Other users can access your computer at vnc://thebmac.comcast.net/ or browse for "beckyiMac"'. The odd thing here is the vnc address. It seems to be using an old name for the computer. The current name of the computer is "beckyiMac".
On other computers on my LAN some are listed with their local ip numeric address in the vnc address and others are listed with terms such as "homemacproethernet.comcast.net".
I guess one of my questions is how does the computer assign the vnc address seen on the Screen Sharing set up page? Is there a way to change this?
Thanks.
John

Have you tried Bonjour for screen sharing on your local network?
It works without problems on my local network, these are the settings that work for me:
Enable Bonjour messaging in iChat preferences>select use Bonjour instant messaging.
With iChat open select "enable screen sharing" from the top menu>video
In order to get it to work on my local network I had to disable screen sharing in Apple menu>System preferences>sharing.
The firewall settings are set to specifically allow the iChat application.
These settings should be set on all Mac's on your local network you wish to use iChat screen sharing with.
It might not work with a mac that has the file vault feature enabled.
My router settings are in default.

CAN'T SCREEN SHARE! TRIED EVERYTHING! PLEASE HELP!

My girlfriend just got a new Macbook and I've been helping her set it up across campus though our network at my university. It worked fine and then one day it didn't. Every time she asks or I ask to share her screen it gives this error to both of us:
"Failed to start Screen Sharing because: Screen sharing could not be established."
I've been reading discussions on how to fix this for 2 weeks now and nothing has seemed to work. What is weird though is that I can screen share PERFECTLY with my Uncle who lives in Wisconsin (I am in Arkansas) from campus. However, I can't seem to connect to my girlfriend's computer who is simply just a few buildings away.
The following is what we've tried:
1. Switch from wired to wireless network
2. *Set "System Prefs>Quicktime>Streaming" to "1.5 Mbps T1/Intranet/LAN"
3. *Set "iChat Prefs>Audio/Video>Bandwidth Limit to both "500" and "None"
4. *Both computers have a firewall set to "Allow all incoming connections"
5. *When #4 didn't work we set firewall to "Set access for specific services and applications > iChat.app set to "Allow incoming connections"
6. Rebooted both Macs
7. Deleted all com.apple.iChat.X.plist files and started over fresh
8. *Enabled "Screen Sharing" in System Prefs>Sharing
*Restarted iChat afterwards
I think that's all. It is just really frustrating because I can screen share with someone clear across the nation but not someone who is on my same network. The only difference is that she is using a Gmail account through AOL and I am using a @me.com address. I thought maybe Gmail wasn't working so I had her switch to an AOL account and still same error.
We cannot port forward for obvious reasons at school but it worked before and nothing on the firewall has changed. I work at the IT department at our university and spoke with the person who runs the Firewall and supposedly there are no blocked ports on the part of the network we use. I know with iChat 4 in Leopard it doesn't use a specific port, it bounces around until it finds one according to article regarding port forwarding and NAT routers and iChat.
The weird part is that when we are both off campus (different houses) and try it, Screen Sharing tries to start, she gets the big words across her screen ("Screen Sharing Started" I think...) and we can hear about 5 seconds of audio and then it errors out again. I really want to get this working can someone please tell me how? This is really frustrating.
Thanks,
-jg

Hi,
First off from reading this it should be an AIM valid name (@mac.com, AIM or @me.com) to AIM valid name or
a Jabber valid name (which includes Googletalk valid Gmail IDs) to another Jabber valid name
(that is both should be using the same type of Buddy list)
As you say the Apple Doc on this is not clear on the Screen Sharing part - listing only the changes to the AV ports compared to the Previous Doc (Now article HT1507). It does not mention the Screen Sharing at all.
Reading around suggests the Screen Sharing is based on Apple Remote Desktop and reading the com.apple.ichatAgent.plist with QuickLook shows a reference to a ARD link/process. (the same can be seen if you install Developers Tools from the Install disk which will give you Property List Editor which will open the .plist files).
The Article TS16929 (Previously Doc 106439 shows that Apple Remote Desktop uses port 5900 and 5988.
Having said that though I run Little Snitch, an application that monitors and reports which IPs and Ports and application is trying to use. This shows me a completely random port in the 15xxx range along side the AV port 16402 for the Audio component. It maybe that Apple Remote Desktop also moves to a random port after it has established a connection.
Most people fail on the Audio part and get the standard Log Pop up screen to send or not to Apple - BUT you clearly have the other message...
"Failed to start Screen Sharing because: Screen sharing could not be established."
.... which is unrelated to the Audio part.
This would clearly put things in to the realms of a firewall or setting issue with possibly modem/router or LAN features getting in the way. (Leaving aside ISP related things for the moment).
You say iChat is in the Allowed Specifics List in the Leopard Firewall.
You say that nothing has changed on the Campus Firewall and can connect Off-site form On-site so it would seem not to be there.
On this last issue, check if they have introduced a Streaming cap on Intra-Site links. They may be trying to prevent other things such as Peer-to-Peer File Sharing or thing like everyone sharing their iTunes Libraries and other similar activities. The ability to Share Optical Drives re MacBook Airs maybe a factor.
I would tend to look towards your girlfriend's Mac.
Since iChat 2 it seems that some failed chats seem to hold on to ports or have some hold over the Network going on.
It seems most common when in System Preferences > Network the drop down at the top listing "Location" is left at the Automatic Default.
There are essentially two fixes for this.
1) Set up another Location and copy the settings across and switch between the two to force the Network to re-establish itself.
2)A longer way of clearing what is going on.
a) Shut any Airport card down if using WiFi
b) Shut down the computer.
c) Disconnect any Ethernet cable from either Computer or routing device (whichever is easier to reach but leave the routing device still connected to the Internet - just isolate the computer from the Internet)
d) Restart the computer (this is with no Internet Connection)
e) Restart iChat.
f) Restart Airport card or plug in Ethernet cable.
g) Using the Buddy List, select Available and make iChat Login (can also be done from the iChat Menu (> Accounts submenu in iChat 4)
On your last paragraph I would ask if you can Video chat at this set of locations ?
This is because in this scenario a feature of one of the modems may be an issue.
Some modems and routers have DOS (Denial of Service) or SPI (Stateful Packet Inspection) protection. These tend to be threshold based and have no setting control in the devices set up pages (other than On or Off).
iChat can stream so much data, particularly in Video chats over what are now quite high Internet speeds that a DOS feature will consider it an Internet attack and cut the port involved. SPI tends to be judging whether the data stream is valid and does not seem to keep up and the result is the same.
In Video chats the end that has the Problem tends to get a Error -7 In the Log.
The Other end gets the "No Data for 10 Secs" message.
Summary.
Essentially though as you have tried a deletion of all the .plists for iChat and you imply both ends it is more likely something about the Network or how the Mac thinks Network resources are already allocated.
There is not an easy .plist deletion for this hence the two methods listed above.
NOTEs: 1) #8 in your list is not related to iChat.
This is what you can now use of Apple Remote Desktop itself. It has it's own Screen Sharing app (without Audio like iChat) that is invoked from the Finder's Go Menu > Go to Serve and entering a VCN:// IP address. (As a System Application, as it were, it is in /System/Core Services/Screen Sharing.app)
It does need both Macs to have the Setting Enabled as you have done it #8 though
2) Some ISPs it is suggested block Screen Sharing. (Verizon was the name I heard mentioned). How they tell what the data steam is specifically I do not know as it would seem that the Audio part of an iChat Screen share would make it look like an A/V chat and that Apple Remote Desktop must be a valid way of working for some people. However iChat is Peer-to-Peer in AV chats and Screen Sharing and some ISPs are known to actively work against these file sharing apps that bear the same generic term.
In your case I do not think this applies as you can Connect Off site via whatever ISP your Campus uses.
I hope this helps.
9:58 PM Wednesday; October 1, 2008

If remote access is allowed on the server, Then can my users on the local network access this server by ie

Dear all,
If my server is enabled for the remote desktop connection, then the users on the local network can access my server IIS services by entering the IP address of my server in the IE (http/https) on the local network only.
I went to control panel>>system>>Allow Remote desktop Connection>>with network level authentication.
Now If my team wants to access this server not by opening the Remote Desktop Connection, rather by entering the IP address of my server on the IE and access the resources offered.
Is it possible by this way,
Or is there any other method to do so.
Regards,
Ahmed

3. My web Developer is installing an application on the server for our department team. To test this application running, he wants to access this application through the local machine from browser (rather than logging in through the remote desktop connection).
4. He wants this application to run on the local network only.
5. He wants me to do some setup, that he must be able to enter the IP address of the server in the browsers address bar on his local machine and test the functionality of his application on the local network.
If this is the requirements of the developer, I guess he wants you to configure IIS.
You can do a test, whether IIS is working properly.
Log on to server, enter https://localhost or http://IP_address_of_the_server don't know whether some ports are configured in order for your IIS to work.
check out this youtube video:
https://www.youtube.com/watch?v=tNAdv1EPj-I
Every second counts..make use of it. Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
IT Stuff Quick Bytes

After the 10.9.2 upgrade I can't screen share with any Macs using Back to my Mac.

I did the 10.9.2 combo upgrade on a bunch of Macs I manage and now I can't use Back to my Mac for screen sharing on any of them. Does this upgrade mess with the original settings? Any suggestions? Anyone else see this?

Back to my Mac has been unreliable for me (and a lot of other users) ever since the Mavericks upgrade, 10.9.0.
I find that if I turn all screen sharing off, then back on again, remote macs can share my screen. But the fix usually lasts just a few days, sometimes as little as 24 hours.
So everything depends on me remembering to open Sys Prefs and then toggle Back to My Mac (in iCloud) and Remote Login, File Sharing, and Screen Sharing (all in Sharing) in the morning before I go to work. If I remember, I'm able to do screen sharing that day from work. If I forget, I'll get errors when I try to Screen Share via the link that appears under Shared in the Finder sidebar. The link is reliably present in the Finder sidebar, it just doesn't work if I haven't refreshed the Sys Prefs settings.
Hope this workaround is helpful. Wish they had a more permanent fix.

How can I 'screen share' from my Lion machine to my old Tiger mac?

I have a new MacPro running 10.7.3.
I have an old Mac desktop running Tiger (10.4)
I can't seem to screen share.
I want to remotely control the old Tiger machine from my Lion one.
I checked 'Remote Desktop' on the Tiger- but still no happiness.
I CAN mount the drives from that older computer just fine.
mark

Mark, sorry for any misunderstanding, CoVNC is only needed if you want to control the newer one with the old one.
On the old one enable...
Personal File Sharing
Remote Login
Apple Remote Desktop
Remote Apple Events
On the ARD choice click Access Privileges and fill in what & who can do what.
Easiest to sign into the old one with the old one's username & old one's PW if you checked that as OK on the old one.

Screen sharing on local network - broken on snow leopard

I will try to be clear:
problem is: cannot get a screen sharing window on mac mini when accessing from macbook pro on local network. Problem began after clean install on snow leopard all computers.
setup: 1 mac mini, two macbook pros (1 is 1st gen, 1 2nd gen), all connected through Airport Wireless N basestations.
filesharing works fine. all computers recognised.
when i connect to screen sharing, blue bar comes for a minute, then goes off, then on again, then after a couple more minutes just disappears. screen sharing does not give me an error message, just stops trying. please help, getting fairly desparate.
best,
Charles

This is not normal. Although I have no experience with screen sharing SL-to-SL, I have no problems connecting from my MBP running SL to several other machines running older systems.
What might be different between my setup and yours I'm not sure. But here are a few things:
1) At home, I'm also using an 'n' AirPort Extreme base station, but I'm using 'g' mode, because my MBP is the only machine in the house capable of 'n' speeds. No problems with the PB G4 or iMac G5 running Leopard.
2) At my wife's office, we're using a LinkSys router (not an 'n' router), and no problems accessing the screen of a headless Intel Mac Mini running Tiger.
3) You mention base stations, emphasis on the "s". If you have multiple base stations, that could be the problem. Have you tried simplifying the network so there's only one base station in use?
4) What settings are you using for Screen Sharing in System Preferences -> Sharing? Look both in the main window and in the window that pops up if you push the Computer Settings button.

Mac Mini drops out of "Shared" status in Finder of iMac - can't screen share-

I have a 27 inch mid 2010 iMac (with the WiFi problem fixed) 10.8.2
I also have a new 2012 Mac Mini. 10.8.2 + OSX Server (no monitor or keyboard/mouse)
(Both are connected via WiFi to a FIOS - Verizon/ActionTec MI424WR-GEN3I router.)
Randomly, the Mac Mini dropps out of sight to the iMac -- i.e. it no longer shows up in the "Shared" section of the Finder and, consequently I can no longer "screen share" with it.
However, OSX server continupus to serve up web pages as expected -- I can ssh into the Mini from the iMac with no problem (i.e. IP connectivity is fine). My Epson WiFi printer and my son's XP based PC show up in the "Shared" section of the FInder. Only the Mac Mini is missing.
At that point, the only way I know of to get the Mac Mini visible again is to do a "sudo shutdown -r" and viola it reappears in the Finder on the iMac.
Is there some other way to get the Mini to show up in the Finder of the iMac?
Is there some kind of "wake-up" command I can send from the iMac to the MIni via ssh?

Looks like half of the issue is answered... The WiFi in the mini DOES support WOL, as does the iMac.
However, the basic problem still remains --
The Mini is NOT sleeping, but actively running as a server 24x7 -- web and mail (I run my own domain) -- and I can log in to the mini via ssh -- but it is NOT visible as a shared device in the Finder on the iMac, and I cannot use screen sharing. Since the mini has neither keyboard nor monitor, I have to remotely reboot it via ssh - i.e. "shutdown -r" to get it to re-appear so I can screen share.
The timing is an isue. This "disappearence" seems to happen infrequently and irregularly, but has happened twice since I acququired the Mini on "Black Friday," not quite 30 days ago. If it were a simple "sleep" issue, I would have expected it to happen "hourly" or on some such frequency.
So, since WOL does not appear to be an issue in and of itself, I suspect I'll have to try to find out if "Shared Screen" is an "Advertised Service" via BSP.
Your link to http://superuser.com/questions/306651/wake-macbook-on-wi-fi-without-airport-extr eme is providing a lot of pointers. Now to spend some serious "Google time."
Since I'm working with the Verizon/ActionTec MI424WR-GEN3I router (FIOS), which seems to handle all of the various protocols without issue, I may have to dig out my old Airport Extreme.
Now retired, I sold my old 4 story Victorian and moved into a one-floor one-bedroom, and don't need the multiple routers I used to run to inorder for WIFI to cover the house. Sigh.
And to think "I thought" I retired from the world of System Administration
I have a query in to ActionTec to see if they have a configuation Option I have not "deciphered" which will deal with the WOW issue.

Mac Mini, screen share setup over network out of the box?

Greetings,
Is it possible to screen share and setup a new Mac Mini out of the box? Ultimately, I'm trying to figure out if I really need to purchase a separate screen just to setup the machine.
Thanks,

Hello,
den.thed wrote:
What other equiptment (HDMI TV, computers, etc...) do you have?
see > Setting up new mac mini without a monitor - Google Search
I have a MacBook Pro Retina, iMac, MacBook Air. I'll check out that link.

Can Time Capsule use another local network for backup?

Our LAN has a a separate wireless network solely for backup. The machines on the network use ethernet for routine operations and wireless to access backup disks. Can a Time Capsule access this backup LAN or must the machines all tune into its own wireless network?

Yes, you can. Just mount the disk you want to backup onto and select it in the Time Machine preferences. The backups are deadly slow wirelessly, so you'll want to backup with your mac getting it's internet over FireWire from the computer with the disk attached. But restoring works well wirelessly. As you can probably tell by my description here, I backup to a network volume myself. I do know that you can't backup to the same backup scheme both with a local disk and network volume (same disk).
Hope this helps,
Alex

My Mac-Pro can no longer see my local network after install

My older Mac-Pro hard drive died & I had to install Snow Leopard again from scratch. For some reason, now I can't see any of the Windows PC on my network. I CAN see the Internet (I'm on the Mac-Pro writing this) & I can see my old Mac with Tiger, but I can't seen any of the Windows XP or 7 systems. I know, they XXXX but, I still need to see them so I can taunt them & make fun of them etc...
Here's the troubleshooting part of the show:
I CAN ping them by name from Terminal & from the Network Utility.
I can NOT see them when I go to Finder > Go > Connect to Server & enter their names.
I've rebooted 4 or 5 times & installed the latest updates.
I could really use some help on this, I have about 20 computers on my network & I used to be able to see them all.

For anyone who may have this problem in the future, I thought I would post a reply myself on how I solved this problem.
The problem turned out to be my router. In the middle of the night I had an idea, so I rebooted my router & switches & now ALL the computers (even the Windoze ones) show up!

Can't screen share in messages osx mountain lion

Since upgrading to Mountain Lion, I have been unable to connect to someone else's computer via Messages and share their screen. I use this to help my parents with computer problems.
I have checked, and their "capabilities" do not show screen sharing, but I never had a problem with this before. Any suggestions?

Use the email form to contact Apple here > Apple - Support - Mac App Store - Contact Support

Can't screen share on local network

Similar Messages

Maybe you are looking for