Configuring a NAT server in Win 2003

xiaoxiao2021-03-06  14

This article describes how to configure the Network Address Translation (NAT) server by using Windows Server 2003. Windows Server 2003 "Routing and Remote Access" services include NAT routing protocols. If you install and configure the NAT routing protocol on a server running Routing and Remote Access, an internal network client using a dedicated Internet Protocol (IP) address can access the Internet through an external interface of the NAT server.

How to configure routing and remote access NAT servers

The NAT protocol driver intercepts the request when the internal network client sends a request to connect to the Internet and forward it to the target Internet server. All requests look like an external IP address from the NAT server. This hides your internal IP address configuration.

Configure "Routing and Remote Access" NAT Server:

In the Administrative Tools menu, check "Routing and Remote Access".

In "Routing and Remote Access" MMC, expand your server name (where the server name is the name you want to configure the server, then expand the IP route in the left pane.

Select normal and select New Routing Protocol.

Click the NAT / Basic Firewall check box, select it, then click OK.

Right-click the NAT / Basic Firewall in the left pane, and then click New Interface.

Click the interface indicating the internal network interface and click OK.

In the Network Address Translation property, click "Private Interface to Connect to Private Network" and click OK.

Right-click the NAT / Basic Firewall in the left pane, then click on the interface.

Click the interface indicating the external network interface and then click OK.

In the Network Address Translation property, click the "public interface to connect to the Internet".

Click "Enable the NAT" check box on this interface to select it, click OK.

The NAT server can automatically assign an IP address for the internal network client. This feature may be required if you do not have a DHCP server that has been assigned address information on the client on the internal network.

How to configure routing and remote access NAT servers to assign IP addresses and execute proxy DNS Query NAT servers can also perform a domain name system (DNS) query on behalf of the NAT client. "Routing and Remote Access" NAT server parsed the Internet hostname included in the client request and then forwarding the IP address to the client.

To configure the Routing and Remote Access NAT Server to assign an IP address and represent the internal network client to execute a proxy DNS query, follow these steps:

Right-click the NAT / Basic Firewall in the left pane, and then click Properties.

Click Address Assignment tab, and then click Use the DHCP Auto Assign IP Address check box to select it.

In the IP address box, type the network ID.

In the mask box, type the subnet mask.

Select Name Resolution tab, and then click Use the Domain Name System (DNS) check box to select it.

If you are connected to the Internet using the request dial interface, click "Connect to the Public Network" check box when the name needs to be parsed, will be selected.

In the request dial-up interface box, select the interface you want to dial.

Select Apply, and then click OK.

Note: After completing these basic configuration steps, the internal network client can access the server on the Internet.

How to configure Windows Server 2003-based computers to use NAT servers

Click Start, point to Control Panel, point to Network Connections, and then click Locally.

Click Properties.

Click Internet Protocol (TCP / IP).

Click Properties.

In the Default Gateway box, type the internal IP address of the NAT server.

Remarks: If your computer receives its IP address from the Dynamic Host Configuration Protocol (DHCP) server, click Advanced, click the IP Settings tab, click Add, Type the internal IP address of the NAT server, click Add, click OK, then proceed to step 6. Click OK, click OK, and then click Close.

转载请注明原文地址:https://www.9cbs.com/read-47884.html

New Post(0)