So you have DFSR setup and you run into issues with files not being copied, missing files or even performance issues. Here are some troubleshooting tips to investigate and possibly correct common DFSR issues.
First a quick introduction on DFSR. DFSR (Distributed File System Replication) formerly DFS, is a replication service that keeps folders/files synchronized across multiple servers. This allows for higher data availability using RDC (Remote Differential Compression). RDC allows for efficient updates of files across the network.
Read the full post »
So what is RSA Encryption and how can you benefit from it?
First, I’ll explain some background on RSA Encryption. RSA is basically an algorithm which uses a public key and private key. The public key encrypts information and the private key decrypts information.
How would this benefit you?
Read the full post »
Simply having Admin access to your server isn’t always enough. Here are some tips to help you stay up and running:
Read the full post »
Imagine this scenario: you’re sitting at your desk, finishing your work before the end of a long day. Suddenly, your phone starts ringing. You answer, only to hear a frantic voice on the other end notifying you that your site is down.
Insert panic here.
Before you start scrambling to change website configurations or code (or even pulling your hair out), try going through this checklist:
- Can you replicate the issue? I can’t stress how important this is. If anyone can distort what’s happening, it is the end user. An “Error 404 Request” (File not Found) can be explained to you as “The site is missing!” Verify that you get the same results following the steps reported to you. Maybe the user has an issue on their end or has a cached page. The possibilities are endless.
- Take a moment and think “Did I or anyone change anything recently that could cause this?” Maybe your developer was up late working on something, or maybe you made some changes and forgot to test the change. Many times, developers are typing away on the keyboard in the early morning hours, possibly changing code that will unknowingly bring the site down. Did anyone know the developer was working? Probably not.
- What is the specific error you are getting? There are numerous responses that can help you determine the cause. Remember that if you are using Internet Explorer, uncheck the “Show Friendly Http Errors” option. This can turn a blank page with no information into a page screaming “ERROR OVER HERE”.
- Is the site viewable outside your network? There are many sites online that can give you an external view. Don’t forget there is always the “Phone A Friend” lifeline. Asking someone you know to test it on their end can lead to some helpful results.
- DNS, DNS, DNS. Have you recently changed DNS or scheduled DNS to change? Depending on the change you made, DNS can be almost instantaneous or it can be a 24-hour long process. Perhaps you forgot a change was going to happen, or maybe you forgot to notify your users that there was maintenance happening.
- Is your web service even running? Regardless if it is IIS or Apache, etc.. There is a possibility that this service has stopped. Call your hosting provider or if you have server access, login to the server and verify it is running.
- Permissions? Maybe a file you changed doesn’t have the correct permissions. Maybe “Read” is not set properly.
Although many variables can come into play, it is important to cover the basics. Simply running through this checklist can save you time and frustration!
