Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
When I try to connect to Windows 2012 Server using Remote Desktop Connection, I'm connected for about 1 sec. and then disconnected with following error:
Because of a protocol error (code: 0x112f), the remote session will be disconnected.
Until yesterday, connection was working fine with no error, no server changes. I never saw this error before. I tried to lower visual appearance settings in Experience panel (found as possible solution to similar error), but with no result.
This error may be triggered by insufficient memory on RDP server.
After few tries with this error, RDP managed to get a connection to the server and I was able to stop a bogus service consuming too much memory. This can be done also with sysinternals or sc.
Might not be a solution for all but I found that if I reduced the screen resolution of the RDP session, I was able to get in. The server was at 95% capacity I went from 3 high res monitors to 1 800x600 window.
Server restart helped, I'm able to connect to server again.
If the server accessible with RPC (basically, if you can access a shared folder on it), you could free some memory and thus let the RDP service work properly.
The following windows native commands can be used:
To get the list of memory consuming tasks:
tasklist /S <remote_server> /V /FI "MEMUSAGE gt 10000"
To kill a task by its name:
taskkill /S <remote_server> /IM <process_image_name> /F
To show the list of desktop sessions:
qwinsta.exe /SERVER:<remote_server>
To close an old abandoned desktop session:
logoff <session_id> /SERVER:<remote_server>
After some memory is freed, the RDP should start working.
A simple thing. Disable the vsphere options 3D for the virtual maschine . It works perfect. When you want, reinstall the vm-tools for the virtual maschine.
Resized VM with more memory fixed this issue.
I got the same error recently. I think McX is right it was caused by insufficient memory on RDP server. Here is the solution that works for us.
use sc cmd to get running services on the remote server. Make sure you can use windows explorer to access the remote server \\remote_server.
sc \\<remote_server> query
find out the service you can stop.
sc \\<remote_server> stop <service_name>
After stopping one service, the remote desktop works again.
If anyone comes to this thread and has this issue when you remote to a VMware VM with windows 10 1903, disabling 3d in the graphics card worked for me.
There may be a problem with the video adapter. At least that's what I had. I picked up problems immediately after updating Windows 10 to the 2004 version. Disabling hardware graphics — solved the problem.
https://www.reddit.com/r/sysadmin/comments/gz6chp/rdp_issues_on_2004_update/
Related
I have an issue I want to debug. On Superuser the question has more details about my issue:
https://superuser.com/questions/1243000/local-taskbar-visible-during-remote-desktop-fullscreen
Killing explorer.exe works but after 30 minutes later or so it comes back. I have killed off all of my notification icons but so far I had no luck to find the bad guy who wants to send me a notification.
The answer tells me that an application has set in explorer the MustBeSeen flag which added to Windows 10 some time ago.
My question is which C/COM API is used to set this flag?
I want to intercept that call in a debugger and find the bad guy which is forcing the taskbar of my local machine to overlay the remote one.
I got a new computer at work and I need to work remotely using citrix receiver. It works on my old computer. I download a .ica, launch it, and a remote desktop opens where I can work. The old computer had windows 7.
On the new computer, I installed the last version of citrix and tried, but it doesnt work. I dont get any error, it actually seems to work, but needs like 1 minute to detect my mouseclicks, until it finally disconnects. The new computer has windows 10.
I tried to uninstall the lastest version of citrix receiver, and install the same I have on the old computer (4.6) but the same happens.
So, the problem is it works VERY slow (1 minute to detect each click) and then before I even log into the remote machine, it just disconnects.
Im using the same network and citrix receiver version than in my old computer. Any idea if it can be windows 10 related or how can I find out what it is causing it?
Maybe this info can help: Ive noticed a difference when opening the network central. On my old computer (where it works) I see: Terminal Server - Citrix receiver. And at the bottom it says: 1 server 0 remote applications
On the new computer (doesnt work) it says: MAD-BDCOT-PS-02 - Remote Desktop Connection. And at the bottom: 1 server 1 remote application
That's the only difference I see, but Ive done the same in both cases.
Thanks
Made it work.
After trying many things for 2 days, even installing almost every citrix receiver version, a coworker gave me a file called CitrixOnlinePluginWeb, Instead of CitrixReceiver.
I dont know what it is, and I cant post a link since he gave it to me, but Im sure knowing the name makes it easy to find in google. With this, it worked.
By the way, I think the problem was windows 10, since before knowing this other installable, I tried in several computers, and it always worked on win7 ones and didnt on win10 ones.
I have a windows 2016 server running RDS. It is configured to run a single application when a user accesses it from a .rdp shortcut. The user just sees the application as though it is running on their local machine, not a whole remote desktop.
If from a client PC, if I launch the application and log in then I can see a new connection in the RD Gateway manager.
However if I launch the application from the same client PC multiple times I am only asked to login the first time, and whilst I see many instances of the application I only see one connection in the RD gateway manager.
I would like a new connection each time I launch the application, so that I can simulate multiple users running the app concurrently in their own sessions.
I have tried adding "prompt for credentials on client:i:1" to the .rdp shortcut and this has no effect.
Thanks you your help.
I don't think it's possible. Let me try to explain:
Whenever you launch the RDP file, you connect to a session on the RDSH. Now, if you want separate connections, that means that there should be multiple sessions (probably for the same user since the credentials don't change) which is not allowed by the RDSH by default.
Assuming you get passed multiple sessions for same user, MSTSC actually recognizes that for the given RDP file, there is already an open connection, so it will try to reuse that.
Last but not least, there is the problem of licensing - you are "working around" the system: both per-device and per-user licensing would report 1, therefore it would probably be a violation of ToS.
It would be much more useful if you could tell us what you are trying to achieve and then maybe we can help you more.
P.S.: This question has nothing to do with programming, so it probably belongs to https://superuser.com
Hi I figured out a solution to this, so I will share in case it is useful for anyone else.
Modify the hosts file to include different names for the target machine ip address:
eg:
51.xxx.159.233 test1.xxx.uk-user1
51.xxx.159.233 test1.xxx.uk-user2
51.xxx.159.233 test1.xxx.uk-user3
51.xxx.159.233 test1.xxx.uk-user4
Then in each rdp launch shortcut, reference a different alias.
eg:
Shortcut1:
full address:s:test1.xxx.uk-user4
Shortcut2:
full address:s:test1.xxx.uk-user3
Then when the RDP is launched it will ask you to log in even if you already have an active connection and server will have a new user logged into it.
Hope this helps somone in the future.
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 8 years ago.
Improve this question
I'm trying to connect to a database using SQLDeveloper and I get the following error:
An Error was Encountered performing The requested operation:
IO Error: Conection reset
Vendor code 17002.
Could you please help me?
Listed are the steps that could rectify the error:
Press Windows+R
Type services.msc and strike Enter
Find all services starting with ora start these services and wait!!
When your server specific service is initialized (in my case it was orcl)
Now run mysql or whatever you are using and start coding.P
I encountered same problem with ORACLE 11G express on Windows.
After a long time waiting I got the same error message.
My solution is to make sure the hostname in tnsnames.ora (usually it's not "localhost") and the default hostname in sql developer(usually it's "localhost") same. You can either do this by changing it in the tnsnames.ora, or filling up the same in the sql developer.
Oh, of course you need to reboot all the oracle services (just to be safe).
Hope it helps.
I came across the similar problem again on another machine, but this time above solution doesn't work.
After some trying, I found restarting all the oracle related services can fix the problem. Originally when the installation is done, connection can be made. Somehow after several reboot of computer, there is problem.
I change all the oracle services with start time as auto. And once I could not connect, I restart them all over again (the core service should be restarted at last order), and works fine.
Some article says it might be due to the MTS problem. Microsoft's problem. Maybe!
I had the same Problem. I had start my Oracle TNS Listener, then it works normally again.
See LISTENER: TNS-12545 ... No such file or directory.
In your case the "Vendor code 17002" is the equivalent of the ORA-12541 error: It's most likely that your listener is down, or has an improper port or service name. From the docs:
ORA-12541: TNS no listener
Cause: Listener for the source repository has not been started.
Action: Start the Listener on the machine where the source repository resides.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
We are currently investigating different remote-desktop support solutions to help our clients if they have any problems with our software and I would like some input on the best solutions out there.
We have the following needs / wishes:
Cross platform
Preferrably no installation on the user-end
Should penetrate firewalls and not be bothered by antivirus stuff.
Should leave no residu behind after support.
I know of VNC, logmeinrescue.com, dameware remote control, msn remote desktop and many others, but which one is the best?
I would also suggest TeamViewer, there is a free version and a commercial one that you can rebrand with your logo to redistribute to your clients. It does require (non administrative) install but works also behind firewalls.
Copilot
We use UltraVnc SC (Single Click), see here:
http://www.uvnc.com/addons/singleclick.html
Your client needs only download a small file from your helpdesk and run it. Then your helpdesk can control the client's desktop. The small file will uninstall itself after closing the session. The requirement is your UltraVNC should be run in listen mode.
Definitely TeamViewer!
Especially because it's very easy for the 'other side'.
No complicated skills required. Just install and run it. Easy to explain over the phone while immediatly asking for their 'code'.
Try CoPilot.
TeamViewer has been a great help to me so far but it's only available on Windows and Mac. No Linux support unfortunately.
I personally feel that UltraVNC is the best support tool for Windows boxes, especially since the end user can see what you're doing as you're doing it. Very good for training purposes as well.
RDP is neat, but I find it very frusting to use, unless on high-bandwidth or bandwidth stable machines. Port forwarding can also be a pain if the routing hardware is not great at the end users endpoint. You also need to worry about user permissions and enabling RDP as well, which if you need to do in 3rd person, can be tricky.
UltraVNC (like the other VNC clients) has a cool "Listening Host" which allows you to still VNC into a VNC server if the server's endpoint is not a direct connection to the net. This can be very useful. I've worked in the financial services sector, and we use VNC in this capacity and have never had any issue both installing it enmasse and have never had a security breach.
SSH is also an option, and with OpenSSH you can use it on windows (using cygwin) but this isn't always suitable.
In the end, I think VNC is possibly your best bet.
I've had very good experiences with CrossLoop. It's free and allows you to setup a connection within 2 minutes.
I use logmein.com quite a bit which works very well but it does have a full client installation. However it is available at any point and once installed does not require user to allow remote connection (which may or may not be ok with your customers).
Given your requirements, I think CoPilot is probably your only option, although you will require client interaction - they need to download and run an executable, but its very straightforward.
I have had good experience with the remote control of NTRSupport. Quite easy to use with no installation required.
I also used and/or use the following software that does not cover all your requirements:
Timbuktu Pro - Bad performance, few features, can't recommend it nowadays.
UltraVNC - Works, but I remember some problems with clipboard and file transfer support.
PCAnywhere - Works, but the performance was never satisfying, Awkward clipboard handling.
RDP - Great for Windows machines but can be problematic when it is not clear whether you have to use the console session or not. Sometimes, you disconnect a server session just by accident.
For windows only: Crossloop