Re: Invalid IP address for DHCP server
- From: "Daniel Crichton" <msnews@xxxxxxxxxxxxxxxxxx>
- Date: Tue, 1 Nov 2005 14:57:48 -0000
Wazza wrote on Tue, 1 Nov 2005 05:18:03 -0800:
>> Thanks for your interest in my problem. I have previously had this
>> network running correctly. ICS was working fine and I had access to share
>> files and printers on both PC's. The only change to my set-up has been
>> the addition of an ADSL modem. Could this be causing the problem?
Entirely possible, as you may well have caused ICS to stop working. For
instance, if the ADSL modem is also a router and by default uses the same IP
range as ICS, your XP PC will have 2 interfaces setup to deal with the same
IP range - and only one of them will respond correctly.
> About my set-up:
> Host PC is running Windows XP Home 2002 SP2 directly connected, via
> ethernet cable, to Client PC which is running Windows ME 4.90.3000
>
> Work-arounds I have tried:
> Release and renew ipconfig on both PC's
> Winsock repair procedures(as detailed by Chuck in other posts)
> Download and install new driver for Host PC NIC
>
> When renewing ipconfig on Host I get an error message: "An error occured
> while renewing interface Local Area Connection : unable to contact DHCP"
OK, first thing to check is that the XP firewall has an exception to allow
DHCP, if you've got the firewall enabled.
> The event viewer has this to say:
> Event Type: Error
> Event Source: ipnathlp
> Event Category: None
> Event ID: 30013
> Date: 27/10/2005
> Time: 5:49:43 PM
> User: N/A
> Computer: BEAVER1
> Description:
> The DHCP allocator has disabled itself on IP address 169.254.7.140, since
> the IP address is outside the 192.168.0.0/255.255.255.0 scope from which
> addresses are being allocated to DHCP clients. To enable the DHCP
> allocator on this IP address, please change the scope to include the IP
> address, or change the IP address to fall within the scope.
So the LAN interface which the ICS connection is made over isn't getting a
DHCP allocated address from the ICS DHCP server. This could be an issue with
the XP SP2 firewall, or something the ADSL modem drivers have done.
> It suggests that the network connections have the wrong address manually
> configured but both PC's are configured to obtain addresses automatically.
>
> Both PC's are able to ping themselves and each other on the 169.254.x.y
> addresses listed in the ipconfig files below. I know these addresses
> should be in the 192.168.x.y range but I'll be darned if I can find out
> how to achieve this.
This again indicates that DHCP isn't working, so the the LAN interfaces are
being left with addresses in the range Windows uses when unable to get one
from DHCP.
> Description . . . . . . . . . . . : Speedstream Ethernet USB
> Adapter
> Physical Address. . . . . . . . . : 00-0B-23-D7-B1-3A
> Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 10.0.0.1
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
OK, so the ADSL modem is using a different DHCP range so it doesn't appear
to be a conflict (ICS uses the 192.168.0.0 address range). However, as
everything was fine before it was introduced, it's well worth checking all
the ICS configuration on the PC and the firewall settings.
Dan
.
- Follow-Ups:
- Re: Invalid IP address for DHCP server
- From: Wazza
- Re: Invalid IP address for DHCP server
- References:
- Re: Invalid IP address for DHCP server
- From: Wazza
- Re: Invalid IP address for DHCP server
- Prev by Date: XP not reconnecting mapped network drives at login
- Next by Date: Re: XP not reconnecting mapped network drives at login
- Previous by thread: Re: Invalid IP address for DHCP server
- Next by thread: Re: Invalid IP address for DHCP server
- Index(es):
Relevant Pages
|
Loading