Xerox 7300DN User Guide - Page 96

Discover Problems, Discover Error message is returned immediately and no, printers are discovered,

Get Xerox 7300DN - Phaser Color Laser Printer PDF manuals and user guides View all Xerox 7300DN manuals
Add to My Manuals
Save this manual to your list of manuals

Page 96 highlights

Discover Problems If the printer is on an IP network Discover Error message is returned immediately and no printers are discovered This normally occurs if the Discover process does not initialize properly, possibly due to an invalid setting on a Discover configuration option. A pop-up window containing a discover error message is displayed. Check the log file, [Drive]:\[Install Directory]\discover.log. If the cause of the error is not apparent, increase the debug level for the discover process and re-run Discover. Most likely one of the following caused the problem: • Invalid discover parameter or missing initialization file, pmap.ini • No discover type specified in discover configuration • Incorrect router address or local IP submask • IPX Discover specified but local machine is not configured for IPX (NetW are client). Incomplete Discover If any printers are not discovered, check the following: Refer to [Drive]:\[Install Directory]\pmap.log and increase the level of debug for the discover process if necessary. When discover is re-attempted, the log file [Drive]:\[Install Directory] \discover.log contains more information. If a particular printer is not discovered, try the following: 1. Verify that a response is received from a ping. 2. Try manually adding through the Topology > Add Printer menu item. 3. If the router Discover configuration option is in use (local or secondary), check contents of the arp cache via a MIB browser. 4. If the printer is not listed as a MIB object value, Telnet to the router and issue a broadcast ping to update the router cache. 5. Ensure the correct Community String discover configuration option is set. ("Public" is used by default). 6. Increase the SNMP time-out values (snmp_get_local_time-out and snmp_get_remote_time-out) in the pmap.ini file. If the printer is on an IPX network 1. Ensure IPX discover configuration option is selected and that the IPX server name is correct. 2. See if it can it be manually added through the Topology > Add Printer menu item. 3. Ensure the correct Community String discover configuration option is set. ("Public" is used by default). 4. Increase the SNMP time-out values (snmp_get_local_timeout and snmp_get_remote_timeout) in the pmap.ini file. PrinterMap User Guide 80

  • 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
PrinterMap User Guide
80
Discover Problems
Discover Error message is returned immediately and no
printers are discovered
This normally occurs if the Discover process does not initialize properly, possibly
due to an invalid setting on a Discover configuration option. A pop-up window
containing a discover error message is displayed. Check the log file,
[Drive]:\[Install Directory]\discover.log.
If the cause of the error is not
apparent, increase the debug level for the discover process and re-run Discover.
Most likely one of the following caused the problem:
•
Invalid discover parameter or missing initialization file, pmap.ini
•
No discover type specified in discover configuration
•
Incorrect router address or local IP submask
•
IPX Discover specified but local machine is not configured for IPX (NetW
are client).
Incomplete Discover
If any printers are not discovered, check the following:
Refer to
[Drive]:\[Install Directory]\pmap.log
and increase the level of debug for
the discover process if necessary. When discover is re-attempted, the log file
[Drive]:\[Install Directory] \discover.log
contains more information. If a
particular printer is not discovered, try the following:
1.
Verify that a response is received from a ping.
2.
Try manually adding through the Topology > Add Printer menu item.
3. If the router Discover configuration option is in use (local or secondary),
check contents of the arp cache via a MIB browser.
4.
If the printer is not listed as a MIB object value, Telnet to the router and issue
a broadcast ping to update the router cache.
5. Ensure the correct Community String discover configuration option is set.
("Public" is used by default).
6. Increase
the
SNMP
time-out
values
(snmp_get_local_time-out
and
snmp_get_remote_time-out) in the pmap.ini file.
1.
Ensure IPX discover configuration option is selected and that the IPX server
name is correct.
2.
See if it can it be manually added through the Topology > Add Printer menu
item.
3. Ensure the correct Community String discover configuration option is set.
("Public" is used by default).
4. Increase
the
SNMP
time-out
values
(snmp_get_local_timeout
and
snmp_get_remote_timeout) in the pmap.ini file.
If the printer is
on an IP
network
If the printer is
on an IPX
network