Event ID: 31002

[Randy Lynn]

I have a server running Windows Server 2000 SP4. The log
shows a fatal error event ID of 31002; The DNS proxy
agent was unable to bind to the IP address of
192.168.0.1. This error may indicate a problem with
TCP/IP networking. The data is the error code.
000: 1d 27 00 00
Source: ipnathlp

Technet has no referance for this error code and I cannot
find any sources at microsoft.com.

Can anyone help solve this error or point me in a
direction to solve it?


Randy

 

[Kevin D. Goodknecht Sr. [MVP]]

In

I have a server running Windows Server 2000 SP4. The log
shows a fatal error event ID of 31002; The DNS proxy
agent was unable to bind to the IP address of
192.168.0.1. This error may indicate a problem with
TCP/IP networking. The data is the error code.
000: 1d 27 00 00
Source: ipnathlp

Technet has no referance for this error code and I cannot
find any sources at microsoft.com.

Can anyone help solve this error or point me in a
direction to solve it?


Randy

Is ICS enabled?
DNS also installed?
Disable ICS If you have DNS server running on the machine

 

[Michael Johnston [MSFT]]

You need to disabled ICS on the box. Use NAT within Routing and Remote Access instead. This will solve the problem.

Thank you,
Mike Johnston
Microsoft Network Support

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.

 

[Ace Fekay [MVP]]

In

Is ICS enabled?
DNS also installed?
Disable ICS If you have DNS server running on the machine

Yes, and recommend to use NAT instead of ICS. The ICS DNS proxy service and
also DHCP (if y ou;re running that) will also conflict with ICS. NAT is the
better way to go, especially if you have AD running.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Randy Lynn]

Thanks for the input.

Your were right about ICS. NAT is a better solution.
After failing with my attempt to get NAT working I
contacted Microsoft Tech Support for additional help.
After sometime with them it was decided that NAT would
also not solve the problem. Reason? The Internet
connection is a one way Satillite connection. In other
words, all inbound traffic comes via the dish and all
outbound traffic goes out via a dial-up connection. A
very slow connection at that. The final solution was to
move Internet sharing to a computer in the domain. No
fun, but the problem is solved.

Thanks again for your input.

Randy Lynn

 

[Ace Fekay [MVP]]

Well, either way, glad you came up with some sort of solution!
Cheers!

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory