NXC 2500 " Wrong CLI command" after Login...

Zaddel
Zaddel Posts: 3  Freshman Member
First Comment
edited August 2022 in WirelessLAN
After Login on the NXC 2500, " Wrong CLI command" pops up on every point of the menu. a restart has no effekt.... any ideas ?

Comments

  • Zyxel_Kathy
    Zyxel_Kathy Posts: 76  Zyxel Employee
    First Anniversary Friend Collector First Comment
    edited November 2017
    Hi @Zaddel

    Before you login the NXC's GUI, please note that 
    1. Turn on Javascript and Cookie setting in your web browser.
    2. Turn off Popup Window Blocking in your web browser.
    3. Turn on Java Runtime Environment (JRE) in your web browser.

    Test the browser with those version.
    The NXC Web Configuration allows easy management using an Internet browser. Browsers supported are:
    •Firefox 36.0.1 or later
    •Chrome 41.0 or later
    •IE 10 or later

    Please confirm the firmware version is using the latest 5.10 and check the pop up message if has the error number or other message? Is any possible share the screenshot for us? Thanks.

    Kathy
  • Zaddel
    Zaddel Posts: 3  Freshman Member
    First Comment

    Hey Kathy,

    the issues is still happen with each kind of browsers and settings. Firmware is 5.0...

  • Zyxel_Kathy
    Zyxel_Kathy Posts: 76  Zyxel Employee
    First Anniversary Friend Collector First Comment
    Hi @Zaddel

    I suggest you upgrade firmware to 5.10 by FTP.
    There is FAQ teach you upgrade FW by FTP.
    https://businessforum.zyxel.com/discussion/649/how-to-upgrade-firmware-to-controller-access-point-by-ftp#latest


    Kathy
  • Zaddel
    Zaddel Posts: 3  Freshman Member
    First Comment

    Ahoi Kathy,

    upgrading the firmware solved the Problem, cheers :)

  • Zyxel_Kathy
    Zyxel_Kathy Posts: 76  Zyxel Employee
    First Anniversary Friend Collector First Comment
    @Zaddel

    Great news~ =)


  • ChrisGer
    ChrisGer Posts: 205  Ally Member
    First Anniversary Friend Collector First Answer First Comment
    Zaddel said:

    Ahoi Kathy,

    upgrading the firmware solved the Problem, cheers :)

    This issue was also existing (but solved) with the pre-Firmware from a USG ;)
    With the last fW release, this issue is solved, too ;)