Lost lease on IP address...?

  • Thread starter Thread starter Kenneth
  • Start date Start date
K

Kenneth

Howdy,

I run Paradox as a database with Windows 2000 on our small
lan of 6 boxes.

In Paradox, I occasionally get "Unknown Internal Operating
System Errors."

Today, it happened while I was at one of the machines and
because I knew the precise time of the error, I was able to
learn more from the Event Viewer Log.

It seems that both on my system (the one displaying the
error) and on the system that is nominally the server (I say
"nominally" because our server is a peer-to-peer also
running Win 2000) there is the error "Your computer has lost
the lease to its IP address" in the system event log.

But, both systems can browse properly in both directions.

Might any of you folks have suggestions about how I might
proceed with this problem?

Sincere thanks,
 
You may want to use NetBEUI in such an envirorment.
Click to expand...

Howdy,

I while back, I ran NetBEUI and TCP/IP on all (six) of our
systems, but was advised that having both was not a good
idea. With that, I went to TCP/IP only.

Is there a downside to adding NetBEUI again?

I would love to lick the IP address lease problem I am
having, and thank you for any further ideas on this.

All the best,
 
You were advised correctly, generally speaking the fewer protocols the
better, it avoids network collisions which can slow down the network.
In a small peer network consisting of only Windows 2000 machines TCP/IP
is usually the best and only protocol to use, NetBEUI is usually only
required to connect to older DOS machines.

What is the event ID error in the event log?

Being that your network is so small an easy way around the problem is to
give the machines static IP addresses and do away with DHCP leasing
service altogether.

John
 
You were advised correctly, generally speaking the fewer protocols the
better, it avoids network collisions which can slow down the network.
In a small peer network consisting of only Windows 2000 machines TCP/IP
is usually the best and only protocol to use, NetBEUI is usually only
required to connect to older DOS machines.

What is the event ID error in the event log?

Being that your network is so small an easy way around the problem is to
give the machines static IP addresses and do away with DHCP leasing
service altogether.

John
Click to expand...

Hi John,

I appreciate your comments...

Though I don't have access to the precise wording of the
error, it relates to the lease for IP address having
expired.

I use Paradox as my database.

As I understand the situation (and this is according to the
Paradox gurus on another group) Paradox gets unhappy when
there is even a momentary discontinuity in network
availability. So, a machine loses its IP address lease, and
grabs a new one from the DHCP function of the router, but in
that moment, Paradox chokes.

It was suggested to me that I simply assign static IP
addresses. That seemed simple enough, but I soon discovered
that when I did, I lost Internet access. (Comcast says that
is because they do not support the Static address, but I
don't understand how they can "see" beyond my router.

In any case, because of that hassle I thought of the
possibility of using NetBEUI to provide Paradox a completely
stable access to the Lan.

I do thank you for the thoughts you have offered, and for
any further suggestions you might have about this,
 
Posted below from here on.
Hi John,

I appreciate your comments...

Though I don't have access to the precise wording of the
error, it relates to the lease for IP address having
expired.

I use Paradox as my database.

As I understand the situation (and this is according to the
Paradox gurus on another group) Paradox gets unhappy when
there is even a momentary discontinuity in network
availability. So, a machine loses its IP address lease, and
grabs a new one from the DHCP function of the router, but in
that moment, Paradox chokes.

It was suggested to me that I simply assign static IP
addresses. That seemed simple enough, but I soon discovered
that when I did, I lost Internet access. (Comcast says that
is because they do not support the Static address, but I
don't understand how they can "see" beyond my router.

In any case, because of that hassle I thought of the
possibility of using NetBEUI to provide Paradox a completely
stable access to the Lan.

I do thank you for the thoughts you have offered, and for
any further suggestions you might have about this,
Click to expand...

Ok, feels strange down here and my newsreader is configured to answer
above. Hmmm... I find it surprising that it should matter to Comcast
how your network is configured internally and more so even that it
should matter whether your workstations are assigned static or dynamic
IP addresses. If they say that's the case then who am I to doubt or
question them. Furthermore, I have no experience whatsoever with
routers so perhaps Comcast needs DHCP routers to connect to workstations
on a network. These things are beyond my technical knowledge.

If you can't resolve internet addresses make sure that DHCP Client
Service is set to "Automatic" start on all your workstations. Even a
stand alone Windows 2000 cannot resolve internet addresses if DHCP
client is set to manual, or so is my experience. You can have a static
IP address but to go outside the network your machine will probably need
DHCP Client Service started. To boot, I have found that the net start
command does little to change that, the client has to be started
automatically. Although the DHCP client is started or needed that
doesn't mean that you have to use DHCP addressing.

If that doesn't work or if DHCP addressing is really needed then set the
(DHCP) IP lease so that it never expires. I'm having a hard time
finding out how to do it, but I know it can be done. Poke here and
there or search technet for "dhcp leasing" and "lease never expires" and
you will find. My leads are here:

http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cnfe_opt_rmea.asp
http://www.microsoft.com/resources/.../server/reskit/en-us/w2rkbook/CoreNetwork.asp
http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cncb_dhc_klom.asp
http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cncb_dhc_nxxi.asp

Seems to me it's in the registry. And from reading here and there if
you need or use NetBEUI make sure your network security is at it's
utmost. And your dhcp leases should never expire.

John
 
Hmmm... I find it surprising that it should matter to Comcast
how your network is configured internally and more so even that it
should matter whether your workstations are assigned static or dynamic
IP addresses.
Click to expand...

Hi John,

This turned out to be my error, (and theirs.)

I had neglected to configure with a DNS specification
pointing to the router.

Right now, I have all systems assigned statically. It will
take a few days to know if that has solved my problem, but
all systems do have Internet.

We shall see...

Thanks again,
 
Kenneth said:
On Sat, 26 Nov 2005 05:08:50 -0400, John John

This turned out to be my error, (and theirs.)

I had neglected to configure with a DNS specification
pointing to the router.

Right now, I have all systems assigned statically. It will
take a few days to know if that has solved my problem, but
all systems do have Internet.

We shall see...

Thanks again,
Click to expand...

You're welcome. It did seem strange to me that the addressing method on
the network would have mattered to Comcast. Thanks for the follow up &
good luck.

John
 
Back
Top