[-mcg-]

justyn-

If the subnet mask you typed in your original post is in fact configured on your network as 255.255.0.0 (not 255.255.255.0), then in effect you have created one large LAN of 65535 addresses (a supernet, as opposed to a subnet). Essentially all address in the range of 192.168.0.1 – 192.168.255.254 are valid on each of your ‘subnets’. When you connect the two subnets together with a hub, you are creating one giant broadcast domain that overlaps which can lead to all kinds of odd problems and performance issues.

Not knowing how your network is designed, I can only offer a few ideas based on the info you’ve given thus far. Please take these options with a grain of salt as I might be barking up the wrong tree based on some assumptions I’m making…

Suggestions:
A — Fix the ‘supernet’ issue
– remove the hub
– give each subnet a mask of 255.255.255.0 thus cutting your LANs down to a more reasonable 254 usable addresses, i.e. 192.168.167.1 – 254 & 192.168.168.1 – 254
– now you’ve truly created two subnets…the problem is now you’ll need to route between the subnets for any communication to take place

B — Fix the routing issue
Options:
a) buy a cheap router (a multiport dsl/cable router would work) and configure it to pass traffic between subnets, then plug the two subnets in and try pinging to verify…you might be able to use your Airport Extreme for this by fixing the IP of the ethernet interface to one subnet while providing wireless connectivity to the other subnet…not sure though as I’ve never used an Airport station. The router will isolate DHCP requests to the subnet the requesting machine is physically/wirelessly connected to, so it should allow you to run a DHCP server per subnet as you currently do. Printing to the next subnet should be simple if the router IP for the respective subnet is used as the default gateway…if you already have a different default gateway, then you may need to fiddle with adding static routes. IIRC the Airport Extreme can provide DHCP services, so you might be able to offload this from the XServe if you so choose.

b) pick one of the XServes and dual-home the network connections, i.e. connect one ethernet port to each subnet and IP the interfaces accordingly. Enable DHCP on this server and create two scopes, one for each subnet. Disable DHCP on the other server. This should provide for DHCP addresses to be served on the respective subnets. Configure print queues on the dual-homed XServe to be used as a print server for the common printers.

C — Ignore everything I’ve written and leave your network alone. Go to each DHCP server and create address ‘reservations’ for every device that will pull a dhcp address. In essence you will be tying an IP address to the MAC address (hardware address) of the network port on each client. This way your client systems will always pull the same IP from DHCP. You just have to remember to do this every time a new computer gets added to the network.

Hopefully that’s somewhat coherent…it’s a tad late as I’m writing this up!

[-mcg-]

Taking this concept one step further…

How would one go about moving the software updates from from an Internet accessible server running Apple’s SUS to a [i]non[/i]-Internet accessible server in an attempt to host a mirror of the Apple SUS updates. Think unclassified to classified networks here.

Is it as simple as copying the /usr/share/swupd/ directory over, or is there more to it, i.e. copying receipts, etc.?

I posted this once before ([url]https://www.afp548.com/forum/viewtopic.php?forum=18&showtopic=14512[/url]), but had to responses, so I figured I’d try again since I hadn’t gotten around to experimenting with it myself yet.

Any inputs would be appreciated…thanks

-mcg-

[-mcg-]

Here’s what I find useful (and free!):
Netrestore — for imaging & restoring OSX — sucessor to CCC
Cyberduck — FTP/SFTP application
TNEF’s Enough — for stubborn email attachments from PC’s
MS Remote Desktop Connection — to access Windoze systems from OSX
Subnet Calculator — for network folks
TftpServer — more network tools
X11 — in case you didn’t install it with OSX
GIMP — for graphics work on a budget — needs X11
LoginWindow Manager — for adding legaleese to Login Window — not really for end users though
TextWrangler — from the makers of BBEdit
Citrix ICA Client — only applies if you have a PC server running Citrix
OSX Server Admin Tools — only if you have need to monitor/modify the server from one of the client machines
Adium — chat program with broader support — only if they need it, otherwise a distraction and wastes bandwidth
VLC — Video LAN Client media player
Classic — run from a .dmg so people can’t boot from it to bypass OSX security

…enough for now!

-mcg-

[-mcg-]

I just had this happen a few moments ago. In my case, I had logged in to a new admin account that had no network home directory specified in WGM when I initially created it. Looks like it just contains the Desktop and Library directories…

[-mcg-]

I too have the original XServe RAID, so I’ll answer what I can…

1) Yep, you can expand an array. Using the RAID Admin app there is a wizard to walk you through the steps necessary…under the ‘settings’ menu item IIRC.
2) I haven’t tried it, but I don’t see why not. Let us know if it works.
3) I believe that all drives are supposed to be the same size, although it would likely work if you included a larger drive size…you’d likely lose the excess capacity on that drive though, i.e. if you added the 250GB drive to the array of 180GB drives I believe that only 180GB of it would be accessible. I admit that I haven’t tried this on the XServe RAID box, but this is how our other SCSI RAID chassis work.

Make sure you have a current backup of all your XRAID data before trying this…it’s a Murphy’s Law thing, if you have a current backup, you’ll likely never need it…if you don’t, it’s almost gauranteed that something will go wrong!

I hope that helps somewhat…

[-mcg-]

…had this prob with a gen 1 xserve as well. my solution was to disconnect the sensor from the mobo…just follow the wires from the sensor and slide the socket off the pins. no ill side effects to speak of…

[-mcg-]

I’m also trying to track down this info in order to configure our Win2003 DHCP servers to provide the LDAP server address (my OD Master XServe) to each of the OSX clients. In theory this should allow for automatic search policies to be pushed down from the server.

In Apples’ OD Administration guide they make reference to configuring DHCP option 95 for an LDAP server address on non-OSXS DHCP servers (page 37, paragraph 3)…except that Windows DHCP servers don’t list an option 95. A trip through Microsoft’s Technet site yielded several documents about configuring DHCP options, but they were all the pre-defined ones…nothing that I came across regarding defining new options.

Have any of you folks sucessfully done this? If so, how painful is it…and any chance on a quick tutorial? Thanks for any insights you can provide…

Misc. Info:
DHCP Servers: Windows 2003 Server
OD Master: OSXS 10.4.2
Mac Clients: OSX 10.3.9 & 10.4.2

in reply to: OS X Server 10.4 Tiger on PowerBook G4 17" #362287

[-mcg-]

OSXS 10.4 installed fine on my PB G4 1.5 15″. I made a seperate 8GB partition to hold it…haven’t tried burning a CD/DVD from OSXS yet though.

[Author]

Posts