Fun with Local IP Addresses
- From: "W. Watson" <wolf_tracks@xxxxxxxxxxx>
- Date: Fri, 17 Nov 2006 02:33:19 GMT
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
--
"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>
.
- Follow-Ups:
- Re: Fun with Local IP Addresses
- From: dominictiberio
- Re: Fun with Local IP Addresses
- From: prakashbisth@xxxxxxxxx
- Re: Fun with Local IP Addresses
- From: Pegasus \(MVP\)
- Re: Fun with Local IP Addresses
- Prev by Date: Define preferred wireless networks in Group Policy
- Next by Date: Re: Fun with Local IP Addresses
- Previous by thread: Define preferred wireless networks in Group Policy
- Next by thread: Re: Fun with Local IP Addresses
- Index(es):
Relevant Pages
|
