VNC setup in Leopard

I have an iMac at home running leopard and connected to my Airport extreme base station (new model) through an ethernet cable. I would like to remotely connect to this iMac with my MacBook from school over the internet. I know i must configure a VNC connection but I am a bit confused as to how to do it. From what I gather, these are the steps to take:
1. Enable screensharing on iMac through systemprefrences\sharing and allow VNC viewers to control with password.
2. Configure Airport Extreme Base Station port mapping to allow "apple remote desktop" connections.
3. Use Chicken of the VNC to remotely connect by typing the ip address of my home internet connection followed by the port number....example: 89.94.4.292:5900, enter password and click connect.
When I do this, Chicken of the VNC does not connect and it gives me error. what am I doing wrong? Do I have to enable "Remote management" under systemprefrenses\sharing also or is it a firewall problem? I would appreciate step by step instructions or a link to a website with instructions for doing this with Leopard. (I've found some but they're outdated). Thank you.

Enable "remote management" then under settings, enable "VNC Viewers can...."
Screen sharing is for local network, unless you have .Mac and can use Back to My Mac, in which case you would not need VNC.

Similar Messages

Will Leopard to Snow Leopard upgrade mess up my SSH / VNC setup?

I have an SSH server and Vine server set up on Leopard with public key file in .ssh directory and appropriate settings in the /etc/sshd_config file.Will upgrading to Snow Leopard overwrite this requiring me to set it all up again? And how about the SSH Key Fingerprint - will this be changed by the Snow Leopard upgrade?

>will this do anything to Office 2011, in terms of my ability to access it?
It shouldn't but it can't hurt to be careful:
https://discussions.apple.com/docs/DOC-2455
>I have all of my important materials saved onto Dropbox
The big question is, where is the physical location of DropBox. If it is on the same machine it is not a backup. A backup is a separately stored location.
Time Machine shouldn't search for a wireless device unless you set it up with a Time Capsule, or connected the drive to an Airport base station which was using drive sharing at the time that Time Capsule was connected. Time Capsules, are special wireless (WiFi, Airport) routers that include hard drives. See my link on my user tip above (2455) which includes information about backing up. Time Machine backups to external hard drives are back ups that are most usable if they are backups from older Macs or the same aged Macs as the ones they are being restored to. The only problem is if the old Mac was pre-2006 in age. Then you may need to cherry pick data out of the Time Machine backup to an Intel Mac. Also older applications may not transfer if the were initally designed to work on pre-2006 Macs.

TIP: Use VNC for Headless Leopard Server Installs

Wish I had figured this one out before...
Quick little tidbit for all those installing Leopard Server on a machine that doesn't have a display. You can use server admin tools and 'Server Assistant' running on a different box. Or, once the installer has started on the Leo Server box, you can VNC into it directly! Then its just like installing it with a display connected.
This was useful for me to be able to run disk utility on an old XServe that didn't have a display card.
Once you've figured out what IP the box has (take a look in the Server Assistant for this info) VNC into this using your favourite client (or Leopard Client's Screen Sharing app):
The username is blank (i.e. no username), and the password is the first eight characters of the machine's serial number.
Very useful little addition there by Apple.

Craig Bowman wrote:
So does anyone here run their Mac Mini headless for both iTunes serving (to include iTunes TV and movies) and i-device syncing?
i do
Is it practical?
pretty much.
Would I use Snow Leopard Screen Sharing to control it?
i use a combination of screen sharing and iTeleport on my iPad.
what i found to be necessary is to enable +automatic login+ for the user account on which iTunes is running via system preferences > security for when you do software updates and the mini needs rebooting.
JGG

VNC setup

I have a mac mini at my office that's connected to a brand new Airport N. I want to be able to access this computer from home with my Powerbook. I've installed Vine server on the Mac mini, set the TCP/IP prefrences to manually with IP 10.0.1.232, router and dns server to 10.0.1.1, I've created a mapping for VNC (the desktop remote access tab) enabling the 5900 port for 10.0.1.232. I can access the mac mini via the internal airport connection but cannot do the same from the exterior. What am I doing wrong here?
Thanks for the help.
Mark

Just realized is SSH necessary ? if so how do I set
that up ?
SSH is not necessary, however SSH is the most secure way to login to a server over the internet or on a LAN.
I only allow my VNC server to be accessed over SSH. I don't have to open up any unecessary ports on my firewall this way. You only need to have port 22 opened in your firewall for SSH.
I first learned how to setup SSH using public keys using a howto that my friend wrote.
Howto setup SSH
Once you have ssh setup using public key authentication it is really secure and to make OSXvnc work with only with SSH you need goto the sharing tab in the OSXvnc GUI and check the box 'Only Allow local connetions (require SSH)'
Once that is done here is how it works.
For this example I am using the OSXvnc server on port 5900.
First of all we start a secure SSH tunnel, in your terminal issue the command
ssh user@server -L 5901:127.0.0.1:5900
Then in your vnc client you login using a server address of
localhost:5901
or if using chicken of the vnc like this.
Also enter your VNC servers password if you had set one of those up with OSXvnc.
iBookG4 1.33ghz. 20inch iMacG5, 1.2ghz Mac Mini, ipod video, iSight Mac OS X (10.4.3) Linksys WRT54gs+1.05 Talisman Firmware, Telewest 10mb/384k

Help with Proper DNS Setup for Leopard Standard Server Setup

Hello All,
Problem Description-
I was reviewing some training today on DNS setup and checking for proper setup with the sudo changeip - checkhostname tool and I seem to have an incorrectly configured DNS setup. So I need some help on correcting it. When I go to the "Server Preferences" tool I cannot log in using apple.ourdomainname.com instead in order to use the tool I have to input localhost as the server name. Now I just thought that the system was broken or something and with the help of my training I now see it's a DNS problem. I thought I had everything proper since I followed the steps of creating proper DNS/RDNS entries with my ISP. Now I am stuck wondering what else isn't working properly due to the DNS issue. Thanks in advance.
Technical Info-
My ISP provides us with 5 static IP's and we have asked them to create entries and verified the setup of apple.ourdomainname.com = x.x.x.x which is one of our public IP's assigned currently assigned to the WAN port of our Apple Airport Extreme. We have also had them create a PTR record which also is present, verified and functional. Our MacMini running 10.5.5 is connected directly to one of the ethernet ports on our Apple Airport Extreme which is our NAT/Firewall for the LAN. So during the setup of the Standard Server install the OS configured the Airport with the required ports for chat/web/vpn. And mobile Mac's can VPN in and gain folder access and web works fine too. We don't use the e-mail portion so I can't say how that works. The server is using the DNS of 10.0.200.1 which is the IP of the Airport and the airport is programmed with the DNS of OpenDNS servers 208.67.222.222 and 208.67.220.220. The reason for this whole long shpeal is that I want to give as much technical background as possible for the best possible help.
Thanks
DM

What happens when you use 'Localhost' instead of 'localhost' (i.e. capitalizing the 'L')?

Do i need to setup a VNC to use microsoft rdc for mac?

I am trying to gain access to my work pc (xp pro) with my intel based mpb at home running snow leopard. I've been told that everything is setup to allow an RDC on my work computer and I have microsoft RDC on my mac. However, I am still running into problems. I'm wondering if I need a VNC setup prior to using the RDC. I would appretiate any help. Thanks.

VNC & RDC (a.k.a.: RDP) are separate and for the most part have nothing to do with each other.
Did you mean VPN (virtual private network) instead of VNC? (Virtual network computing protocol.)
More than likely, you need to configure the firewall at work to allow incoming RDC sessions. (i.e.: configure port forwarding) or use a VPN. The VPN connects your remote computer "directly" onto the office's network, bypassing the firewall. Creating a VPN is not trivial. But configuring the firewall or VPN will probably require you to contact your network administrator to get the proper settings anyway.

Windows VNC clients cannot connect to Snow Leopard Server native VNC server

I am resurfacing the following related comment made in another post that discusses the same issue I am having with VNC on Snow Leopard. This is still an issue and I cannot connect to our Xserve's Snow Leopard Server with a VNC client on Windows.
I don't want to install another third party VNC server onto our SL Server, and am looking for a VNC client for windows that will connect to our SL Server.
Does anyone have any solutions?
== QUOTED TEXT BELOW ==
Re: Newbie: Connect Windows -> OSX Server
Posted: Nov 4, 2009 9:26 AM in response to: Antonio Rocco
I would politely disagree. Yes, definitely, the Mac 'Screen Sharing' app works a treat, and Apple Remote Desktop.app works as well, but I am coming from a Window's PeeCee.
For me, connecting to my 10.5(.8) Server via tightvnc gives 'Server did not offer supported security type!". Using RealVNC to this machine states "No matching security types Do you wish to reconnect to ... ?" a telnet to this AppleVNCServer service (port 5900), shows RFB 003.889 *, or Remote Frame Buffer Major 3, minor 889.
Also, connecting to multiple 10.6(.1) Clients with Tightvnc correctly asks for a password but then hangs at "Status: Security type requested". Using RealVNC opens, connects, asks for authentication, and exits. Telneting to this AppleVNCServer service (port 5900), also shows RFB 003.889 *.
The Current Version of the protocol is supposed to be 3.8, that is Major version 3, minor version 8. Not 80 or 800 but Eight). http://www.realvnc.com/docs/rfbproto.pdf and I believe that tightvnc only supports up to version 3.7.
On each station I have installed the 'old' OSXVnc.app as a service (to a unique port). OSXVnc utilizes protocol 3.3 and I can control them successfully, but that is of my own doing because of this issue.
Now JollysFastVNC works a treat to any machine I have EVER tried to connect to. I have not tried COTVNC or any of the others (too slow for me, when they wer e around)
Also, I just noticed that RealVNC states that their free and personal version will not connect to Mac OSX (x86 and PPC) but the Enterprise one will. I just Dl'ed the Enterprise Viewer and it gave essentially the same thing ('protocol is not valid' message, even after it asks for a password). Anyway, I am not here to hijack this thread, just trying to keep the info flowing and open.
Maybe I am the only one with these problems but the bottom line is I cannot use Real or Tight, or UltraVNC to administer my server or clients as long as AppleVNCServer gives out the 003.889 protocol version.
Peter
* The ProtocolVersion message consists of 12 bytes interpreted as a string of ASCII characters in the format "RFB xxx.yyy\n" where xxx and yyy are the major and
minor version numbers, padded with zeros.

Searching on the net brought me to the same solution that Mr. Hoffman found as well, I was a bit skeptical at first but since he recommended it, and all my other attempts failed, it was a last resort and I have some additional notes of my own for a successful solution. Read the two links below first before doing anything, as they contribute to the solution in tandem.
http://forums.macrumors.com/showpost.php?p=7221295&postcount=20
http://forums.macrumors.com/showpost.php?p=9081641&postcount=28
I should probably just create an entirely new post with all of the steps that worked for me, but it's rather straightforward nonetheless.

10.5.7 Leopard Server - Standard Setup

Im looking to see if the standard setup of leopard server can be configured to use PPTP rather than IPSec.
Also, is it possible to share the ethernet connection of my MacMini (running leopard server) to wifi?
I want to use it as a router for my home.

The built-in VPN server supports both PPTP and L2TP over IPSec.
For sure the Advanced setup can support either, or both simultaneously. I've never run a standard setup, but I don't see why it would be any different.
As for network sharing, you can share any interface with any other interface. It doesn't matter what media the interface uses (e.g. wired or wireless).
I would suggest that you carefully consider your server use before deciding to use it as the gateway to your network. For most people a standard $50 router does just as well, and, in fact, provides better security.

Snow Leopard Server DNS setup

Where is there a step by step setup for making my Snow Leopard Server with DNS? Essentially, I am looking to setup a mail server but seem to be missing what information I need to gather from the folks that host my domain and how to point traffic to my network.

When I started setting up my first Mac OS X Servers a few years ago I had to completely retrain my brain because the MacOS does not follow the traditional nomenclature of Windows Active Directory and DNS setup. That being said like AD for Windows MacOS relies very very heavily on a healthy and properly running DNS system, both internally and externally. So one great resource I found was about 10+ hours of training on Leopard Server over to Lynda.com. I think you can sign up for a month long membership but it's well worth the investment if your looking for some basics thru advanced setup of Leopard Server. Now SLS is much much easier at the setup and deployment and some of the fundamentals of the setup interface have changed greatly (as an improvement) but the videos are still very applicable.
Basically it comes down to the following steps in order to get your website/e-mail/wiki services working.
1. Purchase your .whatever with a registrar, godaddy, doster, network solutions ect...
2. Make sure you have a fully routable PUBLIC IP address from your ISP that you can assign to the WAN (internet side of your router)
3. Contact your ISP and ask then to create an rDNS entry for your .something to the IP address they assigned you. Usually this will look like xxx.xxx.xxx ---> mail.mydomain.com when you test later on.
4. Modify the DNS records with your registrar to point the MX & A record to your new IP. You will log in create an A record for mail.mydomain.com ---> xxx.xxx.xxx (your public IP on router) and then you will create an MX record for e-mail which will simply be mail.mydomain.com with a value of 10 (there is usually a screen for this).
5. Once all the DNS is setup and working properly (Can take several days for these changes to take affect and be visible by your ISP) then you can begin the configuration of your router. You will need to determine what IP internally you want your Mac to be. Usually 10.0.0.1 or 192.168.1.1 or other and document that. Program your router to port forward ports 25,110, 80, 143 to the IP that you decided your Mac will be at so those services will be publicly available to you to user. Otherwise nobody will ever be able to send you e-mail or visit your site.
6. This is a good time to check your work and settings by visiting www.mxtoolbox.com and you verify your rDNS (setup by ISP) and your DNS (Setup by you) before beginning your setup of OS X SLS. If everything checks out then start the install if not STOP HERE and fix it because it will haunt you in the long run.
7. Start the install of SLS and at some point the system will get you to the screens at which you input your domain information. If all was setup properly up to now SLS will auto-populate the domain and local hostname of your Mac Server. U can change the local hostname if you wish but the domain name information should reflect your rDNS and A record information of mail.mydomain.com and you can hit next and proceed with the rest of the install.
8. Once up and running you will need to make a small adjustment to the alias of your e-mail. For some reason the engineers at Apple left a flaw in (my opinion) that is as such. Whenever you send e-mail it will go as [email protected] instead of what you really want which is [email protected]. So follow this post below and you will be all fixed up in a jiffy.
http://discussions.apple.com/message.jspa?messageID=10110723#10110723
Hope this helps.

Install Mac OS using Screen Sharing or VNC - is it possible?

I've always wondered how to do this: Is it possible to remote install a Mac OS (in this case Leopard and up) using screen sharing or a vnc connection, when once the remote machine restarts and boots from the installation volume, you know longer have those sharing capabilities?
Essentially I want to know how do you control a remote mac installation without having the ability to activate screen or vnc sharing options?
In our office setting, what I'd like to be able to do is make an image of our installation disc and save it on our server, an remotely install it on other computers in the office.

how would a remote machine be controlled without screen sharing or vnc control if it's booting from a disc or networked volume?
The normal way to mass deploy an upgrade across many macs on a local network is to setup snow leopard server then you create an install image using a copy of a snow leopard disk. You can fully customise the install image with all your 3rd party applications etc. Then you just netboot each mac and the installation is automated.
see Create a Leopard to Snow Leopard Upgrade NetInstall Image
You would setup the server first. then you would have to setup dns correctly, then your users and groups. your sharpoints. Then when you build your image you customise it to suit your new network settings.

Setting up Snow Leopard Server with Address Book, iCal for Small Business

Hello Folks,
I have a small business with 2-3 people and I want to setup Snow Leopard Server on a Mac Mini. I have everything in place, RAID, Backup drive etc.
What I need is a guide on how to setup the server correctly and how to setup Address Book Server, iCal Server, DNS, etc. I was in IT a long while back but have gone back to my creative roots and sworn off IT but I am in a situation where my IT guy's wife is pregnant so he is busy painting the baby's room, etc.
I was looking at Snow Leopard Server for Dummies and a few other books. Do you guys have any suggestions on resources for me to read or research that would give me very straightforward steps in getting this setup. I am at a point where I can re-install from scratch if needed.
For the ease of those that might respond let's assume I know my way around Mac and general networking as a whole.
Thanks in advance for any advice.
Cheers,
Jason

Hi Guys,
First of, I will give you a brief background on me regarding networking as a mac user since 1994. I can setup and network multiple macs without a server in our home and small office. Turning file, print and internet sharing with a regular Mac OS X client version at no problem at all. This would be my first time setting up a Mac OS X Snow Leopard Server.
I'm in the same boat as Jakekub but we do not have a static IP from our DSL provider. We just bought a Mac Mini Server for our small office with 3 iMacs and 1 MacBook. We will just use the server for internal usage and to centralized things out and use some of server's features like Address Book, Mail, iCal etc. I've search the forums and found Orhidy's post here:
http://discussions.apple.com/thread.jspa?threadID=2148553
I even followed the sample IP Address, Subnet Mask, Router, DNS Server and I think I had it correctly setup initially. And I think I got it all running on the basic setup base on his instructions. So I tried to test my DNS settings via Terminal > hostname then got answer as
servername.companyname.private
And double checking DNS again with a command: sudo changeip - checkhostname and was given an answer of:
Primary address = 192.168.1.192
Current Hostname = servername.companyname.private
DNS Hostname = servername.companyname.private
The names match. There is nothing to change
dirserv:success = "success"
But here's another one that bugs me. I tried to follow from "Mac OS X Snow Leopard for Dummies" the command line:
NSLOOKUP hostname
and got an answer of:
;; Got SERVFAIL reply from 192.168.1.192, trying next server
Server: 192.168.1.1
Address: 192.168.1.1#53
** server can't find hostname: NXDOMAIN
So does it mean that I still haven't configured my server properly?
Thank you all for the help in advance!
dive

A stable, fast reliable VNC connection to Lion or Lion server

I hope this post help people with VNC setup from non Mac machines to a Mac running Lion or Lion Server 10.7.4.
Apple has changed quite a few things in Lion regrading VNC and screen sharing. As a consequence many VNC viewers are no longer compatible until the VNC software is upgraded to be Lion compatible. You will find many posts about this topic in this forum, eg
https://discussions.apple.com/thread/3289794?start=0&tstart=0
Often, the result is that the user can't proceed beyond the gray login screen (screen locks up etc).
This post describes how configure Real VNCs VNC server on Lion Server 10.7.4 to work in conjunction! with ARD, thus allowing you to keep screen sharing enabled and still use ARD from client if that is desired)
Download the VNC server at (Version 5! necessary)
http://www.realvnc.com/download/vnc/latest/
and install the VNC server on the host (the computer you want to login to via VNC)
Single User Host setup
==================
- Install the VNC server and follow the intsruction
(If you your Mac is configured for remote management, screen sharing, remote apple events the installation may complete with error stating to contact the manufacturer....ignore the error as it most likely caused by a port conflict because VNC server and ARD (or apple scrren sgaring both use port 5900 per default), the software was still completely and correctly installed.
- start VNC Server by opening Finder -> Applications -> Real VNC -> VNC Server (User Mode)
You will see a small VNC icon in the top tsak bar of the screen.
(if you open the "information Center" the issues tab will show a port 5900 conflict)
- open VNCserver Options and select the connections tab:
+Change the default port from 5900 to 5901 and serve Java viewer on Port from 5800 to 5801
+ Change Authetication to "Mac password"
+ Select Encryption "always on"
- Selct the expert tab
+scroll down to the bottom of the list and change "StopUserModeOnSwitchOut" to "no"
(this settings prevents the VNC server to be stopped automatically if you have Fast Switching User Mode enabled on the host.)
- select "Apply"
(now if you open the Information Center" again, the port conflict problem should be solved.
- select "open" from the VNC server menu:
If the configuration was succesful, thw window will show a check mark in a green box stating everything is ok.
- In addition you will find the address that the client user will need to connect to the VNC server on the host
it will say something like "VNC viewer user can connect using the address 192.168.x.y:1"
Note: If you start several VNC servers, each session will need a dedicated port (like 5902, 5903 etc)
Router/Firewall Settings:
===================
Depending on the router/firewall you use your ports may have been automatically configured for you (airPort extreme for example).
You need to open port 5901 and 5801 and forward these ports to the IP address of the host. If ARD was alredy working in your setup, you can copy the port coniguration for ports 5900, 3283 and 3306 that are used by ARD and implement the same rules for the new port used by VNC 5901.
Review the settings of your firewall/router.
VNC client
========
- download the VNC client for your OS from
http://www.realvnc.com/download/viewer/
and follow the install instructions.
- Start the VNC client on your client PC (Windows for example) and enter the address that the VNC server reported to you earlier (192.168.x.y:1)
- Encryption : "Let VNC Server choose"
- select "connect"
- enter your Mac username and password that was setup on your host
you are now connected via VNC to your host.
You can also configure the VNC server to allow other users to login to the same! VNC session using their user credentials (friends/family or serverAdmins that want to share access to the host)
To do this open the options dialog box on the VNC server host computer and select "configure" next to authentication.
- add the users that are supposed to get access to your VNC session using their own credentials. (make sure this is what you really want, otherwise read on in the multi user section of this post)
Multi User Host Setup
=================
If multiple users are supposed to access the host computer using their own credentials logging into their own! desktop, follow these instructions:
- first enable Fast User Switching on your host computer by going to
System preferences -> User/Groups -> Login Options and select the check box "show fast user switching menu as..."
- For each user on the host that should be reached via a VNC session start VNC server (user) as described before and assign a new port number to the new user like 5902 etc.
- repeat the configuration outlined above for each user (eg. "StopUserModeOnSwitchOut" to "no")
(note initilally when you start the VNC server for the first time again, you will get notified that a port conflict exists again....this disappears as soon as the new port is configured)
now another user can login via VNC into his own desktop using the server address : "191.168..x.y.:2"
Final notes:
=========
I spent hours trying to get a variety of VNC viewers to work with the new screen sharing/VNC implementation in Lion and finally gave up. I called Apple Enterprise support and they confirmed that "a majority of the existing VNC products are not compatible with the new VNC implementation in Lion yet and that Apple recommends ARD". The discussion on what other non Mac users (Windows, Linux) should do did not go anywhere....
I have tested the above configuration with the free version VNC server 5 on the host and the free version VNC viewer 5 on a client. It worked flawlessly, fast, reproducable and very stable. You need to be aware that depending on the features you want (number of desktops, users etc) that you may have to purchase the personal or enterprise edition for the server.
The featurs are described here:
http://www.realvnc.com/products/vnc/
I personally installed the enterprise edition after I verified that the free editions worked stable and reliably as I needed them to work.
I hope you now have a stable VNC link into your Lion host from the platform of your choice !

I'm using the free VNC edition from RealVNC on Mt. Lion (10.8.5) and the basic information is in this article for Lion is confirmed for the VNC Server 5.0.6 (r113416) on Mt. Lion.
The main Options... window shows the Connections tab and I just changed my port to something other than 5900 and the port conflict went away.
The Free edition does not allow Mac password and encryption can't be enabled. (Ya gotta pay for that.)
Connected to it from my iPod Touch using Mocha VNC with no problems.

ML setup from pen drive question

Hi, I'd like to upgrade a Mac running 10.5 (Leopard) to ML. I've made a setup pendrive. Is it going to work the same way it did with Snow Leopard or do I have to setup Snow Leopard first and then install ML? Any other option?
Thank you

Thank you. It's just a matter of time. The Mac has been restored to factory settings and the default OS was 10.5.
I have the original SL DVD but it's going to take time to upgrade to ML. So when I purchased ML I also made a pendrive setup disk ... "just in case". It usually takes a lot of time to download the latest version and unfortunately 10.5 hasn't got the App store.
So, a clean install should work but an upgrade maybe not... is that correct?
Thank you

Snow Leopard Server combined with Snow Leopard OS

I have a MacPro (4x1 TB Drives, 16GB, RAID Card, 2 x Quad-Core Intel Xeon 2.8 GHz) that has MacOS 10.5 installed (including MS Windows running under VMWare Fusion).
The RAID setup is shown at https://www.radii.org/doc
The computer is used as an everyday workhorse (running OS 10.5.7 on Volume RS1, with Volume R1V2 partitioned into 2 data and file/document stores).
Given the specs of the machine, I plan to setup Snow Leopard Server (Raid 0) also — on a separate partition so that when the system on RS1 freezes, the server does not have to be crashed also.
Is there any advantage in partitioning the volume OSXSERVER to install Snow Leopard Server to perform a number of tasks:
1. provide first level backup and coordinate backup of data to an external/offsite filestore in the clouds for two Microsoft Small Business servers, plus about 5 Mac and Windows desktop machines
2. Provide a mail server
3. iCal server
4. address book server.
The above assumes that I can run both OSs simultaneously — is that possible, or does the system for everyday usage need to be virtualised within the Server OS?? If not, which OS will manage access to the processors?

I guess my biggest concern is the frequency with which Mac OSX gets itself tied in knots and a reboot is the only way out of the mess.
I haven't seen that myself, personally. About the only time any of my machines get rebooted is after software update.
Of course, server systems tend to be more focussed than client systems, so that might help too - the server is typically setup, configured and left to do its thing. It's not like you're constantly launching and quitting different applications throughout the day.
However, I know from years of experience with desktop systems in a variety of flavours that they will need to be rebooted at least once a week.
Ahh, there's the Windows-thinking coming through.
I have Mac OS X Server systems that, quite literally, have not been rebooted in years. Most of them have months of uptime. Of course, this means that not all my systems are running the latest OS updates but that's a call I've made.
in general, the smaller the capacity (memory, speed, HD) the more often they need to be rebooted.
Sure, but that's a matter of right-sizing your server for the load you're putting on it.
Again, there's a difference between client and server installations - client systems tend to jump between active processes with minimal background processing, whereas server systems tend to run more focussed tasks.
I have found that software such as MS Office has been highly unreliable in the last couple of years — I still get Excel saying that it 'had to close' sometime in about 10% of the times I am using it.
Right, but you're not running Office on your server, right?
I was hoping there would be a better solution than having to reboot the server — or crash it when the system freezes with a kernal panic brought on by a desktop app
Sure - don't run a desktop app on your server
If you do see that need, then run another virtual machine for your desktop apps. That means you've got one 'master' OS running multiple virtual machines - one per server process, plus another one for desktop/GUI apps.
Or, run all your server processes on a single server with sufficient resource (CPU, disk, memory, etc.) for the tasks you're running, and get an iMac or a Mini for those desktop tasks. Be cheaper that way, anyway.

Leopard long file name windows support

I have a Windows 2003 file server and Leopard client 10.5.5 build 9F33. One leopard client is able to see more than 27 caracteres file name and others are not able to see more than 27 caracteres on NTFS partitions.
Any Idea how to setup all Leopard clients to see more than 27 caracteres file names on Windows 2003 with apple file share enable ?
Best regards

You post your questions all over the Internet, in many different places ...
... you get partial answers all over the Internet, in many different places.
http://www.linuxquestions.org/questions/showthread.php?t=451208
You're seeing a limitation of Windows and your CD writing software within Windows, not of Solaris.
The answer is in that other website's forum thread.

VNC setup in Leopard

Similar Messages

Maybe you are looking for