Search Results

Search found 59 results on 3 pages for 'mstsc'.

Page 1/3 | 1 2 3  | Next Page >

• MSTSC crash on connect

  - by rotard

  We are supporting a client with primarily Windows XP machines. The users need to use Remote Desktop to connect to a terminal server. Unfortunately, after upgrading to SP3 on some machines MSTSC.exe crashes when they try to connect to the terminal server (a Win 2008 machine). The resolution I have found has been to revert to an older version of MSTSC as described here: http://it.tmod.pl/Blog/EntryId/115/Remote-Desktop-Connection-crashes.aspx . Another tech at my company independently arrived at a similar solution. Unfortunately, now some of the user's printers are missing (when connected tot he terminal server). Has anyone else seen this issue? How did you resolve it?

  Read the article

• Change the default resolution of Remote Desktop Connection (mstsc)

  - by Simon

  Is there a way to change the default resolution that mstsc uses? I dont want it to default to the full resolution of the client machine.

  Read the article

• Is it possible to increase the size of mstsc's connection cache

  - by mollmerx

  On my windows box mstsc.exe caches the last ten hosts I connected to. However, I connect to about 15 on a regular basis, so increasing the number that the combobox remembers would be really welcome.

  Read the article

• Windows Remote Desktop (RDP/MSTSC) fails with Error Code: 5

  - by BryCoBat

  I have 2 Windows XP boxen: A (running XP SP3) and B (running XP SP2). I'm using Remote Desktop to connect from A to B. When I connect, I get the login screen (which is slow to respond to keyboard/mouse input), and after logging in, I get the following: Fatal Error (Error Code: 5) Your Remote Desktop session is about to end. This computer might be low on virtual memory. Close your other programs, and then try connecting to the remote computer again. If the problem continues, contact your network administrator or technical support. I've seen one way to (sometimes) get in by opening a second RDP session to the same box [1], and if I wait long enough sometimes it will go ahead and log in anyway. Is there something broken/missing on the PC I'm trying to remote in to? Edited in reply to djangofan: There's nobody listed under "Lock pages in memory". When the double login trick works, a glance at Task Manager shows plenty of free memory, 800MB available out of 1.5 GB. (Performance tab, Physical memory) For what it's worth, this happens consistently after a reboot. What sort of exact info would be useful? There's very little remaining installed on that machine that's not Windows + Office... [1] found at http://www.fdcservers.net/vbulletin/archive/index.php/t-1580.html

  Read the article

• Supply username and password to mstsc

  - by Will

  In previous versions of the remote desktop client there were methods of passing in the password through various methods. Has anybody found a good method using the latest remote desktop client? I'm aware of LaunchRDP but that doesn't meet our needs. Perhaps somebody knows the algorithm so I can dynamically assemble RDP connection files?

  Read the article

• MSTSC RDP over the public internet

  - by stuart Brand

  My first question so please be gentle :) I have a client who is insisting that they have to let their third party vendor support access to there server directly from the internet via RDP. Our policy does not allow direct access to the infrastructure from outside of the data centre for administration except from an approved VPN connection and then virtual desktop there on to the servers. I am now in the situation where I must give good reasons why it is dangerous to use RDP over the public internet. any help would be appreciated Thanks in advance Stuart

  Read the article

• MSTSC Not working, disconnects shortly after connecting

  - by F4r-20

  I'm currently having a problem connecting remotely to a server. It is a brand new build Windows 2008 R2, remote users are enabled. I'm trying to connect from a Windows 7 machine. Everytime I remotely connect to the server it will stay connected for a matter of seconds (maybe 3-5) and then disconnect and I get the standard old cannot connect and list of reasons it could be. Then I cannot connect again and get this prompt until I restart the server. As soon as it's finished restarting, it happens all over again. The network and hardware configuration between the two machines is completely reliable. Does anybody know what else I could try? Thanks.

  Read the article

• Strange RDP / Remote Desktop problem

  - by John Landheer

  I'll try to be as specific as I can be: Server is running SBS 2008 R2 (with all updates) Server is connected to the internet Server has 2 NIC's, one is disabled Server is running RDP Service (accessible directly from the internet, I know, not as secure as it should be) Computers A and B are on the same local net. Computers A and B are both Windows 7. Users X and Y are both admins on the server Computer A can connect as user X to the server with mstsc Computer A can connect as user Y to the server with mstsc Computer B can connect as user X to the server with mstsc computer B CANNOT connect as user Y to the server with mstsc! The last point is the problem, I get an authentication error. This used to work flawlessly for the last year. The server and desktops have been rebooted. I find it very strange....

  Read the article

• Strange RDP / Remote Desktop problem

  - by John Landheer

  I'll try to be as specific as I can be: Server is running SBS 2008 R2 (with all updates) Server is connected to the internet Server has 2 NIC's, one is disabled Server is running RDP Service (accessible directly from the internet, I know, not as secure as it should be) Computers A and B are on the same local net. Computers A and B are both Windows 7. Users X and Y are both admins on the server Computer A can connect as user X to the server with mstsc Computer A can connect as user Y to the server with mstsc Computer B can connect as user X to the server with mstsc Computer B CANNOT connect as user Y to the server with mstsc! Error that username/password is incorrect. The last point is the problem, I get an authentication error. This used to work flawlessly for the last year. The server and desktops have been rebooted. EDIT: I tried: prefixing domain to the username prefixing the server computer name to the username change the password copy/paste the password from notepad to make sure it was correct I find it very strange.... EDIT: The computers are not on the same subnet as the server. The server is at my hosting provider. All computers as all users can reach the web app that is running on the server.

  Read the article

• Diagnose remote desktop freezes in Windows 7 when no BSOD?

  - by Paul Smith

  Okay, I'm getting no joy from Asus or Microsoft on this, so hoping for some clues on how to narrow down the cause. I have very frequent OS freezes, always & only when running Remote Destkop Client (mstsc) in Windows 7 x64. I never have a bluescreen, and there is never a minidump. The display & input just freezes -- no keyboard, no mouse, and sound will just continue the last wavelength if any. So far, I can't find a way to trap the hang given that there's no bluescreen; advanced startup & recovery settings for system failure are "Write an event" checked, "Automatically restart" checked, and "Kernel memory dump". I've updated to the lasted BIOS, and tried a few different graphics drivers, both generic & ATI. I've also tried disabling Aero, and everything about the remote desktop experience (incrementally unchecked every box in the mstsc - options - experience tab), even disabled/unplugged external monitor to make sure it wasn't a dual-monitor issue. My specs are: Asus G73jh notebook 8GB RAM ATI Mobility Radeon HD 5800 Series graphics (recently tried driver versions 8.791.0.0, 8.801.0.0) American Megatrends G73jh.211 BIOS (7/27/2010) Windows 7 Home Premium x64 Windows Memory Diagnostic passed all of the following at least 3 times with no errors: MATS+ INVC LRAND Stride6 WMATS+ WINVC This notebook is better than most at removing heat (laudable vent design), so I'm not inclined to suspect thermal causes (especially since running 1080p video for hours has never caused a freeze, but mstsc does, reliably, within 5 minutes to an hour). This did seem to start happening after a Windows Update, but I've since reverted every patch applied since a week before the first occurrence, with no joy. (And I'd only had the PC for a couple weeks before that, so it could have been chance + less actual time spent remoting at the beginning.) I'm at my wits end, and I bought this laptop primarily as a remote terminal client (go figure, right?) Any ideas on how to identify the cause of this? Thanks!

  Read the article

• Does the color depth on terminal services have an effect on the experience

  - by Midhat

  I connect to a remote computer using mstsc on a slow connection. Now I have set the settings in the experience tab to the lowest. I was wondering if reducing the color depth will improve my experience any further

  Read the article

• The RPC services keeps stopping

  - by oshirowanen

  For some reason, the RPC service keeps stopping which prevents me from remoting into the server. When this happens I have to manually make my way to the server to restart it as simply starting the service (which does not complain when starting), does not let me remote into the server. I have to restart the server manually to be able to remove into the server again. It seems to be happening a few times a day. Does anyone know why this might be happening?

  Read the article

• Using Terminal Services 'query' in batch file

  - by dboarman-FissureStudios

  I have a batch file that checks several of our servers for a user. From the command: query user %userID% /server:ServerName I want to capture the output before it goes to the screen. Is there a way to redirect the output to a variable? The basic gist of what I want to accomplish is this - we iterate through our servers: query user %userID% /server:Server1 query user %userID% /server:Server2 query user %userID% /server:Server3 query user %userID% /server:Server4 Instead of outputting a message that the user could not be found on a specific server, I would like for it to only notify me if it finds the user on a server.

  Read the article

• Recent remote desktop connection sources

  - by altendky

  How can I identify the source of recent remote desktop connections to my computer? While at work I connected to my desktop there (XP SP3) from another system with files I want to access. I am now at home and connected to my desktop at work but I do not know the name of the other system there.

  Read the article

• We are able to connect to remote desktop but randomly keyboard does not work in remote machine. Wher

  - by user340071

  Description: The project deals with interaction with the remote desktop connecting through web browser (Internet Explorer). What we did: We have created an activex which installs through the web browser into client machine which lets the user to connect to different servers through web browser. What is in Activex In Activex we used an MSTSC.lib file and by passing the relevant parameters to it. It connects to the remote Desktop. What are the Problems facing now? We are able to connect to remote desktop but randomly keyboard does not work in remote machine. Where as mouse works perfectly.

  Read the article

• 'The rpc server is unavailable' or 'access is denied' error when using Remote desktop Services Manager on Windows 7 (but mstsc.exe works!)

  - by tbone

  I am trying to connect to a Windows XP workstation from a Windows 7 Ultimate workstation using Remote Desktop Services Manager. I am able to do a Remote Desktop (mstsc.exe) session from the Win7 machine to the WinXP machine with no problem at all. When running the Remote Desktops Admin (tsmmc.msc) too on a Windows XP box, I can also connect with no problem. However, when I use the new Remote Desktop Services Manager on Windows 7 and try to connect, I get the error: "The rpc server is unavailable" What could cause this? Has there been some fundamental change in Remote Desktop Services Manager, does it connect in a different way somehow? Update #1 Turned off firewall on the Windows XP box and the "The rpc server is unavailable" error went away; so RDSM seems to be using an entirely new port/connection/service compared to mstsc.exe or the old Remote Desktops Admin tool. Now... after disabling the firewall, I get a new error: Access is Denied. After doing some googling, I found some articles discussing this; basically, the error is very misleading - the actual problem is, if either side of the connection has dual monitors, and they are not both Win7 Ultimate, then you cannot connect using Remote Desktop Services Manager...the reason is, by default it uses the /multimon switch, and this switch requires a certain level of Windows license - and, there seems to be no way of changing this default (if anyone knows of a way to change this default, please post an answer or comment!). Nice going Microsoft. http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2rds/thread/4d06278f-e0f4-4f8e-a8e1-3697ee967ef4 http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Windows/Windows_7/Q_26225743.html

  Read the article

• "Snapping" when in RDP

  - by Paul

  I am using mstsc.exe version 6.0 (Remote Desktop non-Metro version) from an XP machine and cannot get Windows 8 snapping to work. I can drag a metro app window to the left or right, but it doesn't stick, it just bounces back to full screen. The snap bars do not appear. The client PC has two monitors, each with a resolution of 1280x1024. While mstsc.exe 6.0 does have an option to use both monitors simultaneously in normal settings, I am launching it with spanning enabled: mstsc.exe /span So the effective resolution in the session is 2560x1024. Is there a trick to getting this to work over RDP?

  Read the article

• Remote Desktop Client Crashes following domain join

  - by Roberto Charlie Ciarleglio

  I recently joined my laptop to our windows domain and now the remote desktop client crashes when i try and connect to any machine. It works if I run as administrator but not ordinarily. The domain join migrated my local profile to the domain profile which i think is where the problem lies. I'm guessing its a permission thing as I had a similar problem with dropbox and had to delete reg keys and reinstall. I can't figure out how to fix this problem though. The event viewer shows this: Faulting application name: mstsc.exe, version: 6.1.7601.17514, time stamp: 0x4ce7ab44 Faulting module name: FACredProv2.dll, version: 2.4.95.1, time stamp: 0x4bb8d766 Exception code: 0xc0000005 Fault offset: 0x00000000000025b2 Faulting process id: 0xb24 Faulting application start time: 0x01cd43fbd3a81fba Faulting application path: C:\Windows\System32\mstsc.exe Faulting module path: C:\Windows\System32\FACredProv2.dll Report Id: 154ee55a-afef-11e1-a443-b8ac6f704c5d any help would be appreciated!

  Read the article

• RemoteApp Security Warning

  - by nairware

  I have a Windows 2012 Standard x64 RemoteApps RDWeb portal where I can launch apps. We have one remote app in particular which is RDP (mstsc.exe). Whenever a user launches it, they receive three different prompts--the second one is this alert (shown below). How can I get rid of this alert? I have other RemoteApps launching as well, and they do not throw errors or alerts like this one. And they are applications with the .exe extension, so I do not understand what is so unique about the RDP RemoteApp that would cause this alert. One thing perhaps worth mentioning is this particular RDP remote app points directly to the mstsc.exe executable residing on a particular session host/terminal server (as shown in the "From" value of the warning). As such, a gateway server would not be used to load-balance and choose the RDP client launched from a session host at random. This RDP RemoteApp is explicitly associated with one particular terminal server.

  Read the article

• Remote Desktop Client in Windows 7 Full Screen Issue

  - by Langdon

  I'm running Windows 7 Home Premium on a new laptop and I'm having one of the most annoying issues with the RDP client (mstsc.exe). If I restore the full screen RDP window, I lose the ability to go back to full screen. The only way I can get it back is by running a new instance of mstsc, setting the option back to full screen, and connecting again. I don't have this problem on any other machine (granted, this is the only copy of Home Premium I have). Is this a known issue? Is there a patch/fix? It's pretty obnoxious, I'm having to train myself to not use the restore button and only minimize it (which limits uses).

  Read the article

• Windows non-responsive during Remote Desktop connection

  - by pvieira

  This is Windows 7 Ultimate 64 bit. I use the command mstsc to establish a Remote Desktop connction to a remote server. The login window shows up, and while I'm entering the password the system almost freezes. Each character of the password takes 3 or 4 seconds to be accepted, and all other opened programs are not accessible. This behavior tends to happen only the first time I use mstsc. If I used it again moments later, everything is normal. Whar can be the cause of this problem?

  Read the article

• Magnetic Stripe Reader over Terminal Server has random Uppercase/Lowercase nonsense

  - by Peter Turner

  The Magnetic Stripe Reader that I'm using and testing is just supposed to be sending keystrokes. Unfortunately, it seems to randomly be sending upper case and lower case keystrokes, sometimes substituting % for 5 and ^ for 6 and vice versa. (If you've ever programmed for a magnetic strip reader, you know that's not a good thing.) Is there something in the RDP protocol that causes this? I've got kind of a convoluted system, running XP inside virtualbox on Fedora 11 RDP'ed into a win2k3 server. It works on the XP VM and it doesn't work on the RDP'ed one. What's weirder, is that I'm not even emulating the USB drivers for my Mag Card Reader. Linux is sending keystrokes straight in to windows, and MSTSC on windows XP is sending crap to the Win2k3 server. I'm 99% certain this isn't a problem with the card reader, it has nothing to do with my programming either. (I get the same junk coming into notepad that I get coming into our software [that's why I didn't ask on SO]). And, it works with rdesktop programs other than MSTSC.exe! Needless to say, I'm in need of some RDP Guruship.

  Read the article

• What's problem with multi monitor usage in rdc7?

  - by e-turhan

  Hello, I want to use dual monitors with remote desktop on windows 7 ultimate. Host machine is win server 2008 r2. I open the run window type mstsc /multimon and press enter, also "use all my monitors for the remote session" is checked.By this way RDC is opening but only in one monitor.Do I need to do any changes on host too? I have tried /span attribute and it worked but I don't want it.

  Read the article

• Remote desktop from Mobile phone

  - by Faruz

  How can I remote desktop from my mobile phone? I understand that using windows mobile, its easy. But what if I want to use a good operating system like Android or Symbian? Is there a known way to do it without installing client-side software? (I want to use classic mstsc)

  Read the article

• Tools for Remote Desktop with Relay feature

  - by Stan

  Is there good tool that can do same thing as windows 'mstsc' and also has some features, like save different session info, so don't need to remember difference IP/ID/pwd. Thanks. EDIT: Since I can't directly RDP to remote hosts, instead, I have to RDP to a terminal server and RDP from their to my destination. Is there client that can relay my connection from local and pass through the terminal to the real destination?

  Read the article

1 2 3  | Next Page >