Buffering Using Ftpwebrequest - Allows Users To Login To The System

This will be my first post on this site, so I thought I would make it a doozy. I have an web application on our site at work that allows users to login to the system, and submit filings for dockets that our state agency governs. Without getting to involve with what that means, they basically upload mostly .pdf files, but there are others that are acceptable to upload as well. The current system that is being used, uses a simple FileUpload and saving it to a folder on the d: drive of the webserver. I ran into a problem that with anyone outside the building/network, the upload is extremely slow and seems to be limited files no larger than about 1.4MB. There have been a few cases where larger file have made it through, but those ar few and far between. I've tried a couple different 3rd party components, but seem to run into the same limits. So, I install the FTP server on the box with the IIS and am trying to go the FTP route using ftpwebrequest.

Below is what I have put together so far:

Imports System.Net
Imports System.IO

Partial Class _Default

[CODE]...

This seems to work as it is at the moment, but I know it has a long way to go for catch exeptions, speeding it up...

1.) The first problem I have run into is if you try to upload to large a file, you get Out of memory error. I'm needing to change the buffer so that it is buffering chunks instead of the entire file. I've googled over and over again and seem to find several good options in C#, but can't seem to convert them to VB. So, could some one give me some idea how to take what I have and change the buffering to use smaller chunks.

2.) I need to catch an empty UploadFile field.

3.) I will eventually be changing this so that it handle multiple file uploads like my current system uses. (Did I mention that I'm new to the ASP.NET and have been programming in .ASP)

4.) As you will notice from my list of acceptable file types, I might have a problem with some needing to be upload as Binary and some not. So I'm going to have to come up with a way to test and change the Requested.UseBinary = False as needed.

I'm sure that I'll find other items as I progress or the big bosses will find other things that they want to add, but for now.... I know that given enough time, I will get all of these items worked out.

By the way, we have a network adminstrator that leave a lot to be desired and most IIS and now FTP I'm having to learn, implement and configure. I'm wondering if there is anything else that could be causing these limits in file size. Since I've tried 4 completely different forms of uploads and they all seem to run into the same limits, I thought there might be something in a router, firewall, server configuration.... that I might need to look into as well.