http://www.netviewcctv.co.uk/blog/MBWfirm0902/
i got it from here the firmware
[h=2]Mini PTZ camera[/h]
i got it from here the firmware
[h=2]Mini PTZ camera[/h]
Based on your sig you needed another cam.....lol
Welcome on board. I was waiting for you to finally give in
Looks like they sold quite a few of these now and gaining popularity. So far the ones I have are working great, except annoying motion detection which sending out tons of false alarms. Frankly, after initial setup I am no longer using PTZ functions, they are static.
Issue is your gateway. If possible, resetting to defaults would be the easiest way, but meanwhile you should be able to use pc/laptop and change the NIC card IP to 192.168.1.254, Subnet: 255.255.255.0, GW: 192.168.1.254 and connect the pc/laptop and camera to a switch. Use the web gui to access the camera and fix the gateway. Gateway more than likely is 192.168.1.1, with a 255.255.255.0 subnet mask. try that to see if it works.
I had similar issues where the camera would drop off the network randomly, sometimes minutes, hours or even a few days and it would come back itself. I mentioned it somewhere in this thread. In the log, it would show net err. I crimped a new cable thinking it was my bad crimping and same thing was happening. Ended up not liking my router cause when I hooked it up on my switch, problem went away.Thanks djangel,
The gateway address is only used for IP traffic destined to hosts outside of the local network. So, any traffic staying on my 192.168.1.0/24 should not be using the gateway address. I Just double checked my HIKs and I have .254 for the GW on all but one of them which has 0.0.0.0. as the GW. They all work fine. And you are correct, my actual GW is 192.168.1.1
Since I can ping the camera, poorly but I can ping it, and I get a login prompt from my browser, the camera is reachable on my network. It's just not good enough to connect due to the packet drops and bad latency.
I see it as a connected device on my Netgear switch ( 192.168.1.200 58:04:CB:10:2B:F1 ).
It's behaving like a duplex/speed mismatch. I'll take it to work this morning and connect it to a Cisco switch so I can see how it's negotiating to the switch.
I appreciate everyone's input and will let you guys know what I find.
I really need to refresh my networking skills Anyway, I did experience a similar issue before with the camera giving me a Network Anomaly error, but it was due to changing the http port from it's default.
I think this was brought up before and the reason is the plugin must be loaded before the settings come up. Sounds like internet explorer was blocking the plugin?I did the same with my camera. I lost access to it when I did this. I could still log into the camera with Internet Explorer, but all the "fields or settings" in it's browser pages were blank. I couldn't even do a "Reset" or "Default" from the "Maintenance" tab. I tried from 2 other computers with the same result. I even tried using SADP to change the setting back, but this didn't work either. My solution was to log in with "FireFox. For some unknown reason, I was able to login to the camera and access all settings. So I started over by resetting the camera to the default settings. I have had no problems with the camera except for the vertical position changing slightly in some of my presets.
The funny thing is, my camera has been rock solid on my network. No drop offs, or loss of connection since it's been installed.
No need for the password, just upload the zip file to the camera.
Thanks djangel,
The gateway address is only used for IP traffic destined to hosts outside of the local network. So, any traffic staying on my 192.168.1.0/24 should not be using the gateway address. I Just double checked my HIKs and I have .254 for the GW on all but one of them which has 0.0.0.0. as the GW. They all work fine. And you are correct, my actual GW is 192.168.1.1
Since I can ping the camera, poorly but I can ping it, and I get a login prompt from my browser, the camera is reachable on my network. It's just not good enough to connect due to the packet drops and bad latency.
I see it as a connected device on my Netgear switch ( 192.168.1.200 58:04:CB:10:2B:F1 ).
It's behaving like a duplex/speed mismatch. I'll take it to work this morning and connect it to a Cisco switch so I can see how it's negotiating to the switch.
I appreciate everyone's input and will let you guys know what I find.
You may have, but I wouldn't give up hope that this is a bad configuration issue. Did you get in touch with Monica?Guess I just drew the short straw on this one.
I think this was brought up before and the reason is the plugin must be loaded before the settings come up. Sounds like internet explorer was blocking the plugin?
Sent from my LG-D852 using Tapatalk
You may have, but I wouldn't give up hope that this is a bad configuration issue. Did you get in touch with Monica?
As I recall I had address detected as 169.254.XXX.XXX when I was messing around with itHikvision SADP did something funky.
I'm guessing explorer cached the page. Did you try and delete history and cookies? Just checking you were access the page with HTTP://ipaddressort right?I'm not sure about this. Internet Explorer had been working fine with the camera before I changed the setting. Would changing the port then cause the plugin to stop working? Maybe someone else might know.
I'm guessing explorer cached the page. Did you try and delete history and cookies? Just checking you were access the page with HTTP://ipaddressort right?
Sent from my LG-D852 using Tapatalk