I needed to setup a catch all for one of my clients domains. This is what I needed to happen: If user typed in an incorrect sub domain for mydomain.com that did not exist I needed it to redirect them to www.mydomain.com. For example: if they type in notreal.mydomain.com it will send the user to www.mydomain.com. Here is what I did to accomplish this:
I recently had the task of setting up VNC Server on CentOS for a client of mine. VNC is very much like remote desktop in windows. You can even use VNC on Windows servers. I found VNC to be a little bit slower then remote desktop and it kept kicking me out every once in a while. Here are the steps I took to set it up:
First I opened the necessary ports.
Path to access the firewall:
In this post I will show you how to setup an URL redirect in IIS 7. In this post I will assume you have some working knowledge of IIS.
Open IIS (Start –> Administrative Tools –> IIS Manager)
Expand your Web Server then right click on Sites and choose Add Web Site.
Give the site a name such as domain.com redirect. Be sure to add something to the name so you will know that it is a redirect if you need to reference it later. Put in a path for the web site. Redirects don’t really use the path but IIS won’t let you add the web site without this. I created a directory in the following location: C:\inetpub\redirects. I alwyas create this and use this location to place all of my redirects in. Put in the desired IP address or leave it on all unassigned and click OK.
Now double click on “HTTP Redirect” the properties will appear.
Do you want to setup Exchange Server in your house and run your own email server? Let me guess you do not have a static IP address and do not want to get one. Well below are my steps on how to set this up.
What you will need:
- A Windows domain and an Exchange Server setup.
- Dynamic DNS service such as no-ip.com or dyndns.com.
- A purchased domain name from somewhere like voxdomains or any other service. Just make sure you have full management of the DNS.
Go ahead and setup your Domain controller with AD and your Exchange server. I assume you have some working knowledge of domains and networking so I am not going to cover how to do this in this article.
Once you have your Exchange up and ready to go. Go download the no-ip client or update client from the dynamic DNS service you signed up for. This client runs in your system tray and will update your no-ip address with the public IP whenever it changes. Now install the update client on your Exchange box.
Configure your router/firewall to forward incoming traffic on port 25 (my port is different as my ISP blocks incoming port 25. I will explain further below.) to your Exchange server. Configure your router/firewall to allow outgoing traffic on port 25. (my port is different as my ISP blocks outgoing port 25. I will explain further below.)
Go to your domain host and add the address your dynamic DNS service gave you. For example your domain MX record points to test.no-ip.com. Now you should be able to receive and send mail.
Ok. above I mentioned my setup is a little bit different. This is because my ISP (Comcast) blocks outgoing and incoming SMTP traffic on port 25. This is a tactic by them to combat SPAM. They do however allow SMTP traffic in and out on port 587. Below I explain how to get around this.
Some applications on my network were having issues because the workstation clocks had the wrong time. I had to fix this but did not want to manually change it on every workstation. I did not want the user to have to always update this either. What I did is checked the time server my domain controller was using to sync with. It was set to time.windows.com. I used the NET TIME /QUERYSNTP command to check the NTP server.
I then went to Microsoft’s time server list here: http://support.microsoft.com/kb/262680 tracked down the correct time server. Once I found the NTP server I wanted to use I set the Configure Windows NTP client GPO to reflect this so all of the workstations would sync with this time server. Here is the GPO path:
Computer Configuration\Administrative Templates\System\Windows Time Service\Time Providers
I checked the next day and all of the computers on my network had the correct time.
If you don’t want to wait you can run the following commands to stop and start the time service on your clients:
Are you running server 2008 on your laptop or 1 box and don’t want to pay a bunch of money for antivirus? I have some Virtual Servers running 2003 and 2008 server for testing. I want them to be protected. Below are download links to ClamWin and Rising Antivirus. They are both free and are … Read more
Here is something new. Comodo is now offering Antivirus software for free. Wait! This is not just another free antivirus program. It is ok to use for commercial purposes. I wonder how long it will be before other antivirus companies offer a free commercial license. A way to save your company money and stay protected … Read more
We requested a new certificate for our website from a CA. We applied the certificate on the Internal IIS6 web server. I then exported the certificate including keys and imported onto our ISA 2006 firewall.
I then went into the publishing rule for our website and updated it with the new certificate.
When external users went to our website using https they got the following error:
Error Code: 500 Internal Server Error. The target principal name is incorrect. (-2146893022)
If you get an activation error after installing and trying to Activate windows 2008 server. You will need to call Microsoft. First type “slui 4” into a command prompt. This will bring up the Activation Call Center wizard and give the Installation ID Microsoft will need. They will give you a Confirmation ID and you … Read more
Have you ever setup a website in IIS and then you got this generic error: “Server Error in ‘/’ Application.
This is what I got right after installing SharePoint server 2007, setting up a portal and trying to access the site. Here is what you need to do to get a more detailed error so you can fix the issue. You need change a couple of settings by modifying the web.config file of your website.