Client no longer visible in Remote Desktop

For years I've controlled my Mac Mini from my MacBook over my home Wifi, but all of a sudden it's stopped working. The client (Mac Mini) is no longer visible in "Scanner", and will not connect via IP address 192.168.0.3
I've confirmed both computers are definitely on the same WiFi network, sharing options are turned on in Mac Mini's sharing preferences. I've deleted ARD prefs file from the client, I've restarted both machines.
Client is also not controllable from the VNC apps I have on my iPhone and iPad - so I think it's a client issue rather than the MacBook running ARD.
Any advice of things I can check? I've also just noticed that (despite being switched on) the Mac Mini is not visible for File Sharing. So there's definitely something fishy going on with that Mac Mini's network settings.

****. Seems I didn't try rebooting the wifi router. It's showing now. **** cheap netgear rubbish...

Similar Messages

PXE Boot a client to connect to a Remote Desktop Session Host/Terminal Server Farm via SCCM 2007

Hi all,
we've got a bunch of old desktops which are destined for disposal but i was wondering if we couldn't use them as disk-free clients to connect to our Remote Desktop farm. I did some digging and have managed to put together an iso which will boot
the machine into WinPE and then connect to our farm. However, since it's an iso i have to use either a cd or usb for this to work. (This is pretty much what i did: http://www.iammacgyver.com/2011/02/easy-rdp-60-from-winpe-30-simple-boot.html)
What i want to do is to advertise the boot.wim to the client via SCCM so that it boots via PXE and then picks up the WinPE image and connect to the RD farm. I've imported the boot.wim file into SCCM under Boot Images and created an empty Task Sequence
with the boot.wim as its Boot Image. I then advertised this Task Sequence to a collection which contains the old desktop clients. The machine PXE boots ok and loads up WinPE but rather than launch a remote desktop connection, it trundles through the normal
WinPE stages and once it's finished 'Preparing Network Connections' it simply ends and the client reboots.
Is what i'm trying actually possible?
Can anyone tell me why the ISO works yet pushing the boot.wim out as a Boot Image doesn't? I know the boot.wim file (which is the same one present in the ISO) is ok since the client boots into WinPE fine when PXE booted so why doesn't the remote
desktop session conenction launch? How is booting from the ISO different from booting from the PXE boot.wim file?
Slightly long winded problem so many thanks in advance to anyone who can pass some info my way!

It doesn't work because importing it into ConfigMgr injects binaries and the task sequence engine along with the process to launch the engine thus suppressing whatever you've got configured.
Perhaps you could use a pre start command (pre-execution hook in 2007 parlance) to launch your RDP process though.
Jason | http://blog.configmgrftw.com | @jasonsandys

I have just installed 10.7 and bootcamp is no longer visible on my desktop, nor can i start computer in windows mode. I started the bootcamp 4.0 upgrade assistant, but don't want to wipe windows 7 out and lose my data. Any suggestions?

I have just installed 10.7 and bootcamp is no longer visible on my desktop, nor can i start computer in windows mode. I started the bootcamp 4.0 upgrade assistant, but don't want to wipe windows 7 out and lose my data. Any suggestions?

I have just installed 10.7 and bootcamp is no longer visible on my desktop, nor can i start computer in windows mode. I started the bootcamp 4.0 upgrade assistant, but don't want to wipe windows 7 out and lose my data. Any suggestions?

Why can I no longer use my remote Desktop Apps?

I have the unlimited data plan on my Droid Razr (I know its a tad dated) and was able to use these apps flawlessly until about 2 months ago. It says that I am unable to reach the host due to the configuration of the network I am using. Wifi still works and connects at home, but it seems that there are issues when trying to do so via both Google remote desktop app and Splashtop. Any help would be greatly appreciated!

Let's look further into this nkfitz1313! Did anything specific take place when this began (new phone, update)? Have you tried working with your home internet provider to try changing the beginning and end ranges of the IP range on your router? Please share more details. Thank you.
TominqueBo_VZW
Follow us on Twitter @VZWSupport

Windows Embedded 8.1 Industry Pro Application Launcher Remote Desktop Services Feed VDI with Windows Store Remote Desktop Client

I wanted to make kiosks which are joined into a domain and set up with an Remote Desktop Web Feed with VDI Desktops (to support Single Sign On and minimize configuration needs on the client side). And I wanted to lock those Clients to launch only the Remote
Desktop Windows Store application. And if somebody clicks on a Desktop Pool then connect to the choosen Pool. But instead of doing this the Remote Desktop application opens the Pool within the old mstsc.exe and right after connecting the OS switches the focus
back to the Remote Desktop Windows Store application. And nobody can work in the office with this configuration.
So how can I correct this problem? Any other solutions? What is the official way to doing this?

Hi,
Based on my test, we cannot associate .rdp files with the Remote Desktop Windows Store App. Therefore, you may have to use MSTSC or configure the setting in the Remote Desktop
Windows Store App manually.
Best Regards.
Jeremy Wu
TechNet Community Support

Remote Desktop not listed in Applications, but installation says it's already installed

When I try to install Apple Remote Desktop, I get a message that says a more current version is already installed. I look in Applications and see no reference to Remote Desktop.
1) Does Max OS X Lion 10.7.3 come with Remote Desktop installed, as some documentation suggests?
2) If so, where is it?
I'm trying to remote from macBook Pro to a windows server via ip address

If you are connecting from a Mac to a Windows server,
you should really be using Microsoft Remote Desktop Mac.
Get it here:
http://www.microsoft.com/mac/remote-desktop-client
As far as Apple Remote Desktop, each Mac ships with the
server. It is the client, what you use to connect to another
mac, that requires a download and is $79.99 at the MacApp Store.
The server function is integrated into OSX and is not visible as an
app.

After MS13-098 and SecurityAdvisory(2915720), Windows Server 2003 Remote Desktop(TermService) cannot start service

I have trouble with Windows Server 2003 R2 Standard. I installed the KB2893294(MS13-098) patch, and I changed the registry that is suggested actions of Security Advisory(2915720) http://technet.microsoft.com/en-us/security/advisory/2915720
Suggested Actions:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Wintrust\Config]
"EnableCertPaddingCheck"="1"
After rebooting the event viewer(system) says:
Event Type: Error
Event Source: TermService
Event Category: None
Event ID: 1014
User: N/A
Description:
Cannot load illegal module: C:\Windows\system32\rdpwsx.DLL
After I cannot use Remote Desktop Connection from other client.
So I check the all security patches and other hotfixies. I checked the KB2653956 and KB958476.
But TermService do not recover the error.
And then, I delete the "EnableCertPaddingCheck" registry and reboot systems.
TermService have no error. I can use Remote Desktop Connection from other client.
After KB2893294 installed, Remote Desktop Connection cannot use from other client that "EnableCertPaddingCheck" registry set to "1".
Other Windows Server 2008 systems do not effect the KB2893294 patch. But All Windows Server 2003 systems cannot use the Remote Desktop Connections after the KB2893294 patch.

Update on this issue:
The debug team has accepted the issue and has identified it as a regression. Right now they're targeting *June* as the release date for a fix. I'm attempting to educate them that customers don't just install patches the day (or even month) they're
released and that the fix needs to be moved up in priority to give a minimum of 60 days to install the patch before the time-bomb explodes.
In the meantime, a workaround has been provided that will turn off the new functionality. Note that I have not yet had a chance to test this. It entails creating a new DWORD registry entry--UseLegacyPE--and setting it to 1.
HKLM\Software\Microsoft\Windows NT\CurrentVersion\ImageHlp\UseLegacyPE
I will update this thread when I have further information.

Windows Server 2008 R2 Remote Desktop - The requested session access is denied

Hi, I have been using Windows Server 2008 R2 since it was released, and have 100 servers up and running. I configured Allow Remote Desktop on all of them and have been able to connect to them and manage them via RDP since then. I also have two servers configured as Remote Desktop Services.
That was up until yesterday. Yesterday afternoon I started getting the The requested session access is denied. I managed all Terminal services via Group Policy and have three users entered.
I am connecting to the servers via Windows XP SP3 and Windows 7. Both clients have been updated to the latest Remote Desktop Services client.
I have been searching for the answer, and I am not finding it.
I have also tried KB954369 without any success.
Thanks,
Brian

Ok, from my trials and tribulations and discussions with Microsoft I have identified the following;
Assumptions;
A. My terminal server is in domain widget
B. All the users are in domain contoso
1. I had the Terminal Server configurured with a specific Login, which would launch a specific application only and not give them any desktop functions. Wiht this configured this way, I get the error I wrote about.
2. If I turn the specific login off, then I can login normally and perform the functions as Administrator that I need/want to do.
3. Microsoft said to configure the Terminal Server with Single Sign-on. I did as instructed and went thru all the steps, however because my terminal server is in domain widget, the users get prompted twice each time for login. Once on the website, and then again as the application launches. Microsoft said that the users needed to Remote Desktop Client 7.x or the self-signed certificate that I have has to be included in the domain contoso certificate authority so that they will not be prompted for the second sign-on.
4. Conclusions - I need to have a chat with our enterprise security team about including the self-signed certificate in the contoso certificate authority. I need to also work on my RDWeb website so that it meets our company standard look.
Here are the links that Microsoft provided;
http://technet.microsoft.com/en-us/library/cc772108(WS.10).aspx
Enable RDC Client Single Sign-On for Remote Desktop Services
http://technet.microsoft.com/en-us/library/cc742808.aspx
Blogs -
http://blogs.msdn.com/rds/archive/2007/04/19/how-to-enable-single-sign-on-for-my-terminal-server-connections.aspx
http://blogs.msdn.com/rds/archive/2009/08/11/introducing-web-single-sign-on-for-remoteapp-and-desktop-connections.aspx
http://blogs.msdn.com/rds/archive/2009/06/05/publishing-in-windows-server-2008-r2.aspx
http://blogs.technet.com/pfe-ireland/archive/2008/09/05/windows-server-2008-terminal-services-presentation-virtualisation-and-windows-xp-clients.aspx
I hope this help you in your troubleshooting.
Brian

Drag copy in Remote Desktop 3.7.2

Drag coping a file from Remote Desktop Admin computer to Remote Desktop client does not work in remote desktop 3.7. It does work in the other direction. when dragging from client computer to admin computer. I have downgraded to 3.6.1 on my Mountain Lion computer to get this functionality back however the 3.6.x version is flakey at best running on Mountain Lion. Is this going to be fixed? I was excited to see the 3.7.2 version release today but was disappointed to find that drag copy still does not function properly.
I am not sure if this is the 3.7.x Remote Desktop Admin app that is malfunctioning or the 3.7.x ARD client agent that is at fault or a combination of both.
Drag copying is a vital function of ARD that I use all of the time.
Any insight would be greatly appreciated!

disable remote management on client
enable screen sharing on client
enable remote management on client
It works for me

The Remote Desktop Administrator software does not match......

The Remote Desktop Administrator software does not match the installed Client software version.
The Remote Desktop Administrator software must be upgraded on this computer.
This is the message I have when I installed ARD 3.0 on a new Imac running leopard with no ARD installed previously when I opened up ARD for first time - doesn't let me go any further.
Have I missed something here and made a stupid install mistake??
Many thanks
Message was edited by: art_ik

Please search the discussions before posting as this question has been asked and answered more than once.
If this is ARD 3.x, try this:
• Insert your ARD CD
• Open in Finder
• Right click on the Remote Desktop.mpkg and show contents
• Navigate to contents/installers
• Drag the RemoteDesktopAdmin.pkg file onto the workstation and install
• Run Software Update
• Upgrade to 3.1 admin
Otherwise, you'll have to completely uninstall ARD and then reinstall it. Follow these instructions for the uninstall:
http://docs.info.apple.com/article.html?artnum=108021

Remote Desktop Connection no longer works.

After verifying that all Remote Desktop Connection settings and firewall settings match the requirements, I cannot connect to the host computer running Windows 8.1 Pro with Media Center from a client computer running Windows 7 Home Premium SP1 over my
home (private) network. I was previously able to connect these same two computers when the host computer was running Windows XP Pro, but now that I have upgraded its operating system to Win 8.1 Pro the connection no longer works. The Windows Troubleshooter
cannot find the problem. What is wrong?

If you turn off a firewall in a router it is still using NAT which will also act like a firewall. In my experience its better to let your router be the firewall.
On most routers that have an SPI firewall you have to setup 2 rules to allow remote connections. One would be the firewall rule and other would be the port forwarding(NAT) rule.
Are you forwarding the correct ports to your mac from the router? Does your Mac have a fixed IP address?

Messages.app no longer connects to Jabber after App Store auto-installed Remote Desktop Update 3.8.2

Messages.app no longer connects to my company's Jabber server after App Store auto-installed Remote Desktop Update 3.8.2 (even though I never purchased that app). The Remote Desktop app can not be found anywhere on my machines.
I suspect the Remote Desktop update because Messages stopped connecting on my office MB Air after the update but still worked on my home iMac. Next day the iMac received the update and Messages stopped connecting on that machine too.
Messages attempts to connect for several minutes (it's been trying for 30 mins as I type this) and just hangs. Occasional I get the following error message:
Error: Messages lost the connection to the Jabber account 'account'. A network error occurred.
I've tried:
- Deleting and recreating the Jabber account in Messages.app
- Toggling on/off SSL (SSL required by our server)
- Toggling on/off auto detect server and port (port 5222 on our server)
- Deleting every plist, cache, etc., I could find in the Library for any IM client I've ever used
- Checked that Keychain trusts the Jabber server SSL certificate (it is a self signed cert)
- Tried connecting from three completely different networks including the company VPN
- Multiple PRAM resets
- Setup a Google Talk account in Messages - works fine
I'm at a loss...
Kurt

I installed and setup Adium. Adium works but Messages.app still does not connect to Jabber.

Mac Mini not visible in Mac network (shared drives, remote desktop)

Hi,
I got the following problem since a few months and can't figure what the problem could be.
My Mac Mini in not visible on my other macs in Finder oder Path Finder.
With unsing Apple + K shortcut I can connect to alle Mac Mini drives.
- Both machines have 10.8.4. installed
- Router is a Time Capsule
-> MBP connected via WiFi
-> Mac Mini via LAN cable
- IP Adress will be set via DHCP (static IPs won't help, tried that of course)
- Remote Desktop und Sharing is activated on both machines within preferences
- MacMini sees my MBP und my GFs MB
- MBP is able to see my GFs MB, but not my MacMini
- No Firewall acticated on both machines
- rights have been checked and repaired with the harddrive tool
Anybody an idea what I can try next?
Thanks!

Error resolved. It's was obviously my fault...
I changed the plist to deactivate multicasts a long long time ago
http://blog.tsunanet.net/2010/02/how-to-disable-bonjour-on-osx-106-snow.html
After deleting the entire line my mac mini is visible again.

What is Remote Desktop Client Update v 3.8.2

Why do I need Remote Desktop Client Update 3.8.2

It's just something that comes built into every Mac. You can either download it or right click the update and choose "Ignore" or "Hide". It's a very small update that doesn't take long to download or install so it's probably easier in the long run just to click the "Update all" button in the App Store when you see more than one update available along with 10.10.2 for example.
You can also have these updates install automatically. See the bottom of the first link "App Store preferences" for how to do this:
Mac Basics: Mac App Store is the built in way to purchase and update software - Apple Support
Update OS X and App Store apps on your Mac - Apple Support
Software update, upgrade--what's the difference? - Apple Support

Apple Remote Desktop-client mac issue

     Dear all,
               I have using Apple Remote Desktop 3.7.2 on maverick,in that some of the client machine also visible offline, but i can take remote.
i don't no why.plz help me
Regards,
Venki

Yes I've tried to ping the IP address and I get a reply.
I've just discovered this morning that the issue appears to be with Apple remote desktop.
The issue came up again this morning...I ended up shutdown ARD completely then loaded it back up, and guess what! The MAC address was showing up properly. I've discovered this is working for SOME of my issues. For the ones that weren't displaying properly I deleted the computer account out of ARD and then manually added the computer though a scanner import via single network address. The scanner finds the computer and it displays the correct Ethernet ID.
So I’m guessing there is a bug with ARD and its mixing up/displaying the wrong Ethernet ID of some machines....
Q

Client no longer visible in Remote Desktop

Similar Messages

Maybe you are looking for