Why do all Dahua camera IPs default to 192.168.1.XXX?

OK, so I didn't crawl under the desk and got it configged anyway. I just reset the IP on my LAN to .1 to work on the camera and switched it back when done. The config tool, V4, didn't work. It never went to a login screen, just directly to the IP address page and failed. I assume that is because it was not logged in. I logged into the camera directly to set the IP. When doing that it wants to add a plug-in, I was using IE11 on Win7/64, and Norton detected some malware in the file. I was able to set it up with no problem, but live view ain't a happening thing under IE11 given that malware warning. I just tried FF and got the same message when installing the plugin.

So far, I like the camera, but Dahua software leaves a lot to be desired.

Use Smart PSS for your live view. I use IE v11.729.15063.0 exclusively and only to access the cameras and it works just fine with the plugin
 

Attachments

  • IE.PNG
    IE.PNG
    320.9 KB · Views: 25
It may work with the plugin, but the plugin seems to have some malware in it. No thanks.
 
It may work with the plugin, but the plugin seems to have some malware in it. No thanks.

Because you already say the name of the malware: Norton...

Mcfee and others didn’t see any malware...


Verzonden vanaf mijn iPhone met Tapatalk
 
Maybe they're blind?
 
Are you absolutely positive about that? Are you certain that no one has inserted some malicious code since the last time you installed that plugin? I have enough ways to view the video stream without using the cameras web interface. As long as I can control the camera is all that I am interested in. I am not interested in pissing contests about AV software so take your crap somewhere else.
 
It may work with the plugin, but the plugin seems to have some malware in it. No thanks.
With norton you need to read the description of the warning....it flags files that are new to its database...upload the plugin to virustotal and you will see its fine.
 
Because you already say the name of the malware: Norton...

Mcfee and others didn’t see any malware...


Verzonden vanaf mijn iPhone met Tapatalk
Norton is great and has been since 2010.....you are simply stuck in your old ways...as I explained the flag was likely because it was new to the database and the user simply didnt read the exact warning.
 
I am stuck in my old ways, too. I've used Norton/Symantec since the 90's when I got into networking. I did look at the information and it identifies it as "WS.reputation.1". I will admit I didn't do a search for that particular piece of malware.

As I said, there are many other ways to view the video stream besides the plugin for the web interface. Control of the camera functions is not effected at all so it's not a big deal. All I am trying to do is report what happened when I tried installing that plugin for the edification of others who may encounter the same thing. Looking at the reported malware found, it is based on a lack of "reputation" in the Norton database and is probably safe to install.
 
I am stuck in my old ways, too. I've used Norton/Symantec since the 90's when I got into networking. I did look at the information and it identifies it as "WS.reputation.1". I will admit I didn't do a search for that particular piece of malware.

As I said, there are many other ways to view the video stream besides the plugin for the web interface. Control of the camera functions is not effected at all so it's not a big deal. All I am trying to do is report what happened when I tried installing that plugin for the edification of others who may encounter the same thing. Looking at the reported malware found, it is based on a lack of "reputation" in the Norton database and is probably safe to install.
That is not malware...that is simply saying that there are not enough folks in their database using that file, which makes sense...
 
  • Like
Reactions: awsum140
I agree, it's not malware just not heavily used. Norton should be more clear with the warning message and offer a choice when this kind of thing pops up. A weakness on their part, at least to me. On the other hand I'd rather be warned than not. Niche software can present problems to virus protection schemes.
 
CAn you view these cameras via their web interface somehow with IE or Edge any more? Whenever I have tried it says, "dpownload plugin" and it is for Chrome. Then when I try to view in Chrome I still cannot and it tells me I have to launch the chrome plug-in separately and only then with that plugin can I see the camera in its web interface.
Are there other ways or browsers the camera's web interface will work with anymore?
 
I've found Pale Moon to be my goto browser working on Dahua equipment nowadays. Seems to have very few problems. Thanks to whomever it was here on IPCT for suggesting it ;)
 
  • Like
Reactions: awsum140
+1 for Pale Moon. As for the issues with using lots of x.x.1.x equipment on an x.x.0.x network, why not switch the router to 1.x? Easy peasy. Asus routers, for one, come this way anyway.
 
CAn you view these cameras via their web interface somehow with IE or Edge any more? Whenever I have tried it says, "dpownload plugin" and it is for Chrome. Then when I try to view in Chrome I still cannot and it tells me I have to launch the chrome plug-in separately and only then with that plugin can I see the camera in its web interface.
Are there other ways or browsers the camera's web interface will work with anymore?

Chrome with the IE TAB extension installed works fine.
 
+1 for Pale Moon. As for the issues with using lots of x.x.1.x equipment on an x.x.0.x network, why not switch the router to 1.x? Easy peasy. Asus routers, for one, come this way anyway.
I'd I change my router t0 1.x won't I have to change everything att a h3d to it to 1.x?

I have an old Asus router I ma not using. If it is 1.x and Ixonnect a camera to it then plug the asus into my existing router would that work or does that nor make any sense?
Sorry if stupod questions but I am not very network savvy.
 
I'd I change my router t0 1.x won't I have to change everything att a h3d to it to 1.x?

Hard to say, but if everything is currently connected by dhcp then everything will automagically connect with 1.x. You could also lock yourself out of the internet and LAN on your main computer after you change the router if the computer is set to a static IP of 0.x.

If you have the old Asus router you could always plug everything into it and make sure your network functions normally for a while before making the plunge of changing your new 0.1 router to 1.x. This would include things like network printers, smart TVs, etc.

As far as plugging the Asus into your existing router and plugging cameras into it, to be honest I'm not sure what would happen. Some routers automatically change their IP ranges to something completely different when daisychained like that. What you COULD do is plug new cams into the Asus as a standalone router not plugged into anything and connect to the Asus via WiFi from a tablet or whatever, change the cam's IP to 0.x, and then plug the cam into your main network. If you really want a secure network with no outside access, plug all of the camera equipment into the Asus and don't connect it to the internet at all. Run all of your computers, phones, tablets etc from the other new router. What's not connected to the internet can't be hacked.
 
  • Like
Reactions: awsum140
Give each ip range a own workgroup... ip via DHCP. Done


Verzonden vanaf mijn iPhone met Tapatalk
 
Give each ip range a own workgroup... ip via DHCP. Done


Verzonden vanaf mijn iPhone met Tapatalk
Sounds simple...but how do I do that?

What typically is the fixed IP for a Dahua camera anyway?
I tried switching my computer to1.x and ran the tool but not finding any cameras.
 
Sounds simple...but how do I do that?

What typically is the fixed IP for a Dahua camera anyway?
I tried switching my computer to1.x and ran the tool but not finding any cameras.


Ip of the camera:
192.168.1.108
255.255.255.0
192.168.1.1

Ip of your pc:

192.168.1.10
255.255.255.0
192.168.1.1

You have also set the range of the camera (192.168.1.0/255(24)) in the config tool... you have to tell him where to look..


But in 99,9% of all cases you can directly Ping the camera:

Windows + R/ cmd / Enter

Ping 192.168.1.108 -t

When you see a response then close the window.

In IE or other browsers you can now connect directly to the camera by filling in the address bar with http://192.168.1.108 and hit enter. Then you will see a login page. From the you follow the manual.

The part with the different workgroups... we did it by a customer of us which have a really big network.

A 24 port switch connects 512 pc’s and other network devices in different networkranges up to 6 vlans...
By building vlans and workgroup we were able to connect seceral ip-addresses in various combinations up to 1 new virtual network adapter.. thats how we did it...
The workung time: 270 hours....



Verzonden vanaf mijn iPhone met Tapatalk
 
  • Like
Reactions: nbstl68