Is the Nx Cloud up? Visit our Status Page for the current health and performance of the Nx Cloud.

Status Page

Network Optix Server thinks the server IP is different than actual

Answered
Permanently deleted user
Edited

Under routing, and also under /static/index.html#/health network interfaces, the IP of the sever is WRONG.  It is not showing the internal LAN static IP of my server.

I've tried changing the port to something else, then back again - doesn't fix it.

I've tried changing the static IP of the server to something else, then back again - doesn't fix it.

Why are there 3 separate places where Network Optix thinks the server LAN IP is a value different from the actual IP assigned to the system under NIC properties in Windows???

It doesn't even make sense that I can access the server webpage using an IP address that is NOT assigned to the server.

0

Comments

4 comments

Date Votes
  • Norman
    • Network Optix team

    Hi,

    Can you share screenshots that show the IP addresses?

    Also, please tell us which version of Nx Witness you're using.

    Thank you.

    0
  • Norman
    • Network Optix team

    Hi @...,

    Just to be sure I checked my systems, but all good here.

    Both internal NICs displayed their IP address correct. Both IPv4 and IPv6 were correct.
    Also, the external IP address was displayed correctly.

    As you can see below, all IPv4 addresses correspond with eachother in the WebAdmin, Nx Desktop client and for the system.

    0
  • Permanently deleted user

    I can't explain exactly what happened, but I'm back up and running.

    The old system was at IP .100.5
    I took the static IP out of windows and the old machine got a DHCP lease of .100.35

    I made a backup of the DB, moved this file to the new machine

    I gave the new machine a static IP of .100.5

    Imported the DB file, and that's where I noticed that NXWitness still thought it was running on .100.35, even though that old machine was off.

    How I finally solved it....
    Gave the new machine a DHCP reservation so it would always get .100.5
    Changed Windows NIC properties from static to DHCP,
    again, machine still has the same .100.5 IP
    Restarted system
    NxWitness finally realized it was running on .100.5
    Changed the Windows NIC properties to static IP .100.5 again
    All seems good

    I also realized I had an ARP cache issue on either the switch or the firewall (flushed both) and then everything was working again.

    Honestly, not sure what happened.

    0
  • Norman
    • Network Optix team

    Thank you for the update @....
    Good to read all is good now.

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post