IP Autoconfig problems. Class B IP ??

[Bakkoda]

Here is my dilemna... I have a small network at home with three computers. The problem is one of my newer computers has "Obtain IP automatically" and when it does it grabs a class B IP of "169.24.xxx.xxx" or something along those lines and I have no internet or network access. Now when I go into the registry (Loc. Machine\System\CurrentControlSet\Services\VxD\DHCP \), the IPAutoConfigurationEnabled key is gone. And in the subfolder of the above reg entry (\DhcpInfo00\) there is a IPAutoconfigurationAddress key equal to the "169.24.xxx.xxx". After enabling AutoIP and setting the IPAutoconfigurationAddress value to "0.0.0.0", winipcfg.exe crashes after trying to renew my IP. How the hell do I get my normail IP back? All my other machines are set uop exactly like this one and they all have a "66.66.24x.xxx" IP. Why is this one screwing up?

[Jim9999]

The 169.254.y.z address is what you should expect using AutoIp Addressing in 2000, Win98SE, and Me. It's working properly.

Getting that address means the computer didn't get a response from a DHCP Server or DHCP Allocator on your network. It therefore gave itself an address in the proper range.

You said your computer got that address and you couldn't get to the Internet. But you didn't say how you expected to be able to. Are you using ICS? Or a router? Proxy?

The other machines sound like they may be getting addresses from a cable ISP. Is that right?

You'll need to provide a little more info than you have, but it doesn't sound too complex.

The first thing I'd do is to set the registry back to the way it was and get out of the habit of poking around in there unless you know exactly what you are doing. It sounds like the computer was working as it should before you edited that key.

[This message has been edited by Jim9999 (edited 08-09-2001).]

[Bakkoda]

Actually the reason I poked around in the registry is because the machine was not working properly. Even with the AutoIP I had no internet or network access.
I have a 4 port hub connected to a cable modem (no proxy). I turned on the machine that was giving me trouble and noticed I had no internet access. I then opened up winipcfg to maybe renew the IP and noticed that the IPAutoconfig had taken over. Only then did i try to reinstate the original reg entries. I just restored the original reg entries and still no ping or anything.


[This message has been edited by Bakkoda (edited 08-09-2001).]

[Bakkoda]

Didn't mean to sound hostile. I guess i'm just pissed off.

I have the computer directly hooked up to the modem right now. Still no response from DHCP server. My guess is to uninstall and pull out the NIC card and then reinstall it. I will keep everyone posted I guess.

[DVNT1]

It could be your physical cabling that is the problem. Easiest way may be using a known good computer on that cable. See if it still gets an IP when you release/renew it.

If using Windows PCs then you can run netdiag on that computer and also on another to test [NIC, NIC driver, and cabling] regardless of the protocols installed.

[Jim9999]

You never said if this computer had connectivity in the past or not. I took it as though it was a new box on the network. Is that right?

If it was never on the network, or never had Internet connectivity, then it sounds like the was working properly. You won't have IP network connectivity between a machine on 169.254 and others on 66.

You can't just put a cable modem on a hub and have all computers access it. It doesn't work that way.

For that to work, you have to have an IP address assigned to you by the cable ISP for each computer you want to access the Internet.

If you have 3 computers, you need to have 3 IP addresses assigned to you from the ISP. If you have this, you didn't say.

You also need to follow the ISP's instructions for connecting the box, but that's usually just a matter of changing the NetBIOS name to that assigned to you by the ISP. That will automatically change the host name of the box.

Then use DHCP, as you have set.

If all has been done, then tshoot by connecting this computer to the cable modem directly (take the hub out of the picture) and see if that works.

Like I said, though, it doesn't sound like yo have a computer problem. It sounds like the computer wasn't assigned an IP address and therefore assigned itself one (as it should have). And based on that, you should not have connectivity (wich you didn't).

How many IP addresses are you paying the ISP for per month, and do you have that many unique names given by the ISP?

[This message has been edited by Jim9999 (edited 08-09-2001).]

[mtpros]

Try verifying that the port that your computer is plugged into on the hub is working properly, by plugging one of your machines that is working into that port and then release and renew your ip address again and then see what the IP of that machine is and if able to surf. It might not be able to contact the DHCP server due to a bad port.

[This message has been edited by mtpros (edited 08-09-2001).]

[Bakkoda]

In the past the machine has had acces to the internet. Its original IP address was "66.66.xxx.xxx" and all the computers had connectivity between them. With my hub and cable modem, I had every computer connected to each other and the internet. I have checked to see if it was the port on my hub and it was not.

I guess what I'm trying to say is originally each computer had a seperate IP (I played LAN games with all three) beginning with the "66.66" and now this machine has no connectivity and has a class B IP. How do I get it back to normal?

In the future, please do not assume that if a person asks a question that they don't friggin know their way around a computer. You guys can be a little intimidating.

[Jim9999]

The only assumptions I made were about your computer configuration. They were made due to lack of detail in the original post. The answer I gave was meant to address the non-connectivity issue along with the actions taken by you.

I don't assume friggin knowledge - one way or the other. From everything you've stated to this point, your issue does not sound like a misbehaving computer to the point the registry editing was necessary. That was where that comment came from.

My suggestions may help. I'd try hooking the computer to the cable modem directly and make sure the network settings are in line with what the ISP needs.

Good luck.

[Bakkoda]

I guess the problem was my ISP. They must have gotten wise to the fact that I had been using 3 IP and tried to limit them. After plugging the nonfunctional computer directly into the router, renewing and releasing the IP, and then plugging it back into the router, all is good again.

Thanks for your help.