General discussion

Locked

Releasing IP

By fernando.rubiano ·
I have a cable modem, I was able to access the web with no problems. Yesterday started having problems, called Cable provider told me to release the ip using the ipconfig /release but it did not work, they told me I need a new NIC I installed it butsame thing. the message that I get when executing the command is: "all adapters bound to DHCP do not have DCHP addresses. The Addresses were automatically configured and cannot be release" I am unable to get to the web.
FYI- I did installed a different NIC, also unistalled the TCP/IP protocol and still cannot release. I am running win 200 pro.

Thank you

This conversation is currently closed to new comments.

23 total posts (Page 1 of 3)   01 | 02 | 03   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Releasing IP

by JustAnAdmin In reply to Releasing IP

From the sound of that error message, you may not have had an IP address to release. I would suggest first running the ipconfig without the /release after it. That will show you what address is currently assigned (it may not have an IP address at all).

If you do get an IP address, try the ipconfig /release command again. If you get the same error, try ipconfig /renew and see what happens. If you are still having problems, please post the error messages here and I will try to help.

Good luck!

Collapse -

Releasing IP

by fernando.rubiano In reply to Releasing IP

When I do the ipconfig I get a 169. address. (which is local). Besides unistalling the tcp/ip protocol is there something else I need to unistall? FYI- I do have norton antivirus, and when I deleted the tcp/ip protocol it gave me an error, that no settings were found for tcp/ip.

Collapse -

Releasing IP

by VinnyD In reply to Releasing IP

Your right that 169 address means that no dhcp server was found to get an ip address from.

Are you using a cable router? Is so the DHCP server in the router is not on or not working.

If you do not have a router, then the W2K machine is not getting an IP address from the cable provider.

This kind of error can also mean something very simple! You 10-base-T cable from the computer to the cable modem is not plugged in all the way.

Ethernet cables can look like they are plugged in but are not locked in place so that the pins inside the connnector are not making contact.

Collapse -

Releasing IP

by fernando.rubiano In reply to Releasing IP

I'm not using a cable router, I'm only using the cable modem. I did change the NIC for testing purposes. I am also able to ping my 129.0.0.1 I will try another 10-base-t cable to see if that works.

Collapse -

Releasing IP

by jose_12650 In reply to Releasing IP

Try powering off your cable modem and restart your computer. Try connecting to the internet. If this does not work, issued a command, ipconfig /flushdns, then ipconfig /registerdns then ipconfig /renew.

Collapse -

Releasing IP

by jose_12650 In reply to Releasing IP

Off course after powering off your cable modem you have to power it back on, then restart your system.

Collapse -

Releasing IP

by fernando.rubiano In reply to Releasing IP

Tried did not work. Please see Answer 6 (yes too early in the morning) Thanks

Collapse -

Releasing IP

by fernando.rubiano In reply to Releasing IP

I did still did not work.
It is something else preventing me from picking up an IP. I tried a different NIC and same results, I also tried using the USB (took out the NIC completely) and still same thing. I checked the event viewer and here are the messages that I'm getting. (for the DCOM microsoft is not too clear on how to fix):
Event Type: Error
Event Source: DCOM
Event Category: None
Event I 10005
Date: 4/7/2003
Time: 9:47:58 PM
User: NT AUTHORITY\SYSTEM
Computer: RUBIANO-FR
Description:
DCOM got error "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. " attempting to start the service BITS with arguments "" in order to run the server:
{4991D34B-80A1-4291-83B6-3328366B9097}

Event Type: Warning
Event Source: Dhcp
Event Category: None
Event I 1006
Date: 4/7/2003
Time: 9:46:38 PM
User: N/A
Computer: RUBIANO-FR
Description:
Your computer was unable to automatically configure the IP parameters for the Network Card with the network address 00095B06B1EA. The following error occurred during configuration: The requested service provider could not be loaded or initialized. .
Data:
0000: 7a 27 00 00 z'..

Collapse -

Releasing IP

by TechKid In reply to Releasing IP

Your problem has nothing to do with DNS so flushing your local DNS cache is irrelevant. Besides, it gets flushed after every reboot.

You won't be able to release the 169 IP address, that's why you're getting that message. That's normal.

One note: Most cable modems remember the last MAC address thats connected to them. If the modem is still remembering your old NICs MAC address it won't let the new NIC connect. You need to power off the modem for 15min to clear the modems memory.

Of course, make sure all appropriate lights are lit on the modem when it comes back up.

Collapse -

Releasing IP

by fernando.rubiano In reply to Releasing IP

please see answer six (I added an answer instead of an actual reply) thanks

Back to Windows Forum
23 total posts (Page 1 of 3)   01 | 02 | 03   Next

Related Discussions

Related Forums