October 2011 - Posts
You can find this week’s video here.
This week's video shows how to easily and quickly track down IPs and ports that need to be opened to allow legitimate traffic through the firewall.
Part of being a web server administrator is keeping your firewalls properly configured and troubleshooting to track down the necessary ports and IPs that have legitimate reasons to pass through your firewall. It’s not unusual to run into difficulty trying to find out which ports are required by a particular application. Sometimes you can determine which ports to allow by reading the specifications of the application. However, there are times when documentation is limited or you deal with a custom app.
This is now week 40 of a 52 week series for the web pro. You can view past and future weeks here: http://dotnetslackers.com/projects/LearnIIS7/
You can find this week’s video here.
You can find this week’s video here.
Log Parser is a powerful tool that every web administrator should become familiar with. With Log Parser we can do deep troubleshooting and data mining of the IIS Logs, Event Viewer, the File System, other file types and more.
Useful examples of parsing the IIS logs include: finding long running pages, finding all error pages with a 500 status code, all requests from a particular IP (potential hacking attempt), and much more.
This week is an introduction to Log Parser with walkthroughs covering Event Viewer, IIS logs, various filtering, different output formats, how to find your own way around, Log Parser Lizard GUI, and more. Log parser is a tool that no web administrator should be without.
This is now the 39th week of the entire series. You can view past and future weeks here: http://dotnetslackers.com/projects/LearnIIS7/
You can find this week’s video here.
You can find this week’s video here.
Note: This week’s video got stuck in the publishing process so sorry for the delay, but here it is. Next week I’ll move on to some other topics besides web farms, to mix it up.
Application Request Routing (ARR) does not have high availability built in, so it's up to us to implement a solution to ensure that ARR doesn't become a single point of failure. Options include hardware load balancers, other software load balancers, or two Microsoft options-namely NLB and Clustering Services.
Today's video discusses these options and then takes us on a walkthrough of setting up Microsoft's Network Load Balancing(NLB) solution. There are certain considerations to ensure that NLB works with your network and that it properly health tests to ensure that a failed node is automatically taken out of rotation.
For your reference, the following four links were mentioned in the video:
This is now the 13th week in a mini-series on web farms, and the 38th week of the entire series. You can view past and future weeks here:http://dotnetslackers.com/projects/LearnIIS7/
You can find this week’s video here.
More Posts