Windows Forum

Ask something
Discussion Locked

NAT under Win2K fails randomly.

0 helpful
3 replies

by evan tallas

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Here's the issue... NAT inconsistently fails to route 98 and NT4 machines. The Win2K machines on the network never have problems. There are no messages in the logs as to what happened, even after I turned loggin up all the way for NAT. At some points in time NAT fails altogether, and just stops. The only way to restart NAT is by disabling and re-enabling the Public NIC, or by restart.

The server has 2 Nics in it, Public(Inet) and Private(internal).

DNS is bound to the Public Nic. Therefore DNS should not interfere with the NAT DNS on the private NIC. DHCP is not installed, nor is NAT setup to use the miniDHCP server.

3 replies

by sleathwood

Do you have a WINS Server installed someplace? 98 and NT4 require WINS to function properly in a W2K environment. Using the NAT DHCP server would help as well. Remember what NAT is doing (or not doing in you case :))NAT cannot route to a workstationit can not find. However if the NAT service fails inexplicably you may have additional problems. I'd try to fix the WINS and DHCP issues first, then see if the service continues to crash.

by evan tallas

I've since added a hardware router, but I was using the NAT DHCP, and was using a WINS server. At this point I'm going to throw it up to a Win2K issue. Thanks.

This discussion is closed to new replies.