#5 improper operation as service after reboot

[Anonymous]

Hello. I am Edward Kuester, email address:

kuester@schof.colorado.edu

I have setup Zebedee server to run as a service on my
Windows XP machine (all updates applied). I am using it
to tunnel the Ultr@VNC server, also run as a service,
and with the option "Loopback only" checked so that
only tunneled connections are permitted. I have
verified the correct operation of this setup in a
variety of ways---examined the ports through a netstat
command, tried establishing a VNC link without using a
zebedee tunnel, etc., and everything seems fine
(clients are also XP machines).

However, if I reboot the server machine, I can no
longer establish a Zebedee-tunneled VNC client
connection from outside the domain where the server is
located. The curious thing is that if I use my laptop
as a client, sitting on the desk next to my server (and
obviously on the same subnet---same router even---as
the server), the VNC can be established over the tunnel
just fine. The problem can be worked around as follows:
after a reboot, if I open a command window and perform
the following commands in sequence from the zebedee
program directory:

zebedee -S remove

zebedee -S install="c:\program files\zebedee\vncserver.zbd"

net start zebedee

where vncserver.zbd is the config file used by the
zebedee server, I can thereafter establish the desired
tunneled VNC connection from outside the zebedee
server's domain with no problems. I see by looking at
the installed services that the bootup command used for
the zebedee service is:

"C:\Program Files\Zebedee\zebedee.exe" -f "c:\program
files\zebedee\vncserver.zbd" -Srun

What I infer from this is that somehow this bootup
command using the -S run option has a slightly
different effect than that of the -S install option
followed by a manual service start. Is this expected
behavior, or a bug? I can provide you more deatils upon
request, if you tell me what to look for. Thanks.