I cannot invoke a product application on a sytem when connected through RDC but able to invoke application when connected through VNC. The error i am getting is “could not get proper license file in the path is given” .When check the path given in message on the connected sytem the lic file is present.
If i connect through VNC and invoke the application it is working fine.
Why is it happening so?
What about single user PC’s where the single user chooses not to have a password because they can’t be bothered with the Welcome screen every time they reboot? How can this type of user use Remote Desktop, given that RD seems to require a User Account with password?
I work with Ultra@VNC several times a day and with Remote Desktop a couple times a week. Out of the two, all things considered, I prefer Ultra@VNC. One of the things that I think makes VNC better (especially for technical support) is the ability for both the local and remote users to view the same screen and share the mouse, it makes explaining things a lot easier and makes fixing problems a lot faster. There are several options though: VNC (Real, Tight, Ultra, etc.), Remote Desktop, GoToMyPC, Terminal Services, Citrix… to name a few.
As I understand, with UltraVNC both people (i.e. server and client) can see the same desktop… like pcAnywhere. What about Windows RDC? I have read that the session is not displayed on the server monitor. Is there an option to enable the person on the server side to observe what’s happening? I am deciding what solution to use. Maybe Window’s Remote Assitance is what I’m looking for. Does anyone care to comment and compare. Thanks.
“Plus there was really no way to get to their session to see what they were seeing at any time. I believe this is “Remote Assistance” which is basically the same thing, but different. I never quite understood the differences”
Remote Assistance will allow you to “shadow” the existing session. This means that the current user is not logged out.
By default W2K TSE and 2003 Server both allow two concurrent connections in what they call administrator mode. This allows the IT department to manange the servers without having to go to the server room for everything little thing.
With both versions, you can install a license pack and have as many users connect to the server as you like (make sure you have enough memory). Then an administrator can start his (her) own session and run a TSEADmin execuatble that will list all the currently logged in users and allow you to shadow them.
The system can be configured that the user must accept the shadow request, or allow connection without them knowing. When you connect, their screen will have one quick flicker and that is it.
At work we deploy our product in a TSE environment and it works great. You can have a very low end client running the remote desktop program connecting to the server to run their app. Support can make their own connection and assist any user they want by shadowing the session.
The shadow feature is also great for remote training.
I’m a big fan of remote desktop protocol and thought it was a great plus when I learned xp pro would have it. I’ve been using it since it first rolled out with the 2000 server. I use it admin all my servers and even my customer’s servers where applicable.
The steps at http://sig9.com/articles/concurrent-remote-desktop explain how to set up Windows Xp to allow up to three concurrent logins at once. Appears to work OK ona Windows XP PC with all updates.
I have remote users that need to have support by multiple technicians. The client clicks on the application created by WinVNC to connect to the UltraVNC server listening on port 5900.
Once the viewer is executed, I have setup my windows 2003 server to listen to port 5900. The connection is then established. However, I would like to add a few more techicians to the server to allow multiple connections to the vnc server on separate terminal sessions. Is there a way that you know of in order to redirect the VNC Server to the RDP sessions to a specific Terminal Service session.
Please advise.
Thank you for your time.
Ryan Deschaine
RCS Technical Support
I’ve no comment but have a question.
Is there any VNC Server built in C #
I need to display a single main desktop to multiple remote viewers (around 10 remote parties). (The scenario is a user wanting to share images to multiple remote specialists to seek advice and support). There is no need for remote the viewers to control the machine being viewed.
Can anyone suggest how this might be done. Sounds like neither remote desktop nor vnc are good for this?
I did a VPN connection to a remote machine (much slower than LAN), then used MS Remote Desktop and Tight VNC (development version with mirage mirror driver). For my surprise Tight VNC showed better responsiveness than MS Remote desktop. but on LAN Remote Desktop is faster.
I’m pretty new to using remote desktop, however I’ve found it really useful for using my office computer using my laptop at home.
Regarding using multiple screens, I have two screens on my office PC and obviously only one on the laptop and I didn’t have any problems working at home. In fact the way it displays everything on the one screen and still remembers the location of the windows and files when I came back to the office was handled far better than I thought.
In answer to the questions about VNC and C# or VB…I found a solution. There is a company called SmartCode Solutions that has a VNC Server and Client ActiveX control. The website is:
To Answer jlo’s questions, you can not use VNC or RDP to share with 10 users but a good product is Goto Meeting which does exactly that. It does however cost a monthly subscrip fee.
Has anyone found a version of VNC in C# or VB? Would anyone be interested in teaming up to develop one?
Anyone want multiple RDP sessions on 1 (yes, thats one) XP Pro box!
(I’ve had this working gave up creating new sessions after * concurrent sessions 
)
We’ve found the easiest tool for remote computer access:
Techinline Remote Desktop
http://www.techinline.com
Our support team has been using it for a year and have no any complaints about it. It’s really amazing.
Create a shortcut with this path:
hcp://CN=Microsoft%20Corporation,L=Redmond,S=Washington,C=US/Remote%20Assistance/Escalation/Unsolicited/Unsolicitedrcui.htm
Run it and the user will be prompted to allow an administrator to connect to their session. From there you can remote control the users XP machine and still have them see what you are doing. Works using remote assistance, but allows the administrator to initiate the connection rather than waiting for the user to request assistance.
I think it may require some changes in group policy in a non SBS environment but with an SBS domain it will work by default.
There’s a way to increase the maximum number of connections to a Terminal Server, running on Windows XP Professional.
Restart your computer in Safe Mode (Press F8 several times after the BIOS screen disappears. And select Safe Mode)
Turn off/disable Remote Desktop Connection (RDC) and Terminal Services:
Now download this file:
http://members.lycos.nl/nessyh/files/termsrv.dll
At last, we’ve to change some settings