@remote Instructions

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 3

A Complete @Remote Registration Including Possible Errors and Blocked Port Procedures.

=====================================================

Call before you go to the site with the serial number. If the device hasn't reported in less than 30 days,
you can walk the customer through a test call (from the keypad). 24 hours later, check to see if the device
has started reporting again. Worse case, we can delete it off center server before you leave. Deleting can
take up to 45 minutes.

ENSURE IP, GATEWAY, SUBNET MASK AND DNS ARE CORRECT IN THE MFP!

Clear (Basic) Procedures:


-----------------------------
(if 5816-201 is a 0, you do not need to do a Clear)
5816-209 Execute
Power Cycle
5870-003 Execute
5870-001 Execute
Power Cycle

Registration Procedures:
----------------------------
Ensure the device has been deleted off of center server.
Ensure that the Req ID is less than 30 days old.
5816-201 will equal 0 if a clear has been done.
5816-202 = <new Req ID> (all Capital Letters, no spaces)
5816-203 - Execute
5816-204 - Countdown from 9 to 0
5816-206 - Register
5816-207 - Countdown from 9 to 0

If Errors, check 5816-208 for error codes

5816-208 Error Codes


-------------------------
These are not all inclusive, just the most common.
-12002 Inquiry registration attempted without acquiring device status.
-12003 Attempted registration without execution of an inquiry and no previous registration.
-12004 Attempted setting with illegal entries for certification and ID2.
-12005 @Remote communication is prohibited. The device has a problem with an internal @Remote
function (see Do Not Prohibit procedures)
-12006 After confirmation is completed, confirmation request was made again.
-12007 Different request number was used for registration than the number which was used for
confirmation.
-12008 Certification update failed because the device was in use.
-12009 ID2 mismatch between an individual certification and NVRAM
-12010 Certification area is not initialized.
Countdown numbers (not all inclusive)
1 = Expired or already in use Req ID number
4 = Network connectivity error. Usually means it is being blocked on Port 443
5 = Proxy error (illegal user name or password)
8 = Network connectivity error. Usually means it is being blocked on Port 443
9 = Still confirming request number…
11 = Request number error (Device is already registered)
12 = Request number error (Parameter error)
0 = Good

Port Openings:
-----------------
If the customers network is using a proxy server, they will have to add:
https://210.173.216.40/i02/AS (that is "i<zero>2)
https://210.173.216.50/i02/AS (that is "i<zero>2)
to their White List

If they are using a firewall, port 443 will have to be opened for bi-directional, no timer traffic for both TCP
and UDP. Depending on how strict their requirements are, they may also need to know the IP address(s)
of the MFP and center server, which are:
210.173.216.40 (embedded, appliances)(512 bit)
210.173.216.59 (embedded, appliances)(2048 bit)
210.173.216.50 (Enterprise Pro, appliances)
210.173.216.47 (Certificate Recovery)(512 bit)
210.173.216.60 (Certificate Recovery)(2048 bit)

If using Firmware updates (not recommended as of Mar 2014):


210.173.215.43 (512 bit)
210.173.215.142 (2048 bit)

Some Firewall Software can block traffic to/from countries. The Center Server is in Japan.

Some switches/routers have and use ACL's. These can also stop @remote traffic as well as SNMP traffic.

Some ISP's do not allow connection to remote systems that do not have a DNS entry. Center server does
not have a DNS entry. If network policy allows for exceptions, their IT support will need to know the IP of
the device and the IP of center server.

Do Not Prohibit
-----------------
User Tools\System Settings\Administrator Tools\Extended Security
Press the NEXT button until you see the @Remote (RC Gate) option. Set it to Prohibit to stop @Remote
or Do Not Prohibit to allow @Remote.
https://210.173.216.63/i02/AS   
◄ 12:03:00 PM
Center Server URL 210.173.216.63
(2048 bit)
Auto Discovery URL 210.173.216.59
(2048 bit)
Rescue Gateway URL
210.173.216.60 (2048 bit)
Global Server URL 2048 bit
133.139.21.122
133.139.21.126

You might also like