Connecting _from_ a windows machine through remote desktop?

I have a os x server set up so that users can get to it through vpn by logging into a specific account ( lets call it remote_user ). The users are on windows machines, and they get remote desktop running, at which point the problems start. Instead of seeing the remote_user's desktop, they see whatever happens to be on the screen at the time, even the Administrator's account, if that happens to be logged in. Furthermore, these users have full control over even the Administrator's account and are able to do whatever the administrator might be able to do locally. Is this normal behavior or is there something I should be doing otherwise. Thanks in advance!

Further details:
the server is running on a mac mini, the internal interface is the built-in ethernet, the external interface is a usb-ethernet adapter connected directly to a cable modem. on the internal network there is a windows computer which has a program which needs to be run remotely. for this, a vpn connection to the server is established (using the vpn module in the server admin) and then the server is accessed though the virtual network that is created. the server runs wonderfully when left alone. however, when a vpn connection is made, the server lives for about 10 minutes and then freezes up. if no account is logged in on the server, the login window becomes unresponsive. if, for example, the administrator is logged in and is watching the server admin window, the server refreshes and remains that way, in a permanent refresh. if you have a preview window open reading a pdf, you are able to scroll though the pdf. you are, however unable to access any menus in the menu bar, nor start any new programs from the dock. the only way to get things up and running again is to hold down the power button. the last bit of bad news is that even after restart, the only way to get vpn up is to manually shut it down in the server administrator and to start it up again. i hope this can be resolved somehow. thanks in advance!

Similar Messages

How to enable users to access windows 2012 through remote desktop client on windows XP SP3

Hi I have just installed Windows Server 2012 and trying to give access to the users. The users are on windows XP Pro SP3 remote desktop client (Shell and control version 6.1.7600 with Remote Desktop Protocol 7.0 support).
I have enabled the windows server 2012 remote desktop users through "control panel -> systems and security -> Remote access" for the users. When I try to connect to the windows server as administrator, it is getting connected.
But when I try to connect as other users I get the following message.
"To sign in remotely, you need the right to sign in through Remote Desktop Services. By default members of the Administrators group have this right. If the group you're in does not have the right, or if the right has been removed from the Administrators
group, you need to be granted the right manually."
Is there any other setting to be done to eanble the Remote Desktop for the users.

Hi I have just installed Windows Server 2012 and trying to give access to the users. The users are on windows XP Pro SP3 remote desktop client (Shell and control version 6.1.7600 with Remote Desktop Protocol 7.0 support).
I have enabled the windows server 2012 remote desktop users through "control panel -> systems and security -> Remote access" for the users. When I try to connect to the windows server as administrator, it is getting connected.
But when I try to connect as other users I get the following message.
"To sign in remotely, you need the right to sign in through Remote Desktop Services. By default members of the Administrators group have this right. If the group you're in does not have the right, or if the right has been removed from the Administrators
group, you need to be granted the right manually."
Is there any other setting to be done to eanble the Remote Desktop for the users.
Have you tried adding those users to the "Remote Desktop Users" group? It's in Active Directory Users and Computers and it's a Built-In group. Might want to give that a try ...
- JJ

Connecting to a Windows computer using Remote desktop connection

I have connected a Windows 7 computer to my network using an ethernet cable to my Time Machine which is configured as an extension to my Airport network. My Mac sees the computer as shared, and I can connect to it using the name and password so I can browse files on it etc.
Nevertheless Microsoft Remote Desktop Connection will not connect to it, saying there is a network error. It has been suggested that if I use its IP address rather than its name it may work, but how do I remotely find out what its IP address is on the Airport network? I have not found the way using Airport utility or help.
thanks in advance...

You are using the Mac version of RDC aren't you?
If so, please post questions regarding it on Microsoft's own forums for the Mac version of RDC, as Apple discussions only provide support for Apple products

I am accessing a windows server using remote desktop and I am wondering if I can transfer files by sharing drives?

I am accessing a windows server using remote desktop and I am wondering if I can transfer files by sharing drives?

Probably. You may be able to use Finder > Go > Connect to server to access the server. You may be able to share folders using Remote Desktop too. Whichever one you like the best.

Allow log on through Remote Desktop Services Group Policy for Domain Controllers

Hello,
We want to allow our Helpdesk Operators to be able to connect to Domain Controllers with the Remote Desktop Services. This is by default not allowed but according to many sites, it should be able to configure by using a Group Policy.
We made a new Group Policy with the setting 'Allow log on through Remote Desktop Services' and 'Allow log on locally' (as an extra for testing) and applied Security Filtering to only use it for a specific Security Group. Our test user is a member of this
security group and should be able to access the Domain Controllers now. However this isn't working.
The error message we receive upon trying to connect:
The connection was denied because the user account is not authorized for remote login.
For troubleshooting, we also applied the Security Group for that setting in the Default Domain Controllers Policy but that doesn't seem to work either. We want to avoid customization on our Default Domain Controllers Policy but this was just a test case
for solving our problem.
What should we do to solve our problem?
I hope to hear from you soon.
Thanks in advance.

Hi, I just found out what the problem was. This site helped me alot:
http://blogs.technet.com/b/askperf/archive/2011/09/09/allow-logon-through-terminal-services-group-policy-and-remote-desktop-users-group.aspx
In my case, I had the group added to the Allow Logon Through Remote Desktop Services but was not added to the Builtin\Remote Desktop Users group. After knowing this I made some changes to our situation and are now using the builtin\Remote Desktop Users group
rather than a new self made Security Group. I also added the Remote Desktop Users to the Allow Logon Through Remote Desktop Service in the Default Domain Controllers Policy as this is not done by default. By default only the Domain Administrators are able
to logon through remote desktop services.
You do not need the 'Log on Locally' permission within the Group Policies.
In short:
Add the desired users/groups to the 'Builtin\Remote Desktop Users' security group.
Add the 'Builtin\Remote Desktop Users' security group to the 'Allow Logon Through Remote Desktop Services' within the 'Default Domain Controllers Policy'.
Thank you anyway for the fast reply.
Have a nice day!

Multi devlepers to work through remote desktop on mac power?

Hello.
is it possible 2~3 devlepers to develop the iPhone application through remote desktop on a mac power?
if it is possible, please let me know the way.
thanks

Hi,
A connection was forcibly closed by a peer. This normally results from a loss of the connection on the remote socket due to a timeout or a restart. On a datastream socket, the
connection was reset. This reset could be generated locally by the network system when it detects a connection failure, or it might be received from the remote host (in TCP terms, the remote host sent an RST packet). This error is also possible on a datagram
socket; for instance, this error could result if your application sends a UDP datagram to a host, which rejects it by responding with an ICMP Port Unreachable.
Please check the following:
1. Ping the remote host you were connected to. If it does respond, this problem might have been a transient one (so you can reconnect now), or the server application you were
connected to might have terminated (so you might not be able to connect again).
2. Type tracert at the command prompt to determine the path to the host you were connected to. This won't reveal too much unless you know the router addresses at the remote end,
but it might help to identify if the problem is somewhere along the way.
3. Check if there is any related error log in the server side.
Thanks.
Jeremy Wu
TechNet Community Support

Sign-in through remote Desktop Services

To sign in remotely you need the right to sign through remote Desktop Services. By Defaults members of the administrators
Group have this right, if the group you are in doesnot have this right or if the righthas been removed from the
administrators group you need to be granted this right manually

Actually, the user needs to be member of "Remote Desktop Users" group to have this right, is not necessary to do this editing the user rights.
Jesús Peñaranda| MCP,MCT,MCTS,MCITP,MCSA,MCSE

2~3 devlepers to work through remote desktop on a mac pro?

Hello.
is it possible 2~3 devlepers to develop the iPhone application through remote desktop on a mac pro?
if it is possible, please let me know the way.
thanks

It's ok, found this
http://lists.apple.com/archives/macnetworkprog/2008/Feb/msg00070.html

UAG SP4 and Windows 8.1 Remote Desktop Connection 8.1

Hello,
I found on the description of SP4 for UAG the following: "Remote Desktop: Forefront UAG SP4 supports the Remote Desktop Connection (RDC) 8.1 client." Does that apply to the publication of servers using "TS Client Tunneling
(Windows Vista/Windows XP)"?
When I use my Windows 8.1 32bit client to connect to the portal, I can see the published application, click on the icon that is on the portal and it start the SSL Application Tunneling and the SSL icon appears at the Taskbar. Then it opens the "Remote
Desktop Connection" client. However when I type the name or IP of the machine to what I want to connect, it fails. Is something wrong? Or this is not working on Windows 8.1? My windows 7 cliesnt have no problem to connect using this application.
Thank you!

Hi Rob,
Let's confirm some situation:
Did you mean connect to Windows 7 from Windows 8.1 computer?
Did you mean the printer connect to another Windows 8 computer at home, and shared to that Windows 8.1 or the printer connect to that Windows 8.1 directly?
Firstly double check your settings:
1. Launch Remote Desktop Connection.
2. Click Options, and then click the Local Resources
tab.
3. Under Local devices and resources, select the Printers check box.
After that make sure that the proper printer driver version is installed on the remote computer.
Meanwhile, refer to this thread to check the port:
http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/win-7-remote-desktop-and-local-printing-not/544acb1b-a259-4170-bc05-2c6dbfd0ca05
Karen Hu
TechNet Community Support

Windows 8.1 Remote Desktop Not Connecting - "Credentials Did Not Work"

Hi,
I am having trouble connecting remotely to my work's servers. It was previously working fine, but today I upgraded to Windows 8.1 and now I'm getting an error. It says my credentials do not work. Now, my username and password are both still
valid, as they were used to log in from another computer. I initially thought it was that the firewall was preventing me from connecting, but I enabled the Remote Desktop app and it still does not work.
I'm kind of at a loss on where to go from here so any help would be appreciated.

Hi,
Please try the method below to fix this problem for test.
Open Group Policy, then navigate to
Local Computer Policy\Computer Configuration\Administrative Templates\System\Credentials Delegation\
Open Setting Allow Delegating Saved Credentials with NTLM-only Server Authentication, set it to
Enabled click on button Show... and in Show Contents
window add Value TERMSRV/terminal.server.com. Close all windows by pressing
OK.
In the end, Open cmd and enter gpupdate
command to update your policy.
Roger Lu
TechNet Community Support

Another Windows 8.1 Remote Desktop Connection Issue

I want to connect to my PC running Windows 8.1 from my tablet running 8.1. I have allowed RDC in the windows firewall. I open RDC on my tablet and enter my PC computer name, KENSPC, into the Computer field and get "Remote Desktop can't connect to the
remote computer for one of these reasons:
1) Remote access to the server is not enabled
2) The remote computer is turned off
3) The remote computer is not available on the network.
I get the same message when I use the IP address for the PC.
My PC is wired to my router and my tablet is wireless and both use my Microsoft account for credentials. I can ping the PC from the tablet, so I know the tablet can see the PC and I can open files on the PC from the tablet. I have "Allow
Remote Assistance connections to this computer" turned on. And I have, in fact, had HP help via remote assistance. But nothing I do seems to work. The steps as specified in the Helps do not work. Any help would be appreciated.
kenfrantz at outlook dot com

Hi,
According to your description,we need to know the detail edition of your remote PC.
You can use a PC running any edition of Windows XP, Windows Vista, and Windows 7, or a PC running Windows 8, Windows RT, Windows 8.1, or Windows RT 8.1 to initiate a connection.
But the remote PC must be running one of these Windows operating systems:
Windows 8.1 Pro ,Windows 8.1 Enterprise ,Windows 8 Enterprise ,Windows 8 Pro ,Windows 7 Professional ,Windows 7 Enterprise ,Windows 7 Ultimate ,Windows Vista Business ,Windows Vista Ultimate ,Windows Vista Enterprise ,Windows XP Professional.
Also, I would like to share the following article with you:
http://windows.microsoft.com/en-us/windows/remote-desktop-connection-faq#1TC=windows-8
http://www.microsoft.com/en-us/windows/enterprise/products-and-technologies/windows-8-1/compare/default.aspx
Hope this helps.
Regards,
Kelvin Xu
TechNet Community Support

Can't Print In App through Remote Desktop

Some users are stating that they are unable to print through a certain application when they are connected to an RDP server. When they try to print, this log comes up and the application crashes:
“Print driver host for 32bit applications has stopped working”
Problem Event Name:                          APPCRASH
Application Name:                             splwow64.exe
Application Version:                           6.1.7601.17777
Application Timestamp:                     4f35fbfe
Fault Module Name:                          mxdwdrv.dll
Fault Module Version:                        0.3.7601.17514
Fault Module Timestamp:                  4ce7c883
Exception Code:                                  c0000005
Exception Offset:                                000000000004e891
OS Version:
6.1.7601.2.1.0.16.7
Locale ID:
1033
Additional Information 1:                  0f86
Additional Information 2:                  0f86ddcc0aa605af31ef1b7f5abedf57
Additional Information 3:                  539e
Additional Information 4:                  539e0f43d86d39f144fdb012e341ed8d
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Hi,
Are they able to print from other applications while connected via Remote Desktop to the same server?
Are you using RD Easy Print driver for your redirected printers? If yes it may be that this specific application is incompatible with the RD Easy Print printer driver for some reason. One possible workaround may be to Disable Use RD Easy
Print printer driver first group policy setting and then install a matching printer driver on the server for each client printer.
-TP

Possible to login into Win7 machine via Remote Desktop?

hey guys, i've been trying to find a solution to be able to write to NTFS drives. i've read that using exFAT is a good way to go. the other thing i wanted to try was to login to a Windows machine that's connected to the NTFS drive and write to it that way. how can i do this?
thanks

If you want to write to the NTFS drive via the Windows system, then you want to have Windows share the drive, so that you can use Mac OS X:
Finder -> Go -> Connect to Server -> smb://windows.machine.address/share_name
This would mount the shared NTFS file system on your Mac OS X system and allow you to read and write to it.
If you need to access the Windows Desktop, then use the above mentioned Microsoft RDC software, or download CoRD from MacUpdate.com. Both good Windows Remote Desktop Clients.

HP Laserjet 1020 not working through remote desktop

I have a hp laserjet 1020 that I am vpn and remote desktop to a computer at work. I am suupose to be able to print from remote desktop to my local printer (the hp laserjet 1020) using the microsoft terminal Easy Print. The printer is showing up in the printer list, but when I try to print I get an error of Printer not ready. The printer is working fine on the local machine, just not through the remote desktop. I have install the printer drivers on the machine that I am remoting into , just to make sure. Is there anything else I can try. I am not finding any firewalls on either end blocking it?

After many months of frustration and 7 1/2 hours with Microsoft advanced prof support I've finally pinned down this printer and a slew of others. This problem as far as I have come across deals exclusively with HP printers. In simple terms: the drivers are flawed. This 1022 is a prime example. It prints locally and via TCP/IP just fine. I have about 7 other printers and dummy printers in my printer folder. Enter a remote desktop session and ALL of them populate except the 1022. This shows that the hooks and RDT finders are locating your printers and installing them properly as remote printers. All except the 1022.
Log out of your RDT session: goto the local 1022 setup and change the printer driver to a PCL driver. I used a 1200 PCL driver. Now log back into your RDT server and hockus pocus! there is your printer. Totally un-usable because the driver will not run this printer. Caveat: each time I did this XP crashed (I couldn't get to the properties TAB anymore -- I had to un-install the 1022 and then re-install it with at least 1 reboot in the process)
Moving on we go to the HP OfficeJet/LajerJet2840. Same thing. It won't pass through as remote printer in RDT. Go local. Set the printer driver to AppleLaserWriter8500 and boom. (same logout, change, back in steps) and your LJ2840 shows up and works.
While I will have to wait until tomorrow I am betting that this will fix the exact same problem with the HP Officejet 8500A all in one with the exact same problem.
Hey HP? Whats with the drivers??
Another work around if you have a static enough environment is to install your local printer that will not show up under RDT on the server, and then point the port to your fixed IP on your router, and passthru port 9100 to your locally installed printer that is failing. You can now be on RDT and chooses the network printer that is printing to the TCP address of your home (or office) router.

Windows 2012 R2 - Remote Desktop Sessions, RemoteFX, GPU, Blue Screen RemoteFX adaptor

Nvidia GPU GRID K1
Host Server - Dell Power edge R720 128 gig RAM 2 Xeon E5-2640v2 2.0GHz, 20M cache 8c
Windows 2012 R2 full installation – Bios and all hardware with latest updates.
Roles - Hyper V and Remote Desktop Virtualization Host
EPT, GPU, WDDM (latest drivers) compatible for RemoteFX and fully up to date.
I have disabled the video adaptor on the motherboard.
I cannot complete with administrative permissions;
dism /online /enable-feature /featurename:Microsoft-Windows-RemoteFX-EmbeddedVideoCap-Setup-Package
Error: 0x800f080c
Feature name Microsoft-Windows-RemoteFX-EmbeddedVidoCap-Setup-Package is unknown
Question 1 - because video card on motherboard disabled, do I still need to complete this command?
VM’s
**I’m not interested in VDI but more Remote Desktop Sessions and the option to ‘pinch and zoom with Windows 8.1 tablets**
VM1 - Windows 2012 R2 configured as generation 1 that is fully patched.
This VM is able to start up and run until I add the new hardware for the RemoteFX Video adaptor from within the Hyper V settings. When I start the VM the server blue screens. I have tried multiple VM’s with 2012 but same thing
If I created the VM as Generation 2 I am able to start the VM but the RemoteFX adaptor doesn’t appear in the device manager. I have read generation 2 isn’t compatible with RemoteFX.
VM2 – *Testing purposes* - Windows 8.1 Enterprise configured as generation 1 that is fully patched.
This VM I am able to start up and run the VDI after the RemoteFX video adaptor is installed, also the correct adaptor appears in the device manager. This seems to at least work correctly but I cannot pinch and zoom and the experience is poor.
GPU summary within the Hyper V settings state there are 4 physical GPU’s all of which can be used with RemoteFX and that 1 virtual machine are using the GPU (Windows 8.1 enterprise VM)
Firewalls off, latest RDP clients
I have read you should be able to use Windows 2012 R2 and we should be able to use the sessions with pinch and zoom but now and then you come across something that tells me different.
Question 2 – I need this to work with Windows 2012 R2 so we can use Remote Desktop Sessions
and the tablets can use pinch and zoom, anyone tell me what I may be doing wrong?

Hi,
Thank you for posting in Windows Server Forum.
As per my research, you need to run the command although video adapter is disabled on motherboard. If you install the RemoteFX cap driver, the integrated video adapter is disabled while the operating system is running.
For more information you can refer beneath article.
1. RemoteFX (with Hyper-V) is a serious business tool. For games.
2. Configure RemoteFX in Hyper-V running Windows Server 2012 with low end GPU
Hope it helps!
Thanks.
Dharmesh Solanki

Connecting _from_ a windows machine through remote desktop?

Similar Messages

Maybe you are looking for