Snow leopard server set up

question regarding network preferences on server itself "What DNS Server do you have in your Network panel in System Preferences on the server?

What DNS Server do you have in your Network panel in System Preferences on the server?
No one can answer that for you becaise it depends on your network setup. What's right for me is likely not going to be right for you, nor the guy sitting next to you.
Ultimately, though, you need a server that understands your LAN network and can resolve the local LAN addresses (e.g. 192.168.x.x, 10.x.x.x, etc.) of your LAN. This absolutely precludes using your ISP's DNS server or any other external DNS server since they cannot know your LAN setup.
So you are going to need to specify a DNS server on the LAN. If you have one that's already managing your local DNS then use that.
If you don't have one then you're going to need to configure DNS on some device to do that job. You could do it on this machine, in which case you'd enter '127.0.0.1' as your DNS server, or you could do it on another machine in your LAN (in which case you enter that machine's address).
Either are fine approaches. Using your ISP, GoogleDNS, OpenDNS, or any other DNS server outside your LAN is doomed to failure, though.

Similar Messages

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

MySql Database set up on Snow Leopard Server for Wordpress

I am trying to set up a mySql database on the snow leopard server in order to install wordpress.
I have played around with the MySql database settings (in the server admin window) but can't seem to figure out how to set the database name, username, and password within the Snow leopard server.
Do I need to use third party software like Navicat to create the database and user names etc? If yes, any idea how to do that? If now, how do I create a MySql database, username and pw?
I have put the Wordpress install folder on my Snow leopard server. When I navigate to my domain it says I need to configure wordpress by providing my database name, username and password.
Thanks in advance.. I am struggling here.

That's set up via the [MySQL command line|http://labs.hoffmanlabs.com/node/376]. Or you can install the (free) Sequel Pro GUI package, given you're probably more comfortable in the GUI. The steps required for Mac OS X Server are the same as most any other platform, so [launch the MySQL client per the Wordpress Codex|http://codex.wordpress.org/Installing_WordPress], and follow the instructions.

Why can't Firefox set permissions for Snow Leopard Server Web-Site Wikis

I've established a web-site for collaboration of planning for a state-wide NGO and a local citizens-government oversight commission.
I'm using Snow Leopard Server v10.6.4, to drive the web-site, which includes the use of wikis.
In creating a wiki and setting permissions, I find that I cannot set permissions for users or groups to 'read only' from the default 'read & write' while using Firefox. However, I CAN set them to 'read only' using Safari. And, once the permission has been modified in Safari, THEN it can be modified in Firefox.

Solution found at http://michaeljin.wordpress.com/2010/01/05/locked-out-of-mac-os-x-server/
It’s blog update time! Updates have been a little scarce lately, been super busy with getting trophies on PS3
Anyway, recently encountered the following with a Mac mini server running Snow Leopard Server:
Despite being able to ARD / Screenshare the Mac mini, I was unable to get any further than the login window. Authentication credentials are obviously valid. No weird access permissions have been set. However, the weird thing was, I can connect to the server via Server Admin tools (from another Mac) and all other services were running without a hitch.
After much head scratching it turns out to be a sACL (Service Access Control List) issue.
This thread solved the mystery!
http://discussions.apple.com/thread.jspa?threadID=1654864
To save you the trouble, I’ll lay it out here. I cannot take credit for this, but Randall can!
Open Server Admin on a computer (any), and connect with the local admin to the machine.
Select the server and authenticate.
Select Settings, then go to Access. You’ll want to make sure that Login Window and SSH have the local admin account listed if you select the option to “Allow only these users”. For now, I would suggest making sure all services have “Allow all users and groups” selected.
If (as in my case) it was set to Allow All in the first place, simply toggle the settings – back and forth.
Save.
Try logging in again… should be a good one!

Can't rename folders on Snow Leopard Server

I have 10.6.8 Snow Leopard Server running on a new Mac Mini server. Attached I have a Pegasus Raid storing all my files. I have a sharepoint set up for every project we work on but a couple act strangely. Users can create and delete folders but can not rename them once created. In order to rename they must drag the folder onto the desktop, rename and then replace the folder on the server. All permissions are set up identical to the other sharepoints which work fine. I have had a couple so-called "experts" look at the permissions in both the terminal and Server Admin. Everyone seems stumped. Any ideas?

Thanks for the input but I finally soved the problem. Here is what I found...
Although I had given users/group the ALLOW/FULL CONTROL premission with a sharepoint, I discovered that in Server Admin if you double-click on the User or Group name under the ACL permissions that a drop down box appears. This box allows you to fine tune the ACL but it appears that by default all of the boxes are not checked even though I granted the user Full Control. After checking all of the boxes I was able to create and rename folders in my share as expected.
This also had an similar effect if I denied Full Control. Some of the boxes remained unchecked and it left holes in my system where denied users could still access some files. Again by checking all boxes these holes were closed.
Does anyone know how to change the default so that all boxes are checked when assigning the Full Control permission?

I transferred files from a NAS server to the Mac Mini Snow Leopard Server and now some of the files have Custom Access and can't be opened by some users. How do I fix this?

We're setting up our Mac Mini Snow Leopard Server, and in the process transferred files that had been stored and accessed from our Blackarmor NAS server over to the Mac. These files were all created on PC's and are Office Excel files, WordPerfect files or PDF's. When you look at the files on the Mac from the Mac and bring up Get Info for the affected file, it says that the file has Custom Access. The files that work properly don't have that configuration. I can access and open the files on some computers, but some users can't open the files from their computer even though they can see it. We're all using PC's and they get the Error: Access Denied-Contact your administrator--or something similar. I've seen on the web similar issues and it may have something to do with ACL permissions. I don't know enough about Mac OS to understand this, but what is baffling is that they can be opened from some PC's but not others, and all of the Users have the same accessibility to the files. Thanks for a solution!!

Oh, on the losing Internet, try this...
Make a New Location, Using network locations in Mac OS X ...
http://support.apple.com/kb/HT2712
10.7 & 10.8…
System Preferences>Network, top of window>Locations>Edit Locations, little plus icon, give it a name.
10.5.x/10.6.x/10.7.x instructions...
System Preferences>Network, click on the little gear at the bottom next to the + & - icons, (unlock lock first if locked), choose Set Service Order.
The interface that connects to the Internet should be dragged to the top of the list.
Instead of joining your Network from the list, click the WiFi icon at the top, and click join other network. Fill in everything as needed.
For 10.5/10.6, System Preferences>Network, unlock the lock if need be, highlight the Interface you use to connect to Internet, click on the advanced button, click on the DNS tab, click on the little plus icon, then add these numbers...
208.67.222.222
208.67.220.220
Click OK.
PS. Your English is quite good & completely understandable.

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.

Error configuring services from Snow Leopard Server to Mountain Lion Server

I am trying to upgrade a Snow Leopard Server Mac Mini to Mountain Lion Server.
We have two Mac Mini servers at our office (production and backup) so I migrated the everything from our production server to the backup using the migration assistant when setting up the backup computer.
I now have the backup at home trying to upgrade it to Mountain Lion Server. I have downloaded and installed Mountain Lion as well as the Server App version 2.2. I basically followed the simple directions found in the Apple documentation.
I started the server app and it got to the part where it said "Upgrading services". After running for a few minutes, I get a window that states "An error occurred while configuring your server." It also sayd "The following actions failed or were not attempted:" with a red dot next to "Upgrading services". The other three items: "Authenticating to local directory", "Reading directory configuration" and "Authenticating to local directory services" have gray dots so I'm sure they were not even attempted.
Our Snow Leopard server is setup for SMB file sharing, LDAP services, FTP, Web, DNS, DHCP.
Can someone point me to where I can figure out what exactly is failing? Are there specific log files I need to look into?
Thanks

Have EXACTLY the same issue - also tried reinstalling mountain lion server fresh and still had the same problem...

How do I remotely access my Snow Leopard server from my Mountain Lion MacBook Air

Does anyone know of an idiot's guide to setting up a VPN to access my server? I'm running Snow Leopard server in the office and I'd like to be able to access the server, probably just from one computer (MacBook Air runnung Mountain Lion) from home.
I'm not sure if it complicates things or not, but the office is in an area with poor broadband and so the internet connection is via satellite broadband. The set up is a satellite modem into a Gigabit router and the server is connected to the router via an unmanaged switch.
As an aside, I'm considering changing this set up so that the modem plugs into a Time Capsule and the server will connect directly into the TC. The desktops will then run into the server via the unmanaged switch or wirelessly via TC - any thoughts on the best set up here? Are cables into a switch better/worse than using TC's wireless facility.
Is this something that I, as a reasonably competent computer operator but definitely not an IT expert, could do, or should I get someone in to set it up for me?
Thanks in advance
Jim

VPNs aren't particularly special or weird or secret or such. They're "just" a network connection. A sometimes very fussy network connection, but a network connection.
My preference is to use a firewall that includes an embedded VPN server. This for several reasons, as it avoids trying to forward the VPN through a device that's using NAT [1], and it means you can connect to multiple devices on the target LAN, and you can connect even if the OS X Server box is down.
Other folks will forward the VPN through NAT, and use the VPN server that's available in various versions of OS X Server.
Forwarding a VPN through NAT does work, but can also sometimes not work. NAT can cause some types of VPNs to get tossed off when (for instance) there's a second VPN connection arriving.
In various cases everything connects and works the first time, and in other cases it's trial-and-error.
With a VPN-capable firewall (which is a step above your average residential firewall), usually configuring the firewall as a L2TP server or the Cisco protocol, if you want to use the standard OS X or iOS clients. Or PPTP — which is easier to get working — but less secure. Once the firewall and the VPN server is set up — and that's where most of the "fun" is — then the set-up in Network Preferences is (usually) pretty simple.
There are thousands of OS X VPN set-up articles around, but the details all hinge on the particular VPN server, and whether you're going to try to push the VPN through (for instance) that Tome Capsule and its NAT. Until you sort out your VPN target and/or VPN client, and what sort of attacks you're securing against...
As for this case, satellite latency is large. The latency involved is the time it takes to the command or the text from your local Mac to the satellite ~35,786 kilometers up and then ~35,786 kilometers back down, and then the response back again. That's about a quarter second, each way, at the speed of light. Transferring big files is fine (once the connection is open and the transfer gets rolling), but anything interactive — such as a typical use of a VPN — is going to have a noticable lag.
Yes, it'll be easiest to get somebody to work through your requirements and expectations, and initially set this up for you. Or you can use this as an opportunity to read about and learn more about IP routing and networking and VPNs, too.
[1] VPNs seek to ensure that the network connection is secure, and from a known client IP source address to the IP address of the target VPN server. NAT explicitly obscures the network connections, and often has multiple client hosts located behind one IP address. Put another way, the VPN and NAT software implementations are working at cross-purposes.

I've got Snow Leopard Server, but don't need the server functions. What to do?

This is somewhat complicated, so please bear with me. My Mac Pro was running OS X 10.5 and required updating. But we have legacy Power PC apps (mainly FreeHand) that we want to continue using, even though Mountain Lion doesn't support them.
As a solution, I'm going to run Snow Leopard Server in emulation on Parallels 8 Desktop. I would rather have used plain old Snow Leopard instead of the server version, but Apple's EULA only allows 10.6 Server to run in emulation.
So, I got Snow Leopard Server and have used it to upgrade 10.5. Eventually, (once I get everything working properly), I'll upgrade that to Mountain Lion and use SL Server in Parallels emulation to run the old Mac apps we can't do without.
But I've run into a problem I didn't anticipate: I don't have a clue about running a server.
I'm having trouble setting it up so the other Mac user in my department can access a shared folder. Also, I want the login window to display the list of users, but that option is grayed out.
What I'd like to do is strip out all the server functions and just run as if 10.6.8 was a standard version of Snow Leopard, which I'm familiar with. If that's not practical, please explain how to get sharing to work since that's the main problem.
I've tried turning off the services listed in the Server Preferences (iCal, Mail, etc.) but that hasn't fixed the problems. I think there may be server functions running that I haven't found preventing me from fixing the problems. Or it could be something else entirely (as I said, no clue).

DON'T MAKE A MOUNTAIN (lion?) OUT OF A MOLEHILL!
Several points in response to your post, in chronological order, not necessarily in order of importance:
• It was a common Urban Myth that Snow Leopard (client's) EULA prohibited its virtualization in Lion or Mt. Lion on a Mac! That myth has been largely debunked in the last 18 months.
Here are detailed instructions on how to install Snow Leopard client into Parallels 7 or 8:
http://forums.macrumors.com/showthread.php?t=1365439
That being said, and being the author of the aforementioned thread, I STRONGLY recommend that, where possible, you use Snow Leopard Server in favor of Snow Leopard client. This will side step some later corruption problems that can arise from the improper use and shutting down of this Parallels partition.
Historically, this thread was written when Apple sold Snow Leopard Server for $499+ or ceased sales altogether. Now, Apple has rendered the (now diminishing) debate over the EULA moot, by its recent release of Snow Leopard Server to the US & Canadian community for $20; leaving those who cannot purchase SLS (or get someone to purchase it for them) to continue to follow the instructions in my thread (or asking me to purchase SLS for them and forward it to them; my preferred course of action!).
• I ALWAYS recommend that data files be stored on the real Mac's HDs and NOT in a virtualized world. This is easy to accomplish and establishes a backup regimine (Time Machine, etc.) that will protect the users data. Lost applications are easily restored from their installer discs.
• In practice I find that using SLS in Parallels 8 is the same as using SL client in Parallels. I have even removed the Server apps from the Dock so as to not be confused by them.
So, your solution is to establish a "shared folder" on the hard drive of the Mac that is hosting Parallels. When in SLS in Parallels you will have access to your shared folder, ironically through Parallels' "Shared Folders" feature that is now present in Mac OS Guest installs on version 8 (see the "Shared Folders" SERVER on the right side of the screenshot, below).
When using Freehand MX or other PowerPC apps, save your data files into your shared folder through access to it by Parallels' Shared Folders. Other users on your network will have access to the SAME data files, through their customary use of file sharing to access your shared folder from your Mac's hard drive.
IGNORE the Server applications in the Applications folder...
Freehand MX running in Snow Leopard Server installed into Parallels 8 for use in Lion or Mt. Lion:
[click on image to enlarge]
Postscript: your post was so easy to follow!

DNS Configured-Best Practice on Snow Leopard Server?

How many of you configure and run DNS on your Snow Leopard server as a best practice, even if that server is not the primary DNS server on the network, and you are not using Open Directory? Is configuring DNS a best practice if your server has a FQDN name? Does it run better?
I had an Apple engineer once tell me (this is back in the Tiger Server days) that the servers just run better when DNS is configured correctly, even if all you are doing is file sharing. Is there some truth to that?
I'd like to hear from you either way, whether you're an advocate for configuring DNS in such an environment, or if you're not.
Thanks.

Ok, local DNS services (unicast DNS) are typically straightforward to set up, very useful to have, and can be necessary for various modern network services, so I'm unsure why this is even particularly an open question. Which leads me to wonder what other factors might be under consideration here; of what I'm missing.
The Bonjour mDNS stuff is certainly very nice, too. But not everything around supports Bonjour, unfortunately.
As for being authoritative, the self-hosted out-of-the-box DNS server is authoritative for its own zone. That's how DNS works for this stuff.
And as for querying other DNS servers from that local DNS server (or, if you decide to reconfigure it and deploy and start using DNS services on your LAN), then that's how DNS servers work.
And yes, the caching of DNS responses both within the DNS clients and within the local DNS server is typical. This also means that there is need no references to ISP or other DNS servers on your LAN for frequent translations; no other caching servers and no other forwarding servers are required.

I want to install Snow Leopard Server on our MacPro (2.66) using Mac Mini Snow Leopard Server disks? I kept getting an error for backwards compatibility. Is this possible or do I need to purchase another copy of Snow Leopard Server?

I want to install Snow Leopard Server on our MacPro(2.66) using Mac Mini Snow Leopard Server disks? I kept getting an error for backwards compatibility. Is this possible or do I need topurchase another copy of Snow Leopard Server?

The OS disks that are shipped with a particular product
are set up so that tey will only install on that product.
It will install on any Mini of that exact vintage, but that
is all.
This is to prevent people from doing exactly what you
are trying to do. The license for OSX shipped with any
is only valid for that product. Also, Snow Leopard,
including Server, is only permitted to be run on one
computer at a time. Bottom line, unlike Lion, legally
you cannot install the same copy on multiple
computers unless some "family pack" or site license
is purchased.
Yes, you need to purchase another copy.
The copy of Snow Leopard license is here:
http://images.apple.com/legal/sla/docs/macosx_snowleopard.pdf

Complications migrating from Snow Leopard Server to Mountain Lion Server.

I'm migrating from Snow Leopard Server to Mountain Lion Server. The article "OS X Server: Upgrade and migration" (http://support.apple.com/kb/HT5381) says
"Make sure that any DNS or DHCP servers on which your server depends remain running during the upgrade"
This advice is reinforced by the details of the article "OS X Server: Steps to take before upgrading or migrating the Open Directory database" (http://support.apple.com/kb/HT5300).
As the server I'm migrating from provides these services it will need to be running during the migration process. This would seem to limit my options to doing the migration from a Time Machine backup (or, making a seperate clone of the server's drive and connecting it externally to the new box)
My main concern is the seemingly inevitable clash that is going to occur on the network as the new server takes on the roles of the old one - while it is still running.
What are my options here ?
This is my second attempt as on my first try I did the migration from the TM backup with the network down - and none of my local network users or their home directories were migrated, although the settings for the mount points were, but there were no actual directories where they pointed to!
Clear directions on how to procede would be VERY MUCH appreciated
Thank you.

Moving from Snow Leopard to Mountain Lion means first installing the client (non-Server) version of Mountain Lion and then install Server.app this means that for at least part of the process you will not be running DNS, DHCP or Open Directory.
If you are going to end up using the same DNS name and IP address after the change then an approach you could follow would be as follows.
Destroy any Open Directory replicas
Archive your Open Directory Master (to make a backup)
Note down your DNS records in case they get messed up
Export via Workgroup Manager your users, and groups (you might not need this but better safe than sorry), make sure you do not include the diradmin account
Keep a full back of the server (you should always have backups)
Note down your DHCP server settings in case they get messed up
Note down any other service settings
Install Mountain Lion
Install Server.app
Install Workgroup Manager (extra free download)
Run Server.app
Make sure settings for services are as much as possible the same as before
If your lucky that may be all you need to do, otherwise...
Restore Open Directory archive, if your lucky that will be all you need to do, otherwise...
Make new Open Directory Master
Run Workgroup Manager
Import users and groups you previously exported
You will then have to set passwords for each user as these are not preserved via Workgroup Manager export
When I did this, I was also being forced to change all my IP addresses so I had no choice but to use Workgroup Manager to export and import accounts.

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.

Problems deleting pdf's generated from files off of Snow Leopard Server

The small design studio I work at has just upgraded from G5's running 10.4 Tiger, working off Tiger Server, to new iMacs running 10.6 Snow Leopard and a Mac Mini Server, on Snow Leopard Server.
Normal working practice is to open files off the server across the network, making changes and saving them back down. Most of the time, a pdf will be generated from the file to send to the client when copy changes have been made, then saving down the pdf file to the iMac to email to the client.
The issue is now that when the pdf has been emailed, attempting to delete it brings up a warning window that 'You do not have sufficient accesses privileges to delete the file' and this then has to be done by selecting secure empty trash.
We are all registered users on the Mac Mini Server and this was not an issue we had when using Tiger.
Could anyone suggest any setting changes that would be required to get around this issue?
As a note, all the work files were originally on a older G4 being used as a sever and were copied to the new Mac Mini Server, that was set up as a new machine and was not done via transfer files.
Thanks
Ben

Hello Ben,
I'm very sorry, but this is not the correct forum in which to post your question! Universal Access is the facility for ensuring that all Mac users can benefit fully from their machines, regardless of disability.
Try Snow Leopard Server—Installation, Setup and Migration instead!
Cheers,
Archie

Snow leopard server set up

Similar Messages

Maybe you are looking for