Leopard Server on G4 XServe?

I run a lab of 31 Intel iMacs (plus a number of assorted machines around the school) using a G4 1.33 GHz XServe with 1.25 GB of RAM. The lab iMacs and the server are both currently running 10.4.11.
I have purchased an unlimited license of Leopard server, but am hesitant to install it at this busy moment in the school year. I have two questions:
1. Will my old G4 XServe handle Leopard Server well?
2. If so, would I be advised to update my lab clients to Leopard as well?
Any advice would be helpful.

From experience, the G4 server does Leopard pretty well. 10.5.0 would occasionally deadlock the server when running multiple services and mail services would run away under 10.5.1. 10.5.2 is so new I can only say that three days and nothing to report. You might want to max the RAM out depending on how many services you are running. Recall that a G4 Xserve can take a max of 2 GB of RAM so there is not much room to grow - but it will be worth it if you have a lot of services.
Also, the 1.33 model commonly came with only a CD Rom drive. Leopard is DVD media only. So you will need to be creative and either find an external firewire DVD drive, clone the install media to an external drive, install in firewire target disk mode, or do a net install.
Additionally, if you are doing any level of RAID on the system, I usually recommend backing up the data, breaking the raid, and then recreating it. While Tiger to Leopard does not seem as vital, Panther to Tiger was an issue because the Apple software raid went from version 1 to 2. Old habits die hard. I still do clean installs from major release to major release.
And the final piece of advice is - why change mid semester? If you have a stable, working environment, let it play out until you have a break. While there are some compelling reasons to upgrade to Leopard, I doubt you will use many of them, especially if you have no time to explore and learn. Also, Leopard is still a little shaky with AD integration so if you have a parent directory service, stay on 10.4.11 until Apple gets a few more releases out (I will say that 10.5.2 is much better, but I am waiting for the shoe to drop and I am basing this on one environment with a single domain). Plus, while you have not mentioned what the lab is used for, I would bet a round of drinks that those iMacs have some piece of software that is not yet Leopard compatible. Adobe just released the Acrobat compatibility fix. InDesign is rocky (although 10.5.2 seems to have smoothed things up). Hang in there and finish out the school year/semester.
What is the rush. Hold off until the students are out of the way. That way you do not disrupt the classroom experience or worse, shut it down because of a blown upgrade.
Hope this helped.

Similar Messages

Virtualization of snow leopard server on a xserv

Hello
I'm looking for someone how have already use virtualization on a xserv.
thanks

We have an xserve + 2 Snow Leoaprd VMs + 2 Win2k3 VM's. It's mostly been used for 10-20 clients, but we're starting to move the rest of our staff on it which adds about 50 more.
We chose vmware because of cost and stability. Parallels requires their server version which costs a lot more money than their desktop, and it didn't seem worth it if we only ran 2-3 VM's.
Vmware also seemed more stable than Parallels5 at the time.
It might be different now, they did not have hypervisor even announced a year ago when we last compared the two.
Message was edited by: InterHmai

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.

Snow Leopard Server Software - Mac Mini Copy vs Retail Copy

Hi All,
I recently purchased a mac mini server, with what I thought would be a SL Server license.
I've used the Mac Mini to run a Leopard server whilst our Xserve was out of action.
Now the xserve is back, I was thinking of installing SL on the Xserve and keep the mini running leopard until we migrate over.
When I tried to install SL on the Xserve, it gave me an error. I rang Apple, and the enterprise guy told me this wasn't possible, as the copy that came with the mac mini was hardware specific and just a restore copy of snow leopard server. Bottom line I can't install the Mac Mini version of SL on an Xserve, even though I have paid for a SL license in buying the mac mini!
Does anybody know if there is any real differences between the hardware specific software copy and a retail version. If there isn't I'll install a copy on the mac mini and copy it over to the xserve. I just want to be sure that I'm not getting a downsized version of software!
Thanks.

There are ways to extract the OS from the restore disk so you can use in other system. you will just have to do a little online search. but I think it will be illegal if you care of course... but it would probably be easier to just download a copy from rapidshare or something like that and use your key ..
As far as feature there is none between the restore and retail copy.

Problem XP accessing Leopard Server Shares

Hi there,
I have read through a lot of posts but have not exactly found my problem. So here it goes:
I have made a clean install of Leopard Server on a Xserve G5 and set it up as "Standard".
By default AFP and SMB are turned on, so Windows XP users should be able to read and write.
While setting it up with "Server Assistant", I added users. These, however, had vanished from the earth when I booted the server for the first time.
I then updated to 10.5.1.
By logging in as root via "Server preferences" I added the accounts manually (again).
Now the thing is that everything works fine from a Mac. I can access Public and read/write to it.
Windows Users, however, cannot log into the server. They see my xserve but when they put it their username and password, nothing happens.
The only way I got this to work, is to add all my users locally using "Workgroup Manager". Then my users can log in and everything seems to work.
From my limited understanding this is not really what I should do though.
I have read that this might have something to do with the DNS server.
But I use the xserve as a standalone server that get's all its information from a DHCP router that's connected to the internet. So there's no local DNS server.
I would like to point out that the exact setup (minus the local users) worked great under 10.3.9.
Any ideas?
-chris.

OK, after having talked to some Apple support guy, I totally was about to give up. He pretty much told me to do a re-install in advanced mode. Apparently, they are aware that standard configurations just don't work as advertised.
But I fiddled around a bit more and finally solved the issues I had, so I wanted to share that with the community.
Basically what I did was this:
1. I set up DNS service using "Server Admin" (I am not sure if that was necessary but I did it anyways)
2. I "kerberized" my Open Directory service in "Server Admin". that made it possible to add users with "open directory passwords". it was enough to hit the "kerberize" button, so so went unexpectedly well.
3. I changed all passwords to open directory passwords.
4. I went back to "Server Preferences" to re-enable all services for users. those somehow got unchecked by whatever Server Admin did. probably you can do that in Server Admin/Workgroup manager, too, but I am not sure how and what I did at least worked.
Now everything seems to function properly. SMB as well as AFP access works and everyone has read/write-access to Public.
-chris.

Are there any problems with Snow Leopard Server (Xserve) and PPC Clients

Hi,
are there any problems identified yet with Snow Leopard Server, installed on a Xserve and PPC Clients running Mac OS X Tiger and Leopard?
Currently I have a Xserve Intel running Leopard Server and about 12 Mac Minis PPC running Mac OS X Tiger and Mac OS X Leopard. The Xserve serves services like DNS, OpenDirectory, Software Update Server, NetBoot, etc. All users have Home Directories stored on the Xserve.
Now I want to install Snow Leoaprd Server on the Xserve, but I wonder if there are any problems using the PPC Clients? I have read something like this on a german website.
Thanks!

We've actually found that the Server 10.6.3 DVD does an amazingly smooth job of upgrading 10.5.8. We've been upgrading our production servers and nothing has gone wrong yet. Snow Leopard employs an archive and install method of upgrading which results in an install which is very close to a clean install. So it's been very convenient for us because our servers are used as Windows PDCs and it's a pain in the *** to have to re-join all PCs to the domain if we start from scratch.

Problems installing Leopard Server on Xserve

I have an Xserve with no monitor or keyboard access. I need to install Leopard server upgrade, I read the instructions on-line and in the booklet that comes with the software. Obviously, I cannot press C upon boot since I cant see the monitor nor can I see if I need to update my bios.
I tried enabling Remote Desktop using the kickstart command, but whenever use Chicken of the VNC to connect it says it cant find the server.
I used the "Server Assistant" and it tells me the same thing "Cant find server" but i can ping it and log into it using terminal. I can also run all the other applications like "Server Monitor", "Server Admin", and "Workgroup Manager" just fine.
The server is in another segment because it is in our server room I used one of the server room connection and still cant find server.
Can someone please help getting Leopard installed on this Xserve?
Thanks

The general answer is yes. But the conditional answer is that you must have the original installation media from the Xserve model before it started shipping Snow Leopard exclusively. This means you would need to have bought an Xserve as recently as December to have the combo OS pack as I believe Apple stopped shipping Leopard around early January (although that might be on BTO models so if you got one from the channel it may still have the original media kit). You need to be mindful of the machine's Boot ROM version. The change of one digit can cause some issues with older installation media.
If you don't have recent media kits, you "should" be able to construct a functional OS by building on other hardware and patching up to 10.5.8. Then cloning it to the new unit.
And, you've peaked my interest. What specific issue have you had with 10.6 and Xsan?
Hope this helps

Mac OS X Leopard Server - Run BootCamp on a Xserve

Hi all.
Can I install & run BootCamp (to use Windows) over a Mac OS X Leopard Server version on a Xserve?
Thanks in advance.

The Xserve's firmware doesn't appear to support Boot Camp usage.
(25920)

Intel Xserve with Leopard Server 10.5.5 won't let me in via login

A power outage appears to have created some issues with my intel Xserve, running Leopard server 10.5.5
The System identifier light was blinking, so I booted up from the Leopard disk and found out that my mirrored internal array needed to be rebuilt. No problem, 4 hours later, I repair permissions on the mirrored internal array, everything gets "repaired". Change bootup disk to the internal 10.5.5 mirrored array and reboot. System Identifier light stopped blinking, things were looking good.
The login screen comes up and when I put in the admin username and password, the screen does the shake of the wrong login.
What's weird is, on my laptop I can use Server Admin, Workgroup Manager, and the screen sharing for the server....with the admin username and password.
So, I figure, perhaps the mirror rebuild requires me to reset the admin password. So, boot back up from the Leopard Server install DVD, run the password utility. and reset the main account password.
I change the boot drive back to the internal mirror, same thing. I'm stuck. I can't get past the login screen on the actually server....or via the screen sharing...and Server Monitor appears to be stuck at 'waiting for response'. I can, again, use Server Admin and Workgroup Manager on my laptop and make changes to the X server software....but I can't log into the X serve.
My webpage, wiki, etc....are all serving fine. But, I'd like to be able to figure out what I'm doing wrong...log back in and run super duper, etc.
Help...please...

Spent all day with apple support. They said it sounded like the LADP database was corrupted. They had me try to login as root, via an opendir account, etc. No luck.
So, they suggested I do a fresh install of the Leopard server on an external drive. Did that. They then suggested I use my laptop and the workgroup manager app to log in to the xserver, export users, groups and computers....and to copy over the library/collaboration folder to the external "clean install" of Leopard server.
Did that and followed the instructions to "relink" the metadata.plist files in each group, to the GUID to the groups in workgroup manager. First issue, they weren't different GUID strings.
Well, that didn't work...kept getting file not found error. When trying to access the domain.com/groups/groupname...it should've asked for authentication. And let me into that wiki...but no, apache error page.
So, they had me create a new "test" group....added a user. Start and stopped the web...etc. This didn't create a new wiki entry (when we replaced my custom index.html to the default index where groups/wikis/blogs populate automatically at the main). And, there's no new "test" folder in the library/collaboration files.
They then said "well, it must be because you don't have reverse DNS configured right, that's why the new wikis won't set up". I've contacted dyndns.com...but I don't think that's the problem.
So, I've rebooted my xserver to the internal drive. The wiki and blog is still there, still accessible the way I like....I still can't login to the xserver.
So, I'm wondering, if anyone knows a way I can boot up my xserve in the target drive mode, hook up my laptop and replace / swap whatever admin files so that when I boot up my xserve, I can login again.
There has to be a way to hard fix a hidden file? Replace a DB? Some awesome terminal command to get me in and fix the admin account / password....
Or, does anyone know if the reverse DNS issue applecare cites is legit? Doesn't make sense how, the same public ip and domain name, that's worked for some time...suddenly doesn't???
I'm hoping someone can help me.

DNS/web-server hosted off-site. How to set up Leopard server for mail?

Hey Everyone,
Brand new xserve with leopard server 10.5.2. Currently, Our web and DNS server for our domain,"company.com" is co-located off-site with an MX record of "mail.company.com" pointed at the static IP of the office where our mail server is. I want to replace the mail server with the xserve. With that in mind, how do I configure the DNS on the xserve during initial configuration to reflect that? Give it a self-referencing FQDN like server.company.office and see if the mail service can handle the domain hosted elsewhere?
I'm pretty new to servers and would love be able to keep this all in Standard but I'm not afraid to jump into Advanced if need be. I've created a test domain through GoDaddy of "company2.com" with an MX record of "mail.company2.com" pointing at the IP address of the xserve. Any help would be greatly appreciated!

Hello,
Have a look at this blog post:
http://blogs.adobe.com/captivate/2010/08/reporting-the-quiz-results-to-a-local-server.html
Lilybiri

Unable to access gateway and DNS via VPN (L2TP) with Snow Leopard Server

Summary:
After rebooting my VPN server, i am able to establish a VPN (L2TP) connection from outside my private network. I am able to connect (ping, SSH, …) the gateway only until the first client disconnects. Then i can perfectly access all the other computers of the private network, but i cannot access the private IP address of the gateway.
Additionally, during my first VPN connection, my DNS server, which is on the same server, is not working properly with VPN. I can access it with the public IP address of my gateway. I can access it from inside my private network. A port scan indicates me that the port 53 is open, but a dig returns me a timeout.
Configuration:
Cluster of 19 Xserve3.1 - Snow Leopard Server 10.6.2
Private network 192.168.1.0/255.255.255.0 -> domain name: cluster
-> 1 controller, which act as a gateway for the cluster private network, with the following services activated:
DHCP, DNS, firewall (allowing all incoming traffic for each groups for test purposes), NAT, VPN, OpenDirectory, web, software update, AFP, NFS and Xgrid controller.
en0: fixed public IP address -> controller.example.com
en1: 192.168.1.254 -> controller.cluster
-> 18 agents with AFP and Xgrid agent activated:
en1: 192.168.1.x -> nodex.cluster with x between 1 and 18
VPN (L2TP) server distributes IP addresses between 192.168.1.201 and 192.168.1.210 (-> vpn1.cluster to vpn10.cluster). Client informations contain the private network DNS server informations (192.168.1.254, search domain: cluster).
_*Detailed problem description:*_
After rebooting the Xserve, my VPN server works fine except for the DNS. My client receives the correct informations:
Configure IPv4: Using PPP
IPv4 address: 192.168.1.201
Subnet Mask:
Router: 192.168.1.254
DNS: 192.168.1.254
Search domain: cluster
From my VPN client, i can ping all the Xserve of my cluster (192.168.1.1 to 18 and 192.168.1.254). If i have a look in Server Admin > Settings > Network, i have three interfaces listed: en0, en1 and ppp0 of family IPv4 with address 192.168.1.254 and DNS name controller.cluster.
The DNS server returns me timeouts when i try to do a dig from my VPN client even if i am able to access it directly from a computer inside or outside my private network.
After i disconnect, i can see in Server Admin that the IP address of my ppp0 interface has switch to my public IP address.
Then i can always establish a VPN (L2TP) connection, but the client receives the following informations:
Configure IPv4: Using PPP
IPv4 address: 192.168.1.202
Subnet Mask:
Router: (Public IP address of my VPN server)
DNS: 192.168.1.254
Search domain: cluster
From my VPN client, i can access all the other computers of my network (192.168.1.1 to 192.168.1.18) but when i ping my gateway (192.168.1.254), it returns me timeouts.
I have two "lazy" solutions to this problem: 1) Configure VPN and DNS servers on two differents Xserve, 2) Put the public IP address of my gateway as DNS server address, but none of these solutions are acceptable for me…
Any help is welcome!!!

I would suggest taking a look at:
server admin:vpn:settings:client information:network route definitions.
as I understand your setup it should be something like
192.168.1.0 255.255.255.0 private.
at least as a start. I just got done troubleshooting a similar issue but via two subnets:
http://discussions.apple.com/thread.jspa?threadID=2292827&tstart=0

Safari 5.1.4 update breaks SoftwareUpdate on 10.6.8 server, on 2008 xserve, IFJS_PropertyListConvertToType() called with type=3

We've got 3 new-to-us 2008 xserves that we put into service last week. Installed 10.6, updated up to 10.6.8 and took all of the software updates up until Safari 5.1.4. Computers all work fine. Then take the safari update -- afterwards, SoftwareUpdate crashes a bit after launch, gui or command line. The error when you do it on the command line is "IFJS_PropertyListConvertToType() called with type=3".
Over on the osx snow leopard server discussion board, several other people are reporting that they have the problem but only with the 2008 xserve, the 2009 xserve is just fine. (No reports yet about the 2006 xserve.)
I have reported the bug to apple, and they asked for a crash report, which I gave them. It's bug #11048593 (not sure if those are publicly viewable...)

We’re having the same issue on our 2008-era Xserve, but not on our other Snow Leopard servers and clients.
Apple released an Apple Software Installer Update 1.0 release today which may address the problem. See http://support.apple.com/kb/DL1512 Needless to say, you need to install this update manually using the downloaded DMG.
I’ll be installing this update this evening on our systems to see if this resolves our issue.

Leopard Server 10.5.4 + SMB + Windows XP Clients

Hello!
I got quite some interesting problems with my Xserv under Leopard Server 10.5.4 with Windows XP Clients.
The server runs as an open directory master and a standalone server for smb.
Shares are setup for AFP and SMB clients, ACLs are set up with read+write access for the user's group. So far everything works, users can connect from their Macs (OS X 10.3.x - 10.5.4) without problems.
My problem are the windows clients.
Connecting works fine, and apart from one permission bug (more on that later) they can access all files and do everything the macs can do.
Problem 1:
Users cannot rename files if they don't have write permission at the POSIX-level as either owner or group on the enclosing folder. ACLs do not matter at this point, if the user connects through SMB he cannot rename files or folders.
No big problem, I just put all users into one group and set this group as the POSIX-group and do a chmod -R g+w on all shares.
Inheritate this settings for SMB-connections works.
But not for AFP-connections. Every new folder a mac-client creates comes with permissions 755. So I changed UMasks on the clients to 002, and at least folders created by the finder now have the right permissions of 775.
Folders created by "new folder" on most applications load/save dialogs still come as 755 which screws up renaming for windows-clients.
Folders created when expanding a zip-file also behave this way.
The only solution I found for this was to make a cronjob that does a chmod -R g+w on the shares. Not that great.
Another "fun" feature with POSIX-permissions and SMB:
Files inside a folder. Files+Folder have an ACL set up that specifically denies deleting files+folders for a user. This users group has POSIX-permissions with write access to the enclosing folder. Window's explorer will let that user delete files and folders without any complaint about missing permissions to do so. They even disappear from the explorer-window, but are not actually deleted.
If you refresh the view, the files+folders are there again.
If the user instead has no POSIX-permission that grants him write-access, but an ACL that grants him delete, explorer happily deletes the files the user wishes to. And these files actually get deleted.
If the user has no write POSIX-permission and no ACL-permission to delete files, explorer complains about missing rights to delete files/folders.
I tried adding "acl check permissions = no" to smb.conf, but that didn't change this behaviour.
Problem 2:
Sometimes, when copying "large" files to a server share with windows explorer (from 50 MB upto 3 GB), the user immidiately gets an error message: "Cannot copy. The specified network name is no longer available."
The copied file shows up at once in the destination directory and has the correct file size, but only contains "garbage". Half a second later the same copy works and the file is actually copied successfully.
Sometimes this error shows up while a large file is copied and if you browse through other shared folders while the copy takes place.
Most often it will show up when you copy&paste with explorer.
I am stomped and have no idea where to search for a solution to this one.
I tried changing ethernet cables (premade and selfmade), the network switch, ethernet port of the Xserv ... connected a workstation directly to the Xserv - no change.
DNS works, all clients+Xserv have static IPs and the same settings for DNS-Server. Name resolution works, as does reverse resolution.
I even tried using a windows server 2003 as a WINS-Server without success for this problem.
There are no event log entries on the clients when this happens, and smbd.log on the server shows
read failure for 4 bytes to client 192.168.1.137. Error Connection reset by peer
I used wireshark to monitor what exactly happens when this shows up, but it just happens out of nowhere ... the clients just sends a TCP_RST. No unusual things before or after the TCP_RST.
I ran some tests with samba 3.0.32 and samba 3.2.x under linux 2.6.x - no such errors at all.
I tried installing Leopard Server on my Mac Pro, same behaviour.
I ran some batch-scripts that would copy large and small files in excess from/to the server from 4 different windows xp clients for a whole weekend 24 hours - not a single error. As soon as I use windows explorer to copy a file this error has a chance of showing itself.
Problem 3, more of an application bug:
Adobe InDesign CS2 (Windows again ;)) cannot export a PDF to a shared folder if the filename is longer than 8 characters. It starts exporting and after reaching 100% it just stops with the error "PDF cannot be exported." If the filename is shorter than 8 characters, all works fine. Exporting locally or to other samba servers (linux) or windows servers (2003) works fine. Copying this files to the share works, too.
Exporting any other filetype from IDCS2 (eps, inx, jpeg ...) works regardless of filename length. So does saving InDesign-files.
InDesign CS1 and CS3 do not show this, so I guess it's safe to assume this one is Adobe's problem
Did anyone experience similar problems or even better has a solution to some of these?
The real showstopper is problem #2, at least for us.
Thanks in advance and excuse my poor english skills!

I tried several new approaches, but nothing worked so far.
The update to 10.5.5 made things worse. Connections are dropping all over the place, when saving from Adobe programs in particular.
Printing from clients to a Xerox Phaser 5500 works, but choosing a different paper size than the default chosen in the cups admin interface goes all wrong and either prints on the default paper size, but down/upscaled to the chosen paper size or prints on the chosen paper size and down/upscaled as if you were printing to the default paper size. (e.g. default paper size is A4, you choose A3 with an A3 document. Document prints on A4 and is downscaled to A4, or prints on A3 and is downscaled to A4.)
There is no way I can keep this thing in production much longer. I tried reinstalling again, but that did not change any behaviour. Another nice "feature": InDesign disables "edit original" when the path to the linked file contains any directoryname with more than 8 characters in length.
Coupled with a sometimes disappearing "dirserv" (it just stops working until I reboot the whole computer) the decision stands to move away from the Xserve.
Leopard Server 10.5.x just does not seem to work well with windows clients.
We will migrate to a windows server 2003 running ExtremZ-IP for the macintosh clients this weekend. Too bad that Apple does not allow Bootcamp to work on Xserves, at least the hardware would have been useful then.
(As a nice finishing touch, the harddisk partition where all data resides did become corrupt over the weekend. "The volume Daten could not be repaired."
Disk Utility and first aid did show nothing on friday ... saturday after no work being done on the partition this error shows up. The only solution I could find was to reformat the partition and restore from a previous backup. Another weekend down the drain. Sorry for the rant, but 6 weekends in a row is enough.)

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.

Permissions on NFS Rehares in Leopard Server

Hello-
I am having a problem assigning AD groups to NFS reshares (AFP) on my Leopard Server (10.5.8). I can't assign AD groups to the ACL at all. I can add the groups but when I click on save, the groups disappear. I can assign a group to POSIX permissions and can and save it but can't access the reshare from a client over the network. If I assign wide-open permissions to POSIX (777) I can access the shares with no problem - but that is not an option in our secured environment.
All Xserves and Leopard clients are bound to AD. Xserves are OD Masters and operate in a Magic Triangle setup for MCX management. Been using AD integration for years (since Panther) with no issues. This is the first time I have tried NFS reshares. Stumped. Any ideas?

We have an EMC box and I was trying to do the same thing. I was mounting a NFS volume and trying to reshare it via AFP for my local users. I was told by both an Apple rep, EMC, and a few UNIX admins - yeah you really don't (can't) do that without a whole lot of headache. There are issues with user mapping between the OS X box (in your case AD) and the box serving up the NFS shares.
I am still trying to come up with plan B, but it is looking more and more like I will have to just do a straight Fiber LUN setup.

Leopard Server on G4 XServe?

Similar Messages

Maybe you are looking for