Remote service is down

Troubleshoot “Remote Services Down” between Topaz, Ruby2, or C18 POS and Commander. Includes quick triage for single-register, site-wide, and network gear issues.

What this means

“Remote Services Down” usually means the POS lost comms to Commander.

This can be:

• a single-register LAN issue (cable, port, switch)
• a site-wide LAN issue (EZR/MNSP, switch, zone router)
• a Commander issue (down, booting, or unhealthy)

Keywords

Also called: remote services down, RSD, remote services error, register offline, register lost comms, register not talking to Commander, POS offline, till offline, register disconnected, register can't connect, comms down, services down, register down, cards not working, Keywords: Remote Services Down error on screen, register showing remote services, red banner on register, prepay fuel not working, can't authorise prepay, card declined at register, card processing failed, helpdesk login token fails, token not generating, enable helpdesk login greyed out, please call to register your system message, Commander not responding, Commander offline, Commander status not A9, DCR cards declining at pump, pumps not authorising, switch port no link light, Ethernet cable loose, EZR no power, MNSP offline, zone router rebooting, why is my register showing remote services down, how do I fix remote services down, register lost connection to Commander

Example alarm banner at the top of the register screen

Example alarm banner at the bottom of the register screen

Network Topology diagram

Applies to

• Topaz POS
• Ruby2 POS
• C18 POS
• Zone router
• Switch / EZR / MNSP (site network gear between POS and Commander)

Symptoms you might see (even without the banner)

• Helpdesk login token fails.
• Prepay fuel fails.
• Card processing fails at the register.
• Message: “Please Call To Register Your System”.

  • This can be registration-only.
  • Do not assume it is Remote Services Down.

Info to collect first (makes troubleshooting faster)

Have these ready before you make changes:

• How many registers exist.
• Is the issue on one register or all registers.
• Are outside card transactions at DCRs working right now.
• Commander status (if you can see it).

  • Commander typically shows A9 when healthy.
• Exact on-screen wording and when it started.
• Anything changed today (power event, network change, ISP work).

Quick triage flow (symptom → next check)

Use this if you only have symptoms:

• Only one register impacted → likely register-to-switch path.
• All registers impacted → likely Commander or shared network gear.
• DCR card sales failing → treat as Commander-down or forecourt comms issue first.
• Helpdesk token fails → strong signal of broken comms./communication to Commander.

Troubleshooting steps

1

Determine if pumps are still working on cards (DCR test)

Confirm whether customers can still run card sales at the pump (DCR).

• If a customer is actively fueling on a card, confirm it is progressing normally.
• If no customer is actively using a card, attempt a card transaction at a DCR now.

If DCR card sales work

Commander is likely up. Continue to Step 2.

If DCR card sales do not work

Treat as site-wide. Jump to Step 4 (All registers path).

DCRs typically will decline cards if Commander is down or not fully booted.

2

Determine the scope (one register vs all)

Check whether “Remote Services Down” is showing on more than one register.

If it is present on all registers (at a site with more than one register), the issue is likely Commander or Commander’s connection to the switch/EZR/MNSP.

If only one register is impacted

Go to Step 3 (Single register path).

If all registers are impacted

Go to Step 4 (All registers path).

3

Single register path (most common: cable/port/switch)

3.1 Generate a Helpdesk login token (comms. test)

On the impacted register:

• CSR Function → Maintenance → Enable Helpdesk Login → Yes

If a token displays as in picture below, communication from Register to Commander is working.

Example: helpdesk login token successful

If it fails, continue below to next step.

3.2 Reseat cabling end-to-end

1. Reseat Ethernet at the register.
2. Trace the same cable to the switch/EZR/MNSP port.
3. Reseat Ethernet at the network device.

Retest the Helpdesk token. If it succeeds, register↔Commander comms. are good. If it fails, continue to the next step.

3.3 Check link lights and try another port

• Check for a link light on the EZR/MNSP port where the register is plugged in.
• If no light, move the register cable to a different known-good LAN port.

Retest the Helpdesk token. If it succeeds, register↔Commander comms. are good. If it fails, continue to the next step.

3.4 Power cycle the impacted register

Power cycle the single Topaz/Ruby2.

Retest the Helpdesk token. If it succeeds, register↔Commander comms. are good. If it fails, continue to the next step.

4

All registers impacted path - Check power and status

Check the Power and Status of all equipment.

Commander/RubyCi > Status should be powered on and Status A9.

If there is no power on Commander

• Try a known-good outlet.
• Confirm the battery backup/UPS is On.
• If the UPS is the issue (won’t power on / no output), bypass the UPS and plug Commander directly into a wall outlet.
• If Commander still will not power On from a known-good wall outlet, call a VASC technician to check and troubleshoot the Commander.
• Once powered, repeat Step 3.1 (generate a Helpdesk token) to confirm communication.

If power on Commander is OK

• Reseat the Ethernet between Commander and the switch/EZR/MNSP.
• Confirm link/activity lights on that port.

If status shows A9, move to Step 5.

5

Check EZR/MNSP and any switch linking registers to EZR/MNSP for power.

• If no power, attempt to restore power
• If cannot restore power, contact your MNSP(e.g. Cybera, Paysafe, etc.)
• Once the power is back up, repeat step 2.
• If power exists, move to step 6.

6

Power down EZR/MNSP device as well as all registers.

7

Power up the zone router

Once lights on the router have returned to normal status, power up the registers one at a time.

8

If issue persists after trying all the above steps,

Call a VASC technician for on-site troubleshooting.

Need assistance? Contact Verifone Helpdesk at anytime.

• Use our Chat platform
• Or call 1.800.VERIFONE (837.4366)

Tell us the troubleshooting steps you’ve already tried. This saves time and gets you the right support faster.