Represents NetWare print servers.
Class Flags |
Setting |
---|---|
Container |
Off |
Effective |
On |
Nonremovable |
On |
Ambiguous Naming |
Off |
Ambiguous Container |
Off |
Auxiliary Class |
Off |
Rule |
Class/Attribute |
Defined For |
---|---|---|
Super Classes |
Print Server |
|
Containment |
||
Named By |
Print Server |
Inherited from Top |
Inherited from Server |
---|---|---|
(None) |
Inherited from Top |
|
---|---|
Inherited from Server |
|
---|---|
For help in understanding the class definition template, see Reading Class Definitions.
The Print Server class differs from the NCP Server class in that print servers use the SPX protocol for communications rather than NCP.
The Print Server class is used for both bindery-based and eDirectory-based print servers. Bindery-based print servers do not have the Public Key or Private Key attributes. The Private Key and Public Key attributes are present if the server is a client of eDirectory Authentication Services.
The Version attribute (inherited from Server) indicates whether the server is bindery-based or eDirectory-based.
The Operator and User attributes are used by the print server as access control lists. (The User attribute is inherited from Server.) The Operator attribute identifies those individuals who are authorized to act as print server operators. The User attribute identifies individuals authorized to use the print server.
The Host Device attribute identifies the device that hosts the server. This is usually a computer, but it might be some other device. For example, a printer could host a built-in print server.
The Resource attribute contains a list of resources managed by this service.
The User attribute contains a list of objects that are authorized to use this server. The server must determine if the user list is to be maintained by an administrator, or if the list is automatically generated by the server. If the user list is used by the server as an access control list, the administrator will usually maintain the list. If the user list is purely informational, reflecting access control information stored elsewhere, the server usually maintains the list.
For LDAP clients to access this class, the LDAP server must map this class to a name that contains no spaces or colons.