In message <20131209092341.ga30...@cthulhu.home.robinhill.me.uk>,
Robin Hill <tiger...@robinhill.me.uk> wrote:
>> I haven't installed Tiger on a Windows box, so I don't know if the installer
>> asks you to set up the Windows Service or not.
>>
>It normally does, yes.
I didn't see it do that, but perhaps I misssed it.
>Under the TigerVNC Start Menu group, there should be "VNC Server
>(Service-Mode)" and "VNC Server (User-Mode)" sections. Service-Mode will
>allow you to run the server as a windows service, starting automatically
>at boot time, and User-Mode allows you to run it under the user account
>(you can use the Startup group to auto-run it at login).
Let me see if I've got this...
So running the server in "Service mode" is basically a "system wide" kind
of thing, whereas "User mode" just enables the thing for the current UserID,
yes?
>If you're the only user on the windows machine then you'll probably want
>to use service-mode.
This *is* actually a bit confusing.
I indeed *am* the only user of the Windows machine in question, but there
are two user accounts on that machines, i.e. "root" (with admin privs)
and "ronnie", which is an ordinary unprivledged account where I ordinarily
work.
Well, for the moment I've elected to try using "User-mode", just with the
"ronnie" account, and I'll change to Service-mode later on if this doesn't
work out.
>Start with the "Configure VNC Service" option to
>set up the server - the defaults should be okay I think, except you'll
>need to set the password (Security tab, Configure button).
Done.
>Then you'll
>need to run "Register VNC Service" and "Start VNC Service".
I gather than these things don't really apply to "User-mode", correct?
>> *Then* you can run the viewer from the Linux side, and connect.
Well, no apparently not. :-(
Several attempts to perform telnet connects to port 5900 later...
Took me awhile, but I finally figured out that I had to punch a hole in
Windows firewall. I'd never done this before, but Google is my friend,
so it wasn't hard. (The hardest part was just groking the althogether
different world view of the Windows/Microsoft universe, relative to what
I am accustomed to. In my universe, one opens a specific port number in
one's firewall, and then any Tom, Dick and Harry who needs it can use it.
Apparently however, in the MS universe, one simply enables some specific
_program_, e.g. VNCServer/winvnc4.exe, to speak on the network, and that's
it. I'm guessing that after you do this, that "enabled" program can then
talk on _any_ bloody port it likes. Bizzare.)
OK, so with service password set, hole poked in the Win7 firewall, and
with telnet to port 5900 apparently working from my FreeBSD box to the
Win7 box, I fired up vncviewer on the FreeBSD box with great anticipation...
... and ran immediately into yet another mysterious roadblock.
As expected, vncviewer asked me for the password, which I provided. Then,
immediately after that, I got a little pop-up box (and text error message
in the xterm window where I had started vncviewer) informing me that:
CConn: No password configured for VNC Auth
Huh?!? I *did* set a password on the server side. I know I did because
I saw me do it. And also, of course, I *did* provide that exact same
password to vncviewer upon startup. So what gives?
I have no earthly idea what the message above is trying to tell me, so any
help would be appreciated.
Regards,
rfg
------------------------------------------------------------------------------
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
Tigervnc-users mailing list
Tigervnc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-users
