Question Windows 10 Blue Iris PC - Strange issue ?

[garmcqui]

Hi all, happy Friday!

I have a strange issue with the Win10 PC I use exclusively for Blue Iris NVR software. It is not the most modern (Intel I7-6700, 16GB RAM, PCI-E Coral TPU), but copes fine.

The issue is that, every few days, the PC just becomes inaccessible - won't wake up the attached monitor, no access via remote desktop etc. To get access, I have no option but to force power cycle, which obviously isn't ideal.

Things that do work:

• Blue Iris remote Access (via iOS app)
• Ping
• Network shares in windows

This is the output of nbstat:

:\WINDOWS\system32>nbtstat -A 192.168.100.10

VirtualBox Host-Only Network:
Node IpAddress: [192.168.56.1] Scope Id: []

Host not found.

Ethernet 2:
Node IpAddress: [0.0.0.0] Scope Id: []

Host not found.

Local Area Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

Host not found.

Ethernet:
Node IpAddress: [192.168.100.174] Scope Id: []

NetBIOS Remote Machine Name Table

Name Type Status
---------------------------------------------
BLUEIRIS <20> UNIQUE Registered
WORKGROUP <00> GROUP Registered
BLUEIRIS <00> UNIQUE Registered

MAC Address = <<removed>>

QuoteReply
ReportEditDelete

When I have forces power cycled and got back into the PC, I can't see anything major in Event Viewer either.

Any help or advice appreciated.

 

[Ralston18]

This app?

https://blueirissoftware.com/

How many network devices? Cameras?

My thought is an IP address conflict - some device defaulting to its' default IP address.

The above IP addresses 192.168.100.10 and 192.168.56.1 are not what I would expect.....

Did you assign any such IP addresses as static?

Run "ipconfig /all" on your PC. What is the Default Gateway and DHCP Server? What DHCP IP address(es) are being provided to the PC? What lease time is being used?

"arp -a" may also prove helpful.

Check your router's admin menus/screens for a listing of connected and disconnected devices.

Map IP addressess and device MACs (physical addresses) to look for duplicates or misconfigured IP addresses and/or subnet mask.

Sketch out a diagram of the network and include device names, IP addresses, connections, etc. to see the big picture.

= = = =

Another easier place to look for error codes etc. is Reliability History/Monitor. The timeline format may prove revealing with respect to "every few days".