cannot release with DHCP

G

Guest

Both machines are running Windows 2000 and when I type "ipconfig/release" I get the following error:

"All adapters bound to DHCP do not have IP addresses. The addresses were automatically configured and can not be released."

What can be the cause and how do I fix it? I'm using a Netgear wireless.
 
L

Lanwench [MVP - Exchange]

It means you aren't getting DHCP-assigned addresses - you're getting
auto-configured addresses (APIPA) because the workstations weren't getting a
response from the DHCP server.

Assign yourself a static IP (use an Ethernet cable if your wireless isn't
working yet), go into the netgear's web admin tool, and check your DHCP
settings in there.
 
G

Guest

Greetings Lanwench,

My ISP doesn't provide static ip addresses. So, is it still possible to enter some addresses to get it to work? How would I go around this situation if not? Please give me some details on this as soon as you can. Steps would be helpful if you don't mind.

Thanks

----- Lanwench [MVP - Exchange] wrote: -----

It means you aren't getting DHCP-assigned addresses - you're getting
auto-configured addresses (APIPA) because the workstations weren't getting a
response from the DHCP server.

Assign yourself a static IP (use an Ethernet cable if your wireless isn't
working yet), go into the netgear's web admin tool, and check your DHCP
settings in there.
 
L

Lanwench [MVP - Exchange]

If you're using a router that does NAT, which your Netgear should, you can
assign yourself a static IP on the internal IP range. It's usually
192.168.0.x on Netgear if I remember correctly (check your documentation).

The public IP can be dynamic - doesn't make a difference here.
Greetings Lanwench,

My ISP doesn't provide static ip addresses. So, is it still possible
to enter some addresses to get it to work? How would I go around this
situation if not? Please give me some details on this as soon as you
can. Steps would be helpful if you don't mind.

Thanks

----- Lanwench [MVP - Exchange] wrote: -----

It means you aren't getting DHCP-assigned addresses - you're
getting auto-configured addresses (APIPA) because the
workstations weren't getting a response from the DHCP server.

Assign yourself a static IP (use an Ethernet cable if your
wireless isn't working yet), go into the netgear's web admin
tool, and check your DHCP settings in there.
Both machines are running Windows 2000 and when I type
"ipconfig/release" I get the following error:
addresses > were automatically configured and can not be
released." >> What can be the cause and how do I fix it? I'm
using a Netgear > wireless.
 
L

Lanwench [MVP - Exchange]

Probably not necessary. The Netgear should be doing DHCP by default - if it
isn't, assigning a static IP on the private NAT range should allow you to
get to the Netgear and see what the problem is.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

IP release 2
ipconfig /release does not release adapter 1
dhcp not working 6
NIC not able to release IP address 3
dhcp problem? 3
DHCP server unreachable 6
Similar DHCP conflict 1
DHCP problems in Win2000 1

Top