Question about changing a Snow Leopard Server network settings

We have an Xserve running Mac OS X Server 10.6.8, the primary services running on it are afp, smb, dhcp, dns, jabber and the calendar sever.
Right now we have a router connecting two networks together, 192.168.0.0/24 and 192.168.1.0/24. The Xserve has a static IP address in the 192.168.0.0/24 range.
In order to combine two phone systems into one I am required to combine the above networks, this will involve removing the router and changing the subnet mask on every device from 255.255.255.0 to 255.255.254.0, any device that is currently part of the 192.168.1.0/24 network will also need to have it's router setting changed from 192.168.1.1 to 192.168.0.1. That part should all be easy.
However, this is my first experience expanding a network past a standard class C and am wondering if there is anything I need to watch for on my Snow Leopard Sever.
Specifically I wonder about dhcp settings, right now there are two dhcp servers, the Xserve which provides dhcp for 192.168.0.0/24 and the router that provides dhcp for 192.168.1.0/24. Once the router is removed the Xserve will need to provide dhcp for the entire network.
Looking at the Xserve dhcp configuration right now I have one subnet defined providing addresses 192.168.0.5 to 192.168.0.125.
Can I simply click the + to add another subnet and add for instance a range of 192.168.1.5 to 192.168.1.125?
Will it simply give out all of the ip addresses in the first range and then start with the 2nd? Or do I need to find a single range of ip addresses large enough to meet my needs? (e.g. 192.168.1.5 to 192.168.1.225 or something).
Is there anythign else to watch for after making this type of network setting change?
Thanks in advance.

Thank you for your very detailed reply.
I understand the problems that can arise using 192.168.0.x and 192.168.1.x and if this were a new project I would definitely switch to something else, however in this case we have been using these ip ranges for years (they were in use here long before I started) and I don't want to have to redo all of my dns settings at the same time I make these other changes so I'm going to stick with the same ip's we are using at least for now. Anyone here needing vpn access has already dealt with this issue but we have very few vpn users so it has not been a major problem for us to date.
My biggest question is about increasing the size of the dhcp pool. For instance, after I change all the network settings and set up a /23 network is it possible to have a single dhcp pool that includes some ip's in the 192.168.0.x range and others in the 192.168.1.x range? I guess what I am asking is when I am in Server Admin and click on DHCP one of the tabs across the top is "Subnets". Right now there is a single "subnet" configured that provides addresses from 192.168.0.5 to 192.168.0.125.
Ideally I would like one dhcp pool that provides ip's in the range of 192.168.0.5 to 192.168.0.125 and then if all of those are used up, moves to 192.168.1.5 to 192.168.1.125. Can I do that by simply adding another "Subnet" so there are two? Or do I have to find one larger single range? (e.g. 192.168.1.5 to 192.168.1.225?) You may have already answered this indicating I have to have a single larger range but I just want to be sure.
The parts about changing subnet masks, and routers and all that I think I have a pretty good understanding of.
Your last paragraph is something I have been worried about, I do have a feeling that after making this change there will probably be unforseen issues that will need to be resolved, I'm just hoping it is not too many. For the scope of this thread I will just focus on issues that may arise with the Snow Leopard Server however.
Again, thank you for your help.

Similar Messages

Question about downgrading from Snow Leopard to Leopard

After many problems with Snow Leopard (unable to print, programs crashing, dissatisfaction with the new Preview, etc., etc.), I have decided to go back to plain old Leopard for the time being. I was perfectly happy with version 10.5.8 and had no problems whatsoever with it. I'm a freelancer and need my system to be working right. Maybe someday, I'll upgrade to Snow Leopard, but not for a while.
I plan on using Time Machine to restore my old system. The only problem is that I forgot the day I did the upgrade. I think it was either last Thursday or Friday, but I'm not sure.
Is there a way that I can see exactly when I did the upgrade so that I can be sure to restore from my latest backup?
Thanks for any advice.

You will need to boot from your Leopard installer DVD and do an Erase and Install. You cannot reliably downgrade any other way. As for restoring from TM all you really need do is post installation use Migration Assistant which will then restore your Home folder, third-party applications, support files, network preferences from your TM backup (or any other backup.) Just be sure that during the Setup Assistant you create the initial admin account using a different user (short) name than the one you normally use. Migration Assistant will restore a Home folder, but it will not overwrite nor update an existing Home folder with the same username. After you migrate the account and restart the computer, log into your old account. Verify it has admin status, change auto-login to the account, then restart to be sure all is working correctly. If so then delete the initial account created during setup.

Question about Apple's Snow Leopard Up-to-Date program

I just pre-ordered the 10.6 upgrade from Amazon for my older mini; my sister just bought a new MacBook Pro without 10.6. Can I (of course I can, but should I?) use my copy of 10.6 to upgrade her MacBook so she doesn't have to order the upgrade kit? The terms of the program says she's entitled to the upgrade.

So if I understand you guys correctly: even if I bought a new Mac recently and qualify for the Up-to-Date program, I don't automatically get a license for Snow Leopard; the $9.95 for the upgrade kit is not just for shipping and handling but also a license fee? Correct?

No Ethernet/Internet Connection on Parallels 7 Running Snow Leopard Server - Fix?

I have recently installed Parallels 7 on my 2013 iMac, and have both Snow Leopard Server and Windows 7 running great on the Parallels platform.
However, after installing some anti-virus software, "ClamXav" and "MacScan", I need to have the internet connected to my Paralells 7 so I can receive viral updates to both these programs. I am unable to get any ethernet/internet connection on my Paralells 7 running Snow Leopard Server.
I have tried to update the Paralells 7 Snow Leopard Server "network Info" (in SL systems preferences" ... as the same ethernet connection info that I have running my "network connection" on my main OS Mountain Lion, but still no ethernet connection in Paralells 7.
This is a screen grab of the locations where I believe I am able to update my "ethernet" info for Paralells 7 Snow Leopard:
Obviously, I've blurred out the current info in these two windows, for security purposes, but exactly what should be applied to these windows to get my "ethernet" connection in Paralells 7 up and running?
I would think entering the exact same "network info" as appears in my Mountain Lion "Systems Preferences - Network" window, would get me internet connected on Paralells 7 Snow Leopard? Evidently not ... what is needed for me to get this right?
Anyone have experience getting "ethernet/internet" connected on Snow Leopard Server, using Paralells 7?

MlchaelLAX
Since I have been directed to: "NOT waste everyones time on this discussion" the only thing more I am going to do after this post is click on: "Stop email notifications" and never return to this thread again!
Internet access through Ethernet in Snow Leopard Server installed into Parallels 8 on 2011 Mac Mini in Lion:"
I simply don't want to purchase and have to install Parallels 8 .... Parallels 7 should work fine on connecting to the Internet. Also, I was asking about the internet connection issue with the new 2013 iMac (running Mountain Lion 10.8.3 runiing Parallels 7), not a 2011 Mini Mac running Lion with Parallels 8.

How to resolve network issue or dns to access web page on snow leopard server?

I have my network setup like as follows:
internet > router 1 > ethernet ports > switch > router 2
I have a mac osx snow leopard server connected to "router 1", but it is so slow when accessing a web page hosted on the server from a browser on a workstation connected to either router 1 or router 2?
Is there a problem with my network setup or maybe because I changed the name to newservername.local?

@Jeff and @Camelot,
I think it is a DNS issue. I completely reset the DNS settings on server and the local name with the steps below, but now cannot access the site hosted on the server at all
I used a modified version of http://www.mkahn.com/2010/09/configuring-dns-on-mac-os-x-10-6-snow-leopard-serve r-for-hosting/ to reset the server set
1. Stop DNS Service in Server Admin
2. Close Server Admin
3. Obtain 10.6 DNS Default files (below)
4. Overwrite the DNS files with DNS Default files:
/etc/dns/loggingOptions.conf.apple
/etc/dns/options.conf.apple
/etc/dns/publicView.conf.apple
/var/named/named.ca/etc/named.conf
/var/named/named.local
/var/named/localhost.zone
5. Restart your server
All machines have 1ms ping responses within the network including this snow leopard server that I am trying to setup. There is another test web server that return pages instantly within this network so I doubt it is a network issue, but a DNS issue.

New Snow Leopard Server, Slow Network Accounts

We've installed Snow Leopard Server on our XServe quite a while ago and since then all users who work with network accounts are complaining about serious perfomance issues. These issues are for instance logins which may very well take up to several minutes, or applications like Adobe InDesign which take their time to load files from the users network shares.
Our System consist of:
1 XServe running OS X 10.6.8 Snow Leopard Server
48 iMacs running OS X 10.5
1 Windows Server 2008
The XServe serves as an OpenDirectory and Fileserver, while the Windows Server delivers DNS.
We have created ~500 users and 25 groups in the OpenDirectory. All user files are located in their roaming profiles on the Xserve. Additionaly every user has access to one group folder, which is located on the Xserve as well.
All group folders are Sharepoints and added to the dock of all users in the appropriate group.
I have already checked DNS settings, user accounts, network connectivity in general, network load during peak hours, the ACLs on the group folders....
By now im simply out of ideas what my cause the problem, let alone how to solve it.
Any hints are greatly appreciated.

Are you using any redirections? Redirecting the cache folder from the network home to the /tmp should improve speed. Use this white paper from apple. http://images.apple.com/education/docs/Apple-ClientManagementWhitePaper.pdf The redirections are on page 53.

Change user account in snow leopard server??

Trying to change a user account picture in snow leopard server. Have couple computers that are on snow leopard and it uses the the network server that has all the login in. I can't change the user icon within system prefernces. Please help me!

There are server user accounts and computer user accounts. System Preferences is for creating and managing computer user accounts. Server Preferences and Workgroup Manager are for creating and managing server user accounts. If you created the account in System Preferences, you won't be able to manage it with Server Preferences or Workgroup Manager.

Windows 7 (Client) map a network drive VPN Snow Leopard Server

Hi,
I have a Mac Mini Snow Leopard Server and are using a VPN service.
My services on the mac os x sls server are: AFP, DNS, Firewall, Open Directory, SMB and VPN.
I can connect the VPN from Mac clients and Windows 7 clients, but I can only map a network drive/share point on Mac´s.
On Windows 7 I get an error: path or name not found ( I am sure using the correct path, same from Mac client that works).
When I am using my internal network LAN I can map a network drive using Windows 7 and Mac but outside over a VPN not (only Mac works).
The only service, at this moment, that I need is File Sharing outside my network LAN using a VPN.
How can I map a network drive from a Windows 7 client using a VPN, is there any Firewall rules / SMB rules / File Sharing rules that I missed on the server side?
Thank You.

I really don't know what are going wrong with my settings. As you said/write it must be an easy setup.
I'm using a Time Capsule and used the Server app to add VPN to the port forwarding also.
When I am connected thru the VPN I tried to ping the Server IP and got no answer from it, from W7 client!?
My Mac's are just working fine with AFP and SMB share points thru the VPN.
I think I have missed some settings from the SMB or Firewall services for VPN with W7 client's or it is a Windows issue.....

Lion Clients 10.7.4 show network accounts are unavailable and server is not responding when binding to Snow Leopard server 10.6.8

Hello,
I am running Snow Leopard Server 10.6.8 and my clients are Lion 10.7.4. While testing I had no issues binding 10.7.4 to our 10.6.8 server's OD. I created a 10.7.4 image to push to all of our machines and in the beginning of last week I was able to push the image and get the machines to bind with OD and apply preferences on these machines through workgroup manager. Towards the end of the week though this stopped working. Now any time I bind a 10.7.4 client to OD it allows me to perform an authenticated bind and the machine shows up in workgroup manager but immediatley after binding the client the status jelly next to the OD server in the directory list is red and says "This server is not responding". If I reboot the client I get a notification that "Network accounts are unavailable" at the login screen. My preferences from workgroup manager are also not applying, which is my main concern because without workgroup manager my mac server is somewhat pointless as we use it for very little else.
I've since tried to bind a snow leopard machine (10.6.8) and this still is working with a green status jelly. I've also built a lion machine from scratch, updated to the 10.7.4 combined update and am still getting the same issue where it shows the server is not responding when binding to OD. I then applied the subsiquent OS update after the 10.7.4 combined update but the problem still persists.
Is anyone else having this issue? Any help would help me keep my sanity.
Thanks,
Dane

Have you had any luck finding a solution to this? The only thing I have found was to unbind and then bind without authentication. Any help with progress on your end would be appreciated!
Nick.

Sharing Canon Wireless Network Printer on Snow Leopard Server

Trying to setup a wireless printer to share on the LAN via Mac Mini Snow Leopard Server, however the sharing option is not available.
Configuration:
Mac Mini Snow Leopard Server (latest updates etc.) (static IP)
TimeCapsule Wireless network (static IP)
Canon MP620 Wireless printer (static IP)
Two MacBook's (DHCP)
Printer drivers (network drivers, and scanner drivers) from Canon installed on Mac Mini and printer is connected and setup via wireless network on Mac Mini; it is operational and can print from Mac Mini directly without problem
Sharing option on Mac Mini for the printer is missing in Print Settings (missing checkbox), so unable to share the printer on MacBook's via the Mac Mini, also under Sharing Settings the printer option is not there (assuming because share this printer option is not in the print settings)
Ideally, I want to setup the printer on the Mac Mini as a print server, without having to hardline (USB) the printer to the Mac Mini.
Thanks for any help, ideas etc.

Hello and welcome to Apple Discussions.
On OS X Server, you need to use the Server Admin utility (Applications > Server ) to share the local print queue. This requires the Print service to be added/started and then a queue created for the local printer.
Seems unusual that you would want to share a wireless printer from the server. The MacBook 'clients' would still be able to connect directly to this printer without having to connect via the server share so without knowing all the details of your setup it just seems an odd requirement.

Kadmin can't change dsimport'ed passwords in Snow Leopard Server

Hello, World.
I am attempting to manage user accounts in Open Directory from a non-Mac system. After a good deal of investigation on Leopard Server, I wound up ssh'ing to our Open Directory server to create new accounts with 'dsimport', and then to manage later changes to the account through LDAP (for non-password data) and through Kerberos with kadmin, on the theory that kadmind was supposed to propagate the encrypted plain text passwords into Password Service for all of P.S.'s hashing needs.
This worked great in Leopard Server, but under Snow Leopard Server, any attempt to change a user's password via kadmin fails with
'change_password: KDC policy rejects request while changing password for <principal name>'
At the same time, the system log (/var/log/system.log) shows
Nov 2 17:53:46 od1 sandboxd[76028]: mkpassdb(76026) deny file-read-data /usr/sbin/mkpassdb
Nov 2 17:53:46 od1 sandboxd[76028]: mkpassdb(76027) deny process-exec /usr/bin/ldapsearch
However, if I create a principal directly with kadmin, kadmin does allow me to change the password for the principal I just created.
Use modprinc to remove attributes (REQUIRESPREAUTH DISALLOW_SVR) from the dsimport'ed principals doesn't affect anything in any positive manner, though the principals I create manually in kadmin do lack these attributes.
So, does anyone know what the story is, here? Is there no supported API that I can use from a Solaris/Linux server to fully manage accounts under Open Directory?

I have a Similar issue, Details below. the summary is that Using the Snow Leopard GUI interface I created 17 users with a generic low security Password. then transferred and converted some mail files to the server. Once the mail was working properly, I changed the passwords to a slightly more secure password, and set it so my users would have to change their password to a more secure password at log in.
Even after these password changes it is very easy to get other user's ticket information, if you know the original low Security Password with
kinit <other user name>
Details and demonstration.
oursvr:krb5kdc root# kpasswd someuser
Please enter the old password for [email protected]:
Please enter the new password for [email protected]:
Verifying, please re-enter the new password for
[email protected] again:
Server error
Unknown error code: 2802413321
KDC policy rejects request Unknown error code: 2802413326
Please enter the old password for [email protected]:
oursvr:krb5kdc root# kadmin.local
Authenticating as principal root/[email protected] with password.
kadmin.local: cpw [email protected]
Enter password for principal "[email protected]":
Re-enter password for principal "[email protected]":
ambiguous user name.
change_password: KDC policy rejects request while changing password for
"[email protected]".
kadmin.local: q
oursvr:krb5kdc root# kinit someuser/admin
Please enter the password for someuser/[email protected]:
oursvr:krb5kdc root# klist
Kerberos 5 ticket cache: 'API:Initial default ccache'
Default principal: someuser/[email protected]
Valid Starting Expires Service Principal
12/21/09 12:00:53 12/21/09 22:00:53
krbtgt/[email protected]
renew until 12/28/09 12:00:53
oursvr:krb5kdc root# kadmin
Authenticating as principal someuser/[email protected] with password.
Password for someuser/[email protected]:
kadmin: cpw someuser
Enter password for principal "someuser":
Re-enter password for principal "someuser":
change_password: Unknown error code: 2529638924 while changing password
for "[email protected]".
oursvr:krb5kdc root# kdestroy
oursvr:krb5kdc root# kinit otheruser
Please enter the password for [email protected]:
oursvr:krb5kdc root# klist
Kerberos 5 ticket cache: 'API:Initial default ccache'
Default principal: [email protected]
Valid Starting Expires Service Principal
12/21/09 12:07:55 12/21/09 22:07:50
krbtgt/[email protected]
renew until 12/28/09 12:07:55
CONFIGURATION
=============
Contents of /var/db/krb5kdc/kadm5.acl:
## This file autogenerated by KDCSetup ##
*/[email protected] * *
[email protected] * *
ADDITIONAL INFORMATION
======================
(1) Using 'passwd' to change the password does not change the Kerberos
password.
(2) Using "dscl /LDAPv3/127.0.0.1 -passwd Users/someuser" does not change
the Kerberos password.
(3)
(4) From /var/log/system.log:
Dec 21 11:57:01 oursvr edu.mit.Kerberos.kadmind[79131]: ambiguous user name.
Dec 21 11:57:01 oursvr sandboxd[82190]: mkpassdb(82189) deny file-read-data
/usr/sbin/mkpassdb
(5) From /var/log/krb5kdc/kadmin.log:
Dec 21 12:02:36 oursvr.sub.dom.tld kadmind[79131](Notice): Request:
kadm5chpassprincipal, [email protected], KDC policy rejects
request, client=someuser/[email protected],
service=kadmin/[email protected], addr=VVV.WWW.YYY.ZZ
Dec 21 12:02:36 oursvr.sub.dom.tld kadmind[79131](Notice): Request:
kadm5chpassprincipal, [email protected], KDC policy rejects
request, client=someuser/[email protected],
service=kadmin/[email protected], addr=VVV.WWW.YYY.ZZ
(6) From /var/log/krb5kdc/ldc.log:
Dec 21 11:56:51 oursvr.sub.dom.tld krb5kdc[62](info): AS_REQ (7 etypes {18
17 16 23 1 3 2}) VVV.WWW.YYY.ZZ: NEEDED_PREAUTH:
[email protected] for kadmin/[email protected],
Additional pre-authentication required
Dec 21 11:56:51 oursvr.sub.dom.tld krb5kdc[62](info): AS_REQ (7 etypes {18
17 16 23 1 3 2}) VVV.WWW.YYY.ZZ: NEEDED_PREAUTH:
[email protected] for kadmin/[email protected],
Additional pre-authentication required
Dec 21 11:56:51 oursvr.sub.dom.tld krb5kdc[62](info): AS_REQ (7 etypes {18
17 16 23 1 3 2}) VVV.WWW.YYY.ZZ: ISSUE: authtime 1261414611, etypes
{rep=18 tkt=16 ses=18}, [email protected] for
kadmin/[email protected]
Dec 21 11:56:51 oursvr.sub.dom.tld krb5kdc[62](info): AS_REQ (7 etypes {18
17 16 23 1 3 2}) VVV.WWW.YYY.ZZ: ISSUE: authtime 1261414611, etypes
{rep=18 tkt=16 ses=18}, [email protected] for
kadmin/[email protected]
(7) mkpassdb -dump 0x4b2bf32f30c3d4860000001e0000001e
slot 0030: 0x4b2bf32f30c3d4860000001e0000001e someuser 12/21/2009
12:28:17 PM
Last password change: 12/21/2009 11:00:36 AM
Last login: 12/21/2009 12:28:17 PM
Failed login count: 0
Disable reason: none
Hash-only bit: 0
Last Transaction ID: 2052
Transaction requires kerberos: 1
Record is dead: 0
Record is not to be replicated: 0
Access Features:
isDisabled=0 isAdminUser=0 newPasswordRequired=0 usingHistory=0
canModifyPasswordforSelf=1 usingExpirationDate=0 usingHardExpirationDate=0
requiresAlpha=0 requiresNumeric=0 expirationDateGMT=18446744073709551615
hardExpireDateGMT=18446744073709551615 maxMinutesUntilChangePassword=0
maxMinutesUntilDisabled=0 maxMinutesOfNonUse=0 maxFailedLoginAttempts=0
minChars=0 maxChars=0 passwordCannotBeName=0 requiresMixedCase=0
requiresSymbol=0 notGuessablePattern=0 isSessionKeyAgent=0
isComputerAccount=0 adminClass=0 adminNoChangePasswords=0
adminNoSetPolicies=0 adminNoCreate=0 adminNoDelete=0 adminNoClearState=0
adminNoPromoteAdmins=0
Group(s) for Administration: unrestricted
digest 0: method: *cmusaslsecretSMBNT
digest length: 16
digest: D6B093421FDF17380F0B695721F0F26A
digest 1: method: *cmusaslsecretSMBLM
digest length: 16
digest: 5C957C596B14237409A48A7AC23C7AB2
digest 2: method: *cmusaslsecretDIGEST
digest length: 16
digest: 8E9181A5F7697D7FB83BF2DA430CBB70
digest 3: method: *cmusaslsecretCRAM-M
digest length: 32
digest:
A08E4B9266A4B8676DEFA8584758F9013D29A479D81EE4E41D857D5A5CA4FA71
digest 4: method: KerberosRealmName
digest: OUR.KRB5.RLM
digest 5: method: KerberosPrincName
digest: someuser
digest 6: method: *cmusaslsecretPPS
digest length: 24
digest: A5AC9D1843D42ED4AF39EFB4AB91E536F733FB2580978860
digest 7: <empty>
digest 8: <empty>
digest 9: <empty>
slot checksum: 7DAA85870308B253D5A9294483A4B0EF
(8) dscl /LDAPv3/127.0.0.1 -read Users/someuser | grep -A 2 authAuthority
dsAttrTypeNative:authAuthority:
;ApplePasswordServer;0x4b2bf32f30c3d4860000001e0000001e,1024 35
14773688809506996593092824880872774590718495204127440029375223520574013330136617 78685429961896612181406054801454823310071429734609519569726042321602422714273008 59946509691313082062885828226653436410277560435615063784052163315144051817774743 254036483144235604939879290290235050919364398951613699884041179183857
[email protected]:VVV.WWW.YYY.ZZ
;Kerberosv5;0x4b2bf32f30c3d4860000001e0000001e;[email protected];OUR.KRB5.R LM;1024
35
14773688809506996593092824880872774590718495204127440029375223520574013330136617 78685429961896612181406054801454823310071429734609519569726042321602422714273008 59946509691313082062885828226653436410277560435615063784052163315144051817774743 254036483144235604939879290290235050919364398951613699884041179183857
[email protected]:VVV.WWW.YYY.ZZ

Transfer Snow Leopard to Snow Leopard server question..

Just wondering, if I use TimeMachine backup(Snow Leopard), and trandfer system to Snow Leopard server, is it working? My point is according to my understanding, Snow Leopard server doesn't have iLife. what will happen with my iPhoto iMove,etc...after transfering...
Thanks

hi taylor,
Your photos, music, videos are all kept in your 'home folder.' You can move your home folder from your old computer (or time machine backup drive) using migration assistant. The only thing you need to check is 'user accounts.'
Migrating the home folder from the old computer would be faster then using the time machine backup.
You will also need to install ilife, you would want to install ilife from an ilife install disk.
What are you running server on? usually a servers is not used as your work computer. It's usually a separate computer dictated to sharing resources.
it's also important to note time machine dose not back up many of the services you can host on server.

Snow Leopard Server Question

Does anyone know if I can use Snow Leopard Server with Windows clients? I would like to use it for backup of user folders and for a Wiki.

Does anyone know if I can use Snow Leopard Server with Windows clients?
Of course you can.

Snow Leopard Server running extremely slow all of a sudden!!

Hi, I'm not a qualified server technician but am currently trying my best to run a server in a Secondary School! Please help, need to fix ASAP.
So basically we've got a Mac Pro running Snow Leopard server which has become incredibly slow in the past week. Nothing has changed in our department to trigger this. Here's everything I know so far...
- If I try to log on to the admin account when "Some Network Accounts Are Available", log on will take under a minute. If I try to log on to the admin account when the light goes green and "Network Accounts Are Available" log on will take forever and eventually just crash and which point I have to just force a shutdown and try again.
- When I can log on, some aspects of the computing seems fast and other aspects are really slow. For example, a few programs open as soon as I log on no problem, however a simple spotlight search or trying to open Sytem Preferences will crash the computer completely.
- Have tried booting in Safe Mode, and everything ran fast and how it's mean to but once restarting and booting normally the problems remained.
Sorry for the lack of knowledge!!
Thanks in advance.

Your comment indicates "crash the computer"? Do you mean that OS X Server itself fails, and you have to reboot? Or that the application crashes, and you have to restart it?
The following are some general approaches toward gathering some data:
Launch Console.app from Applications > Utilities and see if there are blocks of repeating errors.
Launch Terminal.app from Applications > Utilities and issue the following harmess, diagnostic command:
sudo changeip -checkhostname
After entering an administrative password and possibly seeing a one-time informational message about sudo, you should see some network configuration information and then an indication that no changes are required, or that there are DNS or network errors.
Boot from the Snow Leopard installation DVD and run a volume verification pass using Disk Utility, this from the Utilities menu of the installation disl.
FWIW...
If the applications or OS X Server are crashing, then you're generally heard toward either a reinstallation of the software, or a hardware repair, or quite possibly a combination of the two.
Forcing a hard shutdown can lead to corruptions, depending on exactly what's going on when the power drops out; that's probably best left as a last-resort approach and one best avoided.

Lion server or Snow Leopard Server?

From a quick check of postings here, my question of whether to use Lion Server or Snow Leopard server on a Mac Mini for a small office, looks to be "stay away from Lion server" Snow Leopard server just works and is easier to support.
Most of these posts are from 2011, has anything changed where someone can say Lion is now a much better server choice now than considering Snow Leopard Server?
It seems that most posters feel Lion server is a real step backwards, is this the case?
Thanks in advance - Lewis

Which services have been removed or depreicated?
You have to bear in mind that 'removed' or 'deprecated' only really means 'no longer bundled and supported by Apple'. Just because Mac OS X Lion Server doesn't ship with a foobar server that doesn't mean you can't download and install your own foobar server. It just won't be integrated into the Server Admin apps.
For example, Lion Server no longer ships MySQL Server. So download and install your own copy. It's not like the GUI apps gave you any control over the MySQL anyway, other than starting it up and controlling the network ports.
Likewise for print server. Some of the advanced print features such as quotas have been removed from the GUI, but you can implement them yourself.
Likewise with QuickTime Streaming Server, where the functionality is little more than a web service.
What features that have been enhanced?
Lion Server has simplified the setup of a server for small workgroups with simple requirements. If that's you then the whole experience may be enhanced since you're not swamped with a slew of options that you don't understand, or need.
I think a lot of people were also stymied by Snow Leopard Server because they expected the GUI apps to cover all the options, which was never the case.
So my original point stands. There is pretty much nothing you cannot do in Lion Server than you could do in Snow Leopard Server, it's just that it might not be supported by the GUI. Most serious server admins eschew Server Admin.app anyway since even Snow Leopard Server's admin app doesn't cover all the capabilities of some of the services, so you end up driving it via the command line anyway.

Question about changing a Snow Leopard Server network settings

Similar Messages

Maybe you are looking for