Social Icons

twitterfacebookgoogle pluslinkedinrss feedemail
Showing posts with label Windows. Show all posts
Showing posts with label Windows. Show all posts

Monday, 17 February 2014

Setting up FTP on EC2 Windows Instances

Configuring FTP to a running Amazon AWS EC2 Windows instance without an elastic IP.



In this article i am going to configure Filezilla FTP Server on a Amazon AWS EC2 Windows instance.

Loginto your Amazon AWS Management Console and select EC2 . Once the instance is accessible, we will need to change some settings:

In AWS, select “Security Groups” from the left-hand menu.

Select the name of the security group for the instance you just created
In the window at the bottom of the screen select the “Inbound” tab from the small frame.
Pick “Custom TCP Rule” from the “Create a new rule” dropdown.
Enter 50000-51000 in the port range field.

In the source field, use discretion. Leaving the field at 0.0.0.0/0 will allow all. 
(That may be ok depending on your intended use, I’m using it as a disposable server, so I’m not going to get into security in this article.)

Select “Add Rule” and the “Apply Rule Changes” (Make sure you do both!!!).

Now repeat the steps  for port 21.

Finally you can see the inbound rules on the right side

The second step is to setup FileZilla Server. 

Install FileZilla Server on the Amazon Instance and create a FTP user with password.

Click the settings icon on the interface.
On the general settings tab, “Listen on these ports:” will be defaulted to 21. Just leave it.
Select the “Passive mode settings” from the tree on the left.

Place a check mark next to “Use custom port range” and set the port range to “50000-51000”.

Now get your “Public DNS Name” from the Amazon AWS console. Your IP address will be in the Public DNS Name, .
Enter the IP into the “Use the Following IP” field on FileZilla’s “Passive mode settings” screen.
Now we are at the final step. You will now need to adjust the Windows Firewall settings to allow the ports we allowed in the AWS Security Group.

And you are done! Go ahead and connect with your favorite FTP client.


Sunday, 16 February 2014

Redirect HTTP requests to HTTPS on IIS 7

Automatically Redirect HTTP requests to HTTPS on IIS 7 using   URL Rewrite 2.0

 Requirements


 - SSL Certificate for site installed in IIS.
- Site properly installed and configured for SSL (site set up and binding in IIS configured).
- URL Rewrite 2.0 is installed on the sever.
  
Install URL Rewrite 2.0 on your webserver,

download url: http://www.iis.net/download/URLRewrite

This is a plug-in for IIS 7 that allows you to manipulate URL’s.

URL Rewrite has a GUI to allow you to enter rules within IIS 7; in the background all this does is edit the web.config file of the site. I will show you how to create a rule both ways.

- Select the website you wish to configure
- In the “Features View” panel, double click URL Rewrite

Friday, 24 January 2014

TFS 2012: Comparison of Team Foundation Server’s Editions

This blog post is part of a blog series to introduce Team Foundation Server to new users. The blog series will also contain articles targeting intermediate and expert users.  I will be using Team Foundation Server 2012 Update 1 and Visual Studio 2012 Update 1 throughout the series. If you have any questions or you want me to cover a specific topic, please don’t hesitate to contact me.

Expertise Level

Intermediate

Getting Started with Team Foundation Server

TFS comes in three flavours:
  • Team Foundation Server Service (tfs.VisualStudio.com)
  • Team Foundation Server Express
  • Team foundation Server
Choosing which flavour you need depends pretty much on your requirements. In this article I will shed light on each version and why you want to choose one vs the other.

Introducing Team Foundation Server’s Editions

 
Blogger Templates