Remote Desktop Connection on PowerBook, not x86 iMac

My office uses SBS2003 with VPN enabled.
Without VPN, on my PowerBook & the intel-iMac, I can "Remote Desktop Connection" into the server, then subsequently into a workstation through the server.
With the VPN connected, I can use RDC to connect directly to my workstation (say, unit01).
With VPN connected, the iMac can't connect directly to the workstation, yet it can still go through the server to the workstation as usual.
I'm suspecting this is an issue with Rosetta emulating Microsoft's Remote Desktop Connection and not allowing the domain name to be recognized through the VPN.
Both computers are using the exact same settings for the VPN and attempting to use RDC exactly the same.

i've been using just the netbios name, simply because it works on my powerbook. I still don't understand why it wouldn't work on this intel-mac.
I was mainly following this guide:
http://www.smallbizserver.net/Default.aspx?tabid=266&articleType=ArticleView&art icleId=84

Similar Messages

Remote Desktop Connection Solution, VPC NOT an option

I downloaded Remote Desktop Connection yesterday B/C I wanted to be able to do work on my mac, I have virtual PC with WINXP but it was way to slooow.
I do not want to play games, I play games on my compaq laptop that's in a full sized docking station.
So I was looking and reading at this software (RDC) and it sounded like a viable option, My laptop has a 14" monitor but the iMac is a 17".
so I downloaded it and set it up, BTW my connection is iMac to Laptop docking station I used a "Crossover Cable".
Set the IP address and I have (Sorry to say) windows on my MAC for nuthing!
It works great ALOT faster than VPC (since it does not have to emulate a Intel CPU).
And the Laptop monitor goes to sleep after 1 minute so now I can have the best of both worlds!

I'm not quite sure why you posted this.
You marked your post as a question... but I can't find one.
Do you have a question or was this somewhat of an "informational" post?

WRVS4400N Remote desktop on Vista does not work

I have a WRVS4400N and all firmware, software is up to date and current. I can connect using remote desktop on a laptop with Windows XP Pro but cannot connect with a laptop using Vista Ultimate. I have used the new Quick VPN connect software, but when I try and use the remote desktop connection, it does not connect.
Is there a setting that is different in vista than windows XP that I need to change on the laptop or is it someting in the firewall in the WRVS4400N?

if your RDP is already working on your windows XP computer then there are no settings that needs to be changed on the linksys router, you have to double check the settings of your RDP application on your vista computer, possible that it is using a different port number

Remote desktop connection not working in windows 7 Pro x64 bit sp1 3389 port not working

i have still facing same problem in last two week in my system RDC not working . i have installed in my system windows 7 x64 bit Pro sp1 then i check 3389 port working or not in my system use the command netstat -a -o command in
command prompt but this is my bad luck its not woking in my machine after i have decide to change RDC listening port via registry i have change it 3389 to 3391 after restart my system, and
after again testing using same command but no any change again rdc not listening . After i have search this issue on search engine google bing and microsoft , i have found more solutions but i have try one
uninstalled two microsoft updates first is kb KB2621440 second is KB2667402 and after again restart my system and again installed KB 2667402 But not change i have already enabled Remote Desktop connection in windows 7 and select the option
any version computer running , i have try three and four time enable disable remote desktop connection in my machine . but not change i have all windows firewall disable and uninstalled anti virus they intalled in my machine , and using the Mcafee
stinger tools to scan my machine to remove virus but stinger is not found any thread in system. ihave already run this command in my system sfc /scannow Please Can you help me to fix this issue.

Hi,
When you try to start the Remote Destop Connection, what errors it showed out?
Could the other PCs connect this PC with the RDC?
So you have read this blog?
RDP connections might fail due to a problem with KB2621440 - MS12-020
Did you reinstalled the KB2621440?
Besides, did you follow this guide to enable the RDC connection?
Connect to another computer using Remote Desktop Connection
And also this guide?
Why can’t I connect using Remote Desktop Connection?
Please take a check with those settings again.
Best regards
Michael Shao
TechNet Community Support

Remote Desktop Connection not working

I am able to remote desktop connect to my home computer from work; however, I can't remote desktop connect to my work comptuer and server. I believed it has something to do with my Linksys E3000 access point settings but I'm not sure where to look for and verify. I took my home laptop to work and able to do remote desktop connect to the server. I also took a laptop that's working fine with remote desktop connect to the server home and tried to remote desktop connect to the server at work and it's not working. Therefore, I've concluded that it has something to do with the access point and not the settings in the computer because it works fine when I took it out of my home network. I also VPNP in to my work place so that it has the same IP address as at work and still, remote desktop connection from home to work is not working. Any suggestion is much appreciated.

thebluemamba_24 wrote:
Connecting from home to your remote desktop server has nothing to do with your router. Certain ports are needed to be opened from the server’s end in order to host an application. Try to connect your computer to your modem or to another wireless network just to check if your work’s remote desktop will work. In case it will not work, then contact your IT guy.
If you read my previous post it said:
"I took my home laptop to work and able to do remote desktop connect to the server. I also took a laptop that's working fine with remote desktop connect to the server home and tried to remote desktop connect to the server at work and it's not working. Therefore, I've concluded that it has something to do with the access point and not the settings in the computer because it works fine when I took it out of my home network."
I think my above statement answers your question of "Try to connect your computer to your modem or to another wireless network just to check if your work’s remote desktop will work." However, your statement prompts me think of something else. What I have tried is bring my laptop to work and tried connect via RDC to the server and it works but it just not working when trying at home. What I have not done is instead of brining my laptop to work and try RDC there, perhaps I should I try it on a friend's or relative's network and see if I can do RDC to my server at work. If this does not work as well, then, could it be that at work there is something something outside RDC coming? But even if this is so, why can't VPN work?

Remote Desktop Connection to VM does not work after sysprep

Hello altogether.
Often asked, but never answered with an applicable solution!
What shall
we
do if
we
get no access to a Azure VM via Remote Desktop
Connection?
Everything went well: access to the VM via RDC was working perfectly!
Then
the idea came into
our
mind to create an image of the VM by use of the Azure Management Portal.
We
found that
we
had to apply “sysprep”
on the VM.
We
did it.
Then we did not take the image and decided to go on with the VM.
But if we start the VM we get no access via RDC!
We tried to find a solution by reviewing the already published contributions by other Azure
users. But none of the replies marked as answered supply with a qualified solution.
So can one provide a really applicable solution to us on how to arrange the further use of the VM?
Thank you in advance.

There is an issue right now where the VM may start unexpectedly after you have run sysprep and selected the shutdown option (which is normally what you should do).
http://social.msdn.microsoft.com/Forums/windowsazure/en-US/fafb9ee6-1e57-46ba-8440-27467ad986cf/image-capture-issue-vm-unexpectedly-started-after-guestinitiated-shutdown?forum=WAVirtualMachinesforWindows
But regardless of that issue - you can't use that deployed instance of the VM after you've run sysprep on it. It needs to stay shutdown, then you select Capture to create an image from it.
If you start it back up, either intentionally, or it is started unexpectedly because of the issue above, it will be sitting at the first interactive screen of setup. RDP is not working at that point, and since there is no console access to an Azure VM, there
is no way to get past that prompt.
For other scenarios, you might be able to attach the OS disk of that VM as a data disk to another VM, and while you could do that in this case too, there is no supported method for disabling sysprep at that stage of setup.
So while you could attach it to another VM to get data off of it (you would have to remove the VM first), the VHD is no longer in a supported state to use as a VM itself.
Thanks,
Craig

Remote Desktop Connection Not Going To Full Screen on EIZO MX340 Monitor 1536x2048 Resolution

I am using a EIZO Rx-340 as a secondary monitor. So far I am only able to get into full screen by using Ctrl-Alt-Fn-Pause but it does not change the resolution. It does not help to move the slider to large. There is a black space at the top and bottom
of the display.

Hi,
Please take a try with the steps below:
1. Start "Remote Desktop Connection".
2. Click on "Options".
3. Click on the "Display" tab.
4. On "Display configuration" settings, you can change the "Remote Desktop Connection" display by moving the slider from "Small to Large".
5. By moving the "Slider" all the way to large, the display settings will automatically set to "Full Screen".
Here is the screenshot:
Also please take a check if the monitor itself is configured well.
Hope this may help
Best regards
Michael Shao
TechNet Community Support

I have a time capsule connected directly to fiber connection. I have connected a windows server directly to TC and configured it for remote desktop connection. From my interanet I can access srvr but not from my home. What config I need on TC?

I have a time capsule directly connected to fibre optic point out. All pcs and macs are connected wirelessly to the internet. I have connected a windows server pc to TC. When configured for Remote desktop connection, I can access windows server from within interanet but don't know how to access it from internet. I guess I need to change some settings in TC to get some ip adress for the remote desktop connection from my home. Anyone who can help me out? Appreciate it.
Narmin

I am a little lost now.. I have read again your title and your first post.. and they seem inconsistent.
In the title you state.
From my interanet I can access srvr but not from my home.
Interanet is not a word I know.. I assumed intranet...are you talking about internet or intranet? And just to be clear say WAN or LAN.. !! Is your home part of the interanet??
In the first post you state,
I can access windows server from within interanet but don't know how to access it from internet.
Now this is more normal.. the issue is not in the home at all, it is accessible from there but fails from internet. If this is correct, then you can do a few obvious things to determine where the problem is.
But first I need to know are you actually testing from a different internet connection to your home lan.. you are not just trying the public IP from inside the LAN as that will fail due to the TC not doing NAT Loopback.
I am also assuming the TC is the only router in the network, and has the public IP on the WAN interface.
And I am also assuming you have turned on the ping responder and you can actually ping your public ip from the internet and get a response. This helps no end in figuring out where there are issues. Strange but I have no idea if there is a ping responder in the TC WAN so you might need to forward that as well. Also if you have a dynamic public ip address are you using dyndns or no-ip or some other service to connect.
1. Test bypassing the TC.. plug the internet connection straight into the windows server,, and test if you have access. If yes, the TC is the problem.. if not, your setup on the windows server is wrong.. look at firewall in particular.
2. Assuming from test 1 the TC is the problem, Post the screen shots of the port forwarding setup for us to look at.. that is by far the easiest way to check it out.
There are lots of references to port forwarding in the TC.. eg
http://must-know-mac.blogspot.com/2008/07/how-to-port-forward-time-capsule.html
The things that generally go wrong are firewall on the computer that is accepting the port.
The ISP doesn't allow connections on a particular port. (not likely in your case)
The router is behind another router.. double NAT will kill any port forward.
Upnp has already allocated a port.. not an issue as TC doesn't use upnp although a reboot of everything after you set port forwards is well worth it.. amazing how things don't stick properly without a reboot.
IP on the receiving device is not static and so changes.
Not enough or right type of ports are opened. This is always messier than it looks as one port is often not enough for two way communications.

Installed the RDS 2012 Server License per user CAL (5pcs) after not allow over two users remote desktop connection problem

I have successfully to installed the RDS 2012 Server R2 per user CAL (5pcs) Open License after is found not allow over two users to remote desktop connection on this Server problem, I try to uninstall the license and then (internet on-line & telephone
call Microsoft Activate Center get the activate key) to reinstall is still same of the result on below problem.
Select a user disconnect so that you can sign in.
There are too many users signed in
User1 Active
User2 Active
() Force disconnect of the user

Hi,
In addition you can also refer following article for RDL configuration.
RD Licensing Configuration on Windows Server 2012
http://blogs.technet.com/b/askperf/archive/2013/09/20/rd-licensing-configuration-on-windows-server-2012.aspx
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 Connection ok on work wireless but not from home

I've succesfully logged into the Win 2003 SBS (Terminal Services) from within the wireless connection at work using Mircrosoft's "Remote Desktop Connection". However when I try to do this from home I get the following error message "Either remote connections are not enabled, the computer is too busy to accept new connections, or network problems are preventing your connection. Try connecting again later or contact your administrator."
I've got the firewall on the mac on.
Now what I can't work out is why it works when at work and not from home. I have been searching for ages and can't work this out - annoying as I am sure it is very simple!
One thing I can think of is that the first time others connect via PCs they have to download the connection manager from the company web site which installs a security certificate. However this is an .exe file so cannae work on the Mac.
Do all I need to do is ask the IT administrator to email me the certificate and drop it into the keychain?
Thanks in advance.

"Now what I can't work out is why it works when at work and not from home."
Probably because, if your work is smart, they have a firewall in place, blocking external access to the ports needed for use with RDC.

Remote Desktop Connection (RDC) iMac to PC server with fixed IP

I have setup my first imac and as part of this process downloaded Remote Desktop Connection for macs so that I can log onto my server at work. Problem is when I attempt to connect to my remote pc the following message appears "Remote Desktop Connection cannot verify the identity of the computer that you want to connect to. Try connecting to the Windows-based computer, or contact our administrator"

So, what if those don't help? I've had "Always connect, even if authentication fails" selected for quite a while. It was working fine. Yesterday I installed Office 2011 (and immediately installed SP1), and now it broke my ability to connect to a Windows Server 2008 VM that definitely worked yesterday before the Office upgrade.
Anybody have a solution for this? It appears to be a bug in RDC 2.10. Thanks, Microsoft. Off to find a working RDP client for the Mac…

Microsoft Remote Desktop Connection Client for Mac Not Working

I recently purchased Office 2011 for Mac. I work at home on my Mac at work on Windows 7. I also have a work laptop, running Windows 7, that comes home with me. My goal is to RDC my Mac to the laptop running Windows 7 to reduce desktop clutter, and easily work between machines.
I CAN NOT FIGURE OUT how to get Microsoft RDC:mac to connect to my pc.
I know that the pc allows remote desktop connections because I often use RDC at work from PC to PC.
SOME PLEASE HELP! I have spent hours and hours trying to figure this out and I think it is the time capsule that is causing the problem.
My research has found that I have to use port 3389 to get this done. I am pretty computer savy but when it comes to networking I guess I have no clue. I have tried just about everything a and can't figure it out.
Thanks to anyone that can dedicate some time to configureing my time capsule to allow for RDC.

I cannot quite put together your whole network..
I work at home on my Mac at work on Windows 7. I also have a work laptop, running Windows 7, that comes home with me. My goal is to RDC my Mac to the laptop running Windows 7 to reduce desktop clutter, and easily work between machines.
So this is in local lan.. the PC laptop running win7 and the Mac loaded with RDC software. If this is local lan then the issue is nothing to do with TC.
That is only if you are trying to connect from work. to home through the router at work and TC at home. On local lan there is no blocking to ports. Are you using the local network IP of the PC Laptop?
Explain a bit further as it needs a bit more clarification.

Easy print not working on a 64 bit Windows 8.1 client with Remote Desktop connection version 8.1

Easy print is not working on a 64 bit Windows 8.1 client with Remote Desktop connection version 8.1 . Printers dont get redirected when you connect to the terminal server. The server we are connecting to has Windows 2008 server. On 32 bit Windows
7 and windows XP clients Easy print is working fine and printers get redirected in terminal server.

I am having the exact same problem. Windows 7 works fine, but 8.1 will not redirect printers. Others said to check local policy terminal services settings and my setting are all set as they should.
I think Windows 8.1 is not telling the terminal server what printers it has.

The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database.

When I try to install Connection Broker on a Windows 2012 R2 Server in a Windows 2003 domain I get this error:
The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database.
Pooled virtual desktop collection name: NULL
Error: Logon to the database failed.
I have added both the Connection Broker server and the 2 remote desktop servers (also Windows 2012 R2 Servers) to the "Windows Authorization Access Group" in the domain according to this: http://support.microsoft.com/kb/331951
But it still does not work :-(
I keep getting same error....
Any idea what I might be missing ?

Hi,
Thank you for posting in Windows Server Forum.
Firstly please let us know by which method you have setup RDS role. You can have more advantage and feature when you will install with Standard deployment instead of Quick start deployment. So if you have setup with quick start option then you can try installing
with standard type and check the result.
In addition, please check SQL server database is properly configured for RDS server. Also check that domain controller properly communicates. Kindly go through below thread for more information.
Server 2012 RDS - Remote
Desktop Connection Broker Client failed to redirect the user domain\username. Error: NULL
Hope it helps!
Thanks.
Dharmesh Solanki

Having trouble maintaining remote desktop connection with Mavericks. What is this about needing RDC 3.7.1 with Mavericks. I downloaded RDC 3.7.1 but it does not replace RDC 2.1.0 previously installed.

Having trouble maintaining remote desktop connection with Mavericks. What is this about needing RDC 3.7.1 with Mavericks. I downloaded RDC 3.7.1 but it does not replace RDC 2.1.0 previously installed

Lucky you, it did not work for many users (which as it should be) so MS produced a new version, for ML and Mavericks.
It's in the App Store, for free.
FYI, I assume that you were attempting to post a picture, no one can see it (except maybe you) because it is on your computer rather than the forum server.
file:///Users/dbrant/Desktop/About%20Apple%20Remote%20Desktop%203.7.1.webloc
Use the small camera icon in the editor toolbar to post it.
It also looks like you attempted to use Apple Remote Desktop, which does not do Windows.

Remote Desktop Connection on PowerBook, not x86 iMac

Similar Messages

Maybe you are looking for