Step 1: Creating a Sub-Network
In order for the Print Server to have complete control over print jobs sent to the printers, the printers in question need to be isolated on the network such that they only accept traffic which comes from the Server. This way it is not possible for users to accidentally (or purposely) bypass the Print Server and send print jobs directly to the printers. Although there are numerous ways to accomplish this goal, the easiest way is to use the secondary ethernet interface in the X-Serve (en1) to create a sub-network on which the printers you wish to control will be resident. At the X-Serve:
Go to Apple->SystemPreferences->Network->Show->NetworkPortConfigurations
Select "Built-In Ethernet 2" to be active and click Apply
Select Show->Ethernet2->TCP/IP
Select Configure->Manually
Enter an IP into Address and Router (same number), and an appropriate value into Mask. The numbers you select should be from the RFC Private Network Space (http://en.wikipedia.org/wiki/Private_network), and should not conflict with any other PNS currently in use. For example, 10.1.1.1 can be used for the Address and Router, and 255.255.255.0 can be used for the mask to create a private network spanning 10.1.1.1 to 10.1.1.254 (.0 and .255 are reserved for "broadcast"). The Address and Router (a.k.a. Gateway) will be the same because the X-Serve itself will be managing this sub-network.
Step 2: Connecting Printers to the Sub-Network
Next, physically connect the printers to the secondary ethernet interface of the X-Serve. If you only want to manage one printer, you may simply run a single ethernet jumper from Ethernet2 to the proper port on the patch panel where the printer feed is terminated. If you want to manage multiple printers, you will need to run a jumper from Ethernet2 to a hub, and then run jumpers from the hub to patch panel ports where the printers terminate. CAUTION - do not create any kind of physical connection between Ethernet2 and any part of the network connected to Ethernet1, or you will create a "loop" which will bring no end of traffic trouble. You won't "blow anything up", but all kinds of wierd problems will begin to appear. If you begin to get lots of wierd trouble reports after setting this up, a loop is the first thing you should look for.
If you plan to use Static Addressing for the printers, configure each printer with the same Mask as you used on the X-Serve, and set the Gateway (router) to be the same Address you used on the X-Serve. Each Printer should have its IP Address set to be within the Subnet range, but different from the X-Serve and from each other (e.g. 10.1.1.2, 10.1.1.3, 10.1.1.4). You should not use Dynamic Addressing for this specific setup. If you want or need Dynamic Addressing for the printers, you should investigate a different method (e.g. configuring the switches to manage the traffic instead of using a subnet).
Step 2: Configuring the Printers on the Server
For Each printer, go to
Apple->SystemPreferences->Print&Fax
and add/test each printer exactly as you would on any other client. The instructions to do this properly vary from printer to printer, and you may have to download and install drivers. Ensure you can print properly to each printer from the server by sending a variety of test prints.
Step 3: Sharing the Printers with the Print Server
In Server Admin, select Print services and navigate to the Settings->Queus tab. Click the "+" sign to add a printer to the Print services. For each printer, give it a "Sharing Name" which is the name which the server will broadcast to users, and then select the Protocols which can be used by users to find and add the printer. You may need to click the "pencil" icon to edit the printer after using the "+" sign to add it.
IPP (Internet Printing Protocol) will allow ALL users, regardless of platform, to print to the printer if they know the printer's IP Address or FQDN (the same as the server). This works fine if the X-Serve is managing a single printer, but can be problematic if managing multiple printers.
AppleTalk should only be used of you still have clients using Mac OS9
LPR + Bonjour will allow all Mac OSX users to find the Printers by using the "Default Browser" to scan the network when adding a printer.
SMB will allow Windows users to print to the Printers
Step 4: Starting the Print Server and Testing
Once you have added and edited the Printers, switch to the "Logs" section and click "Start Service" at the top. Examine the log output and note any errors. If, for example, you see an AppleTalk error, you don't have to worry about it if you're not planning on using AppleTalk as a user protocol, but if you see a SMB error and plan on having Windows machines print to the printers you'll need to investigate.
Once Print Services is running, set up and test at least one client computer for each protocol with which you expect users to print. Assuming all test go well, you may now publish the procedure to users so they may set up their machines to connect and print to the printers.
In order for the Print Server to have complete control over print jobs sent to the printers, the printers in question need to be isolated on the network such that they only accept traffic which comes from the Server. This way it is not possible for users to accidentally (or purposely) bypass the Print Server and send print jobs directly to the printers. Although there are numerous ways to accomplish this goal, the easiest way is to use the secondary ethernet interface in the X-Serve (en1) to create a sub-network on which the printers you wish to control will be resident. At the X-Serve:
Go to Apple->SystemPreferences->Network->Show->NetworkPortConfigurations
Select "Built-In Ethernet 2" to be active and click Apply
Select Show->Ethernet2->TCP/IP
Select Configure->Manually
Enter an IP into Address and Router (same number), and an appropriate value into Mask. The numbers you select should be from the RFC Private Network Space (http://en.wikipedia.org/wiki/Private_network), and should not conflict with any other PNS currently in use. For example, 10.1.1.1 can be used for the Address and Router, and 255.255.255.0 can be used for the mask to create a private network spanning 10.1.1.1 to 10.1.1.254 (.0 and .255 are reserved for "broadcast"). The Address and Router (a.k.a. Gateway) will be the same because the X-Serve itself will be managing this sub-network.
Step 2: Connecting Printers to the Sub-Network
Next, physically connect the printers to the secondary ethernet interface of the X-Serve. If you only want to manage one printer, you may simply run a single ethernet jumper from Ethernet2 to the proper port on the patch panel where the printer feed is terminated. If you want to manage multiple printers, you will need to run a jumper from Ethernet2 to a hub, and then run jumpers from the hub to patch panel ports where the printers terminate. CAUTION - do not create any kind of physical connection between Ethernet2 and any part of the network connected to Ethernet1, or you will create a "loop" which will bring no end of traffic trouble. You won't "blow anything up", but all kinds of wierd problems will begin to appear. If you begin to get lots of wierd trouble reports after setting this up, a loop is the first thing you should look for.
If you plan to use Static Addressing for the printers, configure each printer with the same Mask as you used on the X-Serve, and set the Gateway (router) to be the same Address you used on the X-Serve. Each Printer should have its IP Address set to be within the Subnet range, but different from the X-Serve and from each other (e.g. 10.1.1.2, 10.1.1.3, 10.1.1.4). You should not use Dynamic Addressing for this specific setup. If you want or need Dynamic Addressing for the printers, you should investigate a different method (e.g. configuring the switches to manage the traffic instead of using a subnet).
Step 2: Configuring the Printers on the Server
For Each printer, go to
Apple->SystemPreferences->Print&Fax
and add/test each printer exactly as you would on any other client. The instructions to do this properly vary from printer to printer, and you may have to download and install drivers. Ensure you can print properly to each printer from the server by sending a variety of test prints.
Step 3: Sharing the Printers with the Print Server
In Server Admin, select Print services and navigate to the Settings->Queus tab. Click the "+" sign to add a printer to the Print services. For each printer, give it a "Sharing Name" which is the name which the server will broadcast to users, and then select the Protocols which can be used by users to find and add the printer. You may need to click the "pencil" icon to edit the printer after using the "+" sign to add it.
IPP (Internet Printing Protocol) will allow ALL users, regardless of platform, to print to the printer if they know the printer's IP Address or FQDN (the same as the server). This works fine if the X-Serve is managing a single printer, but can be problematic if managing multiple printers.
AppleTalk should only be used of you still have clients using Mac OS9
LPR + Bonjour will allow all Mac OSX users to find the Printers by using the "Default Browser" to scan the network when adding a printer.
SMB will allow Windows users to print to the Printers
Step 4: Starting the Print Server and Testing
Once you have added and edited the Printers, switch to the "Logs" section and click "Start Service" at the top. Examine the log output and note any errors. If, for example, you see an AppleTalk error, you don't have to worry about it if you're not planning on using AppleTalk as a user protocol, but if you see a SMB error and plan on having Windows machines print to the printers you'll need to investigate.
Once Print Services is running, set up and test at least one client computer for each protocol with which you expect users to print. Assuming all test go well, you may now publish the procedure to users so they may set up their machines to connect and print to the printers.