osxvnc-server running, cannot kill?

Question

Level 1

4 points

osxvnc-server running, cannot kill?

Ok, I'm up with VNC products and port forwarding. I noted that when I look at my server the client shows two vnc options. one option is turned off in my Share Prefernces while the other is ALWAYS persistant!?!?

I looked at the processes and see osxvnc-server running and when I kill the process it fires back up, is this expected?

If I have all shares turned off in the shared preferences settings why can someone still connect to my mac (LAN) if they know the password?

Mac Mini & MacBook, Mac OS X (10.5.6)

Posted on Apr 30, 2009 11:07 PM

Reply

Answer 1

carboncow Author

Level 1

4 points

Apr 30, 2009 11:23 PM in response to carboncow

My error. It appears the VineServer keeps running as a daemon even if you remove the program. I had to reinstall and then go to the preferences and turn off the restart.

Reply

Answer 2

BobHarris

Level 9

56,933 points

May 1, 2009 6:23 AM in response to carboncow

Yes Vine Server (aka OSXvnc) can be setup so it starts up on system boot and restarts itself should it crash.

But rather than remove it from your system, I would suggest keeping a copy around (you do not need to run it, just have a copy handy).

I have found that there are situations where Vine Server works better than the built-in Mac OS X VNC server. Especially if you need to connect from a non-Mac system. The performance and behavior of the built-in Mac OS X VNC server is not always optimal when talking to non-Mac VNC clients.

Reply

Answer 3

carboncow Author

Level 1

4 points

May 1, 2009 6:53 AM in response to BobHarris

Great info. When I first setup my Mac Mini as my home server a few weeks ago I tried many VNC server clients and forgot I had two running (on different ports). It's good to read that the Vine is better with Windows based systems, as that is what I often connect from at work.

I was doing some how cleaning but with your recommendation I'll leave both running on different ports for flexibility.

Although remote access is great from Mac to Mac it's miserable from PC to Mac over WAN...

Thanks.

Reply

Answer 4

BobHarris

Level 9

56,933 points

May 1, 2009 7:53 AM in response to carboncow

The Vine Server support TightVNC compression protocols, so using a Windows client that also support TightVNC protocols would be a good choice.

Also the Vine Server allows the client to specify reduced color (like 8bit or 16bit), which can also improve internet access. Of course the screen looks very cartoon'ish, but the speed is better 🙂

Then again, you may find a client that works very well with the Mac OS X built-in VNC server, so experimentation is suggested.

Reply

Answer 5

carboncow Author

Level 1

4 points

May 1, 2009 8:05 AM in response to BobHarris

Again, very helpful and good logic.

I use exclusivly at work uVNC simply becuase of the screen acceleration with their "mirror drivers" and the fact they have a file transfer protocol built in for quick admin needs. Works insanly well for PC to PC but I've been struggling with home MAC over lan. I will look st the server side setting for reduced data size to speed things up.

Shawn

Reply

Answer 6

BobHarris

Level 9

56,933 points

May 1, 2009 7:49 PM in response to carboncow

I will look st the server side setting for reduced data size to speed things up.

Actually Vine Server allows the client to choose. So if you can tell you client to use 8bit color, Vine Server will honor the request. Mac OS X VNC often times misbehaves if the client asks for less than 24 bit color.

Reply