dhcp allocator

[Guest]

hi, I got Windows XP Home and I set up a 2-computer network (using a switch
I enabled ICS on this computer (I have a LAN card that connects to the DSL modem and another one that connects to the switch), and it forcefully, without warning, without my consent and without my authorization, changed the IP of my local network connection to 192.168.0.1 (I used 10.something
I said 'ok', and I changed it back manually, but since then I'm getting these errors in the system event log

source: iptnahl
event id: 3001
The DHCP allocator has disabled itself on IP address 10.x.y.z, 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

I'd like to know where are the settings for the dhcp allocator, because I couldn't find them anywhere (I want to change the scope

thank
Adria

P.S. the network still works, at least I can manually set the IP on the other computer to match my settings, but I'd like to have a working DHCP setup

 

[Ron Lowe]

hi, I got Windows XP Home and I set up a 2-computer network (using a switch)
I enabled ICS on this computer (I have a LAN card that connects to the DSL

modem and another one that connects to the switch), and it forcefully,
without warning, without my consent and without my authorization, changed
the IP of my local network connection to 192.168.0.1 (I used 10.something)

I said 'ok', and I changed it back manually, but since then I'm getting

these errors in the system event log:

source: iptnahlp
event id: 30013
The DHCP allocator has disabled itself on IP address 10.x.y.z, 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.

I'd like to know where are the settings for the dhcp allocator, because I

couldn't find them anywhere (I want to change the scope)

thanks
Adrian

P.S. the network still works, at least I can manually set the IP on the

other computer to match my settings, but I'd like to have a working DHCP
setup


You can't change the scope.
That option is gone.

The message is somewhat misleading, as it suggests you can change the scope.
But you cant.
The error text is probably carried over from an earlier version where you
could.

ICS is now hard-coded to 192.168.0.x subnet.
And as you discovered, the ICS host will make itself 192.168.0.1

It's taken the huff at you changing the IP address back to10.x.x.x
You are going to continue getting this notification ( not really an error )
untill you put it back to 192.168.0.1.

If you want ICS to be the DHCP allocator, you need to change
your LAN from the 10.x.x.x subnet to 192.168.0.x.

Otherwise, you'll need to find a different DHCP server for your LAN.

 

[Bob Willard]

hi, I got Windows XP Home and I set up a 2-computer network (using a switch)
I enabled ICS on this computer (I have a LAN card that connects to the DSL modem and another one that connects to the switch), and it forcefully, without warning, without my consent and without my authorization, changed the IP of my local network connection to 192.168.0.1 (I used 10.something)
I said 'ok', and I changed it back manually, but since then I'm getting these errors in the system event log:

source: iptnahlp
event id: 30013
The DHCP allocator has disabled itself on IP address 10.x.y.z, 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.

I'd like to know where are the settings for the dhcp allocator, because I couldn't find them anywhere (I want to change the scope)

thanks
Adrian

P.S. the network still works, at least I can manually set the IP on the other computer to match my settings, but I'd like to have a working DHCP setup

There are no options. ICS only uses 192.168.0.1 for its NIC, and
192.168.0.x for its clients' NICs. If you really insist on using
other IPAs, then turn off ICS and buy something else.

 

[Guest]

thank you for your repl

----- Ron Lowe wrote: ----

You can't change the scope
That option is gone
:

The message is somewhat misleading, as it suggests you can change the scope
But you cant
The error text is probably carried over from an earlier version where you could
ICS is now hard-coded to 192.168.0.x subnet
And as you discovered, the ICS host will make itself 192.168.0.

well, I have some words to say to microsoft about this, but I think I'll be banned if I post them her

If you want ICS to be the DHCP allocator, you need to chang
your LAN from the 10.x.x.x subnet to 192.168.0.x
Otherwise, you'll need to find a different DHCP server for your LAN

then is it possible to disable the ICS DHCP allocator

if all else fails, I guess I can change the IPs to 192.168.0.x (nothing else stops me besides my own preference
in the meantime, I played a bit with the settings, and I found it can make a NAT bridge for several connections (I also have a 480Mbps usb link cable), that's pretty sweet (but it will still set the bridge to 192.168.0.1/24

Adrian

 

[Ron Lowe]

well, I have some words to say to microsoft about this, but I think I'll
be banned if I post them here

Na, you're granted a fairly generous freedom of speech here!
It takes a fair amount to get a post cancelled.
I've never seen a post cancelled just for criticising MS.
The only posts I've seen cancelled are outright spam and obscene material.
Unless you were proposing the latter.....

then is it possible to disable the ICS DHCP allocator?

Sure.
Just leave it set to 10.x.x.x, and it disables itself.
Read the original error message.

 

[Guest]

----- Ron Lowe wrote: ----

The only posts I've seen cancelled are outright spam and obscene material

it would be rather obscene (in words) :
anyway, nevermin

Just leave it set to 10.x.x.x, and it disables itself

well.. not exactl
it tries to start, fails, writes an error message in the log, and then closes till I restart the compute
I was looking for a way to turn it off completely (without turning off ICS) so I wouldn't get those error

in the end I switched to 192.168.0.

Adrian