The lease expiry is set at January 2038. I have tried to release and renew, but it won't release it

[Reply or follow-up to this message]

Need to look at the DHCP server configuration.



Regards,
Crash Override, MCP






On Wednesday, January 30, 2008 at 12:33 pm, Mike wrote:

>The lease expiry is set at January 2038. I have tried to release and renew, but 
it 

>won't release it 

[Reply or follow-up to this message]

How do I look at / access the DHCP server config?


On Wednesday, January 30, 2008 at 1:21 pm, Crash Override wrote:
>Need to look at the DHCP server configuration.
>
>
>
>

Regards,
>Crash Override, MCP

>

[Reply or follow-up to this message]

The DHCP server is controlled by your ISP or you LAN admins if this in reference 
to a pc at work/school.



Regards,
Crash Override, MCP






On Thursday, January 31, 2008 at 5:24 pm, Mike wrote:

>How do I look at / access the DHCP server config?

>

>

> 

[Reply or follow-up to this message]

I am running Windows 2000 on a home desktop. I have other pc's (laptops) running XP all on the same ISP shared through a router. The other pc's have no problems and running fine. The issue with the home desktop occurred immediately after upgrading my ZoneAlarm version. Since then, I have not been able to connect to the Internet with the home desktop. The IP address is obtained automatically with a "169.XXX". I have tried to release all, but no luck. The lease expiry is fixed at Jan. 18,2038. We also tried re-installing Windows 2000 over, but no change. Any ideas what to do next? Much appreciated.


On Friday, February 1, 2008 at 3:26 am, Crash Override wrote:
>The DHCP server is controlled by your ISP or you LAN admins if this in reference
>to a pc at work/school.
>
>
>
>

Regards,
>Crash Override, MCP

>

[Reply or follow-up to this message]

OK.  That gives a better picture of the problem.  For some reason, the win2k desktop 
is not reaching the router.  The 169 address is called an APIPA address and cannot 
be released using the ipconfig /release all command.  The others are probably either 
10 or 192 addresses.  Give this a try.  Go into the proerties of the connection and 
make it a manual not dhcp connection.  From one of the laptops, do an ipconfig to 
get the basic information.  If the laptop shows an ip address of 192.168.0.13, make 
the desktop 192.168.0.150.  Make the dns entries identical.  Then try and access 
the internet.  If this works, then the problem is not the NIC (Network card) and 
we will look at that after.



Regards,
Crash Override, MCP






On Friday, February 1, 2008 at 5:29 am, Mike wrote:

>I am running Windows 2000 on a home desktop.

>I have other pc's (laptops) running XP all on the same ISP shared through a router.

>The other pc's have no problems and running fine.

>The issue with the home desktop occurred immediately after upgrading my ZoneAlarm 

>version. Since then, I have not been able to connect to the Internet with the home 

>desktop. The IP address is obtained automatically with a "169.XXX". I have tried 

>to release all, but no luck. The lease expiry is fixed at Jan. 18,2038.

>We also tried re-installing Windows 2000 over, but no change.

>Any ideas what to do next?

>Much appreciated.

>

>

> 

[Reply or follow-up to this message]

I changed the network connection properties from automatic to manual and used an ip address similar string to what I found on my laptop (ipconfig). I made the dns entries identical to the laptop. I tried to access the internet, however and unfortunately all of this did not work. Any ideas what to do next?


On Friday, February 1, 2008 at 5:59 am, Crash Override wrote:
>OK. That gives a better picture of the problem. For some reason, the win2k desktop
>is not reaching the router. The 169 address is called an APIPA address and cannot
>be released using the ipconfig /release all command. The others are probably either
>10 or 192 addresses. Give this a try. Go into the proerties of the connection and
>make it a manual not dhcp connection. From one of the laptops, do an ipconfig to
>get the basic information. If the laptop shows an ip address of 192.168.0.13, make
>the desktop 192.168.0.150. Make the dns entries identical. Then try and access
>the internet. If this works, then the problem is not the NIC (Network card) and
>we will look at that after.
>
>
>
>

Regards,
>Crash Override, MCP

>

[Reply or follow-up to this message]

I would suspect the NIC is bad.  They are fairly inexpensive so you try replacing 
it and see if that clears it.  



Regards,
Crash Override, MCP






On Wednesday, February 6, 2008 at 10:20 am, Mike wrote:

>I changed the network connection properties from automatic to manual and used an 

>ip address similar string to what I found on my laptop (ipconfig).

>I made the dns entries identical to the laptop.

>I tried to access the internet, however and unfortunately all of this did not work.

>

>Any ideas what to do next?

>

>

> 

[Reply or follow-up to this message]

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum