Re: Lost lease on IP address...?



Posted below from here on.

Kenneth wrote:
On Fri, 25 Nov 2005 16:48:12 -0400, John John
<audetweld@xxxxxxxxxxx> wrote:


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


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,

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/documentation/Windows/2000/server/reskit/en-us/Default.asp?url=/resources/documentation/windows/2000/server/reskit/en-us/cnet/cnfe_opt_rmea.asp
http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/Default.asp?url=/resources/documentation/Windows/2000/server/reskit/en-us/w2rkbook/CoreNetwork.asp
http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/Default.asp?url=/resources/documentation/Windows/2000/server/reskit/en-us/cnet/cncb_dhc_klom.asp
http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/Default.asp?url=/resources/documentation/windows/2000/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
.



Relevant Pages

  • 2 pc network - XP and Win95 - help needed badly!
    ... I've been trying to get these two machines networked for 10 days now with no ... assigning an IP address to PC2, and is assigning an improper IP ... From what I've read, DHCP ... "Your computer has automatically configured the IP address for the network ...
    (microsoft.public.windowsxp.network_web)
  • Re: DHCP Not working properly
    ... Windows SBS Standard running on a Dell server with one NIC ... Desktop Workstations running Windows XP SP2 (wired network connections) ... These two machines will not pick up a DHCP address from the server. ...
    (microsoft.public.windows.server.sbs)
  • DHCP Not working properly
    ... Desktop Workstations running Windows XP SP2 (wired network connections) ... These two machines will not pick up a DHCP address from the server. ...
    (microsoft.public.windows.server.sbs)
  • Re: DHCP Not working properly
    ... computers on the network and I assigned IP addresses to each of them. ... cause them to re-register with the new DHCP database. ... You mentioned "you may want to make sure the old database is gone before ... These two machines will not pick up a DHCP address from the server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Can not access other computer on network
    ... My first problem was the " The DHCP client was unable to obtain an IP ... The computers' network connections are configured to obtain an IP ... There isn't a DHCP server on the network to assign an IP address. ...
    (microsoft.public.windowsxp.network_web)

Loading