More info begets more questions...

[Alex K. Angelopoulos]

I LIKE that trick...

----- Original Message -----
From: "Jacob Hoover" <jacob.hoover "at" marathonelectric.com>
To: <vnc-list "at" realvnc.com>
Sent: Monday, 2002-06-03 08:15
Subject: RE: More info begets more questions...


> Jonathan,
>   You can use I.E. to check the telnet issue. (
> http://SERVER.IP.ADDRESS.HERE:5900 )
> I am using I.E. 6, but an older version might work.
>   You might also want to turn on the debug console output on the remote
> server, but
> this could get very cryptic.
> (HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\DebugLevel,
> HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\DebugMode)
>
> Anybody know if this can be sent to a log file?
>
>
> Jacob Hoover
>
>
>
> -----Original Message-----
> From: J. Meltzer [mailto:zugzwang "at" swordmoon.com]
> Sent: Monday, June 03, 2002 7:48 AM
> To: vnc-list "at" realvnc.com
> Cc: alex "at" bittnet.com
> Subject: More info begets more questions...
>
>
> Greetings.  Just a note, and then I will answer your questions
> below.  Since I started posting this thread, I have learned a couple
> of things.
>
> 1.  My co-worker, when given my VNC password, is able to
> connect to my work machine (W) from his home machine (S2)
> without a problem, using the same setup I have EXCEPT that he
> uses Win2000 on the client, not Win98.
>
> 2.  Win98 telnet may not accept a port argument, so all telnet
> tests may be invalid.
>
> Message: 15
> From: "Alex K. Angelopoulos" <alex "at" bittnet.com>
> To: <vnc-list "at" realvnc.com>
> Subject: Re: Telnetting to B and W
> Date: Sun, 2 Jun 2002 16:29:37 -0500
> Reply-To: vnc-list "at" realvnc.com
>
> Do you have a firewall in place at your office that might be blocking
> all telnet packets?
>
> -- No.  Once I am in on the VPN, I can telnet anywhere that I want.
>
> Normally you would see something like
> "RFB 003.003" when connecting to an open VNC port with a telnet
> client.
>
> -- This is what my coworker sees when he tries it.  See "invalid
> telnet", above.
>
> Let's back up to the beginning of things and see if we can establish
> what is going on... it will take a few exchanges to get it done, but it
> will likely be the fastest way to do it, and will help make sure you
> know exactly what is going on with your VNC access.
>
> Could you verify the following for me?  I am including some notes
> from prior email, since I want to keep this info together for reference.
>
> 1 - There is a VPN in place at your work; things work fine if you
> access the network via the VPN.
>
> -- Yes, there is a VPN.  However, this whole time, I have been
> accessing the network via VPN, so no, things do not work fine.
>
> 2 - You don't use the VPN over your connection.
>
> -- Yes, I do.
>
> 3 - For some reason, your VPN works only over dialup; it won't
> accept through-internet connections.
>
> -- Incorrect.  I connect to the VPN just fine using my DSL
> connection
>
> 4 - You can access B through the Internet, but not W.
>
> -- Again, I use the VPN.  Through the VPN, I can VNC to B just
> fine, but I only get "Initial Screen Loading" when I try to VNC to W.
>
> 5  - This is an item you will need to probably check at work
> (actually a question). Does your firewall/router redirect traffic
> coming in on port 5903 to the internal IP address that W uses?
>
> -- I do not believe so.  As I stated before I answered these, I now
> know that a co-worker on a Win2000 machine is able to access
> ALL machines on our network with no problem.
>
> I appreciate your time and effort, and I wish that I could reward it
> with a successful VNC session.
>
> Thanks,
>
> Jonathan
> _______________________________________________
> VNC-List mailing list
> VNC-List "at" realvnc.com
> http://www.realvnc.com/mailman/listinfo/vnc-list
> _______________________________________________
> VNC-List mailing list
> VNC-List "at" realvnc.com
> http://www.realvnc.com/mailman/listinfo/vnc-list