Xerox 750DP 5750 Administrator Guide - Page 93

Adding the DocuColor to the TCP/IP network

Page 93 highlights

33-21 Configuring a Windows NT server to support the DocuColor Adding the DocuColor to the TCP/IP network If your TCP/IP network consists of Windows NT servers and Windows NT clients, use the directions in this section. If the network also includes UNIX workstations, also check the directions on page 3-31. TO ADD THE DOCUCOLOR TO A TCP/IP NETWORK WITH A WINDOWS NT SERVER: 1. On the DocuColor Control Panel, perform Server Setup, Network Setup and Printer Setup to support TCP/IP printing. Enter the options in Protocol Setup (IP address of the DocuColor, Subnet mask, and Gateway address). In Printer Setup, publish the Print queue. 2. Register the IP address of the DocuColor in the host name database used by your system. For installations that don't have a network administrator or a central host name database, add the DocuColor to the hosts file on the Windows NT server. Also add it to the hosts file on any workstations that have TCP/IP loaded and will use the remote utilities. Adding a DocuColor entry to the Windows NT hosts file The hosts file maps remote devices to IP addresses. Host names are used in TCP/IP environments to locate IP addresses. Users can then communicate with any device over TCP/IP by using the host name rather than having to remember its IP address. A generic hosts file is added to the Windows directory when you install TCP/IP support. NOTE: If there is no system-wide host name database, use the following procedure to create a local hosts file. If there is a system-wide host database, skip the following procedure.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130

3
3-21
Configuring a Windows NT server to support the DocuColor
Adding the DocuColor to the TCP/IP network
If your TCP/IP network consists of Windows NT servers and Windows NT clients,
use the directions in this section. If the network also includes UNIX workstations, also
check the directions on page 3-31.
T
O
ADD
THE
D
OCU
C
OLOR
TO
A
TCP/IP
NETWORK
WITH
A
W
INDOWS
NT
SERVER
:
1.
On the DocuColor Control Panel, perform Server Setup, Network Setup and Printer
Setup to support TCP/IP printing.
Enter the options in Protocol Setup (IP address of the DocuColor, Subnet mask, and
Gateway address). In Printer Setup, publish the Print queue.
2.
Register the IP address of the DocuColor in the host name database used by your sys-
tem.
For installations that don’t have a network administrator or a central host name
database, add the DocuColor to the
hosts
file on the Windows NT server. Also add it
to the
hosts
file on any workstations that have TCP/IP loaded and will use the remote
utilities.
Adding a DocuColor entry to the Windows NT hosts file
The
hosts
file maps remote devices to IP addresses. Host names are used in TCP/IP
environments to locate IP addresses. Users can then communicate with any device over
TCP/IP by using the host name rather than having to remember its IP address.
A generic
hosts
file is added to the Windows directory when you install TCP/IP
support.
N
OTE
:
If there is no system-wide host name database, use the following procedure to
create a local
hosts
file. If there is a system-wide host database, skip the following
procedure.