help! How to make VNC work along with RDP?

  • Thread starter Thread starter networm
  • Start date Start date
N

networm

Hi all,

I use Windows Remote Desktop all the time.

But occasionally I have to use VNC(I chose to use UltraVNC).

My working procedure is:

99.99% time I use RDP, then when there is a stupid software that does not
work RDP(the stupid software won't start if it detects that I am launching
it using a remote desktop connection). So I have to use VNC to start/launch
it. Once it is launched, then I can switch back to RDP to use it as normal.

Once this stupid software crashes, I then have to shut down RDP again and
switch to VNC and use VNC to start/launch that software and then I will be
able to switch back to RDP.

Simply put, I cannot live without RDP. But there is a moment that I have to
switch to/from VNC.

I installed VNC server on that machine. And on another PC I start VNC
viewer. Both are on Windows XP SP2.

The VNC client/viewer gives me a blank screen.

I am sure this is due to some conflict between VNC and RDP.

I shutdown my RDP client/viewer which is originallky in connection with the
remote server, but the VNC still does not give me the screen of the remote
server.

I googled and read some document, I am guessing that perhaps when I use RDP,
as 99.99% times I do, I must avoid using certain session numbers, maybe I
should avoid session 0. And I should let "Console" and "session 0" displayed
on the same line when we query the status of the sessions.

In this way, perhaps I could let the VNC be able to use session 0 and
Console, etc.

I don't know how to let RDP give way to VNC. I try my best not to reboot the
remote server. If I have to reboot the remote server in order for RDP to
make room for VNC, then it is myserable, considering the often times that I
have to switch back and forth daily.

Please help. Please tell me how to let RDP make room for VNC and then after
I close RDP client, my VNC client will able to show the remote server screen
to me...

Thanks so much!!!
 
See below.

networm said:
Hi all,

I use Windows Remote Desktop all the time.

But occasionally I have to use VNC(I chose to use UltraVNC).

My working procedure is:

99.99% time I use RDP, then when there is a stupid software that does not
work RDP(the stupid software won't start if it detects that I am launching
it using a remote desktop connection). So I have to use VNC to start/launch
it. Once it is launched, then I can switch back to RDP to use it as
Click to expand...
normal.
*** Try to find an alternative to the "stupid" software.
Once this stupid software crashes, I then have to shut down RDP again and
switch to VNC and use VNC to start/launch that software and then I will be
able to switch back to RDP.

Simply put, I cannot live without RDP. But there is a moment that I have to
switch to/from VNC.

I installed VNC server on that machine. And on another PC I start VNC
viewer. Both are on Windows XP SP2.

The VNC client/viewer gives me a blank screen.

I am sure this is due to some conflict between VNC and RDP.
Click to expand...
*** Yes, the two products do not always co-exist happily.
I shutdown my RDP client/viewer which is originallky in connection with the
remote server, but the VNC still does not give me the screen of the remote
server.
Click to expand...
*** You have to reboot the RDP host machine to restore
*** fullo VNC functionality.
I googled and read some document, I am guessing that perhaps when I use RDP,
as 99.99% times I do, I must avoid using certain session numbers, maybe I
should avoid session 0. And I should let "Console" and "session 0" displayed
on the same line when we query the status of the sessions.

In this way, perhaps I could let the VNC be able to use session 0 and
Console, etc.

I don't know how to let RDP give way to VNC. I try my best not to reboot the
remote server. If I have to reboot the remote server in order for RDP to
make room for VNC, then it is myserable, considering the often times that I
have to switch back and forth daily.

Please help. Please tell me how to let RDP make room for VNC and then after
I close RDP client, my VNC client will able to show the remote server screen
to me...

Thanks so much!!!
Click to expand...

Instead of using WinVNC to launch your problem program, use
the following batch file:

@echo off
ping localhost -n 30 > nul
start /b "My Application" "c:\Program Files\Your Application\launch.exe"

Now follow this sequence after your problem application has
crashed:
1. Launch the above batch file.
2. Close your RDP session.
3. Wait 40 seconds.
4. Start an RDP session. Your problem application will now be active.

And by the way, please go easy with your cross-posts.
 
Pegasus (MVP) said:
See below.


normal.
*** Try to find an alternative to the "stupid" software.

*** Yes, the two products do not always co-exist happily.

*** You have to reboot the RDP host machine to restore
*** fullo VNC functionality.


Instead of using WinVNC to launch your problem program, use
the following batch file:

@echo off
ping localhost -n 30 > nul
start /b "My Application" "c:\Program Files\Your Application\launch.exe"

Now follow this sequence after your problem application has
crashed:
1. Launch the above batch file.
2. Close your RDP session.
3. Wait 40 seconds.
4. Start an RDP session. Your problem application will now be active.
Click to expand...

Thanks a lot!
This is a smart direction.
However it did not work.
I tried using your batch file, once with 30, another with 60.
I lunched the batch file, and then I immediately close the RDP session. And
I waited once for 1 minute and another for 1 hour.
Then I reconnect the RDP session, the application were not stupid at all.
It still said: using it through Terminal Service is not allowed, etc.
I just don't understand: HOW COME even when RDP is closed, it still detected
RDP???
I think closing RDP is not enough, there must be some clue that was still
open
 
networm said:
Thanks a lot!
This is a smart direction.
However it did not work.
I tried using your batch file, once with 30, another with 60.
I lunched the batch file, and then I immediately close the RDP session. And
I waited once for 1 minute and another for 1 hour.
Then I reconnect the RDP session, the application were not stupid at all.
It still said: using it through Terminal Service is not allowed, etc.
I just don't understand: HOW COME even when RDP is closed, it still detected
RDP???
I think closing RDP is not enough, there must be some clue that was still
open
Click to expand...

Since I know nothing about your misbehaving application, I cannot
assist you any further. As a wild guess you could try the modified
batch file below. Try it first while physically sitting in front of the
console, then under Remote Desktop.

@echo off
ping localhost -n 30 > nul
"c:\Program Files\Your Application\launch.exe"
 
Pegasus (MVP) said:
Since I know nothing about your misbehaving application, I cannot
assist you any further. As a wild guess you could try the modified
batch file below. Try it first while physically sitting in front of the
console, then under Remote Desktop.

@echo off
ping localhost -n 30 > nul
"c:\Program Files\Your Application\launch.exe"
Click to expand...

The question is:

After I close the RDP session, there is still something leave on the server,
which makes the Matlab application detects the existence of a RDP, which is
the same for VNC, VNC thinks the session 0 has been occupied and it only
gives me the blank screen.

The common thing for these two(Matlab and VNC) is:

Even after RDP is closed, there is still something left on the server(cache,
flag, stack, register, line, connection, etc.) that has not been cleared.

I am asking this because I really get it cleared and make room for either
Matlab and VNC.

It does not make sense at all: the PC has to be rebooted or logon again to
reset that particular flag; after using RDP once, it will always be there
even when the RDP session is closed. What is that? What is that?
 
Back
Top