3.

Troubleshooting

Error Codes
If an error code occurs, retry the communication. If the same problem occurs, try to fix the problem as
suggested below. Note that some error codes appear only in the error code display and on the service
report.

Code Meaning Suggested Cause/Action 3

• Check the line connection.
• Check the NCU - FCU connectors.
DIS/NSF not detected within • The machine at the other end may be incompatible.
0-00
40 s of Start being pressed • Replace the NCU or FCU.
• Check for DIS/NSF with an oscilloscope.
• If the rx signal is weak, there may be a bad line.

• The other party is out of paper or has a jammed printer.

0-01 DCN received unexpectedly
• The other party pressed Stop during communication.

Incompatible modem at the

0-03 • The other terminal is incompatible.
other end

• Check the line connection.

• Check the NCU - FCU connectors.
• Try changing the tx level and/or cable equalizer
settings.
• Replace the FCU or NCU.
• The other terminal may be faulty; try sending to another
CFR or FTT not received after machine.
0-04
modem training
• If the rx signal is weak or defective, there may be a
bad line.
Cross reference
• Tx level - NCU Parameter 01 (PSTN)
• Cable equalizer - G3 Switch 07 (PSTN)
• Dedicated Tx parameters - Section 4

Unsuccessful after modem • Check the line connection.

0-05
training at 2400 bps • Check the NCU - FCU connectors.

23
 3. Troubleshooting

Code Meaning Suggested Cause/Action

• Try adjusting the tx level and/or cable equalizer.
• Replace the FCU or NCU.
• Check for line problems.
Cross reference
• See error code 0-04.

• Check the line connection.

3 • Check the FCU - NCU connectors.
• Try adjusting the tx level and/or cable equalizer
settings.
The other terminal did not • Replace the NCU or FCU.
0-06
reply to DCS • The other end may be defective or incompatible; try
sending to another machine.
• Check for line problems.
Cross reference
• See error code 0-04.

• Check the line connection.

• Check the FCU - NCU connectors.
• Replace the NCU or FCU.
No post-message response
• The other end may have jammed or run out of paper.
0-07 from the other end after a
page was sent • The other end user may have disconnected the call.
• Check for a bad line.
• The other end may be defective; try sending to another
machine.

• Check the line connection.

• Check the FCU - NCU connectors.
• Replace the NCU or FCU.
The other end sent RTN or PIN
after receiving a page, • The other end may have jammed, or run out of paper
0-08 or memory space.
because there were too many
errors • Try adjusting the tx level and/or cable equalizer
settings.
• The other end may have a defective modem/NCU/
FCU; try sending to another machine.

24
 Error Codes

Code Meaning Suggested Cause/Action

• Check for line problems and noise.
Cross reference
• Tx level - NCU Parameter 01 (PSTN)
• Cable equalizer - G3 Switch 07 (PSTN)
• Dedicated Tx parameters - Section 4

• Check the FCU - NCU connectors.

• Incompatible or defective remote terminal; try sending 3
to another machine.
• Noisy line: resend.
Non-standard post message
0-14 • Try adjusting the tx level and/or cable equalizer
response code received
settings.
• Replace the NCU or FCU.
Cross reference
• See error code 0-08.

• The other terminal is not capable of accepting the

following functions, or the other terminal’s memory is
full.
The other terminal is not
0-15 • Confidential rx
capable of specific functions.
• Transfer function
• SEP/SUB/PWD/SID

• Check the line connection.

• Check the FCU - NCU connectors.
• Replace the NCU or FCU.
• Try adjusting the tx level and/or cable equalizer
CFR or FTT not detected after settings.
0-16 modem training in • The other end may have disconnected, or it may be
confidential or transfer mode defective; try calling another machine.
• If the rx signal level is too low, there may be a line
problem.
Cross reference
• See error code 0-08.

25
 3. Troubleshooting

Code Meaning Suggested Cause/Action

• Check the line connection.

• Check the FCU - NCU connectors.
• Replace the NCU or FCU.
• Check for line problems.
Facsimile data not received • Try calling another fax machine.
0-20
within 6 s of retraining • Try adjusting the reconstruction time for the first line
3 and/or rx cable equalizer setting.
Cross reference
• Reconstruction time - G3 Switch 0A, bit 6
• Rx cable equalizer - G3 Switch 07 (PSTN)

• Check the connections between the FCU, NCU, & line.

• Check for line noise or other line problems.
EOL signal (end-of-line) from • Replace the NCU or FCU.
the other end not received • The remote machine may be defective or may have
0-21
within 5 s of the previous EOL disconnected.
signal
Cross reference
• Maximum interval between EOLs and between ECM
frames - G3 Bit Switch 0A, bit 4

• Check the line connection.

• Check the FCU - NCU connectors.
• Replace the NCU or FCU.
The signal from the other end
was interrupted for more than • Defective remote terminal.
0-22 the acceptable modem • Check for line noise or other line problems.
carrier drop time (default:
• Try adjusting the acceptable modem carrier drop time.
200 ms)
Cross reference
• Acceptable modem carrier drop time - G3 Switch 0A,
bits 0 and 1

• Check the line connection.

• Check the FCU - NCU connectors.
Too many errors during
0-23 • Replace the NCU or FCU.
reception
• Defective remote terminal.
• Check for line noise or other line problems.

26
 Error Codes

Code Meaning Suggested Cause/Action

• Try asking the other end to adjust their tx level.
• Try adjusting the rx cable equalizer setting and/or rx
error criteria.
Cross reference
• Rx cable equalizer - G3 Switch 07 (PSTN)
• Rx error criteria - Communication Switch 02, bits 0 and
1
3
• Check the line connection.
• Check the FCU - NCU connectors.
The other terminal did not • Try adjusting the tx level and/or cable equalizer
0-30 reply to NSS(A) in AI short settings.
protocol mode • The other terminal may not be compatible.
Cross reference
• Dedicated tx parameters - Section 4

The other terminal sent a

DCS, which contained • Check the protocol dump list.
0-32
functions that the receiving • Ask the other party to contact the manufacturer.
machine cannot handle.

Polarity changed during • Check the line connection.

0-52
communication • Retry the communication.

FCE does not detect the SG3- • FCU firmware or board defective.
0-55
V34. • SG3-V34 firmware or board defective.

The stored message data

0-56 exceeds the capacity of the • SG3-V34 firmware or board defective.
mailbox in the SG3-V34.

The communication mode • The other terminal did not have a compatible
specified in CM/JM was not communication mode (e.g., the other terminal was a
0-70 available V.34 data modem and not a fax modem.)
(V.8 calling and called • A polling tx file was not ready at the other terminal
terminal) when polling rx was initiated from the calling terminal.

• The calling terminal could not detect ANSam due to

The calling terminal fell back noise, etc.
0-74
to T.30 mode, because it
• ANSam was too short to detect.

27
 3. Troubleshooting

Code Meaning Suggested Cause/Action

could not detect ANSam after • Check the line connection and condition.
sending CI. • Try making a call to another V.8/V.34 fax.

The called terminal fell back

to T.30 mode, because it • The terminal could not detect ANSam.
0-75 could not detect a CM in • Check the line connection and condition.
response to ANSam (ANSam • Try receiving a call from another V.8/V.34 fax.
timeout).
3
The calling terminal fell back • The called terminal could not detect a CM due to noise,
to T.30 mode, because it etc.
0-76 could not detect a JM in
response to a CM • Check the line connection and condition.

(CM timeout). • Try making a call to another V.8/V.34 fax.

• The calling terminal could not detect a JM due to noise,

The called terminal fell back etc.
to T.30 mode, because it
• A network that has narrow bandwidth cannot pass JM
0-77 could not detect a CJ in
to the other end.
response to JM
• Check the line connection and condition.
(JM timeout).
• Try receiving a call from another V.8/V.34 fax.

The called terminal detected • Check for line noise or other line problems.
0-79 CI while waiting for a V.21 • If this error occurs, the called terminal falls back to T.
signal. 30 mode.

The line was disconnected The guard timer expired while starting these phases. Serious
0-80 due to a timeout in V.34 noise, narrow bandwidth, or low signal level can cause
phase 2 – line probing. these errors.
If these errors happen at the transmitting terminal:
The line was disconnected
0-81 due to a timeout in V.34 • Try making a call at a later time.
phase 3 – equalizer training. • Try using V.17 or a slower modem using dedicated tx
parameters.
The line was disconnected
due to a timeout in the V.34 • Try increasing the tx level.
0-82
phase 4 – control channel • Try adjusting the tx cable equalizer setting.
start-up.
If these errors happen at the receiving terminal:
The line was disconnected • Try adjusting the rx cable equalizer setting.
0-83
due to a timeout in the V.34 • Try increasing the tx level.

28
 Error Codes

Code Meaning Suggested Cause/Action

control channel restart • Try using V.17 or a slower modem if the same error is
sequence. frequent when receiving from multiple senders.

The line was disconnected • The signal did not stop within 10 s.
due to abnormal signaling in
0-84 • Turn off the machine, then turn it back on.
V.34 phase 4 – control
channel start-up. • If the same error is frequent, replace the FCU.

The line was disconnected • The signal did not stop within 10 s.
3
0-85 due to abnormal signaling in • Turn off the machine, then turn it back on.
V.34 control channel restart. • If the same error is frequent, replace the FCU.

The line was disconnected

because the other terminal
requested a data rate using • The other terminal was incompatible.
0-86
MPh that was not available in • Ask the other party to contact the manufacturer.
the currently selected symbol
rate.

• The receiving terminal restarted the control channel

The control channel started because data reception in the primary channel was
0-87 after an unsuccessful primary not successful.
channel.
• This does not result in an error communication.

The line was disconnected

because PPR was • Try using a lower data rate at the start.
0-88 transmitted/received 9
(default) times within the same • Try adjusting the cable equalizer setting.
ECM frame.

Only one V.21 connection

2-11 • Replace the FCU.
flag was received

2-12 Modem clock irregularity • Replace the FCU.

• Turn off the machine, then turn it back on.

2-13 Modem initialization error • Update the modem ROM.
• Replace the FCU.

JBIG compression or • Turn off the machine, then turn it back on.
2-23
reconstruction error • Replace the EXFUNC board if the error is frequent.

29
 3. Troubleshooting

Code Meaning Suggested Cause/Action

• Turn off the machine, then turn it back on.

2-24 JBIG ASIC error
• Replace the EXFUNC board if the error is frequent.

JBIG data reconstruction

2-25
error (BIH error)

JBIG data reconstruction

2-26 • JBIG data error
error (Float marker error)
3 • Check the sender’s JBIG function.
JBIG data reconstruction
2-27 • Update the MBU ROM.
error (End marker error)

JBIG data reconstruction

2-28
error (Timeout)

JBIG trailing edge maker • FCU defective

2-29
error • Check the destination device.

The machine resets itself for a

2-50 • If this is frequent, update the ROM, or replace the FCU.
fatal FCU system error

The machine resets itself

2-51 because of a fatal • If this is frequent, update the ROM, or replace the FCU.
communication error

Snd msg() in the manual task

is an error because the • The user did the same operation many times, and this
2-53
mailbox for the operation task gave too much load to the machine.
is full.

• Check the line connector.

• Check the connection between FCU and NCU.
4-01 Line current was cut
• Check for line problems.
• Replace the FCU or the NCU.

Communication failed
because of an ID Code • Get the ID Codes the same and/or the CSIs
mismatch (Closed Network) programmed correctly, then resend.
4-10
or Tel. No./CSI mismatch
(Protection against Wrong • The machine at the other end may be defective.
Connections)

5-10 DCR timer expired • Replace the FCU.

30
 Error Codes

Code Meaning Suggested Cause/Action

Storage impossible because • Temporary memory shortage.

5-20
of a lack of memory • Test the SAF memory.
5-21 Memory overflow • Replace the FCU or optional EXMEM board

Print data error when printing • Test the SAF memory.

5-23 a substitute rx or confidential • Ask the other end to resend the message.
rx message • Replace the FCU or optional EXMEM board.
3
5-25 SAF file access error • Replace the FCU or EXMEM board.

G3 ECM - T1 time out during

6-00
reception of facsimile data
• Try adjusting the rx cable equalizer.
G3 ECM - no V.21 signal was
6-01 • Replace the FCU or NCU.
received

6-02 G3 ECM - EOR was received

• Check the line connection.

• Check connections from the NCU to the FCU.
6-04 G3 ECM - RTC not detected
• Check for a bad line or defective remote terminal.
• Replace the FCU or NCU.

• Check the line connection.

• Check connections from the NCU to the FCU.
G3 ECM - facsimile data • Check for a bad line or defective remote terminal.
frame not received within 18
6-05 • Replace the FCU or NCU.
s of CFR, but there was no line
fail • Try adjusting the rx cable equalizer
Cross reference
• Rx cable equalizer - G3 Switch 07 (PSTN)

G3 ECM - coding/decoding • Defective FCU.

6-06
error • The other terminal may be defective.

G3 ECM - PIP/PIN received • The other end pressed Stop during communication.
6-08
in reply to PPS.NULL • The other terminal may be defective.

• Check for a noisy line.

6-09 G3 ECM - ERR received
• Adjust the tx levels of the communicating machines.

31
 3. Troubleshooting

Code Meaning Suggested Cause/Action

• See code 6-05.

• Check for line noise.

G3 ECM - error frames still • Adjust the tx level (use NCU parameter 01 or the
received at the other end after dedicated tx parameter for that address).
6-10
all communication attempts at
2400 bps • Check the line connection.
• Defective remote terminal.
3 V.21 flag detected during
6-21 high speed modem • The other terminal may be defective or incompatible.
communication

The machine resets the • Check for line noise.

sequence because of an
6-22 • If the same error occurs frequently, replace the FCU.
abnormal handshake in the V.
34 control channel • Defective remote terminal.

V.21 signal not stopped

6-99 • Replace the FCU.
within 6 s

• Double registration of the SIP user name.

SIP user name registration
13-17 • Capacity for user-name registration in the SIP server is
error
not sufficient.

• Incorrect initial setting for the SIP server.

13-18 SIP server access error
• Defective SIP server.

Error occurred during sending to the SMTP server. Occurs

14-00 SMTP Send Error for any error other than 14-01 to 16. For example, the mail
address of the system administrator is not registered.

Failed to connect to the SMTP server (timeout) because the

server could not be found.
• The PC is not ready to transfer files.
14-01 SMTP Connection Failed • SMTP server not functioning correctly.
• The DNS IP address is not registered.
• Network not operating correctly.
• Destination folder selection not correct.

No Service by SMTP Service SMTP server operating incorrectly, or the destination for
14-02
(421) direct SMTP sending is not correct.

32
 Error Codes

Code Meaning Suggested Cause/Action

• Contact the system administrator and check that the
SMTP server has the correct settings and operates
correctly.
• Contact the system administrator for direct SMTP
sending and check the sending destination.

Failed to access the SMTP server because the access is

denied.
• SMTP server operating incorrectly. Contact the system
3
administrator to determine if there is a problem with the
SMTP server and to check that the SMTP server settings
are correct.
• Folder send destination is incorrect. Contact the system
Access to SMTP Server
14-03 administrator to determine that the SMTP server
Denied (450)
settings and path to the server are correct.
• Device settings incorrect. Confirm that the user name
and password settings are correct.
• Direct SMTP destination incorrect. Contact the system
administrator to determine if there is a problem at the
destination at that the settings at the destination are
correct.

Access to SMTP Server • SMTP server operating incorrectly

14-04
Denied (550) • Direct SMTP sending not operating correctly

Failed to access the SMTP server because the HDD on the

server is full.
• Insufficient free space on the HDD of the SMTP server.
Contact the system administrator and check the
amount of space remaining on the SMTP server HDD.
• Insufficient free space on the HDD where the
14-05 SMTP Server HDD Full (452) destination folder is located. Contact the system
administrator and check the amount of space
remaining on the HDD where the target folder is
located.
• Insufficient free space on the HDD at the target
destination for SMTP direct sending. Contact the
system administrator and check the amount of space
remaining on the target HDD.

33
 3. Troubleshooting

Code Meaning Suggested Cause/Action

The designated user does not exist.

User Not Found on SMTP • The designated user does not exist on the SMTP server.
14-06
Server (551) • The designated address is not for use with direct SMTP
sending.

Failed to access the SMTP server because the transmission

failed.
3 • PC not operating correctly.
Data Send to SMTP Server • SMTP server operating incorrectly
14-07
Failed (4XX)
• Network not operating correctly.
• Destination folder setting incorrect.
• Direct SMTP sending not operating correctly.

Failed to access the SMTP server because the transmission

failed.

Data Send to SMTP Server • SMTP server operating incorrectly

14-08
Failed (5XX) • Destination folder setting incorrect.
• Direct SMTP sending not operating correctly.
• Software application error.

Authorization Failed for • POP-Before-SMTP or SMTP authorization failed.

14-09
Sending to SMTP Server • Incorrect setting for file transfer

Number of broadcast addresses exceeded the limit for the

14-10 Addresses Exceeded
SMTP server.

The send buffer is full so the transmission could not be

14-11 Buffer Full completed. Buffer is full due to using Scan-to-Email while
the buffer is being used send mail at the same time.

Transmission was cancelled because the detected size of

14-12 Data Size Too Large
the file was too large.

14-13 Send Cancelled Processing is interrupted because the user pressed Stop.

Failed to create the MCS file because:

• The number of files created with other applications on
14-30 MCS File Creation Failed
the Document Server has exceeded the limit.
• HDD is full or not operating correctly.

34
 Error Codes

Code Meaning Suggested Cause/Action

• Software error.

UFS file could not be created:

• Not enough space in UFS area to handle both Scan-
14-31 UFS File Creation Failed to-Email and IFAX transmission.
• HDD full or not operating correctly.
• Software error.

Cancelled the Mail Due to Error detected with NFAX and send was cancelled due to
3
14-32
Error Detected by NFAX a software error.

No Mail Address For the Neither the mail address of the machine nor the mail address
14-33
Machine of the network administrator is registered.

Operational error in normal mail sending or direct SMTP

Address designated in the sending.
14-34 domain for SMTP sending • Check the address selected in the address book for
does not exist SMTP sending.
• Check the domain selection.

Due to an FCU mail job task error, the send was cancelled:
• Address book was being edited during creation of the
14-50 Mail Job Task Error
notification mail.
• Software error.

Not even one return notification can be downloaded:

UCS Destination Download • The address book was being edited.
14-51
Error • The number for the specified destination does not exist
(it was deleted or edited after the job was created).

The cancel operation by the user failed to cancel the send

14-60 Send Cancel Failed
operation.

Notification Mail Send Failed

14-61 All addresses for return notification mail failed.
for All Destinations

At startup, the system detected that the IP address of the

POP3/IMAP4 Server Not
15-01 POP3/IMAP4 server has not been registered in the
Registered
machine.

POP3/IMAP4 Mail Account

15-02 The POP3/IMAP4 mail account has not been registered.
Information Not Registered

35
 3. Troubleshooting

Code Meaning Suggested Cause/Action

15-03 Mail Address Not Registered The mail address has not been registered.

15-10 DCS Mail Receive Error Error other than 15-11 to 15-18.

The DNS or POP3/IMAP4 server could not be found:

• The IP address for DNS or POP3/IMAP4 server is not
15-11 Connection Error stored in the machine.

3 • The DNS IP address is not registered.

• Network not operating correctly.

POP3/IMAP4 send authorization failed:

• Incorrect IFAX user name or password.
15-12 Authorization Error • Access was attempted by another device, such as the
PC.
• POP3/IMAP4 settings incorrect.

Occurs only during manual reception. Transmission cannot

15-13 Receive Buffer Full be received due to insufficient buffer space. The buffer is
being used for mail send or Scan-to-Email.

The mail header is not standard format. For example, the

15-14 Mail Header Format Error
Date line description is incorrect.

The e-mail is not in standard format. There is no boundary

15-15 Mail Divide Error
between parts of the e-mail, including the header.

15-16 Mail Size Receive Error The mail cannot be received because it is too large.

May occur during manual receiving only because the

15-17 Receive Timeout
network is not operating correctly.

15-18 Incomplete Mail Received Only one portion of the mail was received.

Final Destination for Transfer

The format of the final destination for the transfer request
15-31 Request Reception Format
was incorrect.
Error

The transmission cannot be delivered to the final destination:

Send/Delivery Destination • Destination file format is incorrect.
15-39
Error • Could not create the destination for the file
transmission.

36
 Error Codes

Code Meaning Suggested Cause/Action

Reception rejected because the transaction exceeded the

15-41 SMTP Receive Error
limit for the “Auth. E-mail RX” setting.

The delivery destination address was specified with Off

15-42 Off Ramp Gateway Error
Ramp Gateway OFF.

15-43 Address Format Error Format error in the address of the Off Ramp Gateway.

15-44 Addresses Over

The number of addresses for the Off Ramp Gateway
exceeded the limit of 30.
3
15-61 Attachment File Format Error The attached file is not TIFF format.

Could not receive transmission due to:

• Resolution error
• Image of resolution greater than 200 dpi without
extended memory.
• Resolution is not supported.
15-62 TIFF File Compatibility Error
• Page size error
• The page size was larger than A3.
• Compression error
• File was compressed with other than MH, MR, or
MMR.

The TIFF file sent as the attachment could not be received

because the TIFF header is incorrect:
15-63 TIFF Parameter Error • The TIFF file attachment is a type not supported.
• The TIFF file attachment is corrupted.
• Software error.

The file received as an attachment caused the TIFF

decompression error:
15-64 TIFF Decompression Error
• The TIFF format of the attachment is corrupted.
• Software error.

The file could not be received because the attachment was

15-71 Not Binary Image Data
not binary image data.

Could not find the Disposition line in the header of the Return
15-73 MDN Status Error
Receipt, or there is a problem with the firmware.

37
 3. Troubleshooting

Code Meaning Suggested Cause/Action

Could not find the Original Message ID line in the header

15-74 MSDN Message ID Error
of the Return Receipt, or there is a problem with the firmware.

Could not receive the transmission because the destination

buffer is full and the destination could not be created (this
15-80 Mail Job Task Read Error
error may occur when receiving a transfer request or a
request for notification of reception).

3 Could not repeat receive the transmission because the

Repeated Destination destination buffer is full and the destination could not be
15-81
Registration Error created (this error may occur when receiving a transfer
request or a request for notification of reception).

Could not receive the file for transfer to the final destination:
• The format of the final destination or the transfer
15-91 Send Registration Error destination is incorrect.
• Destinations are full so the final and transfer
destinations could not be created.

Transmission could not be received because memory

15-92 Memory Overflow
overflowed during the transaction.

Transaction could not complete due to a malfunction of SAF

15-93 Memory Access Error
memory.

The machine rejected an incoming e-mail for transfer

15-94 Incorrect ID Code request, because the ID code in the incoming e-mail did not
match the ID code registered in the machine.

The machine rejected an incoming e-mail for transfer

15-95 Transfer Station Function
because the transfer function was unavailable.

• Divide the original into more than one page.

Original length exceeded the • Check the resolution used for scanning. Lower the scan
22-00
maximum scan length resolution if possible.
• Add optional page memory.

• Wait for the files in the queue to be sent.

• Delete unnecessary files from memory.
Memory overflow while
22-01 • Transfer the substitute reception files to another fax
receiving
machine, if the machine’s printer is busy or out of order.
• Add an optional SAF memory card or hard disk.

38
 Error Codes

Code Meaning Suggested Cause/Action

Tx or rx job stalled due to line • The job started normally but did not finish normally;
22-02 disconnection at the other data may or may not have been received fully.
end • Restart the machine.

The machine cannot store • Update the ROM

22-04
received data in the SAF • Replace the FCU.

22-05
No G3 parameter
confirmation answer
• Defective FCU board or firmware. 3
Data read timeout during • Restart the machine.
23-00
construction • Replace the FCU

The machine software resets • Update the ROM

25-00 itself after a fatal transmission
error occurred • Replace the FCU.

F0-xx V.34 modem error • Replace the FCU.

• Update the SG3-V34 modem ROM.

• Replace the SG3-V34 board.
F6-xx SG3-V34 modem error
• Check for line noise or other line problems.
• Try communicating another V.8/V.34 fax.

39
 3. Troubleshooting

IFAX Troubleshooting
Use the following procedures to determine whether the machine or another part of the network is causing
the problem.

Communication
Item Action Remarks
Route

• Check that the LAN

3 1. Connection with
cable is connected to
the machine.
the LAN
• Check that the LEDs
on the hub are lit.
General LAN
• Check that other
devices connected to
2. LAN activity the LAN can
communicate through
the LAN.

• Is the IP address
registered in the TCP/
IP properties in the
1. Network settings • Check the network network setup
on the PC settings on the PC. correct? Check the IP
address with the
administrator of the
network.

• At the MS-DOS
• Use the “ping”
Between IFAX and 2. Check that PC can prompt, type ping
command on the PC
PC connect with the then the IP address of
to contact the
machine the machine, then
machine.
press Enter.

• Use the “Network”

• Check the LAN function in the User
parameters Tools.
3. LAN settings in the
machine • Check if there is an IP • If there is an IP
address conflict with address conflict,
other PCs. inform the
administrator.

40
 IFAX Troubleshooting

Communication
Item Action Remarks
Route

• Use the “Network”

• Check the LAN function in the User
parameters Tools.
1. LAN settings in the
machine • Check if there is an IP • If there is an IP
address conflict with address conflict,
other PCs. inform the
administrator. 3
• Make sure that the
machine can log into
the e-mail server.

2. E-mail account on • Check that the • Ask the administrator

the server account and to check.
Between machine password stored in
and e-mail server the server are the
same as in the
machine.

• Ask the administrator

to check.
• Send a test e-mail
• Make sure that the with the machine’s
client devices which own number as the
3. E-mail server have an account in destination. The
the server can send/ machine receives the
receive e-mail. returned e-mail if the
communication is
performed
successfully.

• Make sure that the PC

can log into the e-mail
server.

1. E-mail account on • Check that the • Ask the administrator

Between e-mail
the Server account and to check.
server and internet
password stored in
the server are the
same as in the
machine.

41
 3. Troubleshooting

Communication
Item Action Remarks
Route

• Ask the administrator

to check.
• Send a test e-mail
• Make sure that the with the machine’s
client devices which own number as the
2. E-mail server have an account in destination. The
3 the server can send/
receive e-mail.
machine receives the
returned e-mail if the
communication is
performed
successfully.

• Make sure that the e-

mail address is
actually used.
3. Destination e-mail
address • Check that the e-mail
address contains no
incorrect characters
such as spaces.

• Use the “ping”

command to contact
the router.
• Ask the administrator
4. Router settings • Check that other of the server to check.
devices connected to
the router can sent
data over the router.

• Check whether e-mail

can be sent to another
5. Error message by address on the same
network, using the • Inform the
e-mail from the
application e-mail administrator of the
network of the
software. LAN.
destination.
• Check the error e-
mail message.

42
 IP-Fax Troubleshooting

IP-Fax Troubleshooting
IP-Fax Transmission

Cannot send by IP Address/Host Name

Check Point Action

3
1 LAN cable connected? Check the LAN cable connection.

2 Specified IP address/host name correct? Check the IP address/host name.

Cannot breach the firewall. Send by using

3 Firewall/NAT is installed?
another method (Fax, Internet Fax)

4 Transmission sent manually? Manual sending not supported.

5 IP address of local machine registered? Register the IP address.

Remote terminal port number setting other than

6 Send by specifying the port number.
1720?

7 Specified port number correct? Confirm the port number of the remote fax.

8 DNS server registered when host name specified? Contact the network administrator.

Check whether the remote fax is a T38

9 Remote fax a T.38 terminal?
terminal.

10 Remote fax switched off or busy? Check that the remote fax is switched on.

Request the network administrator to increase

the bandwidth.

Raise the delay level.

11 Network bandwidth too narrow?
IPFAX SW 01 Bit 0 to 3

IP-Fax bandwidth is the same as the DCS

speed. Set IP-Fax SW00 Bit 6 to 1.

Check whether the remote fax cancelled the

12 Remote fax cancelled transmission?
transmission.

43
 3. Troubleshooting

Cannot send via VoIP Gateway

Check Point Action

1 LAN cable connected? Check the LAN cable connection.

2 VoIP Gateway T.38 standard? Contact the network administrator.

3 VoIP Gateway installed correctly? Contact the network administrator.

3 4 VoIP Gateway power switched on? Contact the network administrator.

Is the IP address/host name of the specified

5 Check the IP address/host name.
Gateway correct?

6 Number of the specified fax correct? Check the remote fax number.

Cannot breach the firewall. Send by using

7 Firewall/NAT is installed?
another method (Fax, Internet Fax)

8 Transmission sent manually? Manual sending not supported.

9 IP address of local fax registered? Register the IP address.

10 DNS registered when host name specified? Contact the network administrator.

11 Remote fax a G3 fax? Check that the remote fax is a G3 fax.

12 G3 fax is connected to VoIP gateway? Check that G3 fax is connected.

13 Remote G3 fax turned on? Check that G3 fax is switched on.

Request the network administrator to increase

the bandwidth.

Raise the network delay level. IPFAX SW 01

14 Network bandwidth too narrow?
Bit 0 to 3

IP-Fax bandwidth is the same as the DCS

speed. Set IP-Fax SW00 Bit 6 to 1.

Cannot send by Alias Fax number.

Check Point Action

1 LAN cable connected? Check the LAN cable connection.

44
 IP-Fax Troubleshooting

Check Point Action

Confirm the Alias of the remote fax.

2 Number of specified Alias fax correct?
Error Code: 13-14

Cannot breach the firewall. Send by using

3 Firewall/NAT installed?
another method (Fax, Internet Fax)

4 Transmission sent manually? Manual sending not supported.

5 Gatekeeper installed correctly? Contact the network administrator. 3

6 Gatekeeper power switched on? Contact the network administrator.

7 IP address/host name of Gatekeeper correct? Check the IP address/host name.

DNS server registered when Gatekeeper host

8 Contact the network administrator.
name specified?

Check the settings.

9 Enable H.323 SW is set to on?
See User Parameter SW 34 Bit 0

10 IP address of local fax registered? Register the IP address of the local fax.

11 Alias number of local fax registered? Register the Alias number of the local fax.

12 Remote fax registered in Gatekeeper? Contact the network administrator.

Check whether the remote fax is a T38

13 Remote fax a T.38 terminal?
terminal.

14 Remote fax switched off or busy? Contact the network administrator.

Request the system administrator to increase

the bandwidth.

15 Network bandwidth too narrow? Raise the delay level. IPFAX SW 01 Bit 0 to 3

Lower the modem transmission baud rate.

IPFAX SW 05

Check whether the remote fax cancelled the

16 Remote fax cancelled transmission?
transmission.

45
 3. Troubleshooting

IP-Fax Reception

Cannot receive by IP Address/Host name

Check Point Action

1 LAN cable connected? Check the LAN cable connection.

3 2 Firewall/NAT is installed?
Cannot breach the firewall. Send by using another
method (Fax, Internet Fax)

3 IP address of local fax registered? Register the IP address.

Port number specified at remote sender fax (if

4 Request the sender to specify the port number.
required)?

5 Specified port number correct (if required)? Request the sender to check the port number.

Contact the network administrator.

DNS server registered when host name
6 Note: The sender machine displays this error code
specified on sender side?
if the sender fax is a Ricoh model.

Request the system administrator to increase the

bandwidth.
7 Network bandwidth too narrow?
Lower the start modem reception baud rate on the
receiving side. IPFAX SW06

Check whether the remote fax cancelled the

8 Remote fax cancelled transmission?
transmission.

Cannot receive by VoIP Gateway.

Check Point Action

1 LAN cable connected? Check the LAN cable connection.

Cannot breach the firewall. Request the remote

2 Firewall/NAT is installed? fax to send by using another method (Fax, Internet
Fax)

3 VoIP Gateway installed correctly? Contact the network administrator.

4 VoIP Gateway power switched on? Contact the network administrator.

46
 IP-Fax Troubleshooting

Check Point Action

IP address/host name of specified VoIP Request the remote fax to check the IP address/
5
Gateway correct on sender’s side? host name.

DNS server registered when host name

6 Contact the network administrator.
specified on sender side?

Request the network administrator to increase the

7 Network bandwidth too narrow?
bandwidth.

8 G3 fax connected? Check that G3 fax is connected.

3
9 G3 fax power switched on? Check that G3 fax is switched on.

Cannot receive by Alias Fax number.

Check Point Action

1 LAN cable connected? Check the LAN cable connection.

Cannot the breach firewall. Request the remote fax

2 Firewall/NAT is installed? to send by using another method (Fax, Internet
Fax)

Contact the network administrator.

3 Gatekeeper installed correctly? Note: The sender machine displays this error code
if the sender fax is a Ricoh model.

Contact the network administrator.

4 Power to Gatekeeper switched on? Note: The sender machine displays this error code
if the sender fax is a Ricoh model.

Request the sender to check the IP address/host

IP address/host name of Gatekeeper correct name.
5
on the sender’s side? Note: The sender machine displays this error code
if the sender fax is a Ricoh model.

Contact the network administrator.

DNS server registered when Gatekeeper host
6 Note: The sender machine displays this error code
name specified on sender’s side?
if the sender fax is a Ricoh model.

Request the sender to check the settings.

7 Enable H.323 SW is set to on?
User Parameter SW 34 Bit 0

47
 3. Troubleshooting

Check Point Action

Note: Only if the remote sender fax is a Ricoh fax.

8 Local fax IP address registered? Register the IP address.

9 Local fax Alias number registered? Register the Alias number.

Request the system administrator to increase the

bandwidth.

3 10 Network bandwidth too narrow? Lower the start modem reception baud rate on the
receiving side.
IPFAX SW06

Check whether the remote fax cancelled the

11 Remote fax cancelled transmission?
transmission.

Contact the network administrator.

12 Local fax registered in Gatekeeper? Note: The sender machine displays this error code
if the sender fax is a Ricoh model.

48