Cannot get my EB1304NET to accept my password

[luminous 0]

Hi

 

Total newbie here, and a very frustrate one at that. I work in IT, and am having great issues getting this CCTV up and running.

 

I have a home network, the standalone DVR (EB1304) is on my LAN.

It has been given a static IP address on the LAN to make connection easier

The connection is through a switch, although there is a router elsewhere

The DVR is on the same subnet as my computers.

 

I open up IE 7 and attempt to connect by typing in the address directly. Example 192.168.0.78 (its not 78, but I use that as an example).

 

The interface loads up correctly (I have previously download the webcamx thing).

 

It asks for a username and password. According to the manual there are two different standard usernames, but both with the same password. Superuser and User with 111111 as the password.

 

I have tried either username, caps, no caps, first letter caps, with the default password. After a very long wait and the egg timer showing it tells me that it has rejected my login info.

 

I have gone to the box and gone to the submenu where you can change the password. In order to attempt to change the password you have to enter the current password. I enter 111111 and it accepts it.

 

If I have the right password, why does this not work!?

 

I have tried turning off the firewall and using 3 other computers

I have also successfully update the firmware (that needs the correct address, user, and password info, so the connection to the box is just fine)

 

Please help, I've lost enough hair as it is

[luminous 0]

OK, done some more work on this (I've been on all afternoon).

 

I use ESET NOD32 V3. I think there is some sort of incompatibility here.

 

I just suffered an awful crash a min ago when trying to login. Display drivers went all over the place, lost control of the mouse etc etc, then black screen and dead puter.

 

I just disabled virus protection firewall and its all worked.

 

I'll investigate and report back so that information can be made available for other people. Hopefully, a fix may be lurking around somewhere.

[luminous 0]

I think I have a workaround for NOD32.

 

In the advanced settings you have to change the protocol filtering from ports AND applications to ports only.

 

Then you change the network settings of the box to use a non standard port. This way its not filtered and access is allowed.

 

I have no idea why this is necessary, it should just work without having to do that. Maybe AverMedia wants to give ESET a call to see if this can be sorted with an update. NOD32 is becoming increasingly popular.