Submit a ticketCall us

AnnouncementsWeb Help Desk Integrations eCourse

Looking to reduce response times? Sign up for our eCourse to learn how integrating Web Help Desk with Dameware Remote Support, Network Configuration Manager, Network Performance Monitor, and Server & Application Monitor can improve communication efficiencies.

Register here.

Home > Success Center > Network Configuration Manager (NCM) > Fortinet 200D login validation tests fail with a $ as a prompt

Fortinet 200D login validation tests fail with a $ as a prompt

Updated March 11th, 2016

Overview

This article describes the issue when adding a Fortinet 200D device to NCM, and the prompt is a $ and not a # or a >, NCM fails to connect even with standard customer commands added to the template for EnableIdentifier or Virtual Prompt.

Environment

All versions of NCM

Cause 

This is a known issue and as of the moment, developers are investigating on how to fix the current problem. 

Resolution

Use device credentials in NCM that have full Admin/Root access. These credentials return a # as the prompt.

Another way to fix the problem is to add to the device template using the following command:  

<Command Name="VirtualPrompt" Value="$"/>

 

For more information, click on this link on how to modify a device template for NCM version 7.4: Modify a default device template in NCM 7.4 

 

Last modified

Tags

Classifications

Public