Page 1 of 2 12 LastLast
Results 1 to 10 of 13
  1. #1
    Technician MatthewS's Avatar
    Join Date
    Nov 2012
    Posts
    25
    Rep Power
    13

    @remote issue on MPC3004

    Hello Guys,

    I have a machine that was on @remote and all suddenly stopped working. There is 2 MPC3004's in the building on the same network and the other MPC3004 @remote is still working. On the problem machine I have performed SP's 5816-201, 5870-003 and 001. Trying to re-register machine on @remote is no go and thinks about it for 10 min then times out. Machines firmware is up-to-date. Any suggestions?

  2. #2
    Service Manager 2,500+ Posts TonerMunkeh's Avatar
    Join Date
    Apr 2008
    Posts
    3,298
    Rep Power
    76

    Re: @remote issue on MPC3004

    Is it a Basil box or Cumin communication? Are you using WIM or SP modes to put the @remote code in?
    Computers are serious tools, Michael!

  3. #3
    Technician MatthewS's Avatar
    Join Date
    Nov 2012
    Posts
    25
    Rep Power
    13

    Re: @remote issue on MPC3004

    I am using Embedded RC Gate method and registering via WIM.

  4. #4
    Just a tech 100+ Posts keithxxiii's Avatar
    Join Date
    Nov 2014
    Posts
    179
    Rep Power
    11

    Re: @remote issue on MPC3004

    When you say "trying to re-register", did you remove it from the central server and performed 5816-209 and 5870-003 and 001?

  5. #5
    How'd ya manage that? 500+ Posts zed255's Avatar
    Join Date
    Dec 2009
    Posts
    849
    Rep Power
    36

    Re: @remote issue on MPC3004

    You need to have it removed from Centre Server, do SP5-816-209, SP5-870-3, and either SP5-870-1 (for a 512 bit certificate) or SP5-879-4 (for a 2048 bit certificate). With the newer devices the 2048 bit certificate is preferred and required for features like AFU.

    Don't discount the possibility it is an IT thing. Had one a while back where one device would not register and it turned out the customer was filtering traffic on that one subnet.
    Zed
    One out of four people is mentally unbalanced.
    Think of your three closest friends...
    If they seem okay, then You're The One.

  6. #6
    Technician MatthewS's Avatar
    Join Date
    Nov 2012
    Posts
    25
    Rep Power
    13

    Re: @remote issue on MPC3004

    Yeah I did remove it from the central server and performed 5816-209 and 5870-003 and 001 then checked 5816-201 in exact order. Once I do all that then I go to WIM and try to register with new request number. It's hard to believe in this case it's network causing issue considering the other machine on same network (same IP range/subnet) is currently connected to @remote.

  7. #7
    Ricoh Fanboy 1,000+ Posts Oze's Avatar
    Join Date
    Jul 2008
    Location
    Toowoomba
    Posts
    1,246
    Rep Power
    37

    Re: @remote issue on MPC3004

    When we've had @Remote issues in the past we used to run SP5-870-3 and SP5-870-1 to re-write KeyInfo and that usually resolved the issue.
    And what failure error code does it give you?
    Have you tried setting @Remote up only using the SP settings?
    EnterService Mode.
    SP5-816-062– Use Proxy – Change 0 to 1 if Proxy Required
    SP5-816-063– Proxy Host – Type Proxy Server Name
    SP5-816-064– Proxy Port – Type Proxy Port Number
    SP5-816-065– Proxy User Name (if Needed)
    SP5-816-066– Proxy Password (if Needed)
    SP5-816-200– Manual Polling to check/update status
    SP5-816-201– Check result is 0 before starting
    SP5-816-202– Letter Number - Type RRAP Request number
    SP5-816-203– Confirm Execute
    SP5-816-200– Manual Polling to check/update status
    May take a minute & a couple of 200 (Manual Polling)
    SP5-816-204– Confirm Result – Check reports 0 before continuing.
    If 9 the 200 again until reports 0
    SP5-816-206– Register Execute
    SP5-816-200– Manual Polling to check/update status
    May take a minute & a couple of 200 (Manual Polling)
    SP5-816-207– Confirm Result – Check reports 0 before continuing
    If 9 the 200 again until reports 0

    SP5-816-209– Instl Clear – Deletes all settings above to re-try.

    ForTesting once registered open User Tools, System Settings, Administrator Tools
    Onthe second or third page there will be a Service Test Call button and a NotifySystem Status

  8. #8
    Technician MatthewS's Avatar
    Join Date
    Nov 2012
    Posts
    25
    Rep Power
    13

    Re: @remote issue on MPC3004

    It comes up with this message. (FYI there's no proxy server on network)

    IMG_1728.JPG


    I have tried setting up @remote using both WIM and SP mode methods.

  9. #9
    Just a tech 100+ Posts keithxxiii's Avatar
    Join Date
    Nov 2014
    Posts
    179
    Rep Power
    11

    Re: @remote issue on MPC3004

    Quote Originally Posted by zed255 View Post
    You need to have it removed from Centre Server, do SP5-816-209, SP5-870-3, and either SP5-870-1 (for a 512 bit certificate) or SP5-879-4 (for a 2048 bit certificate). With the newer devices the 2048 bit certificate is preferred and required for features like AFU.

    Don't discount the possibility it is an IT thing. Had one a while back where one device would not register and it turned out the customer was filtering traffic on that one subnet.

    Agree with Zed, you have to check if they are filtering the traffic on that particular IP. Also check if you can ping the central server's IP.

    I always have my netgear extender and connect to 3G to test the connectivity of the device.

  10. #10
    Retired 5,000+ Posts slimslob's Avatar
    Join Date
    May 2013
    Location
    Bakersfield, CA
    Posts
    8,545
    Rep Power
    185

    Re: @remote issue on MPC3004

    Just wild hair but have you tried it connected to the same network that the one that is working is connected to? I have managed switches blocked selected port on selected circuits.

    Had a major account once that after painting the shop office over the weekend and moving everything back in, MFP would not print. After working on it for about 90 minutes their local IT and I noticed that there were 2 jacks in the office. Moved the cable to the other jack and it started spooling. IT did some further checks and when configuration used to be done remotely by corporate IT they had set the switches to allow TCP/IP printing only to selected switch ports.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Get the Android App
click or scan for the Copytechnet Mobile App

-=-=-=-=-=-


IDrive Remote Backup

Lunarpages Internet Solutions

Advertise on Copytechnet

Your Link Here