Fun with Local IP Addresses

  • Thread starter Thread starter W. Watson
  • Start date Start date
W

W. Watson

I've been running two machines on Network Neighborhood, an XP Pro machine in
the house and W2K machine in my garage. I have a 5 port Linksys hub in the
garage. Usually, I do pretty well working over the local network, but that's
changed in the past few days.

I received a device that uses the ethernet for a remote camera outside from
the garage. It's at IP address 10.0.0.50, so I plugged it into the hub. The
mfger says that I should use IP address 10.0.0.2 to access the device from
my machine in the garage. Previously I had been using 192.168.0.1, and
192.168.0.3 in the house (XP Pro). Both have a subnet mask of 255.255.255.0.
All was fine before the new device entered the picture. I set the IP address
on the W2K machine to 10.0.0.2 via the Network icon on Control Panel.

I have gotten the new device to work, but only by disconnecting the hub from
garage machine and using a crossover cable directly to the garage PC. When
the hub is in place with the device plugged into it (or without it), I
cannot get the two PCs to talk to one another. I figured maybe I ought to
put 10.0.0.2 back to 192.168.0.1. Going back through the Network icon via
properties, I used the "Use IP address" entry to enter the old IP address.
When I started to close the dialog, I got an interesting msg:

IP address you have created is already assigned to another adapter,
3ComEtherLinkXL PD. For completeness PC ... is hidden from the connection
folder. Do you want to enter this adapter is the list IP addresses in the
Advanced Dialog now?

Well, I was stumped, so I said yes. That seemed OK until I tried to exit
from the Network dialog. I finally cancelled, and when I got back in the
look at the properties again, the IP address was back to 10.0.0.2.

So what's going on, and how do I get out of the predicament I'm in? That is,
I can't get the two machines to talk, and the new device doesn't seem to
want to work off the hub. The mfger supplied the crossover cable for a
direct connect to the ethernet card, but my guess is that it should be used
from the hub too, instead of a straight through cable.

Wayne T. Watson (Watson Adventures, Prop., Nevada City, CA)
(121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
Obz Site: 39° 15' 7" N, 121° 2' 32" W, 2700 feet

Wayne T. Watson (Watson Adventures, Prop., Nevada City, CA)
(121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
Obz Site: 39° 15' 7" N, 121° 2' 32" W, 2700 feet
--
"The only person that you can trust is someone who
looks you in the eye, and says, 'I'm not voting for you.'"
-- Old political saying

Web Page: <home.earthlink.net/~mtnviews>
 
I've been running two machines on Network Neighborhood, an XP Pro machine in
the house and W2K machine in my garage. I have a 5 port Linksys hub in the
garage. Usually, I do pretty well working over the local network, but that's
changed in the past few days.

I received a device that uses the ethernet for a remote camera outside from
the garage. It's at IP address 10.0.0.50, so I plugged it into the hub. The
mfger says that I should use IP address 10.0.0.2 to access the device from
my machine in the garage. Previously I had been using 192.168.0.1, and
192.168.0.3 in the house (XP Pro). Both have a subnet mask of 255.255.255.0.
All was fine before the new device entered the picture. I set the IP address
on the W2K machine to 10.0.0.2 via the Network icon on Control Panel.

I have gotten the new device to work, but only by disconnecting the hub from
garage machine and using a crossover cable directly to the garage PC. When
the hub is in place with the device plugged into it (or without it), I
cannot get the two PCs to talk to one another. I figured maybe I ought to
put 10.0.0.2 back to 192.168.0.1. Going back through the Network icon via
properties, I used the "Use IP address" entry to enter the old IP address.
When I started to close the dialog, I got an interesting msg:

IP address you have created is already assigned to another adapter,
3ComEtherLinkXL PD. For completeness PC ... is hidden from the connection
folder. Do you want to enter this adapter is the list IP addresses in the
Advanced Dialog now?

Well, I was stumped, so I said yes. That seemed OK until I tried to exit
from the Network dialog. I finally cancelled, and when I got back in the
look at the properties again, the IP address was back to 10.0.0.2.

So what's going on, and how do I get out of the predicament I'm in? That is,
I can't get the two machines to talk, and the new device doesn't seem to
want to work off the hub. The mfger supplied the crossover cable for a
direct connect to the ethernet card, but my guess is that it should be used
from the hub too, instead of a straight through cable.

Wayne T. Watson (Watson Adventures, Prop., Nevada City, CA)
(121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
Obz Site: 39° 15' 7" N, 121° 2' 32" W, 2700 feet

Wayne T. Watson (Watson Adventures, Prop., Nevada City, CA)
(121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
Obz Site: 39° 15' 7" N, 121° 2' 32" W, 2700 feet
Click to expand...

As long as you have all of your class "c" IP addresses in the same
range you should be okay. If the Camera must be 10.0.0.50 then make
the router 10.0.0.1 and use the router's DHCP for assigning addresses
10.0.0.10 - 10.0.0.40 (I assume the computers are set to "obtain an IP
address automatically")

If you can change the IP address on the camera then simply make it
192.168.0.100 and that should work for you.

-- Zadok
 
Zadok said:
As long as you have all of your class "c" IP addresses in the same
range you should be okay. If the Camera must be 10.0.0.50 then make
the router 10.0.0.1 and use the router's DHCP for assigning addresses
10.0.0.10 - 10.0.0.40 (I assume the computers are set to "obtain an IP
address automatically")

If you can change the IP address on the camera then simply make it
192.168.0.100 and that should work for you.

-- Zadok
Click to expand...
My knowledge of what's going on here is pretty skimpy and I manage to get by
using touch and feel. I'm pretty sure that I'm assigning IP addresses in the
case of the two computers. Probably about the time I decided to install a
network some years ago, I found that one had an address of 192.168.0.x, so
decided to follow in the same footsteps using 192.168.0.x for each, at one
time 3, computers I had.

DHCP? Where do I find that? That is, what MS OS (Network Neighborhood)
facility do I use for it? However, ny first concern is why I get the
message? My gut tells me that this is the way to chance the address of the
ethernet card in my PC.

Why the mfger would want me to change it from what I had been using before
seems odd. That is, I would think if I had left it at 192.168.0.1 that the
PC would still know where it is. An address is an address, or maybe not? In
the wide world of networks, it seems as though 150.0.3.2, say, could
communicate with 403.22.7.55 (forgetting about some permissions or whatever
that keeps someone from invading an address).


Wayne T. Watson (Watson Adventures, Prop., Nevada City, CA)
(121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
Obz Site: 39° 15' 7" N, 121° 2' 32" W, 2700 feet
--
"The only person that you can trust is someone who
looks you in the eye, and says, 'I'm not voting for you.'"
-- Old political saying

Web Page: <home.earthlink.net/~mtnviews>
 
My knowledge of what's going on here is pretty skimpy and I manage to get by
using touch and feel. I'm pretty sure that I'm assigning IP addresses in the
case of the two computers. Probably about the time I decided to install a
network some years ago, I found that one had an address of 192.168.0.x, so
decided to follow in the same footsteps using 192.168.0.x for each, at one
time 3, computers I had.

DHCP? Where do I find that? That is, what MS OS (Network Neighborhood)
facility do I use for it? However, ny first concern is why I get the
message? My gut tells me that this is the way to chance the address of the
ethernet card in my PC.

Why the mfger would want me to change it from what I had been using before
seems odd. That is, I would think if I had left it at 192.168.0.1 that the
PC would still know where it is. An address is an address, or maybe not? In
the wide world of networks, it seems as though 150.0.3.2, say, could
communicate with 403.22.7.55 (forgetting about some permissions or whatever
that keeps someone from invading an address).


Wayne T. Watson (Watson Adventures, Prop., Nevada City, CA)
(121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
Obz Site: 39° 15' 7" N, 121° 2' 32" W, 2700 feet
Click to expand...

The addresses need to be in the same range. I misread your msg
thinking that you had a router. You say you have a hub so the
addresses need to be in the same range 192.168.0.x or in the case of
the camera which is at either 10.0.0.2 or 10.0.0.50 change the
addresses of your computers to 10.0.0.10 and 10.0.0.20. Since you got
an error using 10.0.0.2 I'd say that that is the address of the
camera.

-- Zadok
 
Zadok said:
The addresses need to be in the same range. I misread your msg
thinking that you had a router. You say you have a hub so the
addresses need to be in the same range 192.168.0.x or in the case of
the camera which is at either 10.0.0.2 or 10.0.0.50 change the
addresses of your computers to 10.0.0.10 and 10.0.0.20. Since you got
an error using 10.0.0.2 I'd say that that is the address of the
camera.

-- Zadok
Click to expand...
Thanks. I'll give it a go.


Wayne T. Watson (Watson Adventures, Prop., Nevada City, CA)
(121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
Obz Site: 39° 15' 7" N, 121° 2' 32" W, 2700 feet
--
"The only person that you can trust is someone who
looks you in the eye, and says, 'I'm not voting for you.'"
-- Old political saying

Web Page: <home.earthlink.net/~mtnviews>
 
Back
Top