<div>
<div class="content wysiwyg-content">
I'm trying to increase my bandwidth by using a 2nd VDSL line. 
 
Maybe Server#2 maps to a folder on Server#1 in LOCAL LAN and then users can connect to ftp2.server2.com so they are actually still downloading from Server#1 
 
I currently have: 
 
2 VDSL BOXES both 10M/2M speeds 
 
SERVER#1 has NIC#1 connected to VDSL#1 
 
Current FTP downloads are slowing down the system. How would you design the rest to work? 
 
 
Here's my take: 
 
Add additional NIC#2 to SERVER#1 
 
Setup SERVER#2 and add NIC#1 and NIC#2 
 
SERVER#2NIC#1 connects to VDSL#2 
SERVER#2NIC#2 connects to SERVER#1NIC#2 (bridge between servers) 
 
SERVER#2 maps to SERVER#1 FOLDER 
 
Then just setup the FTP SERVER to allow users to download from the mapped folder from SERVER#1 
 
Will this work?
</div>
</div>

I'm trying to increase my bandwidth by using a 2nd VDSL line.

Maybe Server#2 maps to a folder on Server#1 in LOCAL LAN and then users can connect to ftp2.server2.com so they are actually still downloading from Server#1

I currently have:

2 VDSL BOXES both 10M/2M speeds

SERVER#1 has NIC#1 connected to VDSL#1

Current FTP downloads are slowing down the system. How would you design the rest to work?


Here's my take:

Add additional NIC#2 to SERVER#1

Setup SERVER#2 and add NIC#1 and NIC#2

SERVER#2NIC#1 connects to VDSL#2
SERVER#2NIC#2 connects to SERVER#1NIC#2 (bridge between servers)

SERVER#2 maps to SERVER#1 FOLDER

Then just setup the FTP SERVER to allow users to download from the mapped folder from SERVER#1

Will this work?

2xSERVERS 4xNICS 2xVDSL LINES

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).