Release in winipcfg not working

[sverma68]

I am trying to install a cable modem to my system. I have never had a network card installed in my machine. I purchased a network card and have installed it in my computer. My cable company requires connecting to a DHCP Server. This is where I run into a problem. I cannot get the "Autoconfiguration IP Address" to release in the "winipcfg" program. Whenever I hit the release or release all button, nothing changes (They don't all goto 0.0...) The default IP address remains 169.....)
I have tried everything including formatting my hard drive and re-installing Win98 SE. I have also tried other brands of network cards with the exact same problem.

All Diagnostics, PING checks seems to work fine. I have no conflicts. The green light on the ethernet card works. I have tried different PCI slots as well.

I have an ASUS A7v133 motherboard. I have also installed the latest 4 in 1 drivers with no luck.

Please help. this is driving me crazy

Thanks

[Jim9999]

It sounds like it's working as it should. The address it is keeping is the AutoIPAddress it assigned itself when it determined that there was no DHCP server or allocator available. Releasing to 0.0.0.0 would not make sense, so it didn't do it.

You can disable AutoIP, but that isn't likely to fix the issue. 98SE waits to see if there is a response via DHCP, and only assigns itself an IP address as a last resort.

Is your Ethernet card plugged directly into the cable modem, and are you sure the computer is named exactly as assigned by your cable ISP? If the computer name is incorrect, the cable ISP will not assign it an address.

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

[skybolt_1]

Hey i am having this same exact problem, only difference is that I am in a dorm (Umass Lowell to be exact). My computer worked fine for a week, then I decided to swap out the network card to another computer which i wanted to download stuff to. Right after, I got an error saying that my IP was conflicting with a hardware address. I tried to release and renew the IP but the computer doesnt respond to the release and the renew makes it crash. What should I do?

[skybolt_1]

^bump^ does anyone have input?

[cadetstimpy]

First, in winipcfg are you working with the real NIC adaptor or the PPP adaptor?

Second, when an adaptor is running DHCP (even the PPP adaptor) and there's no DHCP service present for that adaptor the address will default to 169....etc as you mentioned. A release of this address will fail because Windows knows it didn;t obtain one in the first place.

[sverma68]

THanks for the reply, There is a DHCP server. The @home cable modem people have that setup in their software. I know other people with @home in my area that are not having any problems and have the same setup as me.

I guess the question comes down to whether or not the Autoconfig IP address should all go to 0.0.0... when the release button is pushed. I believe this is independent of the cable modem or the network. I am surprised that the @home people have not asked for my Network Adapter number.

[pwb0921]

Sounds like you are not really connected at all, and windows is going with the default. If this is the case, it appears to hang for awhile. Try pinging your DNS servers, gateway, pretty much any outside IP you can get your hands on. Most likely will fail. If it does, then you are not connected at all. Call up the techsupport at @home. Be prepared to wait awhile, I use them too btw. Have them ping your modem to see if it is online, if it is, ask them for the IP address of it. Also get some IPs of the DHCP server, some DNS servers, etc. Your cable connecting your computer to the modem might be bad also, try replacing it.