<div>
As an extension to my previous post:<br />
<br />
Try the following link for a mor ein depth description of how RRAS works:<br />
<br />
<a href="http://www.windowsnetworking.com/articles_tutorials/Configuring-Windows-Server-2003-act-NAT-router.html" rel="ugc">http://www.windowsnetworking.com/articles_tutorials/Configuring-Windows-Server-2003-act-NAT-router.html</a><br />
<br />
Let me know how you make out :)<br />

</div>


As an extension to my previous post:

Try the following link for a mor ein depth description of how RRAS works:

http://www.windowsnetworking.com/articles_tutorials/Configuring-Windows-Server-2003-act-NAT-router.html [http://www.windowsnetworking.com/articles_tutorials/Configuring-Windows-Server-2003-act-NAT-router.html]

Let me know how you make out :)


<div>
<div class="content wysiwyg-content">
I have a box with Dual network cards, and windows 2003 configgured on it. &nbsp;Our linkus router keeps dieing on us so for the short term I would like to have this box to act as my router and dish out internet and do some basic port forwarding. &nbsp;I know it is not the best solution but this is what is presented to me.. &nbsp;The firewall on the Linkis is still working well so I will use it primarly as our firewall and the new machine becomes the router. &nbsp;Can someone help me by pointing me to so good documentation on how to do this? 
</div>
</div>


I have a box with Dual network cards, and windows 2003 configgured on it.  Our linkus router keeps dieing on us so for the short term I would like to have this box to act as my router and dish out internet and do some basic port forwarding.  I know it is not the best solution but this is what is presented to me..  The firewall on the Linkis is still working well so I will use it primarly as our firewall and the new machine becomes the router.  Can someone help me by pointing me to so good documentation on how to do this? 

Using win 2003 as a Router and Port forwarding

Servers are computing devices that are similar to desktop computers in that they have the same basic components, but are significantly different in size, configuration and purpose. Servers are usually accessed over a network, and many run unattended, without a computer monitor, input device, audio hardware or USB interfaces. Many servers do not have a graphical user interface (GUI), and are configured and managed remotely. Servers typically include hardware redundancy such as dual power supplies, RAID disk systems, and ECC memory, along with extensive pre-boot memory testing and verification. Critical components might be hot swappable, and to guard against overheating, servers might have more powerful fans or use water cooling.

Server Hardware

Networking hardware includes the physical devices facilitating the use of a computer network. Typically, networking hardware includes gateways, routers, network bridges, modems, wireless access points, networking cables, line drivers, switches, hubs, and repeaters. But it also includes hybrid network devices such as multilayer switches, protocol converters, bridge routers, proxy servers, firewalls, network address translators, multiplexers, network interface controllers, wireless network interface controllers, ISDN terminal adapters and other related hardware.

Networking Hardware-Other

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.