Remote Desktop Connection - viewing screen

Hi, I just installed Remote Desktop Connection on my Imac at home so I can access my work PC. Everything works fine but my image I view is only about 5" x 6". It seems like a waste of the 27" screen. Does anyone know how I can increase the size of this so I can access the whole screen?
Thanks

Hi and welcome to Discussions,
personally I use Screen Sharing for accessing my work PC but I think this also applies to RDC.
What you get on your iMac is the screen resolution of your work PC when using RDC.
Since the 27" iMac has such a high resolution natively (2560x1440) the RDC window might be quite small when your work PC uses a resolution of 1280x1024 (as an example).
You might try to raise the resolution of your Work PC (should be possible through RDC when the resolution change on your Work PC is appliable without a restart of it) but eventually might come to a barrier when reaching the highest resolution possible on your Work PC.
Also keep in mind that the higher the resolution of the Work PC is, the more data has to be transfered which might slow down your RDC connection to a crawl.
Regards
Stefan

Similar Messages

  • Remote desktop connects, black screen, disconnects after a few seconds

    I have several servers running Windows Server 2012 R2. These servers are used for testing, and are members of a domain which has two DCs, each of which are running DNS Server.
    Yesterday I noticed one of the servers was having an issue with its remote desktop connection. If I try remoting into this machine, it connects to a black screen, sits there for 2-3 seconds and then promptly disconnects. No error message is given. I tried
    this from a couple different Windows 7 machines, and got the same result. I tried from my wife's iMac, which runs Jump Desktop, and too was met with the same result.
    I can, however, remote into this machine via RDP from my work-issued laptop, which is running Windows 8. However, I cannot remote into the problem machine via Remote Desktop Connection from one of the 2012 R2 servers--I am met with the same result as the
    other machines: connect, black screen for 2-3 seconds, disconnect without error.
    I can remote into all of the other 2012 R2 servers without issue from any machine, including the iMac. I am experiencing this problem on one server only.
    Since it is a test server, I reinstalled Windows from scratch this morning. This meant formatting the SSD and wiping everything out. I reinstalled the drivers, joined the server back to the domain and installed all of the updates available from Windows Update.
    And rebooted. And yet, the problem persists!
    I tried troubleshooting the "usual suspects," like turning off Windows Firewall, disabling antivirus software (currently none installed), disabling IPv6, setting a static IP instead of using DHCP, etc. I did notice the network adapter said it was
    on a Network, not a Domain Network. I corrected DNS settings, and the network reidentified itself as being on the ParietalBone.net network. And yet, the problem persists. Remote Desktop to this server still yields a black screen for 2-3 seconds, followed by
    a disconnect--EXCEPT from the aforementioned Windows 8 machine.
    I looked in the TerminalServices-LocalSessionManager log on the offending server, and there are no errors. I only see repeated entries that say "Session X has been disconnected, reason code 12," where X is 1 or 2. On a couple occasions, the reason
    code is 11. But I don't see any errors indicating a breakdown in security negotiation.
    Without any robust logs or debug details, I'm at a loss of where to look for a solution.

    I am cautiously optimistic that this may have been resolved.
    The network card in the computer was only a 10/100 built-in card, so I replaced it with a 1Gbps card. Interestingly, this did NOT resolve the issue. I ran netsh to check on the state of the chimney offload, but it was already disabled.
    In the network card properties, I changed the link speed and duplex from automatic to 1Gbps full, re-ran "netsh int tcp set global chimney=disabled" and rebooted. The problem persisted.
    And so I went to the network card properties and set IPv4 Checksum Offload, Large Send Offload (three of these -- IPv4, v2 IPv4 and v2IPv6) and TCP Checksum Offload (IPv4 and IPv6) to Disabled. Jumbo Frames were also disabled. I rebooted again.
    After the subsequent reboot, I was able to connect to this Server from machines that previously gave me difficulty. The only machine I haven't been able to test today (I'm in the office) is my wife's iMac, which is at home. However, I was able to bring this
    server up via Jump Desktop on my iPad, so I'm suspecting that perhaps one of the offload options was to blame. I'm not sure why this would allow me to connect from some machines but not others. And as noted above, I have many other machines running Server
    2012 R2 and they are NOT experiencing this problem. And I've not done any tinkering with network settings on any of them, so their chimney and offload settings are all in the default configuration.
    Regarding the other items -- NIC team, virtual machine, etc. -- there was no NIC team, no SRIOV and no RDMA involved.
    I had to turn IPv6 off on this machine, and only on this machine, because having it enabled was causing a lot more problems. DNS registration would keep failing, it couldn't pull Group Policy, it couldn't get time sync with the DC, etc. The servers are all
    set up with static IPv4 addresses. The router supports IPv6 but I'm not actually using it, so disabling IPv6 wasn't a concern to me.

  • Can't get rid of the black window Remote Desktop Connection left on my screen

    MacBook Air thinks that Remote Desktop Connection is open but I can't close the black window (where it shows the IP Address of the computer I had remoted into). It left the black windown opened on my screen. I can't even click on any menu tabs or take the app to the trash because it thinks it's still open. Well aware I can use different screens on my Mac but I want that black window gone! Thanks.

    I don't understand what you mean when you say 'I can view the main pages', but, you've probably set your video playback to full screen.
    Move the cursor to the top of the screen and go to View, down at the bottom of the list go to Video Playback, and then select 'None' from the list of options.

  • 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

  • When I am using remote desktop connection from PC1 to PC2 and if Firefox has opened before remote connection I will see only black screen in Firefox window on PC2. Os WinXP prof Sp3. If I run FF on PC2 remotely, FF works perfectly.

    I am using an integrated feature Remote Desktop connection on WinXP without any additional software. Connection through internal LAN, so speed is very fast.

    Hi,
    You can try to toggle the various options in the '''Experience''' tab of RD.

  • Remote Desktop Connection to Windows 8 PC from other computers crashing

    Hi all.
    Was hoping someone would be able to help me with an issue I'm having.
    I'm trying to get a LAN remote desktop connection established to my Windows 8 laptop. It's an HP ENVY 17t-2100 CTO 3D Edition Notebook PC. Note that I'm running Windows 8 Pro only - not 8.1 as HP haven't released 8.1 graphics drivers for this laptop and probably
    never will. The computer has a single user profile that has full administrator rights.
    I have followed numerous web tutorials on how to turn on Remote Desktop. I've gone into Advanced System Settings > System Properties > Remote > checked "Allow Remote connections to this computer". All seems ok to me. 
    The problem comes when I try to establish a connection. When the connection is made, it almost instantaneously crashes the session on the computer or device trying to connect. The RDP client on my Windows 7 laptop, Mac OSX or Mac running Windows 8.1 Pro just
    crashes, while the RDP iPhone or iPad app simply flickers for a few seconds then goes back to the main screen. Meanwhile, the HP ENVY loads the lock screen and displays a message saying XXX device is connected remotely and it won't let me log back in to kill
    the connection or do anything. I have to restart the computer from then to be able to use it again.
    I'm convinced there's not a problem with my local network as the HP ENVY can RDP into the Windows 7 laptop or Mac running Windows 8.1 without any problems. All computers are connected via Ethernet to a Linksys/Cisco wireless ADSL modem router which supports
    Gigabit. The iPhone and iPad of course connect to the wifi network from the Cisco/Linksys modem router
    I've also had a brief look at the RDP local connection logs. From what I can make out, they confirm that a user has successfully logged in, but they don't provide a crash log or a log of the user ever disconnecting, probably because I have to restart the computer
    to continue using it. Dead end there, it seems.
    The HP ENVY is connected to 3 external HP LED monitors. I've disconnected them and tried all devices with no luck. I've also played round with the RDP client settings to not mount drives or printers and the HP ENVY has no printers connected anyway, though I've
    done all I can to remove any printer drivers as I've read elsewhere that they are what could cause the problem, but I've had no luck. 
    If anyone can suggest anything more that I can try, I would be unbelievably grateful! I'm more than happy to provide screenshots or videos of what happens when I try connecting. I'm not sure what you experts would find immediately helpful so just ask away if
    you think I can provide anything.
    Thanks in advance!
    rugbyreff

    The first thing that I would try is to uncheck all of the boxes for local resources on computer running the RDP client. It is possible that a device, such as a printer or other redirected device, is causing the crash. You can also look under Event Viewer
    in the event logs of both systems and see if anything unusual appears when you attempt the remote connection.
    Brandon
    Windows Outreach Team- IT Pro
    The Springboard Series on TechNet
    Hi Brandon
    Many thanks for your suggestions. There's nothing in the logs that I could find, like I said in the original post. I've also tried connecting with bare minimum settings on all devices (FYI the iPad and iPhone version don't support the use of printers) and
    this still hasn't helped.
    If you have any other ideas I'd be very glad to hear them!
    rrugbyreff
    "If it's worth doing, it's worth overdoing" -- MythBusters

  • Remote Desktop Connection MAC to MS

    I work in the USA and connect to a server in Australia. I have been using a PC with a MS OS with great success. I just bought this Mac Book Pro Retina 15" and have not used a Mac before. I am not sure I can keep it if I cannot get better performance when working connected remote to the Australian server. This would be a shame because it is a fantastic machine. I have been using a free MS Remote Desktop Connection for Mac program to connect and work. Does anyone have experience working from a remote desktop connection using the Apple $79 Remote Desktop Connection program and is connecting to a MS OS server?
    The main issue is speed, and the view does not fill the screen. It does not fill the screen with either view options, "Fill or Full Screen". There is about 1 1/8 on either side with the best option of "Full Screen" and 1 1/2 to the edge of the lid. The program always creates an error message as well, but it is just a cert warning.
    I have some time left to decide if I can keep this Mac Book or need to go back to a PC. I really do not want to spend another $85 if the Apple program is not much better than the MS free program?
    Any experience with connecting using the Apple software to a server for tasks like email in MS Outlook and data base work would be appreciated.
    Thanks,

    Apple Remote Desktop is intended for managing networked Macs. While it can be used to connect to a Windows system by running VNC on the Windows box, it's no better than Microsoft's RDC and is often tricky to set up. I've been using iTap Mobile RDP, available in the Mac App Store or from the company's web site, to connect to my Windows systems. iTap Mobile is much faster than either Microsoft RDC or CoRD (a freeware RDC client), in my experience, and very stable and has been well worth the money.
    You can get a trial version of iTAp Mobile here and test for yourself before purchasing:
    http://itap-mobile.com/desktop/rdp
    Regards.
    Disclaimer: any product suggestion and link given is strictly for reference and represents my opinion only. No warranties express or implied. I get no personal benefit from the sale of any product I may recommend in any of my posts in the Discussions. Your mileage may vary. Void where prohibited. You must be this tall to ride. Objects in mirror may be closer than they appear. Preservatives added to improve freshness. Contestants have been briefed on some questions before the show. No animals were harmed in the making of this post.

  • Remote Desktop Connection Manager can only open 6 sessions at a time on Server 2012

    I am only able to open, and view thumbnails, for a maximum of 6 RDP sessions on my Server 2012 box at a time in Remote Desktop Connection Manager (RDCM). If I add more sessions I just get a variety of connection errors for the additional sessions. If I activate
    a 7th session one of the existing 6 sessions goes off-line with a connection error message. Sometimes the error says 3334, sometimes the error says 0x8345000E, and sometimes it just says there is a connection error.
    I have checked Group Policy on the server to ensure I don't have any settings restricting the number of RDP sessions.
    In fact, I will often have 30 or 40 RDP simultaneous sessions opened, I am just not able to view them all in RDCM. I have seen reviews of RDCM with screenshots showing dozens of thumbnails so it seems to be something that's possible to do.
    Are there any settings I should make on the server to allow RDCM to connect to more than 6 simultaneous RDP sessions?
    Just to be clear, all these RDP sessions are running on the same server. Also, I am just using the trial license for Server 2012 and Remote Desktop Services right now. I don't think that should have an impact, but I wanted to be thorough.

    Thanks Jakub for "corflags" info.
    Unfortunatelly it doesn't work because running mRemoteNG.exe process in 64bit can't load MSTSC ActiveX component (referenced assemblies) because original files were assembled from 32bit dll [mstscax.dll]?
    Error message when making RDP connection:
    Could not load file or assembly 'Interop.MSTSCLib, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.
    I was able to create new AxInterop.MSTSCLib.dll and Interop.MSTSCLib.dll assemblies from 64bit dll version and now it works with "AnyCPU":-)
    http://www.filedropper.com/axinteropmstsclib-mremoteng
    Using AxImp.exe and TlbImp.exe didn't worked for me because it creates assemblies in wrong namespace "MSTSCLib" instead of "Interop.MSTSCLib" (AxImp.exe) and TlbImp.exe for changing namespace generated many "marshaled errors"
    so final .dll wasn't working.
    Adding MSTSCAX.dll reference in Visual Studio directly created correct and functional assemblies. Who don't know how to create 64bit compatible assemblies or don't have Visual Studio, feel free to check linked file.
    Hope it helps
    P.S. Sorry for possible technical misinterpretation, I am not programmer so creating new assemblies was trial-error process...

  • Using a remote desktop connection with the Macbook pro.

    I use the remote desktop connection on the Macbook pro and am unable to exchange info between the mac and the remote connetion windows. For example, if I am writing an email from the remote connection and want to attach a document, photo etc. that I created on the Mac, it just doesn't work. It seems like the Mac and the desktop connection are completely seperated eventhough they are both on the screen in front of me. the systems I use for work are not Apple compatible and will not work on anything other than windows explorer and in my case the remote desk top connection. Any ideas!

    Welcome to Apple Discussions
    Try running in 'ClamShell' mode (MacBook Pro lid closed and using an external keyboard and mouse) with the Gateway connected and then run System Preferences/Displays, it should show then ...
    My 1920x1080 monitor shows the following:

  • Remote Desktop Connection freezes Windows 7 64-bit

    At home, I just upgraded from a Windows 7 Ultimate 32-bit desktop to a new Dell with Windows 7 Ultimate 64-bit OS.  Remote Desktop Connection from my old home PC to my work PC worked great for years even after upgrading both to Windows 7 Ultimate.  Now everytime I try to use Remote Desktop Connection (RDC) to connect into my work PC (with Windows Ultimate 7 32-bit) the RDC window will freeze after a new seconds of use.  If I wait approx 3 minutes the RDC window will unfreeze for a few seconds before freezing again.  If I minimize the RDC window on my home PC, I can continue to work because it's only the RDC window that is frozen.  Here is everything I've tried already that has not helped:
    1. Trying reducing the home PC screen resolution
    2. Downloaded the latest 64-bit driver from NVIDIA for the GTX 260 graphics card
    3. Taken my home PC to work to test behind the company's firewall--doesn't help
    4. Disabled Window Auto Tuning (suggestion from this website)
    5. Called Dell support--they tried for about an hour to help but couldn't; thier suggestion was to order Windows 7 32-bit version OS and install it
    6. Tried running the 32-bit version of mstsc.exe - no help
    7. Using MSCOMFIG, disabled all Startup items - no help
    I have another home PC running Windows XP, it works perfectly using RDC to connect to my work PC.  Also, I have no problem at all using RDC from my work PC back into my home PC (the other direction).
    Here may be a clue:  if I start up my new Dell Windows 64-bit OS in Safe Mode, the RDC session does not freeze.
    Any suggestions would be appreciated!

    Hi,
    Since it works in Safe Mode, I suspect this should be related to some conflicts, please try the methods in the following Knowledge Base article to have a check:
    How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7
    In addition, please also ensure the NIC drivers on all of the computers are up-to-date.
    Hope this helps. Thanks.
    Nicholas Li - MSFT

  • "remote desktop connection has stopped working" When printing from remote desktop connection

    I have been having a issue when using a windows 7 machine. I have Remote Desktop to a session on Windows2008 R2, I am using the local printer resources to redirect the printing. However everytime i try to print it crashes the remote desktop application.
    Gives me "remote desktop connection has stopped working." I have 4 other computers connected and printing with no issues what so ever. This only happens when i print. It does print by the way just the application crashes.
    -I have also updated the printer drivers to newest possible thru the manufactorer website. The printer is a Brother MFC-8890DW. Windows 2008 R2 is up to date for the RDS server. 3 other machines are able to Remote in and print. The user is able to print using
    diffrent machines just not the Windows 7 machine.

    Hi,
    Happy to hear that you resolved your issue. For another issue which you are facing here trying to provide some suggestion.
    As you have commented that you are facing issue with second screen resolution on wide screen. The setting which I am suggesting can only applies when you are using multi-monitor Remote Desktop connections.  If you are making Connections using a single
    monitor do not use this setting. 
    So for this you can try to apply “Limit maximum display resolution” setting in group policy, where you can mention the width & height for the screen to display. The setting can be applied on below mentioned
    path.
    Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment
    Meanwhile sharing article with you for more information.
    Remote Session Environment
    http://technet.microsoft.com/en-us/library/ee791847(v=ws.10).aspx
    Hope it helps!
    Thanks.

  • Remote Desktop Connection With Custom Certificate on Windows 8.1 fails

    I'm trying to establish a secured remote desktop connection without success.
    The setting
    There are some local pcs with windows 8.1 Pro and windows 7 Pro, no server-edition. I've created a self signed ca-certificate with openssl for Windows. I used this to sign custom certs for the local windows-pcs, which are installed at mmc -> certificate
    snap-in for local computer -> My Certificates -> Certificates. The networkdriver has the right to read the key. The sha1-fingerprint of the custom signed certs are registered at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
    -> SSLCertificateSHA1Hash = sha-1 hash of the custom local cert. Additionally the revocation-list is restrained to the local list by setting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp -> UseCachedCRLOnlyAndIgnoreRevocationUnknownErrors
    = 1.
    The results
    The connection form win 8.1 to win 7 works. The connection info confirms that it is a veryfied connection. The connection to windows 8.1 fails after entering the credentials with error: No connection possible. Network Level Authentication is set, but other
    level don't work as well. The log (Event Views -> Applications and Services Logs -> Microsoft -> Windows -> TerminalServices-RemoteConnectionManager -> Admin) says "Remote Desktop Services has taken too long to load the user configuration
    from server" and "The Local Security Authority Cannot Be Contacted" (error 0x80090304)
    Aditional information
    The connection via linux (remmina) works for win 7 and win 8.1, but I have no information about the encryption. It is the same with the Microsoft Remote Desktop Tool for Android.
    Maybe it is accociatet with a different cert handling by Windows 8.1 but I couldn't find further information or a solution in the internet.
    Best regards
    abditus

    I solved the problem!
    The default openssl certificate signature algorithm is md5RSA but it doesn't work with windows 8.1.
    It is at least sha1RSA needed.
    By adding "default_md = sha1" to the openssl.cnf you create certs with sha1RSA and it works fine.
    Beste Gegards
    abditus

  • Remote desktop connection in windows 7 pro

    I have a problem accessing remote desktop connection using windows 7 64 bit.
    My remote desktop connection shell version 6.3.9600 shows the Network Level Authentication is not supported.
    My other computer also win 7 pro 64 bit has a different shell version 6.2.9200 that supports Network Level Authentication.
    How do I go backwards to shell 6.2.9200?
    I have been trying use remote desktop using the more robust security and could not figure out why I could not log.
    I have screen shots of the two shells and my system screens

    Hi,
    Configure Network Level Authentication
    Click Start, click Run, type regedit, and then press ENTER.
    In the navigation pane, locate and then click the following registrysubkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
    In the details pane, right-click Security Packages, and then click Modify.
    In the Value data box, type tspkg. Leave any data that is specific to other SSPs, and then click OK.
    In the navigation pane, locate and then click the following registrysubkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders
    In the details pane, right-click SecurityProviders, and then click Modify.
    In the Value data box, type credssp.dll. Leave any data that is specific to other SSPs, and then click OK.
    Exit Registry Editor.
    Restart the computer.
    Hope this helps!
    Andy Altmann
    TechNet Community Support

  • Remote Desktop Connection with WRT54G from Novice

    Well, I’m usually pretty good at using Google and forums to eventually figure out how to fix my problem but this one absolutely has me stumped and I’m hoping someone out there has an answer for me. For the record, I have probably a beginner/intermediate knowledge of computers so if you know the answer to my problem, try to explain it simply! ****TO ANYONE WHO TAKES THE TIME TO READ THIS THING AND CAN OFFER SOME ADVICE-THANK YOU!!!!***
    THE PROBLEM
    I would like to be able to use Remote Desktop to log into either of my home computers from basically any computer on the internet.
    THE SETUP
    I have two computers, whose names are LAPTOP and DESKTOP that are both running Windows Vista Ultimate. Both of the computers are connected to a Linksys WRt54G Router ; one wired, the other wirelessly. The Linksys router is then connected to a Westell DSL Modem that connects to AT&T’s internet service.
    SETTINGS
    My DSL service only provides me with a dynamic IP address so I signed up with no-ip.com. Through that site, I bought a domain name and downloaded their small program that runs in the background of my desktop computer. The program checks what my IP address is every couple of seconds and if it changes, it notifies their server so that anyone who types in my domain name is directed to the new IP address.
    ROUTER (Firmware 4.20.6)
    Basic Setup Page: The Router Name is just the model number, the Server Name is my DSL provider and the Domain Name is the name I chose and registered with No-IP.com. (www.mydomainname.com, for example.) DHCP Server is ENABLED. DDNS Service is DISABLED. Under Advanced  Routing, it is set in GATEWAY mode.
    Security Page: Firewall Protection is ENABLED. Block Anonymous Internet Requests is NOT checked. Filter Multicast, Filter Internet NAT Redirection and Filter IDENT ARE checked.
    Applications and Gaming Page: I chose two port numbers, one for each computer that I want to connect to. On the first line, I have Application: RDP, Port Range: 49200 to 49200, Protocol: Both, IP Address (The IP address of the computer I want to connect to) and the Enable box IS checked. [I did the same thing with the second line for the other computer, but with a different port number and that computer’s IP address)
    Administration Page: Access Server is HTTP, Wireless Access Web is ENABLED, Remote Management is ENABLED through Port 8080, and UPnP is ENABLED.
    WINDOWS VISTA SETTINGS
    First, I went to the Remote Desktop Settings of the target computer and ENABLED Remote Desktop Connection and allowed computers running any version of Windows. I also confirmed that the box labeled “Allow This Computer To Be Controlled Remotely” WAS checked. I then made sure that I had a user name, it had a password associated and that it had Administrator priveledges. I went back to the Remote Connections screen and added the user name as being allowed to connect. (I think this is redundant since it’s both the owner of the computer and has Administrator Status.)
    Next, per Randomly Googled Internet Advice, I went into the registry and changed the port number that Remote Desktop listens for incoming connections to Port 49200 to match the router settings. [Registry Entry that I modified was: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp]
    Finally, I went to the Windows Firewall and Added (opened) port 49200 for use as a Remote Connection. I kept the protocol as TCP and confirmed the scope was set for Any Computer.
    CURRENT STATUS
    If I go to Explorer and enter my IP address with a colon and the specify port 8080, I can get the login screen for the router. Same thing happens if I just enter my domain name and port 8080. However, if I switch the 8080 port and use one of the ports I chose (49200), it cannot connect, either using the Public IP address or the domain name. (I’m trying to connect using a wireless card and not connected to my local network so I know it’s the same as if I was anywhere else.)
    I’m not sure why it won’t let me connect; it feels like the router will not allow the connection to pass through it to the port I’m asking it to forward to. I’m guessing someone out there who took the time to read it is shaking their head at all the information I provided and knows the one dumb thing I missed!
    Thanks again!

    I'm attempting to do the same thing with my home network. the only differences are that i have cable internet from comcast and i'm running vista business. my router is the wrt54gs. i'm assuming that the web page is similar for adjustmants. To be honest i cannot figure out how to do a remote destop too. so i went to www.logmein.com and installed the program. once installed to to every computer you want to have access too and log into the website. then click on the add computer icom. full control app sharing etc... even better when you connect you have the option to deactivate the local host mouse and screen to prevent anyone seeing what your doing.
    If you resolve the router issue would you let me know. plz thanks
    Forest

  • Remote Desktop Connection Client 9.3.9600 unable to connect to Server 2012 RDS via Gateway

    Hi,
    I have a Windows Sever 2012 R2 RDS environment with two Gateways servers configured in high availability mode (RD Web Access, RD Gateway, RD Connection Broker roles installed) and four Windows Server 2012 R2 RDS Session Hosts. The servers are all running
    the most recent public server updates. With this configuration I when connecting externally using a Windows 7 computer with the older Remote Desktop Connection client (6.1.7601) I am able to connect without any problems however when I try connecting with a
    newer client from a computer running Windows 8.1 and the 9.3.9600 client I am unable to connect. 
    At the moment a NAT rule is configured to pass 80/443 traffic to only one of the RDS gateway servers, I've removed our load balancer from the configuration for the moment to reduce the complexity. 
    No error is generated by the client when it tries to connect it just stops trying to connect after a while.
    On the Gateways servers event logs for 
    Things I have looked into so far.
    - I've double and triple checked the RDS configuration and checked it against one of my other clients configurations that is working and they are identical. 
    - Connecting from an older client version works fine.
    I'm not sure what else can be checked does anyone have any ideas?

    Hi,
    1. What entries are you seeing in the RD Gateway's log?  Event Viewer\ Applications and Services Logs\ Microsoft\ Windows\ TerminalServices-Gateway
    2. How come you are not forwarding UDP port 3391 in addition to TCP port 443?  It should work without UDP, but you will not have UDP support which is one of the benefits of RDP 8.0/8.1.
    3. Are there any non-default group policy settings being applied to the servers and/or client PCs?  To be clear, I'm asking if any changes have been made to the default local and domain security policies, group policy objects, new GPOs that may have
    been added, etc., that are applicable to the servers and or client PCs.
    -TP

Maybe you are looking for