DHCP Error

[C M]

Hi,

I keep seeing these error messages in the DHCP Servers Event Log, MS have no references for it:

EVENTID: 31002
The DNS proxy agent was unable to bind to the IP address 10.1.x.x. This error may indicate a problem with TCP/IP networking. The data is the error code.

EVENTID: 30013
The DHCP allocator has disabled itself on IP address 10.1.x.x, 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.

Has anybody seen this before?

Thanks for your help, its not stopping anything working i'd just like to get to the bottom of it

Chris.

[TJolly]

Hi

A quick search on google produced this:

http://www.google.co.uk/search?hl=en...e+Search&meta=

[Cantoris]

Hi!

I note there are two different private IP ranges mentioned in your errors. What is the network configuration of this PC? Is it multihomed (2 network cards) and/or do you have Internet Connection Sharing or RAS (with NAT) installed?

Best wishes,

Andrew

[C M]

Hi,

The Server is the domain controller with DHCP,DNS and it also features Internet Connection Sharing (RRAS would not go)

I looked on the MS site for a good few hours and it came back that if you have DNS and DHCP with RRAS/ICS on the same server this error has been seen before.

It would be nice to find a workaround.

The DHCP serve's out one IP range the 10.x.x.x
the 192 address was assigned to the single network card when Internet Connection Sharing was enabled, but was changed to fit our scope.

Thanks,

Chris

[Cantoris]

Hi!

Well that explains the problem you're having. I'm surprised your ICS is working as you're not meant to put it on the same PC as a DHCP server. The reason being that ICS contains its own Mini DHCP Server. Maybe it works as long as the client PCs all have a IP in the range it is performing NAT on. It just means its DHCP Allocator will be disabled.

Also ICS only works on the 192.168.0.0 private IP range so it's understandable it doesn't approve of having the NIC's IP changed to the 10.0.0.0 range. I'm not sure whether there's a registry hack to move ICS' DHCP scope to a different range or not.
I would have thought though that if your client PCs are on a subnet other than 192.168.0.0 then the ICS service would not perform any NAT for them and they would be unable to access the net....??

I wonder why RRAS would not work for you? It would have been much better!

Best wishes,

Andrew

[C M]

Hi Andrew,

It was only a small sub-office so there isn't much infrastructure to correctly implement it all...i didn't arrange the ADSL and we got some bizarre home type USB Router that was very awkward..when we used RRAS it couldn't see it as Windows 2000 treat it as a Modem if memory serves and wouldn't let them out.
So we had to share what it thought was a dial-up connection.

thanks for your help on that..i want to see it using RRAS hopefully i'll try and go down and sought it at a later date

Thanks for your help,
Chris

[Cantoris]

Hi!

You could always try something like WinGate to share the ADSL but it's not exactly free like ICS and RRAS!

Best wishes,

Andrew