Known Issues
Enabling NetInfo Access by Clients
When a Mac OS X Server computer is configured as a NetInfo server, clients cannot automatically get their network configuration information from the Mac OS X Server server. Once you have created a NetInfo server using the NetInfoManager application, there are a couple steps that you must take before client computers can access information on the server.
Note: When you configue the NetInfo server, make sure that you have the correct settings for the Hostname, Internet Address, Netmask and Router fields as appropriate for your network. After you have made all these configurations, restart the computer.
In order for a client to be part of a NetInfo network, you must do the following:
2. Statically configure the client machine's networking information.
In order for a client to boot properly on the network, you must statically enter its network configuration. To do this, launch /System/Library/Preferences/Network.preference on the client machine. Set the Connect via pop-up menu to Ethernet, and TCP/IP Configure pop-up menu to Manually. Enter values for the IP address, Hostname, Subnet mask, and Router address fields (this information should be available from your System Administrator or Internet Service Provider). Once you've entered this information, click Apply. If you are not logged in as root, you will be prompted for the root password. Enter the root password and click the Authenticate button. You must now restart the client computer for the new networking settings to take effect.
The Mac OS X Server AppleTalk API is expected to change in the near future. For this reason, the header files for that API have not been included in this release. Developers who are working with a preliminary version of this API should contact ADR for support until an official API is released. In addition, developers should be aware of a potentially serious problem that is still being investigated at Apple.
The problem is that use of the SPWrite and SPWrtContinue functions can result in a system hang. When this happens, you must restart the system. Although these functions are not normally used, they are typically employed in an Apple File Protocol (AFP) server using AFP on top of ASP/ATP.
We currently have no workaround for this situation. An alternative is to use AFP over TCP/IP, which is not affected by this bug. When a solution has been found, we will notify developers through the usual channels, and will post a new version of the Mac OS X Server kernel.