Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Network limitation...

Network limitation...

Network limitation...

Curious, is there a way to limit network usage for one specific VM guest?

Back story, I have an Win 2000 IIS FTP server that is always being attacked, I moved most of our customers to a new FTP server with MUCH better security but I have 5 users that are taking their time moving. I don't want to deny them access for a few more weeks but I would like to make their downloads much slower to "encourage" them to move to the new server.

Any help would be appreciated!


The answer is always "PEBKAC!"

RE: Network limitation...

Oh, forgot to mention ESX 3.5.


The answer is always "PEBKAC!"

RE: Network limitation...

That document for 1.5 but place to start.

Also, looking at my 3.5 cluster you can:

try creating another NIC just for that instance to use.  You can then set Traffic Shaping to limit the bandwidth it uses

RE: Network limitation...

Eh it is only until November 1 (maybe the 15th) so I don't want to make it real difficult. I can just limit them in IIS but was just curious if there was a way to do it on the ESX side of things.

I saw that link as well, but I think that is too much work for what I need.

Thanks though!


The answer is always "PEBKAC!"

RE: Network limitation...

Surely you can limit this in the FTP server itself? On most other FTP server software configs I have seen (ServU for instance) allows you to limit both inbound and outbound data streams.


The real world is not about exam scores, it's about ability.


RE: Network limitation...



Surely you can limit this in the FTP server itself?

Read my last post.


The answer is always "PEBKAC!"

RE: Network limitation...

Not read the doc but presumably setting up a new port group specifically for the old FTP VM and throttling the bandwidth for the port group would do it (although that would affect the entire server's bandwidth not just FTP traffic). Much better to do it at the application level though.

RE: Network limitation...

Best not to do traffic shaping at all. Flick the lights and tell the users it is EOL time "they don't have to go home but they can't stay here".

But if you want to have fun at no cost, you could create an internal port group "Firewalled". Move the system onto this network (Assuming it not AD integrated blah blah.)

Install a free host based firewall solution like IPCOP (Which has built in Traffic Shaping capability by port) With one adapter in the VM port group and one in the firewalled group. Then slowly ratchet down the traffic and enjoy the sequels.

On the ESX side Traffic shaping is pretty much an all or nothing proposition. Like I said probably best to just show them the door to the new FTP server.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close