Announcement

Collapse
No announcement yet.

New error for Envisalink

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • 519zwave
    replied
    And as an FYI
    EyezON was back to me with support within an hour - quite impressive!

    Leave a comment:


  • 519zwave
    replied
    Solved this problem

    SO: Power went out last night - another device stole the IP address for Envisalink as I guess it booted up first. Was hidden in DHCP and couldn't see conflict. AND for some reason I can't lock my Envisalink via DHCP so let's hope a UPS solves this!

    Leave a comment:


  • MrMxyzptlk
    replied
    The plugin always says duplicate IP for me as well, even though that is not the case.
    I have my own Windows DHCP servers and the IP is definitely not being leased by anything other than the Envisalink.

    Leave a comment:


  • 519zwave
    replied
    No luck.
    Rebooted plugin, router, hs3 - EVERYTHING
    Got this error from envisalink site:
    ERROR: Duplicate IP address detected on the network
    (UPDATE: that error no longer on envisalink site - all seems good there, but error still with plugin.)
    Checked router - no duplicates anywhere.

    Have logged a help request there...
    Last edited by 519zwave; December 29th, 2015, 08:42 AM.

    Leave a comment:


  • spud
    replied
    do you get the same error if you restart the plugin?

    can you access the local web page: http://envisalink ?
    if so you can try to reboot the Envisalink board from the network page.

    Leave a comment:


  • 519zwave
    started a topic New error for Envisalink

    New error for Envisalink

    SOLVED - IP CONFLICT error on my end.

    Hi Spud,

    This error started happening last night and envisalink won't connect. Any suggestions?

    Dec-29 8:14:47 AM EnvisaLink INFO Trying to reconnect to: 192.168.1.142:4025 Dec-29 8:13:47 AM EnvisaLink ERROR No connection could be made because the target machine actively refused it 192.168.1.142:4025
    Last edited by 519zwave; December 29th, 2015, 09:17 AM. Reason: Solved
Working...
X