*** From dhcp-server -- To unsubscribe, see the end of this message. *** I've actually seen this error (error renewing adapter "") on a win95 machine. The machine had two ethernet cards, one on a private network using a static address and one connected to a MediaOne cable modem and using DHCP. Additionally MS networking was bound to the private card. The error occurred on the outside NIC whenever DHCP tried to get an address. Removing MS networking (which was only bound to the inside card's TCP/IP stack) allowed DHCP to work however. Very strange. I've always thought it was a Windows networking bug, since the problem was infinitely reproducible on that machine (removing the MS client made the problem disappear and adding it brought the error back). I don't believe it was a hardware issue because the exact same configuration (same cards, same version of windows, same network setup) on a separate machine had no problems. I hope this helps you narrow down the problem. Good luck. -seren > >The client does not assume an IP address. Using the WINIPCFG utility in >Windows 95 I attempt to renew a lease. Several seconds later I get a error >message back (on the Win95 machine) stating it had an 'error renewing >adapter ""'. > >I guess since I now know that the lease times are not causing the problem >I can start looking elsewhere. Maybe I can begin to elaborate on our >environment. > >Our client base is mostly Windows 95. Due to historical reasons we have >two class B IP ranges and are also utilising several 172.* (intranet) >address ranges. We have three physical vlans separated by a CISCO 7206 >router. Two of these vlans have both a class B and class C address range >while the third is class C only. Currently we have a NT4 server running on >one of the combined subnets which sucessfully does DHCP for the class B >address range but not the class C subnet (as NT apparently cannot do DHCP >for secondary subnets). We are proposing a linux solution that can serve >DHCP to all three physical subnets (vlans). Towards that goal I am simply >attempting to get it working on just one subnet (ie. 172.24.* which happens >to share the same physical network as 202.37.97.*). The NT DHCP sever exists >on the 202.37.97.* subnet and serves 202.37.97.* addresses. > >In the logs I am also seeing DHCPOFFERS from the NT DHCP server. If I turn >off DHCP on the linux box my test Windows 95 client will obtain a >202.37.97.* address from the NT server. When I turn the linux server back >on (which is serving 172.24.* addresses) the test client cannot obtain an >IP address whatsoever. The linux server exists on the network with a >172.24.* address. > >I understand there may be many additional factors including how the router >is configured but I hope tinkering with this is not necessary. My config >is stated in my previous 'cry for help'. > >Any sort of assistance would be appreciated. > >-- > Carey Sinclair (Project Engineer) > > Tait Electronics Ltd > 558 Wairakei Road, PO Box 1645 > Christchurch, New Zealand > Phone. +64 (03) 358 3399 Ext. 8441 > Fax. +64 (03) 358 1933 > Email. [EMAIL PROTECTED] > > > >------------------------------------------------------------------------------ >To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists >If you are without web access, or if you are having trouble with the web page, >please send mail to [EMAIL PROTECTED] Please try to use the web >page first - it will take a long time for your request to be processed by hand. >------------------------------------------------------------------------------ > ----------------------------------------------------------------------- List Archives : http://www.isc.org/ml-archives/dhcp-server/ Unsubscribe : http://www.isc.org/dhcp-lists.html -or- : mailto:[EMAIL PROTECTED]?Subject=unsubscribe -----------------------------------------------------------------------
