Event ID 20169

[Wile E. Coyote]

Anybody know what to do about fixing the following error
message?

Unable to contact a DHCP server. The Automatic Private IP
Address 169.254.133.82 will be assigned to dial-in
clients. Clients may be unable to access resources on the
network.

I already know I'm not running a DHCP server, I have no
need for one. I suspect this message was generated when I
tried to access the Internet from my NT workstation, by
using my Win2000 Professional client as a gateway, as it's
connected to the Internet over a modem.

Unfortunately, the dog won't hunt. I can ping the 2000
machine from the NT box and vice versa, so clearly
connectivity is there. But, I can't get past the 2000
machine from the NT machine. As I'm typing this from the
2000 machine while connected to the Internet, clearly the
2000 machine can in fact reach the outside world.

Obviously there's some blocking going on at the 2000 box
level, however I have the Routing & Remote Access service
started, as well as Internet Connection Sharing, not to
mention RPC and virtually all the other services.

Protocol filtering is NOT enabled, I let everything pass
through.

Anything related to networking is started, except telnet,
messenger and alerter (which I disabled because I'm
getting spam popups - and despite disabling these services
I still get the popups which is baffling in and of itself).

Anybody know what's going on with this useless operating
system?

Email preferred, I probably won't be able to find this
group again, the MS behometh is very good at hiding things.

Thanks in advance.

 

[Sharoon Shetty K [MSFT]]

If the RRAS server has been configured to obtain the IP Address from the
DHCP, and it is not able to contact the DHCP Server. You can get rid of this
problem by configuring the RRAS Server to give IP Addresses to the clients
from a static pool of IP Address.