Chapter | 5 | Configuring The Internal Ethernet Adapter For Novell | ||
|
|
|
|
|
|
|
| Table 12. RPRINTER Setup | |
|
|
| ||
|
|
|
|
|
Step |
|
| Action | Result of Action |
|
|
| ||
|
|
| ||
25. | Enter the line: set rprinter add | One entry is written in the file. One | ||
| pservername printernumber | entry is required for each RPRINTER | ||
| destname where pservername | serviced by the Internal Ethernet | ||
| equals the existing PSERVER’s name, | Adapter. | ||
| printernumber equals the defined |
| ||
| number for this printer in that |
| ||
| PSERVER, and destname equals an |
| ||
| Internal Ethernet Adapter destination |
| ||
| (e.g. d1prn d2prn, etc.). |
| ||
|
|
| ||
26. | Reboot the Internal Ethernet Adapter to | The Internal Ethernet Adapter will boot | ||
| enable these changes. | up and read this entry from the | ||
|
|
|
| CONFIG file and set itself to act as an |
|
|
|
| RPRINTER. |
|
|
|
|
|
NetWare 4 Options
NetWare 4 introduces NDS and some new frame types. The Internal Ethernet Adapter can be used in a NetWare 4 environment with either of these options:
•Set the Internal Ethernet Adapter up as a PSERVER
•Set the Internal Ethernet Adapter up as a RPRINTER interacting with an existing PSERVER.
NOTE: If following a PSERVER setup, bindery emulation is required.
Included in this
To configure the unit as a PSERVER in a NetWare 4 environment, follow the procedure outlined in Table 13.
180