vb.net data matrix barcode Routing with Windows Server 2003 in .NET

Maker Code 128C in .NET Routing with Windows Server 2003

9

Lessons in this :

Lesson 1: Configuring Windows Server 2003 for LAN Routing . . . . . . . . . . . . .9-3 Lesson 2: Configuring Demand-Dial Routing . . . . . . . . . . . . . . . . . . . . . . . . 9-28 Lesson 3: Configuring NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-45 Lesson 4: Configuring and Managing Routing Protocols . . . . . . . . . . . . . . . . 9-57 Lesson 5: Configuring Packet Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-68

Two networked computers, named Computer1 and Computer2, each running Windows Server 2003. Computer1 should be assigned a static address of 192.168.0.1/24, and Computer2 should be configured to obtain an address auto matically. Computer2 should also have an alternate configuration address of 192.168.0.2/24. Connected each computer s modem to a separate phone line (highly recommended). Installed a DNS server on both computers. Computer1 hosts an Active Directory integrated primary zone named domain1.local, which accepts only secure dynamic updates. Computer2 hosts a standard secondary zone of domain1.local and the delegated subdomain of sub.domain1.local as a standard primary zone. Computer1 hosts a standard stub zone of sub.domain1.local. Configured Computer1 as a domain controller in the domain1.local domain and Computer2 as a member of the domain. The domain functional level is Windows 2000 mixed mode. Installed a DHCP server on Computer1. The DHCP server is authorized in the domain and includes the scope Test Scope whose IP address range is 192.168.0.11 192.168.0.254. Through DHCP options, the scope assigns a router (gateway) of 192.168.0.1, a DNS server of 192.168.0.1, and a DNS domain name of domain1.local. Installed Windows Support Tools on both computers. Installed Network Monitor on both computers. Deleted any dial-up connections configured on either computer.

Routing features in Windows Server 2003 are provided by the Routing And Remote Access service, which is installed in a disabled state. Routing And Remote Access is essentially a software router that can be configured to connect separate network segments.

Configure Windows Server 2003 as a network router Configure and manage routing features in Routing And Remote Access View and maintain routing tables Configure and maintain static routes

Routing is the process of transferring data across an internetwork from one local area network (LAN) to another. Whereas a bridge connects network segments and shares traffic as necessary according to hardware addresses, a router receives and forwards traffic along appropriate pathways according to software addresses. Consequently, bridges, operating at the second, or data link layer of the Open Systems Interconnect (OSI) networking model, are sometimes called layer 2 devices. Routers, which oper ate at the third, or network layer of the OSI model, are known as layer 3 devices. In IP networks, routing is performed according to IP routing tables. All IP hosts use rout ing tables to forward IP traffic; IP routers are distinctive from hosts in that they can use these routing tables to forward traffic that has been received from another router or host.

9

The Routing And Remote Access service in Windows Server 2003 is a multiprotocol software router that can be readily integrated with Windows features such as security accounts and group policies. The service can be configured for LAN-to-LAN, LAN-toWAN, virtual private network (VPN), and Network Address Translation (NAT) routing through IP networks. In addition, the service can be configured for routing features such as IP multicasting, demand-dial routing, DHCP relay, and packet filtering. Finally, it offers built-in support for the dynamic routing protocols Routing Information Proto col (RIP) version 2 and Open Shortest Path First (OSPF).