I have a rather complex topology here, which I'd rather not get into unless someone feels they need the info to solve this problem. The bottom line is, I would like to use my XP Pro WS for ICS/NAT for a wireless laptop. Due to a bug in the wireless config tool once upon a time, I was forced to set up my LAN to use a 192.168.1.x network. ICS, however, doesn't like this, and really, really, really wants to use 192.168.0.x. It actually basically works fine on 192.168.1.x, by simply changing the IP address on the WS after turning on ICS, but I get the Event Log warning about "The DHCP allocator has disabled itself on IP address w.x.y.z since the IP address is outside the scope..." I would simply like to get rid of this error. I don't want to use DHCP; my IPs are manually configured and I want/need to leave them that way. But based on everything I've read, this ICS DHCP Allocator is just "part of the package", and there is no way to turn it off, nor is there any way to change the network it wants to operate on. Is this really true, or is the some kind of hackaround for this? I've gone as far as going to netsh>>routing>>ip>>autodhcp and changing the global scope network to 192.168.1.0/24, but to no avail. Evidently ICS lives in a world of its own, outside of the constraints of the basic routing software. So ... any ideas? I can renumber my LAN now, I think, since I believe the old bug with the WAP was fixed a couple sw revisions ago, but it will be an incredible hassle to do that at this point (ie, I'll have to get up in the wee hours, bring down all the public systems, reconfigure, update DNS & WINS ... ugh). I can also use a different NATting sw on the XP WS, but I'd rather not. I could also use one of my servers to do the NATting instead, but as I mentioned at the top, my topology is complex and the servers already have enough "real" routing to do. So, that's the scoop. TIA, folks...
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
ICS/DHCP Allocator/Fixed IP/Workaround?
- Thread starter rmusgrove
- Start date
Steve Winograd MVP notes:
You can get ICS to use a different range. However, this is an unsupported configuration, not tested or suggested by Microsoft. It might cause networking problems on the host computer, so make a system restore point before doing it:
1. Temporarily assign a static IP address to the network connection that you want to share, using an address that isn't in 192.168.0.x.
2. Enable ICS on that network connection.
3. Manually change the IP address of the LAN (home network) connection to a different subnet, such as 192.168.1.x.
4. Restore the proper IP address for the shared network connection.
This unsupported configuration will automatically disable the DHCP server that normally runs on the ICS host. You'll have to assign static IP addresses to all of the ICS clients.
If you have any alternative to this configuration, I recommend using the alternative.
You can get ICS to use a different range. However, this is an unsupported configuration, not tested or suggested by Microsoft. It might cause networking problems on the host computer, so make a system restore point before doing it:
1. Temporarily assign a static IP address to the network connection that you want to share, using an address that isn't in 192.168.0.x.
2. Enable ICS on that network connection.
3. Manually change the IP address of the LAN (home network) connection to a different subnet, such as 192.168.1.x.
4. Restore the proper IP address for the shared network connection.
This unsupported configuration will automatically disable the DHCP server that normally runs on the ICS host. You'll have to assign static IP addresses to all of the ICS clients.
If you have any alternative to this configuration, I recommend using the alternative.
- Thread starter
- #3
Thanks Steve. I tried the steps you outlined, but after a reboot I'm still getting that error about "The DHCP Allocator disabling itself". Perhaps you misunderstood that all I'm really trying to accomplish is to get rid of that. I have this thing about "red errors" in the event log that I need to ignore. I think what I was hoping for was for someone to say "open a hex editor on this dll, and change this address from a 0 to a 1", or something like that. I guess I'm just amazed that ICS is *that* inflexible, and operates completely outside of anything you can reach with netsh. Anyway ... thanks for the effort.
Is this the message? "The DHCP allocator has disabled itself on IP address 169.254.97.214, 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."
You are not going to be able to remove this from the Event Log.
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."
You are not going to be able to remove this from the Event Log.
- Thread starter
- #5
Yeah. That's what I figured, but I thought I'd ask. If that's the case, then why does the error message SUGGEST that you can change the scope to include the IP address? I mean, the error message is explicitly giving you an option that you can't do, and wasted a ton of my time....
Scope is different than subnet. The scope for ICS is controlled by the subnet mask, the only "allowed" network segment is 1192.168.0.x.
In most cases changing first the ICS Host base IP, (this generates the message you receive), and then the clients to static IPs will work, but the DHCP allocator error will be thrown in Event Viewer, because it is in fact disabled by doing so.
There are some additional considerations to static IPs for the clients as well:
In most cases changing first the ICS Host base IP, (this generates the message you receive), and then the clients to static IPs will work, but the DHCP allocator error will be thrown in Event Viewer, because it is in fact disabled by doing so.
There are some additional considerations to static IPs for the clients as well:
- Thread starter
- #7
...I dunno... That's pretty misleading. I mean, ok, in the context of "ICS DHCP" scope and segment aren't related. But in the context of autodhcp (RRAS/netsh/etc), they are. That's like a case of Microsoft saying "If you don't know, we're not going to tell you". Whatever....
This is an issue with a lot of history here. At one time I HAD the LAN configured for 192.168.0.x. Then one day I got a wireless Access Point for the laptop, which absolutley refused to be configured on any IP address but 192.168.1.245. The only reason I need ICS is for the laptop. See the problem? At the time, things were fairly simple here, and so I reconfigured the LAN as a 192.168.1 network, because I was able to get around the ICS problem (event log error notwithstanding), but not the WAP problem. Now things aren't so simple anymore, and going back to 192.168.0.x is going to be a bear, even though I can now configure the WAP on it. But it sounds like this is what I'm going to have to do. It's that, or go back to using one of my servers to control the routing for both a commercial T1 line and a residential cable broadband line, and deal with the various nightmares involved with that (esp, keeping outbound traffic off the cable line). I dunno. What a pain, that's all...
This is an issue with a lot of history here. At one time I HAD the LAN configured for 192.168.0.x. Then one day I got a wireless Access Point for the laptop, which absolutley refused to be configured on any IP address but 192.168.1.245. The only reason I need ICS is for the laptop. See the problem? At the time, things were fairly simple here, and so I reconfigured the LAN as a 192.168.1 network, because I was able to get around the ICS problem (event log error notwithstanding), but not the WAP problem. Now things aren't so simple anymore, and going back to 192.168.0.x is going to be a bear, even though I can now configure the WAP on it. But it sounds like this is what I'm going to have to do. It's that, or go back to using one of my servers to control the routing for both a commercial T1 line and a residential cable broadband line, and deal with the various nightmares involved with that (esp, keeping outbound traffic off the cable line). I dunno. What a pain, that's all...
- Status
Similar threads
