Changing subnet mask makes no difference can still see them so still messes up the sw Thx though
----------------------------- Bambi Saastad office 952-402-7888 cell 612-963-1478 On Mon, Aug 17, 2015 at 2:25 PM, Melvin Backus <[email protected]> wrote: > I’m not sure it’ll help, but try changing the mask on that interface. > Given the IPs I’d try 255.255.255.252 and see what you get. If the other > cameras are on a 10.x.x.x network, it sounds like the program is scanning > all interfaces and searching. Maybe you can disable discovery, etc., > > > > -- > There are 10 kinds of people in the world... > those who understand binary and those who don't. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Bambi J Saastad > *Sent:* Monday, August 17, 2015 3:09 PM > *To:* ntsysadm <[email protected]> > *Subject:* [NTSysADM] IP Camera issue > > > > Hoping someone else has seen this and has idea's > > I have a new tool > > It has 3 NIC's > > 1-Disabled > > 2- on the LAN IP 10.x.x.x SubMask 255.255.240.0 Gateway 10.x.x.x > > 3-Connects to camera on the tool 192.168.1.1 Camera is 192.168.1.3 > 255.255.255.0 no gateway > > > > The software on the tool cannot run because it can see other IP cameras > out on the network and it is stupid software that has issues with multiple > cameras > > The camera's it sees are it's own 192.168.1.1 and others in a different > subnet of 10.1.x.x > > I do not know where these other camera's are so without spending lots of > time trying to find them.... > > > > The tool cannot access those other camera's, just see them > > Is there any way to block seeing those other camera's? > > Even if I remove my gateway settings it still see's those camera's > > The vendor is at a loss on a solution. > > > > TIA > > B >
