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

Similar Messages

  • 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?

  • Apple remote desktop will not show my  computer screen on class screens

    Hi
    I hope someone can help. i have just set up a mac suite running latest OS X 10.10 using apple remote desktop. The system is a bit sensitive but mostly works fine. The odd computer drops off etc.
    However, I want to be able to show the teacher computer on all of the class screens as the projector screen is quite small at the front of the class. When I set up screen share it says it is working but it does not show on their screens. They do get a screen sharing message on the menu bar of their computers but nothing happens. Am I missing a setting? I think I am doing right!
    thanks
    Tim

    Hi jsyedu129,
    Wondering if you found a solutions to your problem. I'm having the same problem. Can't not share my screen with classroom computers. Love to know if you have got this to work.

  • Xfinity online not going to full screen

    Hey idk if xfinity people look at this at all, but with my google chrome browser it won't allow me to hit the button to go to fulls screen. It has set dimensions for the video and cuts off all the options that typically run across the bottom of the screen if you can't see it. anyone else have the problem or know whats wrong? I did install the most recent adobe flash player to and it didn't work.

    Aside my not being able to access the full screen, the mobile site consistently prompts me to update the account with a new email address. Very frustrated

  • Remote desktop connections not showing in server manager 2012 for one of the session hosts

    This is a three server deployment with one server being the connection broker, gateway, licensing, etc with two session host only servers.
    rdmgr
    rd1
    rd2
    Using the server manager on the rdmgr connection broker (or any other server for that matter) yields only connections from rd2 with nothing from rd1 displaying.  
    Users can connect to rd1 without issue.
    At one point rd1 had the connection broker role installed also but high availability was not setup.  I removed the role hoping it would correct the problem but no luck.
    Any help would be appreciated.  Thanks.

    Hi,
    1. Is rd1 part of a collection?
    2. On rd1, in Computer Management, is the broker's computer account a member of the local RDS Management Servers group?
    3. If you run the below command do you get a list of sessions:
    query user /server:rd1
    4. Any errors/warnings in either the broker's or rd1's event log?
    Broker: Event Viewer\ Applications and Services Logs\ Microsoft\ Windows\ TerminalServices-SessionBroker
    rd1: Event Viewer\ Applications and Services Logs\ Microsoft\ Windows\ TerminalServices-SessionBroker-Client
    Both: System and other logs
    -TP

  • 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?

  • 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.

  • 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

  • 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.

  • 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 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

  • 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 - 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

  • 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.

Maybe you are looking for