Remote Desktop Admin - Scanner can't see clients.

Hello,
I have a couple of copies of Remote Desktop UNL admin packages that are used in a education environment. Remote desktop has been working great in all but one lab, where the scanner has trouble finding any machines. It may sporadically find a random machine, but most of the time only shows the machine it is on. I can ping the other machines from the admin station, and the network setup is simple - 24 computers plugged into two 12 port 10/100/1000 D-Link switches, along with a G5 server running only AFS and DHCP.
I've re-installed Remote Desktop, double checked my client settings, and to no avail. Anything I may be missing or should look at?
Thank you!

Similar Messages

HT5422 Different versions of Remote Desktop Admin 3.6.1

How do Remote Desktop Admin 3.6.1 from 24 Sept with Download ID SL1595 and 14.73 MB in size and another from 3 Dec labelled DL1570 and 14.75 MB in size differ? Perhaps this is a version labelling problem, the one from 3 Dec perhaps is actually 3.6.2? There's two separate support pages for the separate downloads, the titles are a little different with some juxtapositioning, "Apple Remote Desktop 3.6.1 Admin" and "Apple Remote Desktop Admin 3.6.1", respectively. My existing copy of Admin 3.6.1 only offers to update clients to Client 3.6.1; I installed Client 3.6.2 manually on the clients via downloading from the download page for it. Gonna wait on the Admin to see if Apple fixes this soon.

There's nothing to fix here. The newer 3.6.1 Admin updater only includes the latest 3.6.2 client software. This updates someone's system properly when they're coming from and Admin version prior to 3.6.1. If you already had Admin version 3.6.1 installed then then you'll be offered the 3.6.2 update on Lion systems. The update is not necessary for 10.8 - 10.8.2 as the only bug fixed was with iChat on Lion. Of course you can manually install the 3.6.2 client update on your Mountain Lion systems if you'd like.

Remote desktop admin 3.8

Is remote desktop admin for accessing my desktop from another device?

This update (1.1 and earlier currently) breaks screen sharing on OSX computers other than Yosemite. There is a bug in the software update.
They should have only updated Yosemite computers and not those still running earlier OSX versions.
There is an explanation on how to downgrade to 3.7 in another thread by UM-LinuxGuru:
"UM-LinuxGuruMar 24, 2015 1:09 PM Re: mavericks messages not screen sharing
Re: mavericks messages not screen sharingin response to David Vrooman
I happened to stumble across this issue. I loaded a test machine with a Mavericks 10.9.0 installer, then selected upgrades to see what would break it. It is RDC Update 3.8.2 v1.1. After spending time with AppleCare, they told me I might see a fix in a week. Right. I need a fix right now.
So, I used my 15 years of Linux diagnostic skills, and came up with a quick fix, which I will test further. I downloaded Apple Remote Desktop 3.7 Client . If you try to install it now, it will say, "Can't, newer already installed." Fine. goto /Library/CoreServices/, archive RemoteManagement, then put RemoteManagement in the trash (as admin), and empty the trash. Now run the 3.7 installer. I now have screen sharing again, while I wait for Apple's fix.
I will test updates 3.7.1 and 3.7.2 if I can find them."
Robert had a correction to this instruction:
"One correction: the path to the Remote Management folder is: /System/Library/CoreServices/ (not /Library/CoreServices/)"
Yosemite Messages Screen Sharing Broken?
The ARD client 3.7 solves screen sharing problems on non-Yosemite computers until they make the upgrade.

Apple Remote Desktop Admin 3.7.2 Yosemite wake issue

Another serious problems is.... Apple Remote Desktop Admin 3.7.2 in Yosemite cannot wake up clients Mac remotely. Control has no problem after waking up.
On 10.9.x I can wake up remote Mac clients if sleeping. Now I have to do it on the other Mac running older OS version.

I have a different issue.
Just updated s classroom full of computers and desktop client will no longer observe more than on computer at a time. I can no longer observe groups of computers. Any thoughts on this issue guys? Mac OSX Yosemite 10.10

HT201068 I updated Remote Desktop Admin 3.8 and now my Time Capsule wireless connection is having.

I recently updated to Remote Desktop Admin 3.8 and since then, I have had issues with the wireless connection from my Time Capsule.
1) I reset modem and had no change. 2) I then plugged the ethernet directly into my Mac and the connection was great so it's not the service or modem.
3) I hard reset the TC and when it came back, the speed was good but went back down after a few minutes. 4) Plugged ethernet directly into Mac and again, the speed was great so it is definitely the TC.
Would love some help resolving this. Hoping I don't have to get a new wireless router. Maybe the TC is too old? I purchased it in 2009 or 2010/ Current version 7.6.4

Hey evebutterflies,
I see that you are having some connection issues with your Time Capsule. Are these issues only present when using Remote Desktop Admin 3.8? If so, you may need to review the information in the following article and see if this sheds some light on the issue:
Apple Remote Desktop: Troubleshooting Connection to Client Behind NAT Router
http://support.apple.com/kb/TA20780
Thanks for coming to the Apple Support Communities!
Cheers,
Braden

HT201068 Updated Remote Desktop Admin 3.8 and now my Time Capsule wireless connection is slow

I recently updated to Remote Desktop Admin 3.8 and since then, I have had issues with the wireless connection from my Time Capsule.
1) I reset modem and had no change. 2) I then plugged the ethernet directly into my Mac and the connection was great so it's not the service or modem.
3) I hard reset the TC and when it came back, the speed was good but went back down after a few minutes. 4) Plugged ethernet directly into Mac and again, the speed was great so it is definitely the TC.
Would love some help resolving this. Hoping I don't have to get a new wireless router. Maybe the TC is too old? I purchased it in 2009 or 2010/ Current version 7.6.4

Most home routers running 24/7 are good for about 3years.. your TC has now managed to survive 6 years.. it is well and truly time for a replacement. Simple fact is, it should be dead by now.. so you are living on borrowed time whatever happens.
Why RDA would slow the wireless I am not sure..
Are you running Yosemite.. ?? I tend to point the finger at the OS rather than an application.. mind you if the amount of data going back and forth has increased.. what appears to be slower wireless might actually be something else.
Apple has reasonable wireless analyser built into the OS since mountain lion.. it is well worth using.
http://osxdaily.com/2012/07/31/wi-fi-scanner-mac-os-x-mountain-lion/
I recommend doing a few things like short names, no spaces pure alphanumeric for everything in networks. Passwords also must comply. Apple made changes to network protocols since Mavericks but did not fix the names being recommended in the airport utility.. and still haven't which break their own rules.
And fix names for bands differently so you can force the connection.. plus setting channels.
However in a unit of that age.. it will have pretty weak 5ghz and that is what is important for high speed wireless.. Apple have hindered 2.4ghz since forever.

Apple Remote Desktop admin update now won't open 3.5.1

So a few days ago I updated Apple Remote Desktop admin and now the program won't launch. It says that the admin version is not compatible with the client. I went to apple's software updater and it doesn't show that anything needs to be updated on the client side. Any suggestions?
Running on:
Mac Pro
Snow Leopard 10.6.8

Okay thanks, dragging the old app to the trash and logging into the app store did it. What threw me a bit is that it was asking for my credit card info in order to process the download. Evidently it only was doing this because it had an old card stored in the system. I don't THINK it charged me to download again .

Remote Desktop Connection Manager can't stop Reconnecting

I use RDCM in different customer sites to connect to their Windows Server 2008/2008 R2 servers. Typically the server on which RDCM is running on is Windows Server 2008 Standard SP2 (64-bit). In some sites, when I disconnect from a server, instead
of completely disconnecting, the session turns gray and a "Reconnecting" window pops up:
Pressing the Cancel button simply grays out the button and I can never actually disconnect until I exit RDCM and restart it. "Disconnect group" doesn't help either. It seems like the problem occurs always in some sites and never in
others.
Is there a fix for this annoying problem?
David Collacott

Hi David,
The RDS feature is also available on Server 2008 but just the name is different, on server 2008 it’s called Terminal Server. So you can able to find the option “Set time limit for disconnected sessions” or the
session is active then you can choose the option “Set time limit for active Terminal Services sessions
“under below mention path.
User Configuration\Policies\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Session Time Limits
Please refer “Session Time Limits” for more guidance. In addition you can refer below article for Remote Desktop disconnection issue with server 2008.
Remote Desktop disconnected or can’t connect to remote computer or Remote Desktop server (Terminal Server) that is running Windows Server 2008
http://support.microsoft.com/kb/2477133
Hope it helps!
Thanks.

Remote Desktop Admin 3.4

Hello
When upgrading my admin computer, I'd to buy a license of compatible version of Remote Desktop Admin, I mean 3.4.
I connect wo problem, however my remote keyboard is seen as a Qwerty keyboard.
Although I found many threads complaining with this, I haven't found any solution.
I cannot imagine to work like this ; passwords are impossible to enter.
Please, tell me someone know how to fix this ?

Probably get a reasoned response posting to the ARD forum: http://discussions.apple.com/forum.jspa?forumID=1007

When I launch a video from Finder the video is not visible, it's like it's playing on an extended desktop but I can't see the other screen - what is going on?

When I launch a video from Finder the video is not visible, it's like it's playing on an extended desktop but I can't see the other screen - what is going on?

Hi Dan - I'm not sure I know what you mean by 'kick in Expose', can you please explain?
It's a weird one as it doesn't happen all the time. Could it have anything to do with running Apple TV and the MacBook 'thinking' there is another display (extended desktop) and playing the video there?

Software Update on New MBA lists Remote Desktop Admin 2.2 but fails

Using my new MacBook Air running Lion, when I run Software Update, it comes up with one item, Remote Desktop Admin Update 2.2, which is old software. I don't have any version of Remote Desktop Admin installed. If I try to do the update, it fails. Any idea what's causing this or how to resolve it? Thanks!

Several places to look for crude that may fool ur mac into thinking it's installed outside of the /applications dir which I assume you checked already, right?
in user/library/application support
in system/library/preferences
in system/library/applcation support/apple
Outside of cleaning up the files, you could try the ARD support forum also here.

Remote Desktop 2012 R2 - Can't get RD Gateway with RD Web Access working through just 443

I have one server (2012 r2 fully updated) running all remote desktop roles (RD Web Access, RD Gateway, RD Licensing, RD Connection Broker, RD Session Host) and a separate domain controller.
I have RD Web Access published to cloud.mydomain.co.uk and accessing cloud.mydomain.co.uk/RDWeb works fine.
I want to setup the environment so only port 443 is open from the outside (thus the RD Gateway is installed) and the user can login through RDWeb and click on an app to launch it.
If I leave port 3389 open along with 443 and log on to RDWeb and click the remote app, this works fine.
If I close 3389 on the external firewall and only leave open 443, I can connect AND login to RDWeb but I cannot open the connection
This is expected:
http://i.imgur.com/9j2HRqm.png
Error:
http://i.imgur.com/2LH2c7T.png
Digging in the event viewer yielded: http://i.imgur.com/M9uHm0o.png
Which led me to test change the following setting in the resource access policy, as a test:
http://i.imgur.com/FlGObFr.png
This still didn't work but yielded a different error in event viewer:
http://i.imgur.com/LkaCfU4.png
Now I suspect I have misconfigured something somewhere in terms of the last event where it suggests it can't connect to resource "cloud.mydomain.co.uk" I would have expected this to be the internal FQDN of my session host. Or, I am hitting some sort
of odd problem because I have all the roles on the same box.
Any assistance greatly appreciated. I'm keen to find the root cause behind this as I need to document this solution so don't want to invalidate by messing around too much with settings.

Hi Gavin,
If you use RD Gateway then you only need to open TCP port 443 and UDP port 3391 and forward them to your RD Gateway server. You may have RD Web Access (uses TCP port 443) and RDG running on the same server.
When an external client launches a RemoteApp they will connect to your RD Gateway via TCP port 443 and UDP port 3391, then the RDG will connect to your internal RDSH servers using TCP port 3389 and UDP port 3389 on behalf of the external client. In
this way the RDG will act as a middleman between your external users and your internal RDSH servers.
In Server Manager - Remote Desktop Services - Overview - Tasks - Deployment Properties you need to specify the external FQDN of your RD Gateway server. If you have RDWeb and RDG on the same server this would be the same FQDN that your users will use
for RDWeb. For example, if your users use https://rds1.yourdomain.com/rdweb to connect to your RD Web Access site, then you would enter rds1.yourdomain.com for the RD Gateway name in deployment properties.
(Above one Quoted from this thread answered by TP).
In addition please see that you have properly configured RD Rap & RD Rap policy under RD Gateway manager and also properly configured certificates to match server name.
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Remote Desktop Admin 3.2 Freezes with Spinning Wheel

I have an Intel MacBook and Intel iMac, both with 10.5.1 installed. I use them to admin a classroom full of iMacs. After logging onto the computers today I noticed that I can not get Remote Desktop to function. Every time I open it I get the spinning color wheel that never stops. I can not do anything with it. I made sure I had the latest updates to the software. Still nothing. I reset my PRAM and Power manager. No Luck. I reinstalled the application. No luck. I manually removed everything emote desktop related and then reinstalled and still no luck. Anyone have any solution advice.

I am also having the same issue on 2 machines. A MacBook Pro and a MacPro. When I look in the console, this is what I see :
Dec 10 10:57:35 Hercule /Applications/Remote Desktop.app/Contents/MacOS/Remote Desktop: error connecting 61 Connection refused
Dec 10 10:57:35 Hercule /Applications/Remote Desktop.app/Contents/MacOS/Remote Desktop: unable to connect to agent - try again
Dec 10 10:57:36 Hercule /Applications/Remote Desktop.app/Contents/MacOS/Remote Desktop: AgentListenerThread messageSize bad 3892510720 67108864
Dec 10 10:57:36 Hercule /Applications/Remote Desktop.app/Contents/MacOS/Remote Desktop: AgentListenerThread messageSize bad 134217728 3892510720
Dec 10 10:57:36 Hercule /Applications/Remote Desktop.app/Contents/MacOS/Remote Desktop: AgentListenerThread messageSize bad 67108864 134217728
Dec 10 10:57:36 Hercule /Applications/Remote Desktop.app/Contents/MacOS/Remote Desktop: AgentListenerThread messageSize bad 3892510720 67108864
I have tried to do a clean install of the app in the MacPro, but I still get the same message. Lovely.
Mack

Remote desktop connection issue with an RDP client while connecting to some of windows 2008 and 2003 operating system flavors and not receiving SDin value choice 26 from DomainMCSPDU

Hi Team
We have our RDP client and i came across with one issue "Expected data got 3" with this client.
This issue is getting while connecting some of below operating system flavors.
Microsoft Windows 2008 Enterprise edition
Microsoft Windows 2008 Standard edition
Microsoft Windows 2003 servers
When we are trying to get RDP to those servers with our client, getting "Expected data got 3" error. One more main thing here is the specified error is not getting for all the servers of same operating system in above list.
Able to get the RDP console for those servers using mstsc client.
When i read the [MS-RDPBCGR] specification, i found the below points
mcsSDin (variable): Variable-length PER-encoded MCS Domain PDU (DomainMCSPDU) which encapsulates an MCS Send Data Indication structure (SDin, choice 26 from DomainMCSPDU), as specified in [T125] section 11.33 (the ASN.1 structure definitions
are given in [T125] section 7, parts 7 and 10). The userData field of the MCS Send Data Indication contains a Security Header and a Valid Client License Data (section 2.2.1.12.1) structure.
In my code i am not getting SDin value as 26. Is it the problem with Remote desktop Licensing in RDP servers as specified in the specification like "The userData field of the MCS Send Data Indication contains a Security Header and a Valid
Client License Data (section 2.2.1.12.1) structure."
Could you please explain me is this issue is happening due to Licence configuration in RDP server and please provide support with server side configuration if any because our code works for other servers ?
Thanks & Regards,
Pavan G.

Hello Pavan -
Thanks for contacting Microsoft Support. I'm researching this for you and request you to please send me mail at dochelp @ Microsoft dot com so that I can share tools and techniques to collect some traces and analyze.
Thanks.
Tarun Chopra | Escalation Engineer | Open Specifications Support Team

Office 2010 Outlook Desktop/Office 365 Issues-Cannot connect to the desktop in Outlook, Can't see more than 6 old messages in Office 365

Hello,
I'm hoping someone can help me out. I'm having an issue all of a sudden with connecting staff members to Outlook 2010 desktop version. Our super kept having issues, so we disconnected her from the desktop, and tried to reconnect her. I wish I wouldn't have
done that, now I can't get connected back up. We thought we would login to the web version so that she could check her e-mails, which is fine. She can get new e-mails just fine, but she can only see 6 old emails, and she has 100's of old e-mails. Someone please
help, I'm about ready to pull my hair out!!! Very frustrating. :)
Thank you in advance,
Ang

Hi Ang
So this is an Office 365 (Exchange-based) email account? Do you mean you've deleted the specific account from Outlook client and tried to re-add it again?
"now I can't get connected back up" - At which step will it fail? Any error messages when things go wrong? Please first check the account settings that you've entered, and make sure they are correct.
"She can get new e-mails just fine, but she can only see 6 old emails, and she has 100's of old e-mails."
- With web mail portal, you are connected to your mail server directly. If you are referring to the web-based mail portal here, then these old mail messages probably have been deleted from the server.
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Remote Desktop Admin - Scanner can't see clients.

Similar Messages

Maybe you are looking for