That was an interesting "Oops", Corni. I tried that when I saw it and just assumed that you did indeed know what you were talking about.
I did note that client response varies.The occasionally-anemic Win2K+ telnet client seemed to just pop up a "connection closed", probably due to the fact that it attempts immediate NTLM authentication. IVT opens it fine and allows the "Get". Note that this is also the ultimate in "safe surfing" methods... ----- Original Message ----- From: "Beerse, Corni" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, 2002-05-30 08:10 Subject: RE: Cannot connect to the VNC server > > -----Original Message----- > > From: Terje Trane [mailto:[EMAIL PROTECTED]] > > > If you telnet to 5800 you reach the webserver that waits for > > a request from > > My oops: should read 5900 in my reply. On the other hand, your reply is > verry interersting, it shows the vnc-web-server response. > > > you. If you would like to test it you can type "GET / > > HTTP/1.0" (or just > > "GET /")and hit enter twice. You should get something like: > > > > $ telnet server.mydomain.com 5800 > > Trying 192.xxx.xxx.xxx... > > Connected to server.mydomain.com. > > Escape character is '^]'. > > GET / > > > > HTTP/1.0 200 OK > > > > <HTML><TITLE>VNC desktop</TITLE> > > <APPLET CODE=vncviewer.class ARCHIVE=vncviewer.jar WIDTH=1024 > > HEIGHT=800> > > <param name=PORT value=5900></APPLET></HTML> > > Connection closed by foreign host. > > > > > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On > > > Behalf Of Chris Stoermer > > > Sent: Wednesday, May 29, 2002 4:29 PM > > > To: [EMAIL PROTECTED] > > > Subject: RE: Cannot connect to the VNC server > > > > > > > > > The blank screen is probably a connected screen. You can't see > > > anything beciase you haven't enabled local echo. You can still > > > enter telnet commands there and get back response from the > > > server. If you hit ! enter, it should drop connection back > > to a prompt. > > > > > > --Chris > > > > > > >>> [EMAIL PROTECTED] 05/29/02 08:36AM >>> > > > When I try 'telnet <ip address of the vncserver> 5800', I get no > > > reply back. > > > I could ping the machine, but when I try to telnet, it just goes > > > to a blank > > > screen and does nothing. There is no firewall involved. > > > > > > When I try to connect to the server through the vncviewer, > > it just times > > > out. There is no response at all. > > > > > > Would this information help to narrow down the problem?? > > > > > > Thanks, > > > > > > Dilash.K > > > > > > -----Original Message----- > > > From: "Beerse, Corni" [mailto:[EMAIL PROTECTED]] > > > Sent: Wednesday, May 29, 2002 4:21 AM > > > To: '[EMAIL PROTECTED]' > > > Subject: RE: Cannot connect to the VNC server > > > > > > > > > > > > > -----Original Message----- > > > > From: Dilash Krishnapillai [ > mailto:[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]> ] > > > > > > This is a very basic problem, but causing me real headache. I > > > have installed > > > the VNC server on a large number of Windows 2000 machines. > > > Connecting from a > > > client machine works for 95% of the servers. But I am not > > > able to connect to > > > a few machines. I am not sure, what did I do wrong with these > > > few machines. > > > Both the server and client environments are Windows 2000. I > > > have set VNC as > > > a service on the server machines and I could verify that the > > > service has > > > been started and running fine. But when I try to connect to > > > that machine > > > using the IP address, I get nothing back. I don't even get an > > > error message > > > or anything. I have uninstalled and reinstalled VNC on these troubling > > > machines, but no luck. > > > > > > > Some things to have a look: > > Does the machine respond to it's ip address? Can you ping it? Can > > you see a > > share on it from an other machine? Does it repot the proper ip address on > > the proper port? (I have a machine with 2 ethernet addresses: one for the > > server room network and one for the external connection. This causes some > > problems if you don't configure all parts properly) Try ipconfig, > > ifconfig, > > winipcfg or other tool to check the actual configuration on the machine. > > Correct this yourself. > > > > Is there some firewalling that can cause trouble? Fix this yourself. > > > > Try telnet to the vnc port: `telnet vncserver 5800`. You should get a line > > of text with 'rfb' in it. > > > > How long does it take for the vncviewer to say it has some troubles? Is it > > an immediate response or can it be on a time-out? Immediate responses > > indicate a running server which does not allow you to connect. > > > > > > > > Success CBee. > > _______________________________________________ > > VNC-List mailing list > > [EMAIL PROTECTED] > > http://www.realvnc.com/mailman/listinfo/vnc-list > _______________________________________________ > VNC-List mailing list > [EMAIL PROTECTED] > http://www.realvnc.com/mailman/listinfo/vnc-list > _______________________________________________ > VNC-List mailing list > [EMAIL PROTECTED] > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
