Remote Desktop Mac/Windows

Hello, i have an ethernet cable between my Powermac and my Compaq Presario (running XP Home SP2) anyway, i want to use remote desktop of some sort, so i can use my compaq, without having to switch monitor cables, keyboard etc. (dont' tell me to buy a KVM switch) i have been searching and haven't found anything yet.

Ze,
Windows XP Home edition does not have the remote desktop server built in. As a result you can set up a VNC server on your windows machine. This will allow you to remote into it.
Fore more help, check out this post: http://discussions.apple.com/thread.jspa?messageID=5975152&#5975152
-Jesse

Similar Messages

Windows Remote Desktop (Mac)

Hello:
I'm trying to use Windows Remote Desktop (Mac) to connect from a Mac (OSX 10.9.5) to a pc (Windows 7 Pro). When both laptops are on the same network I can connect without issue (using the destination pc's IP4 address). However, when they are not on the same
network I get the error message below* (I use the ISP-provided IP address for this connection). I made sure the ISP router port forwarding settings had the open/end ports (which I got from running the necessary CMDs from my destination pc's dos prompt). I
made sure the destination pc firewall settings allowed Remote Desktop connections (public, domain, home/work). What could I be missing? Thanks!
*Error message:
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.

Hi Andy,
Which version of MRD MAC you are using for your case?
Please use the latest MRD v 8.0.15 and verify.
As you have commented, you check every network scenario. Suggest again to recheck the related setting for IP address, firewall, port, user permission access and other things. You can also refer beneath article for information.
https://technet.microsoft.com/en-us/library/dn473006.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 MAC version 8.0.5 crashing when opening format panel in Excel

Remote Desktop MAC version 8.0.5 crashing when opening a format panel in Excel. Attempt to reconnect via RDC do not work until you log into Windows direct and close the formatting window. I'm running Windows 7 Pro, Service Pack 1 and using Microsoft
Remote Desktop version 8.0.5 on a Mac running OS X 10.9.2. Reproduced error 3 times. Has also twice caused Excel to crash, so error does seem specific to the Windows environment and/or interaction with RDC (i.e. - not Mac related).

Hi,
Would you please provide us the log file for check after issue occurs.
Microsoft Remote Desktop -> About Microsoft Remote Desktop -> Send log via email -> Copy and paste the log here.
Thanks.
Jeremy Wu
TechNet Community Support

Remote desktop to windows using vpn

I am unable to remote desktop my window based office pc from my mac book pro using VPN.
I even tried to install rdp , but no luck.Please respond asap.Thanks.

Try TSclientX. I got so sick and tired of MS RDP and the license crap. I mean, it comes bundled with Office, and still stops working every few weeks.
TSclientX just works.

Ctrl+Alt+End in Remote Desktop Running Windows XP with VMWare Fusion

I am using remote desktop on Windows XP in a VMWare virtual machine on my MacBook Pro. When the remote computer I'm connecting to times out and locks the screen, I need to send ctrlaltend to get back to the login dialog to unlock the screen (ctrlaltdel gets processed by the local windows box and never passed through so ctrlaltend is the appropriate sequence in remote desktop). Only one problem ... my MacBook Pro keyboard doesn't have an End key (or any other key that maps to it as far as I can tell) ... neither does the bluetooth wireless keyboard I use. So how do I send ctrlaltend? Anybody else run into this and find a satisfactory solution short of disconnecting remote desktop and logging in all over again?

That's weird.. I use RDC on my Vista's VM all the time and Ive never encountered this issue.
Try running the RDC in full screen, so that the Ctrl-Alt-Del will go to the RDC.
You can close the RDC window, and change the Options "Send Windows Combination Key" either to the RDC or the VM, or while the RDC in full screen.

Remote desktop help windows 7

Hallo
Im work as a help desk . i use remote desktop help windows 7 but some time i have to wait 10 min to the end user because he is not in his place or ...
can i use another software without enduser permission? if yes then wich one
Thanx

Hi,
Based on my research and test, it's impossible. Even shortening time is also unreachable.
Karen Hu
TechNet Community Support

HELP - Remote Desktop and Windows? Is it possible? I need your thoughts...

I am currently trying to set up a connection between my MacBook and my Windows XP PC. I have Leopard 10.5.3 and Windows XP. I want to set up the connection to my PC so I can use my Remote Desktop to control/observe/receive files from my PC to my MacBook. So far its been going well, I was searching on Google for some answers, and I read something about VNC Viewer and Remote Desktop. I am not sure how this works but I just want Remote Desktop to work with my PC. So I was just wondering if anyone here can help me out, or if anyone here has any suggestions/ideas. Thanks.

You've probably figured this out by now, but you can't use Remote Desktop with XP Home. It only works with XP Pro. As a free alternative, you should be able to run a VNC server on the XP machine, and a VNC client on the Mac, and access that way. A brief decription can be found here: http://lifehacker.com/software/feature/geek-to-live--how-to-control-your-home-co mputer-from-anywhere-125607.php (Ignore the parts about opening ports on your router to the internet--this is best used only on local network, unless you get more complicated.) If you do want access over the net, perhaps its better to go with a commercial service such as pcAnywhere or GoToMyPC is an easier route.

Remote Desktop Connection - Windows Network Level Authentication

Hi
I'm trying to find a piece of Remote Desktop "Manager" software for Mac which supports Network Level Authentication (NLA). When NLA is enabled on a Windows Server I am unable to connect via CoRD or Royal TSX.
The reason I say "Manager" is because I have many, many windows servers I need to connect to and so I like to use software such as the above to save a list of all the servers for ease of access - this saves me having to type in the name of the server each time.
At the moment, for those servers with NLA enabled, I have to fire up Remote Desktop Connection for Mac and enter the name. I realise I could save this each time but then I would have LOADS of shortcuts.
Any ideas/proposals on pieces of software that can cater for this?
Thanks!

Hi!
Royal TSX actually supports NLA but you have to use the FreeRDP plugin instead of CoRD and enable the setting in the advanced settings of your RDP connection.
cheers,
felix

MacBook with OS X and remote desktop to Windows server

I am curious if an apple MacBook running OS X 10.4 can be used as a remote desk top to access a Windows 2000 server. It is easy to do so with a Windows PC with Windows XP. However this necessitates carrying a Windows machine while travelling. I like the MacBook Pro I have and would like to use it for remote access. I do not want to install Windows on the MAC even though I can do it with my MacBook Pro.
Any thoughts? Or are there sittes addressing this issue?
Thanks in advance.
Raj

"I am curious if an apple MacBook running OS X 10.4 can be used as a remote desk top to access a Windows 2000 server."
Please search the discussions before posting. Questions regarding ARD controlling Windows computers have been asked and answered dozens of times.
Install VNC server software on the Windows server and control with ARD, or just use Microsoft's own Remote Desktop Connection for Mac.

OS 10.6.3 and Remote Desktop for windows server, PDF Printer problem

We are using Remote desktop for mac by windows in the office to work on a remote windows server, On the server we are using a business software (Mamut) for sale. In OS 10.5 we are using the PDF Printer to transfer PDF (invoice) from the business software (Mamut) 'Mamut is seeing the PDF printer as any other printer' to the desk top of your mac, so we can attach the PDF to a mail before we send it out to a customer, but in OS 10.6 the PDF printer is removed! So we need a different way of transfer the PDF from the windows server to the mac desk top.
So now I am wondering if any one has a suggestion on how to fix this! if not we can't upgrade to OS 10.6, and that would be a shame!

The thing is that in Mamut, we hit print, and because we us the PDF printer as Printer for Remote desk top, it pup up on the desk top of the mac, as a PDF. But in OS 10.6 there isn't any PDF printer to install, so then we have to make a PDF on the windows server and move it from the server to the mac, by mounting the HD from the Mac to the remote desk top, so it become edible in from the server. I think this is cumbersome.

Remote desktop (MAC) app freezes after a sleep/scree-timeout

Hello,
My company needs the Remote Resource Connection -> Remote Desktop Client to be used to connect to Windows (7) desktops over the Internet. The connection is through duo-authentication and once connected all works fine. Highly recommending the Microsoft
Remote Desktop for MAC therefore.
One small annoying glitch I found was when the MAC goes to sleep or screen shuts off (This happens about in a minute to save battery). Once the screen awakes, the Remote Desktop doesn't seem to be able to restore it state. What I notice is that the screen
for Remote Desktop is Frozen. MAC is not frozen, its healthy and all the rest of the apps seem to work fine, just this Remote Desktop app isn't. I will have to either kill the process from the command line (terminal) or just exit the Remote Desktop app (well,
its not frozen, the menus work fine) and restart the process of logging in.
Any advise to fix this issue? Or is this a bug and needs fixing? Please ask if you need further from me.
Thanks
Madu

Hi,
Would you please provide us the log file after you reproduce the issue. Also, please give us the timestamp you put your Mac to Sleep.
Thanks.
Jeremy Wu
TechNet Community Support

Novell login not available with remote desktop on windows 7

Installed Novell Client 2 SP3 for Windows Server 2012 on my terminal server. When I log in from Windows XP to that terminal server I am getting an option to login with Novell Client. On Windows 7 however I only can logon to the server. What am I missing here?

djaquays <[email protected]> wrote:
> Mostly, that MS RDP for Mac ignores the authentication level:i:0 option
> in an RDP file and there's no GUI equivalent to force legacy
> authentication.
Microsoft's Network Level Authentication (NLA) feature is supported in
Windows Server 2008 and later terminal servers, and supported by
Remote Desktop Connection (MSTSC) 6.x and later terminal clients.
Windows XP did not ship with a MSTSC 6.x terminal client, but it is
available optionally through Windows Update.
The NLA authentication is essentially requiring that valid Windows
user account credentials for the Windows Server machine must be
provided /before/ the RDP-level terminal session connection is even
attempted or permitted. If the Windows user credentials you're logged
in with on the client workstation do not already satisfy this
requirement, the NLA-aware MSTSC clients will prompt you for valid NLA
credentials before even attempting to open the terminal session.
In other words, NLA doesn't directly have anything to do with whom you
will become authenticated as within the terminal session, or whether
you'll reconnect to some other already-running terminal session; it's
a new default mechanism which requires Windows credentials for
authorizing you to create an RDP connection to the Windows Server
machine "at all."
Unfortunately Windows Server 2008 and later don't permit you to turn
NLA completely off. You can configure the Windows Server to always
require NLA, which means pre-MSTSC 6.x terminal clients will be unable
to connect. Or you can configure the Windows Server to "not require
NLA" ("Allow connections from computers running any version or Remote
Desktop"), but this still means Windows Server will use NLA if the
workstation's MSTSC client supports NLA.
The only option which has been available to "disable NLA" even when a
Windows Server 2008 or later terminal server and a MSTSC 6.x or later
terminal client are involved is to configure the
"enablecredsspsupport:i:0" setting in the MSTSC client's .RDP file
(e.g. default.rdp in the My Documents folder), in addition to
configuring the terminal server to "not require NLA."
Once you have "Allow connections from computers running any version or
Remote Desktop" set on the Windows Server, and
"enablecredsspsupport:i:0" set in the MSTSC client, now you're back to
the Windows XP & Windows Server 2003 behavior where an RDP terminal
connection can be established without first having to supply NLA
credentials, and the first thing the MSTSC client user will experience
is the full normal credential provider-based login experience just
like you see at the physical console of the terminal server.
Note that if you do leave NLA enabled and supply NLA credentials
during the MSTSC connection attempt, after successfully using those
credentials to authorize creation of the RDP connection, the MSTSC
client will /also/ default to using the NLA credentials as default
credentials to attempt logging on with within the terminal session
itself. In other words, if you successfully supply NLA credentials,
by default you also become logged in on the terminal session and go
straight to the desktop of the Windows user account specified in the
NLA credentials. So even though "NLA credentials" and "whom I will
logon as within the terminal session" are two separate things, by
default the MSTSC client tries to use the same credentials for both.
But it's not that the NLA credentials "must" be used for logging in on
the terminal session; that's simply the default behavior. If you
leave NLA enabled on the Server 2008 or later terminal server, after
NLA credentials are successfully used to authorize creation of an RDP
connection, if you wanted to instead be prompted within the terminal
session with the normal credential provider login experience, enable
the "Always prompt for password" on the Windows Server 2008 or later
terminal server.
(On the Server 2008 or later machine, under "Administrative Tools"
find the "Remote Desktop Services" group and launch the "Remote
Desktop Session Host Configuration" console. Highlight/select the
"RDP-Tcp" connection, right-click and select "Properties". On the "Log
On Settings" tab elect "Always prompt for password".)
That sounds like probably the scenario which fits best for the "I have
a Macintosh-based client which doesn't allow enablecredsspsupport:i:0
/ authentication level:i:0." You would leave NLA enabled on the
Server 2012 machine, but enable "Always prompt for password" in the
RPC-Tcp connection properties on the Server 2012 machine. Such that
after NLA authentication was performed and Windows allowed creation of
the terminal session, instead of immediately also attempting to login
within the terminal session as the Windows account specified in the
NLA credentials, Windows will instead present the normal interactive
credential provider login experience to allow the user to specify whom
they want to login as.
Finally, note that everything described above applies even to a
Windows Server and Windows client workstation that do /not/ have the
Novell Client for Windows installed. The same mechanisms remain in
effect even once the Novell Client is installed; the presence of the
Novell Client just changes what credential providers would be used or
presented within the terminal session once the terminal session was
allowed to be created. The fact that NLA is required by default and
requires valid Windows credentials in order to authorize an RDP
connection is still the same, regardless of whether the Novell Client
is present or not.
Alan Adams
Novell Client CPR Group
[email protected]
Novell
Making IT Work As One
www.novell.com
Upgrade to OES Community
http://www.novell.com/communities/co.../upgradetooes/

Remote desktop to windows pc

I am trying to remote through my company's vpn to my desktop but I keep getting the message that my mac can't find the windows based desktop. I know there is an issue with the java appelet but I downloaded the latest upgrade from java and thought that it would work now. Any ideas

Are you using Apple Remote Desktop? If so, what VNC application do you have running on the Windows system?

Remote Desktop---old windows via new iMac!!

I am running V. 10.5.8 on an intel core 2 duo. Is there software that would be based on my machine that could be used to support my Mother's old windows computer, as a remote desktop. In other words, when she calls and asked "why or how do I", I can "see" what her problem is on my machine and answer her question.
Not a terribly sophisticated problem but one of great social consequence!!
Thanks in advance
David

http://www.microsoft.com/mac/products/remote-desktop/default.mspx

Remote desktop from windows

I am looking for a vpn software (to securely penetrate to network
firewalls) and then I want to do remote desktop to the required mac 10.5
machines.
But I want to do it from windows machine therefore I am looking for a
software for windows machine.
Any pointers will be very helpful.
Any pointers to to a freeware will be good.

Use any of the free VNC clients floating around. Do a Google search.

Remote Desktop Mac/Windows

Similar Messages

Maybe you are looking for