Zebedee with VNC

[Habermann, David (DA)]

Jeremy:

Now that my morning of meetings is over, I can spend a few more minutes helping you out.  Jeremy, you may receive a duplicate message because I copied you directly.  I believe the VNC list is running an attachment stripper which would have prevented my config files from reaching you.

To the best of my knowledge, there is no command to close the Zebedee server, although I'm not sure why you want to close it.  The client end can easily be configured for single-use mode so that it shuts down after one connection has been made and terminated.  I just leave the server end running.  If you feel that you must close it, you might consider using Virtually Unix which has a kill.exe program that can be used to forcibly kill a process (similarly to what Ctrl+Alt+Del does, although some programming is required to get the process id and transfer it to the kill routine - left as an exercise for the student ;<)

As to why you can't get the Zebedee client to contact it's server, here is a brief discussion of how I do this:

start vnc server listening on normal ports (5800 for web, 5900 for rfb)
    (in my case, a PC in my home)

start zebedee server on same machine as vnc server
    c:\progra~1\zebedee\zebedee.exe -f c:\progra~1\zebedee\server.zbd
    (see attached zebedee server.zbd file)
    (reason for serverport 443 is for compatibility with our firewall

start zebedee client on same machine as vnc client
    c:\progra~1\zebedee\zebedee.exe -f c:\progra~1\zebedee\tohomepc.zbd

The client file automatically runs the vncviewer.exe program which connects to the zebedee client on port 5901 (localhost:1 in VNC naming).  The zebedee client the connects to the zebedee server on port 443 through our firewall.  The zebedee server then connects to the vnc server on port 5900 and we are off to the races.  When you first start the zebedee client, NO CONNECTION TO THE ZEBEDEE SERVER WILL BE MADE.  The connection to the zebedee server is only made when a connection request is received at the zebedee client (in my case this occurs when the vncviewer.exe program executes.

By the way, be sure to execute the registry item included with the zebedee distribution causing VNC to allow loopback connections.  This seems to be required both on the client and server end (although the VNC documentation doesn't seem to read this way and I'm not positive of my facts here).

Keep the faith, zebedee will probably work for you.  I, too, was unable to make Intelicom work for the same reason as you.

Dave Habermann

[demime 0.97b removed an attachment of type application/octet-stream which had a name of server.zbd]

[demime 0.97b removed an attachment of type application/octet-stream which had a name of tohomepc.zbd]
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to majordomo "at" uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------