Today I was trying to change permissions on a folder in Windows Server 2008 R2 and I kept getting an "access denied" error. I'm the domain admin, so it was kind of perplexed. After some researching, I found a very quick solution so I decided to post it. I tried taking ownership of it using the GUI, but no dice. All I had to do is open an elevated (right click and run as administrator) command window and take ownership of the folder by running the following command.
In this basic VRF configuration tutorial, we will look at how to set up a VRF for a WAN interface, and get routing from the Internet to the router, or from the default Global VRF out out to the internet and back into the Global VRF. There are a number of reasons you might do this, but I generally configure this to make traffic destined to the router from the Internet be routed independently instead of having the reply traffic be routed according to the routing table in the Global VRF.
I'm kicking off the PRTG tutorials with a basic script to pull the number of RDS sessions into a sensor. This script will be able to pull in the total number of logons, and give quantities of RemoteApp sessions. You can also add specific software that you want to track the number of instances in use. Use this script to pull the aggregate quantity of sessions from a comma seperated list of session hosts, or just a single session host.
If you host an FTP server, you probably want to set it up as a passive FTP. To facilitate this with your firewall, you can do one of two things.
- NAT the standard FTP ports and a range of dynamic ports, and allow traffic on all those ports through the firewall.
- NAT TCP port 21, and do layer 7 inspection of the FTP traffic to dynamically open/forward the ports needed.
This is a walk-through for configuring option number 2. We will be connecting FTP server 10.0.10.15 to external IP 188.8.131.52 using port 21 as the ftp port. This assumes you already have your ZBF configured, and the zone-pair for your WAN to your Intranet is WANS_INTRA_PMAP.
Content filtering built in to Exchange is kinda like free antivirus software. Big promises, but it never works like it says. It either blocks ham (good emails, opposite of spam) or not much of the spam. I use a third party content filtering service called GFI. I'm sure there are others out there, but I have little to no experience with them. If you do use a third party filtering service, you're going to want to disable the filtering built into Exchange, and here's how.
With outdoor temperatures getting hotter and more humid, you may worry about your server room's climate contol systems being able to keep up. To set your mind at ease, check out LM Sensors for all your Linux servers.
In this scenario I was using MS Exchange 2010 and all my domain users were being prompted to login every time they started Outlook. The web app was working fine, but as long as they used Outlook, they would be prompted to login and type in the domain name before their username. It turned out to be an autodiscover problem in IIS. This is how I fixed it...