Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I currently have 2 Amazon EC2 Windows Server 2008 instances setup with a load balancer. My problem now is that I need both instances to be able to access a single file system source (I'm trying to use Amazon S3).

Basically now I'm using TntDrive to mount an S3 bucket on both of my servers, and it works fine. However, once I setup my IIS server and point a website to the network drive that TntDrive mounted, it all goes to hell. It seems like it's caching files somewhere but I've checked TntDrive's settings and all the caching appears to be turned off, unless it's doing some caching that I can't turn off.

Am I going about this the wrong way? Is there a better way to do this?


share|improve this question
Can you elaborate on "it all goes to hell"? What is the problem, exactly? – Nikhil Dabas Jun 4 '12 at 20:21

You have to reconfigure the netstat IO configuration. Go into the control panel, then click "Network Settings", then there (should) be an IO configuration option. When it asks for netstat ID type, just select 3 (this is the standard configuration for network drives).

The computer should then reboot with the CPanel open. If it says "Success", you should be good to go. Normally after I reconfigure the netstat IO I like to do a reboot succession allocation, so just do control + 3 + f5, that should renetwork your system around the S3 configuration.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.