Accessing a device not on the sub-net

  • Thread starter Thread starter mike.james
  • Start date Start date
M

mike.james

We just got an IP camera that for some reason doesn't use DCHP by default.
The instructions say that you have to change the subnet of a workstation to
its default subnet,
then talk to it to change its IP and then change the workstation back to its
original IP.

This isn't much fun.
Is there any way to change the routing table to allow the IP camera to be
accessable on the
network even though its on a different subnet?
mikej
 
mike.james said:
We just got an IP camera that for some reason doesn't use DCHP by default.
The instructions say that you have to change the subnet of a workstation to
its default subnet,
then talk to it to change its IP and then change the workstation back to its
original IP.

This isn't much fun.
Is there any way to change the routing table to allow the IP camera to be
accessable on the
network even though its on a different subnet?
mikej
Click to expand...

Click the "Advanced" button in the IP setup panel of your PC,
then give it a secondary address that lies in the camera's subnet.
 
Pegasus (MVP) said:
Click the "Advanced" button in the IP setup panel of your PC,
then give it a secondary address that lies in the camera's subnet.
Click to expand...

Thanks - this simple solution hadn't occured to me at all nor to the
manufacture.
Is there a way of achieving the same result for all the PCs on the subnet?
After all the camera has a tendency to rest to its assigned IP address..
mikej
 
mike.james said:
Thanks - this simple solution hadn't occured to me at all nor to the
manufacture.
Is there a way of achieving the same result for all the PCs on the subnet?
After all the camera has a tendency to rest to its assigned IP address..
mikej
Click to expand...

Maybe I'm missing something but the obvious solution
would be to give each PC a secondary IP address.
 
Pegasus (MVP) said:
Maybe I'm missing something but the obvious solution
would be to give each PC a secondary IP address.
Click to expand...

No not missing anythng - I just wondered if there was a "central" way to do
the job rather than having to reconfigure every machine on the subnet.
mikej
 
mike.james said:
No not missing anythng - I just wondered if there was a "central" way to do
the job rather than having to reconfigure every machine on the subnet.
mikej
Click to expand...

I didn't see the word "central" in your previous question. There is
a way but there is a bit of work involved in learning the tricks.
You can use psexec.exe (www.sysinternals.com) do run the
following command from a central PC on each and every PC.
Here is a sample that sets a primary address - you must
experiment with it until you find out how to set a secondary
address.

netsh interface ip set address "Local Area Connection" static 125.187.7.56
255.0.0.0

See also http://support.microsoft.com/default.aspx?scid=kb;EN-US;242468
 
The need for a one time connection to a camera or other device to assign it
an address in your networks subnet is not at all unusual. Maybe I'm missing
something, but why on earth would you want to change all your workstations
rather than using the secondary address on one computer to log into the
camera, change its address and be done with it?
--
 
(e-mail address removed)
GTS said:
The need for a one time connection to a camera or other device to assign
it an address in your networks subnet is not at all unusual. Maybe I'm
missing something, but why on earth would you want to change all your
workstations rather than using the secondary address on one computer to
log into the camera, change its address and be done with it?
--
Click to expand...

The answer is in your final line - and be done with it.
The camera in question has a tendency to reset itself to the default IP
address after a power down.
The camera is in a remote location and I don't want to have to keep on
reconfiguring it.

Hence a robust solution to the problem would be to leave the camera on its
default
and somehow route the off subnet camera to the usual subnet.
If the camera would keep its setting though power downs etc then I would
agree that
a one off config would be fine.
mikej
 
mike.james said:
(e-mail address removed)


The answer is in your final line - and be done with it.
The camera in question has a tendency to reset itself to the default IP
address after a power down.
The camera is in a remote location and I don't want to have to keep on
reconfiguring it.

Hence a robust solution to the problem would be to leave the camera on its
default
and somehow route the off subnet camera to the usual subnet.
If the camera would keep its setting though power downs etc then I would
agree that
a one off config would be fine.
mikej
Click to expand...
That's a surprisingly bad design. Webcams I've worked with store the config
in flash memory and I've never had a problem losing it. I certainly see
the sense of your approach now.
 
GTS said:
That's a surprisingly bad design. Webcams I've worked with store the
config in flash memory and I've never had a problem losing it. I
certainly see the sense of your approach now.
Click to expand...

Its got a flash memory but when you set it to DCHP a power outage causes it
to restart and
if it can't find the DCHP server in time it resets itself to factory
default.....
One solution would be to give it a fixed IP but I thought I'd expore ways of
just letting it keep
the factory default and still be accessible to the network.
I was really thinking of some sort of addition to the router table - but I
can't see how to do it as there
isn't a gateway involved.
mikej
 
Its got a flash memory but when you set it to DCHP a power outage causes
it
to restart and
if it can't find the DCHP server in time it resets itself to factory
default.....
One solution would be to give it a fixed IP but I thought I'd expore ways
of just letting it keep
the factory default and still be accessible to the network.
I was really thinking of some sort of addition to the router table - but I
can't see how to do it as there
isn't a gateway involved.
mikej
Click to expand...
I see. I generally prefer to assign static IP addresses for non-workstation
network devices (webcams, WAPs, net printers) for a number of reasons
including most reliable access to browser based configuration pages.
 
Back
Top