Just an update on the issue I posted here. Looks like I was able to
overcome the problem below by just changing the sequence of how I use
Remote Desktop and VNC. I am using a Windows 2003 Server with VNC Server
and an XP Pro with VNC Viewer. I was getting the error right after and
even while I am using RD on Win2003. SO I decided to experiment and
reboot Win2003 and then connecting my XP using VNC without running RD
yet. It worked. Then I run RD and connect from XP to Win2003. They are
now running simultaneuosly. I experimented further by closing VNC and
connecting again even while RD is still running. It was also a success.
I suspect (for verification of course) that there is something in the
initialization of RD that causes the problem with VNC. So if you want to
run RD along with VNC make sure you run VNC first, otherwise you need to
reboot your machine again to connect using VNC.
This is a first step in my objective of chaining 3 computers using a
combination of RD and VNC. I can see that this is the only combination
for me to access a third computer with a local IP behind a DSL router
with a dynamic IP. I have 2 computer with that kind of setup and only my
Win2003 Server has a public IP that is why I want to chain it. The
possible setup would be like this:
Say: PC1 = XP (Behind Dynamic IP Router with local (192...) IP)
PC2 = XP (Behind Dynamic IP Router with local (10...) IP)
SVR1 = Win2003 with Static Public IP
1. PC1 (RD client) ----------------------> SVR1 (RD Server + VNC Viewer
Listening) <---------------------------PC2 (VNC Server initiating add
clients)
2. PC1 (VNC Viewer) ------------------> SVR1 (VNC Server + VNV Viewer
Listening) <-------------------------PC2 (VNC Server initiating add
clients)
Theoretically, PC1 can gain access to PC2 using SVR1 as bridge but I
still have no luck so far. THis is the first time that I am using VNC
listening viewer on SVR1. I have tested listening viewer before with
other PC and it was working fine. Only this time I want it changed. I am
not sure if VNC Server initiated connection uses the same port of 5800
and/or 5900. Those are the only two ports I opened with the firewall for
VNC. Your input would be appreciated.
I hope this helps as well.
Regards,
Cesar
_____
From: Cesar Dela Paz
Sent: Saturday, October 02, 2004 3:50 PM
To: '[EMAIL PROTECTED]'
Subject: SelectObject to CompatbleDC failed
Hello,
Anybody experience the error "SelectObject to CompatbleDC failed."? I
can't connect to my server who has a private and public IP. The public
IP points to the private IP. I can connect thru Remote Desktop. Even web
publishing is working well over the internet.
Any help is aprpeciated.
Regards,
Cesar
[demime 1.01d removed an attachment of type image/jpeg which had a name of Outlook.jpg]
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
