> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/feature-references/feature-references-lac-es/referencias-de-funciones-y-productos/tarjetas-de-flota-commander-fleet/solucion-de-problemas-de-commander-fleet.md).

# Solución de problemas de Commander Fleet

Si tiene algún problema con la función, revise esta lista:

{% stepper %}
{% step %}
La FEPTable está controlada por Verifone Commander Central y se sobrescribirá si los archivos se editan manualmente en Commander.
{% endstep %}

{% step %}
Los FEP no aparecen en línea en Verifone EPS hasta después de que se complete la primera transacción.
{% endstep %}

{% step %}
Asegúrese de que Commander tenga DNS habilitado desde **Configuration Client > Initial Setup> Local Area Network Settings** y que la URL del host pueda resolverse correctamente con el siguiente comando: ping google.com
{% endstep %}

{% step %}
Acumera tenía un problema que no permitía que el tráfico saliera de Verifone Commander hacia el host de Comdata.

Use estos comandos desde una conexión de PuTTY en Commander para verificar que los hosts sean accesibles. Si estos comandos fallan y agotan el tiempo de espera, verifique con Acumera que la regla esté configurada para permitir este tráfico.

**Prueba de Comdata -** Openssl s\_client -connect 10.1.254.200:5003

**Prueba WEX-OTR -** Openssl s\_client -connect 208.64.196.225:8030
{% endstep %}

{% step %}
Verifique que el sitio esté usando el ID de concesionario correcto.

Si el ID de concesionario es incorrecto, recibirá un error del host.
{% endstep %}

{% step %}
Problemas con la descarga de la licencia. Si la licencia se envía correctamente, commercialFleetRoute.prop se establecerá en DIRECT

Verifique que commercialFleetRoute.prop esté configurado en DIRECT con el siguiente comando desde PuTTY:\
**cat /home/pmc/data/license/CommercialFleetRoute.prop commercialFleetRoute=DIRECT**
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verifone.com/feature-references/feature-references-lac-es/referencias-de-funciones-y-productos/tarjetas-de-flota-commander-fleet/solucion-de-problemas-de-commander-fleet.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
