asked on

IP lease expires on Wednesday December 31, 1969

I have a Novell Netware 6.0 sp5 server and it has been running pretty well but recently I have one and only one of about 200 workstations that is consistantly timing out when I do a ping. I did an ipconfig /all and it shows that the lease expires on Wednesday December 31,1969. It does get the IP address from the server on boot up and will connect to the network and internet but after a fairly short period of time it drops the mapped drives and the mapping does not reutrn until reboot. I can also get the mapping to work if I do an Ipconfig /release then renew.

I found some info on a Novell board and they said that there is an option on the DHCP server to shut off to fix.

I have tried to set the IP statically on the server and have tried assigning the IP to have a permanent lease on the server to no avail.

Thanks for the help in advance.

static-void

check the time settings on your PC and DHCP server

Bud Durland

WIndows clients sometimes have a mind of their own regarding DHCP rules. Have you tries explicity canceling the DHCP lease (IPCONFIG / RELEASE), then renewing the address (IPCONFIG / RENEW). Once re3newed, when you do an IPCONFIG /ALL, is the displayed DHCP server IP your NetWare box?

goeden

ASKER

This workstation is using a Novell Client for Windows.

I did ckeck the time on the workstation but not the server. This is the only workstation doing this though.

goeden

ASKER

When I do the Ipconfig /renew it still shows a message that the lease expires in Dec of 1969. This is not what the server lease time is. The server hands out leases with an expiration of 4 days.

alextoft

I believe this is an anomoly that can occur if using "ping-ahead", where the DHCP server pings an IP before offering it to a client to check whether or not it is in use. Try disabling ping-ahead and you should find the problem resolved.

goeden

ASKER

Where do I disable the "ping-ahead" option? Is it in the DHCP console settings.

I did see something in reference to disabling options 58 and 59 in the documentation but when I go into the DHCP console I can only find that setting in the Global settings and then when I try to delete them they will not go away.

ShineOn

Options 58 and 59, if they're not assigned to be handed out, won't affect anything. The table is just a list - if they're not where the assigned options are don't worry about 58 and 59.

Do ipconfig /release, then in the DNS/DHCP console, manually remove the old IP assignment, then refresh the server before you ipconfig /renew. If that still fails to get a decent lease, something else is wrong with this PC.

goeden

ASKER

The DHCP server is setup in such a way that the IP's are manually assigned and are associated with the mac address to limit unauthorized access.

I will try the ipconfig release and see where that gets me.

goeden

ASKER

Tried to do the ipconfig /release, then removed the old IP assignment and refreshed the server. Then I do an ipconfig /renew and it gets a new IP and the lease still says that it expires on Dec 31, 1969. The server DHCP console also shows that the lease is timed for that IP and that it expires on Dec 31, 1969.

I will verify that the time is set correctly on the server.

goeden

ASKER

Verified time on server and pc and it is correct.

I have already tried to replace NIC in pc and new cat5e cable. This pc had worked fine for 3 months and is suddenly not working.

goeden

ASKER

I have now found another pc that shows up with a lease that expires on Dec 31, 1969. This one is not having problems connecting so not sure what is going on.

ASKER CERTIFIED SOLUTION

goeden

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial