Problem connecting to the Admin Session Microsoft Remote Desktop Mac 8.0.12 (Build 25282)

I try to connect to an RDP Admin Session (there are two normal connections at the moment). It will not let me giving me the following errors. Previously I could have a total of 3 sessions, 2 normal and one admin. I can still connect to the admin session
using the older iTap RDP.

Hi,
There is same issue with other users, already forwarded issue to product group for further research.
OSX: Connecting to admin session not working anymore since 8.0.12
https://social.technet.microsoft.com/Forums/en-US/4c3c36f0-d272-4e54-be70-91d2b92f292e/osx-connecting-to-admin-session-not-working-anymore-since-8012
Thanks for your understanding and Support!
Regards.
Dharmesh Solanki
TechNet Community Support
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]

Similar Messages

Problems connecting to the Admin Server

My browser can't connect to the Admin Server. Why not?

If you cannot connect to the Admin Server, ensure that the masks of
Hosts and Addresses entries in /admin-serv/config/ns-admin.conf
include the host and address you are connecting from. After changing
these parameters, stop and start the Admin Server by running the shell
scripts /stop-admin and
/start-admin.

Thanx for the reply Shane.
i had just stumbled upon the imap log before seeing your answer. i've found and fixed the problem.
the imap log showed the following message
Access to imap service for user@domain denied from client address (*mailAllowedServiceAccess)while the http log showed the following message
Access to smime service for user@domain denied from client address (mailAllowedServiceAccess)after some digging, i understood that th mailAllowedServiceAccess is a user profile property.
For my non-admin user, it was set to +imaps:ALL$+pops:ALL$+smtp:ALL$+http:ALL i modified it to include simple imap and the problem was solved.
ps: some threads that pointed me in the right direction
[http://forums.sun.com/thread.jspa?threadID=5361414]
[http://forums.sun.com/thread.jspa?forumID=708&threadID=5099841]
[http://forums.sun.com/thread.jspa?forumID=708&threadID=5401855]
Thank you very much for your help
Pier

Issue connecting through Microsoft Remote Desktop Mac - Yosemite 10.10.2 - Remote Desktop Mac 8.0.13

Hi there,
Recently at my office I have noticed an issue when I attempt to remote in using my MacBook Air. I can remote in using my iPhone & iPad, just not the MacBook.
I am able to add a Remote Resource but when I attempt to connect, I just get a white screen rather than a security warning like I do on both my iPhone & iPad. Does anyone have any solutions for this? It appears to be an OS problem.
Unsure if Microsoft is aware of this?
ANY help would be much appreciated.

Hi,
Can you run other application properly on your MacBook Air?
Never seen this kind of issue before. For a try check with other MAC device and verify the result. Also can reinstall the app. For further research please collect log as below.
Microsoft Remote Desktop>About Microsoft Remote Desktop>Send log via email
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]

Microsoft Remote Desktop

Hi,
i am trying to connect to my office using Microsoft Remote Desktop, a rav3 connection and a macbook. Intermittently i can connect OK but often see an error message saying that I'm unable to connect and the remote PC may be off. If i reboot my
macbook then i can usually connect. is there anything i can do to avoid keep rebooting my macbook?
Thanks

Hi,
Thanks for your post.
For the Remote Desktop Client configuration on MAC, did you refer to this ms article?
Getting Started with Remote Desktop Client on Mac
https://technet.microsoft.com/en-us/library/dn473012.aspx?f=255&MSPPError=-2147217396
Regards.
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]

Typo in error message from Microsoft Remote Desktop for Mac

Just found a bug in error message from Microsoft Remote Desktop (Version
8.0.9 (Build 25073))

Hi Sergey,
Thanks for your feedback, i will update to the product group.
Regards.
Dharmesh Solanki
TechNet Community Support

Problem connect to my office PC with Microsoft Remote Desktop from my MAC OSX 10.9.1

When I try to connect, I get the following message "Java (TM) is required to display some items on this page" and then a prompt to install Java, which I did already, and verified that it is running on my machine. I have downloaded Chrome
vs Safari for use since Safari is not compatible with Java version. HELP!!
CDr

Hi,
As far as I know, Java is not required for the Microsoft Remote Desktop client for Mac.
Please make sure that you download and install this App for the link below.
https://itunes.apple.com/us/app/microsoft-remote-desktop/id715768417
Getting Started with Remote Desktop Client on Mac
http://technet.microsoft.com/library/dn473012
In addition, if issue persists, please provide us screenshots for further research.
Thanks.
Jeremy Wu
TechNet Community Support

Hi there , i use microsoft remote desktop to connect to my work pc - on my 21.5 mac the remote screen is half the size of my screen and i cant get it to be full screen - is this possible or am i just stupid ? many thanks

Hi there , i use microsoft remote desktop to connect to my work pc - on my 21.5 mac the remote screen is half the size of my screen and i cant get it to be full screen - is this possible or am i just stupid ? many thanks

What setting have you chosen in the view menu? Fit to Screen or Window.
And, in Preferences what have you set for Display?

Can't connect remote PC with Microsoft Remote Desktop for Mac after using a new router

I'm using a Windows 8.1 computer as a HTPC to download files and I set it logins automatically and I just need to press the power button then use RD for Mac to control the HTPC without extra monitor, keyboard...
Here is the problem: After I took my Mac and HTPC to another place, I can't connect it with new router now. (I change the PC name to new local IP, nothing else changed)
It shows on screen that:
Unable to connect to remote PC. Please verify Remote Desktop is enabled, the remote PC is turned on and available on the network, and then try again.
I can use shared disk drive of the HTPC on my Mac so I know the connection works.
Thanks!

Hi,
Thank you for posting in Windows Server Forum.
Generally, if it is a home network environment, please use IP address of the target computer as the PC name.
Remote Desktop Client
http://technet.microsoft.com/en-US/windowsserver/dn463762
Above one quoted from below thread.
Microsoft Remote Desktop
Hope it helps!
Thanks.
Dharmesh Solanki

Rdp://full%20address=s: IP or DNS Name is not user friendly... Can rdp:// IP or DNS Name be assumed as the full address in Microsoft Remote Desktop?

We would like to request Microsoft Remote Desktop (MRD) to behave the same as the open source CoRD.app on OS X with respect URL resolution.
Example:MRD will resolve from Terminal rdp://full%20address=s:<IP or DNS Name>, but not rdp://<IP or DNS Name>
As the OS will respect any of the following protocols in Terminal or browser:
afp://<username>@<IP or DNS Name>
cifs://<username>@<IP or DNS Name>
ftp://<username>@<IP or DNS Name>
ftps://<username>@<IP or DNS Name>
http://<username>@<IP or DNS Name>
https://<username>@<IP or DNS Name>
smb://<username>@<IP or DNS Name>
ssh://<username>@<IP or DNS Name>
vnc://<username>@<IP or DNS Name>
(<username> can be omitted to force authentication at connection) it seems slightly redundant to force "full%20address=s:" in the URL.
Can Version 8.0.1.6 be modified address this request?
What is the proper way to report an enhancement request or bug?
Thank you for your consideration.

Hi,
From your description it appears that you want to modify the pattern for assigning the rdp full address but this doesn’t support as per your requirement. That is the default string which we need to have for passing full address.
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]

Can't connect to windows 7 machine using microsoft remote desktop connection

I am unable to connect from my home network to the Windows 7 Professional machine at my office, using either Microsoft Remote Desktop Connection (2.1.1) for Mac or the open source CoRD program.
When connected to the office network (which is running MS Small Business Server 2011 Standard) both CoRD and MS RDC will connect to my desktop machine just fine! (My MacBook Pro runs Mountain Lion.)
From my home network, MS RDC will complain that it cannot find the Windows computer if I just use the Windows computer name. If I use the Windows machine's iPV4 address, it works on it for a minute and then tosses up this error message:
Using the IP address of the Windows machine, CoRD just grinds away for a minute or so and then times out.
I should add that using Internet Exporer under Parallels from home, I can get a little closer to success (after fidding around with ActiveX controls for a bit). I will get to the Windows login screen, but then I am told that my user password is wrong (which makes no sense at all)!
Okay, geniuses, have at it, and thanks in advance!!

The genius for Microsoft products an be found onthe Microsoft forums for their Mac software:
http://answers.microsoft.com/en-us/mac

"Unauthorized Host" error when you try to connect to the admin server

"Unauthorized Host" error when you try to connect to the admin server

If you see this error message when you try to connect to a Netscape
administration server:
Internal Error
The administration server was unable to fulfill your request.
Reason: Unauthorized host
--------------------------
Here is how to solve the problem and gain access. First you should
temporarily open access to all sites, and then once you make sure that
this lets you get into your administration server, try again to set up
the domain name or IP address access restrictions you want.
For all 2.x/3.x Netscape servers on Windows NT and Unix, or for Commerce and
Communications servers (1.x) on Unix:
<OL>
<LI>Open the "ns-admin.conf" file with a text editor. You can
find this file in the "admserv" directory under your Netscape
server root. The directory is named "admin-serv" in 3.x servers.
<LI>Delete the "Hosts" and "Addresses" lines you see there (either one
of them might not be present). Don't confuse the "Addresses" line,
which you should delete, with the "Address" line, which you should NOT
delete.
<LI>Save the file, then restart your administration server (on Unix run
"stop-admin" then "start-admin"; on Windows NT go into the Services
control panel and stop/start the "Netscape Admin Server" service).
</OL>
For Commerce Server or Communications Server (1.x) on Windows NT:
<OL>
<LI>Go into the registry editor. On Windows NT 4.0, run the command
"regedit". On Windows 3.51, run the command
"regedt32".
<LI>Navigate down to the section
"HKEY_LOCAL_MACHINE\SOFTWARE\Netscape\Administration".
<LI>Delete the "Hosts" and "Addresses" entries you see there (either one
of them might not be present). Don't confuse the "Addresses" entry,
which you should delete, with the "Address" entry, which you should NOT
delete.
<LI>Close the registry editor, then restart your administration server
by going into the Services control panel and stopping then starting the
"Netscape Administration" service.
</OL>
Now try again to access your administration server. Remember, the URL
will be something like "http://servername:12345/", where
"12345" is where the administration server's port number goes.
If you still get the same "Unauthorized host" error, then make sure that
your "ns-admin.conf" file really doesn't contain any "Hosts" or
"Addresses" lines any more, and try stopping your administration server
again then starting it back up.
Once you have access to your administration server, you can try again to
set up the access controls you want.
<UL>
<LI>For the administration server on a 3.x server installation, select
"Admin Preferences" from the General Administration page (the first page
you see when you connect to the admin server), then click on "Superuser Access
Control" and enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the subsrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that
your DNS can resolve those hostnames -- it's generally safer to stick
with IP address restrictions. When you're finished configuring this,
click "OK" then restart your admin server.
<LI>For the administration server on a 2.x server installation, select
"Configure Administration" from the Server Selector page (the first page
you see when you connect to the admin server), then click on "Access
Control" and enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the subsrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that
your DNS can resolve those hostnames -- it's generally safer to stick
with IP address restrictions. When you're finished configuring this,
click "OK" then restart your admin server.
<LI>For the administration server on a 1.x server installation, select
"Configure Administration Server" from the bottom of the Server Manager
page, then enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the substrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that your
DNS can resolve those hostnames -- it's generally safer to stick with IP address
restrictions.
When you're finished configuring this, click "Make These Changes" then
restart your admin server.
</UL>
If you still find yourself getting an "Unauthorized host" error message,
you can use the above steps to open up access and try different
settings.

"Unauthorized Host" error when you try to connect to the admin server

If you see this error message when you try to connect to a Netscape
administration server:
Internal Error
The administration server was unable to fulfill your request.
Reason: Unauthorized host
--------------------------
Here is how to solve the problem and gain access. First you should
temporarily open access to all sites, and then once you make sure that
this lets you get into your administration server, try again to set up
the domain name or IP address access restrictions you want.
For all 2.x/3.x Netscape servers on Windows NT and Unix, or for Commerce and
Communications servers (1.x) on Unix:
<OL>
<LI>Open the "ns-admin.conf" file with a text editor. You can
find this file in the "admserv" directory under your Netscape
server root. The directory is named "admin-serv" in 3.x servers.
<LI>Delete the "Hosts" and "Addresses" lines you see there (either one
of them might not be present). Don't confuse the "Addresses" line,
which you should delete, with the "Address" line, which you should NOT
delete.
<LI>Save the file, then restart your administration server (on Unix run
"stop-admin" then "start-admin"; on Windows NT go into the Services
control panel and stop/start the "Netscape Admin Server" service).
</OL>
For Commerce Server or Communications Server (1.x) on Windows NT:
<OL>
<LI>Go into the registry editor. On Windows NT 4.0, run the command
"regedit". On Windows 3.51, run the command
"regedt32".
<LI>Navigate down to the section
"HKEY_LOCAL_MACHINE\SOFTWARE\Netscape\Administration".
<LI>Delete the "Hosts" and "Addresses" entries you see there (either one
of them might not be present). Don't confuse the "Addresses" entry,
which you should delete, with the "Address" entry, which you should NOT
delete.
<LI>Close the registry editor, then restart your administration server
by going into the Services control panel and stopping then starting the
"Netscape Administration" service.
</OL>
Now try again to access your administration server. Remember, the URL
will be something like "http://servername:12345/", where
"12345" is where the administration server's port number goes.
If you still get the same "Unauthorized host" error, then make sure that
your "ns-admin.conf" file really doesn't contain any "Hosts" or
"Addresses" lines any more, and try stopping your administration server
again then starting it back up.
Once you have access to your administration server, you can try again to
set up the access controls you want.
<UL>
<LI>For the administration server on a 3.x server installation, select
"Admin Preferences" from the General Administration page (the first page
you see when you connect to the admin server), then click on "Superuser Access
Control" and enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the subsrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that
your DNS can resolve those hostnames -- it's generally safer to stick
with IP address restrictions. When you're finished configuring this,
click "OK" then restart your admin server.
<LI>For the administration server on a 2.x server installation, select
"Configure Administration" from the Server Selector page (the first page
you see when you connect to the admin server), then click on "Access
Control" and enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the subsrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that
your DNS can resolve those hostnames -- it's generally safer to stick
with IP address restrictions. When you're finished configuring this,
click "OK" then restart your admin server.
<LI>For the administration server on a 1.x server installation, select
"Configure Administration Server" from the bottom of the Server Manager
page, then enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the substrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that your
DNS can resolve those hostnames -- it's generally safer to stick with IP address
restrictions.
When you're finished configuring this, click "Make These Changes" then
restart your admin server.
</UL>
If you still find yourself getting an "Unauthorized host" error message,
you can use the above steps to open up access and try different
settings.

There was a problem connecting to the server. - Keeps getting error message.

Eversince I updated my iMac to 10.7.3 I get this message every 5 minutes.
"There was a problem connecting to the server.
That server was gone for almost 1 month now.
I have checked Login items, launchdaemons, startup items pretty much gone to every website and I cannot get this error message go away.
Please help..

That server was Microsoft Server 2003.
My users used that server and to access our resources files and folers.
But, I retired that server 1 month ago and all of the sudden her iMac just trying wanted to connect to that server.
I have also clear her history of server by just going to command+k and clear history servers.

There was a problem connecting to the server "owner-pc"

For some reason the message "how to stop the pop up for "There was a problem connecting to the server “owner-pc”, keeps popping up on screen. This sometimes happens when I am trying to change my desktop background, but at this moment, I am using Microsoft Word to do a project. Any solution to this problem?

Quit System Preferences, and also quit iPhoto if it's running. In the Finder, temporarily move the iPhoto library (usually located in the Pictures folder) to the Desktop. Open the Desktop & Screen Saver preference pane again. If you don't get the error message, something in the iPhoto library is causing it. Repair the database, or if that doesn't work, rebuild it.
If you still have the problem, use the procedure on this page to find and remove the invalid items.

There was a problem connecting to the server "192.168.1.3

'There was a problem connecting to the server 192.168.1.3 Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.' - How to sort this out so I can connect to my NAS Drive via wifi?
I am running OS X Yosemite all though I had this problem also with the prevues OS.. I can't seem to connect to my NAS Drive any more via wifi at home. I keep on getting this message error. I have tried different things like trashing some of the Library Preferences suggested on other discussions and updated everything I can. I have also re started Finder (as previously that sometime worked) but this no longer a solution.
The server is working fine I can connect to it via remote website. I also I can see the server/drive and even wake it up but that is as far as it goes, soon after it is 'connected/woken up' I get this error messgae and I can't see any of the files etc. Please help, this is extremely annoying, I feel helpless, this is beyond my technical know how..

I have same problem. It started after i replaced my router (which was on 192.168.1.1) to new air port time capsule, which has different IP address. When i start chrome i have to wait half a minute to get this message. Then i click ok and after that everything is working. Until next time you restart the browser. What is happening here?

X61 - Vista Business - Client Security Solution Error - There was a problem connecting to the TPM

During startup my x61 has been displaying the following message, 'Client Security Solution' - "There was a problem connecting to the TPM (security device) ont his computer. It is possile that anti-virus or firewall software is blocking the connection. A missing or disabled device driver could also cause this problem. Please refer to the online documentation for more information".
I have spent an extraordinary amount of time and effort to find identify the cause and a solution for this problem. It occurs whether or not virus software is enabled or disabled and numerous calls to Lenovo, Symantec, Kaspersky, and Microsoft have resulted in finger pointing and no answers. None of the vendors acknowledge the problem yet this same issue is a significant topic of concern as found in various blogs and 'help' sites. Lenovo thought it was hardware and changed the motherboard. Lenovo told me to call Microsoft since it was a Vista issue. Microsoft told me to call Lenovo since Vista Business was preinstalled on the machine. Lenovo told me to call Microsoft and so it goes. I removed Symantec's anti-virus and replaced it with Kaspersky.
The strangest thing is that the module works intermitently and it seems that everytime a Lenovo update is performed (via Thinkvantage) the problem reoccurs for sometime.
Does anyone out there have an understanding of the cause and a potential solution???

I have the same problem on an X 60 platform, which only surfaced in the last two weeks subsequent to running all of the Lenovo updates. Prior to this, I had reinstalled all programs, starting with the Recovery Disks for the Think Pad. Everything, including start up, was exceptionally fast. Once I ran the most recent BIOS updates, along with several others, this error message surfaced. It is intermittent, however, and I have not noted an issue.
In reviewing several other Message Boards, I have seen this issue raised several times. Here is a link to a thread where the individual did achieve a solution through Lenovo, but their response is nonspecific as to what they did: (http://forums.lenovo.com/lnv/board/message?board.id=T400_series_ThinkPads&message.id=7143&query.id=1...

Problem connecting to the Admin Session Microsoft Remote Desktop Mac 8.0.12 (Build 25282)

Similar Messages

Maybe you are looking for