If you can, could you send me a diagram of the network and how you
want to use it.  I still have a little bit of trouble decoding whats
going on.  You don't have to put any real IP's in you can just make
marks, e.g. PUBLIC.IP and DHCP from Range 192.168.0.x .

If you want you can just send that to me instead of posting it to the list.

I should be able to open any kind of document you create it in (dwg,
doc, pdf, visio, etc)


--Angelo


On Tue, 05 Oct 2004 09:49:54 +0400, Cesar Dela Paz
<[EMAIL PROTECTED]> wrote:
> Angelo,
> 
> Firstly, thanks for the offer of help. I am glad to know that.
> 
> Yes, PC1--->SRV1 is working perfectly but not SVR1 (listening)---->PC2.
> I was able to chain 3 computers before using purely VNC but all three
> computers has static IPs, so it was a breeze. The screen update has its
> delay alright but its better than not at all. This is my first attempt
> chaining 3 computers with 2 not having a static IPs not to mention that
> their Dynamic Public IP is not forwarded to Private IP.
> 
> As for option number 1, I think I cannot implement that for the
> meantime. Option number is a candidate though I am not familiar with the
> nitty gritty of SSH and VPN. I have a working knowledge of VPN but I am
> completely unfamiliar with SSH.
> 
> Any help you can throw to me would be appreciated.
> 
> -Cesar
> 
> 
> 
> -----Original Message-----
> From: Angelo Sarto [mailto:[EMAIL PROTECTED]
> Sent: Monday, October 04, 2004 6:35 PM
> To: Cesar Dela Paz
> Cc: [EMAIL PROTECTED]
> Subject: Re: FW: SelectObject to CompatbleDC failed
> 
> Ahhh, I see what you are trying to acomplish.
> 
> I would try this
> 
> PC1 (vncviewer) ---->SRV1(VNC SERVER)
> 
> this works ok, correct?
> 
> then
> 
> SRV1 (vncviewer) --->PC2(VNC Server)
> 
> unfortunatley in this situation you may experience some issues due to
> update delays on both clients.
> 
> the situation you are trying to create (pc1--->pc2 direct) would only be
> possible in two scenarios (that I know of)
> 
> 1.   You have access to at least one router.   If you can configure
> either router then you can make this work.
> 
> 2.  using a tunneling protocol.
>      Set up a SSH server on SRV1  that allows access to the inside LAN
> (i.e. PC2)
>      Install an SSH clicent on PC1
>      on pc1 initiate an SSH connection with the server
>      on pc1 open a connection to pc2.
> 
> what you may be trying to accomplish is actually #2.  But what you are
> looking for is SSH or VPN or someother form of transparent tunneling.
> (I guess you could also try RAS on the server but I usually dont
> recommend that.)
> 
> If you are interested insetting up SSH try searching this/other vnc
> mailing lists.
> 
> If you need help post back and I will help you if I can.
> 
> --Angelo
> 
> On Mon, 04 Oct 2004 09:56:33 +0400, Cesar Dela Paz
> <[EMAIL PROTECTED]> wrote:
> > Angelo,
> >
> > Thanks for the information about port 5500. I guess that's the piece
> > that I am looking to make it work.
> >
> > As for the configuration of the router, I do not have access to it. It
> 
> > is an ISP provided router. I do not know how to do it. I am using a
> > Lucent cellPipe under PPPoA. I can see the menu and possibly tinker
> > with the router but I do not have a manual of it. My guess is it is
> > possible but I just plainly don't know how to configure it.
> >
> > So that makes No-IP not yet possible for me because until I make the
> > IP forwarding for public and private IP with my DSL DSL router, VNC
> > will still not work. Is that right?
> >
> > - Cesar
> >
> >
> >
> > -----Original Message-----
> > From: Angelo Sarto [mailto:[EMAIL PROTECTED]
> > Sent: Monday, October 04, 2004 4:44 AM
> > To: Cesar Dela Paz
> > Cc: [EMAIL PROTECTED]
> > Subject: Re: FW: SelectObject to CompatbleDC failed
> >
> > listening vnc viewer listens on port 5500.
> >
> > so you will need that forwarded to work.
> >
> > Additionally, if you have access to configure the router then  you
> > could just forward 5900 on the router to the xp machine (pc2)
> >
> > if you are worried about dynamic IP then sign up for a free account at
> 
> > no-ip.com.
> >
> > this will give you a domain name to map to your dynamic IP.  the
> > client can run a service (called DUC) that will update the dns at an
> > interval (that you set up).
> >
> > Angelo
> >
> > On Sun, 03 Oct 2004 16:33:43 +0400, Cesar Dela Paz
> > <[EMAIL PROTECTED]> wrote:
> > > 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
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to