Category: Hardware

You get a non-default setting when you run the Exchange 2007 BPA. It says:Disk timeout on server SOLACESERVER.solace.local is not set at the default of 10 seconds. This is normal if third-party storage software is installed. Current timeout value is 30 seconds.

As the message says, if you use some type of storage software, leave this be. I do not use any of this software, so I want to change it back to default. not that it might cause damage, but if it shows up here then it is a possability. As always make sure you backup and do this on a test server or in mock. I have no test server and I am daring, so I am going to do it during lunch on a Wednesday.

The setting is documented here.

Microsoft tells us to:

To revert to the default configuration
1.Open a registry editor, such as Regedit.exe or Regedt32.exe.

2.Navigate to:


3.In the right pane, delete the TimeOutValue entry. Alternatively, double-click the TimeOutValue entry and set it to one of the following values:

On a non-clustered server, set the value to 10.

On a clustered server, set the value to 20.

If your hardware manufacturer recommends a different value for either a clustered or non-clustered system, use the value from your hardware manufacturer instead.

4.Close the registry editor, and then restart the computer for the change to take effect.

So let’s do what they tell us. Ill add some screen shots.

This is what the current registry entry looks like.

Before Change

Before Change

Double click it. Change to 10. It should look like this now:

After Change

After Change

I would like to point out this warning:

Installing host bus adapters (HBA) or other storage controllers can cause this key to be created and configured. When you install or reinstall these drivers, the TimeOutValue registry value is overwritten with the value that is required by those drivers. You may have to contact the hardware vendor to determine the correct TimeOutValue registry value for your configuration.

Read it carefully. I HAVE installed a HBA as well as a storage controller. I looked up the values for my HP Proliant, and they should be at thirty. I will leave this entry alone and safely ignore it from within the BPA.

This is part one, covering the setup and dhcp tabs.

Router documentation is well written from a technical standpoint. It tells you exactly what each option is. What it often lacks is a description of what each option does, and what setting is recommended. In this blog post series, I will describe each tab and setting of a RV016 Linksys router, and what the settings do and should be set to. Your settings will obviously not be the same as mine, but my examples should head you in the right direction.

Before we start, you need to know your IP address scheme. There are a million sites on this, so I will not get into it. I would suggest writing it out on paper to refer to while configuring. It also helps to know what services you will be running on the domain. You only want to allow through what you need to let through, and UPnP often opens “extra” ports in your router that are not specifically needed.

To get a general understanding of how the router works, I will describe the path information takes when leaving a domain.

  1. A workstations sends out a data packet.
  2. It queries a DNS server on where it should go. The DNS server will in most cases be your server, or a server.
  3. It then gets forwarded to the correct IP address- in this case the internal IP address of your RV016, or your default gateway.
  4. Then that router queries its external DNS, which is most likely your ISP. With that information, your router sends the data to the correct location.

I know a lot more goes on under the hood, but this is a basic explanation of how the network path will go- keeping a visual of this in your head helps when designing IP addresses and pointing DNS.

For this explanation, I will assume that you have bought the router, have an internet connection with a static IP address, your server has a NIC, and that you have connected at least 1 workstation and the server to the router ports, and the router is connected to your modem.

This article also assumes that you know the basics, and can gloss over items not generally used in a simple server network. Furthermore, I assume that you know you must hit save after changes, and how to navigate tabbed browsing- do not get angry if you changes do not take due to not saving your work.

In this scenario we use Comcast Broadband cable, with a static IP address of 70.89.23x.x5- I am going to leave some IP bits masked for security purposes. Not that I mind if my public IP address is known, but why risk it, right? The internal IP addressing scheme that I used was In hindsight, this was a mistake. As the default, most home network have this type of IP address. this causes problems when connecting remote machines to the network, with IP address conflicts. Pick something else- even as simple as

Our router is connected, let’s log in. The default IP is, so open up a web browser and type that into the address bar. you will be prompted for a user name and password. Administrator is the user name (the RV016 is case-sensitive, fyi) while the password is either admin, or 1234.

Your ports will not be green, and your ip addresses will not be filled out.

Summary Screen

Summary Screen

The green boxes are port status- telling you if a port is active or not. This can be important for troubleshooting.

LAN IP is the routers internal IP address. This is

WAN1 and 2 IP are the external IP addresses of the router. I only use one, but you can configure two to host another network, provide modem failover, bandwidth throttling, etc.

DMZ is for the demilitarized zone, if you plan to provide a separate network segment for internet access.

You will want the mode to say Gateway if this is your main router.

Then you have DNS, this is your external DNS- the DNS of your IP. Comcast’s main DNS is This can be changed to suit your needs and location. Google Public DNS and OpenDNS are alternatives.

The rest of the settings are for later, lets just skip over them.

The first thing you will do is set up your IP address. Click the setup tab up top.

Setup Tab- Network

Setup Tab- Network

Host and Domain name will most likely be left blank.

Device IP address will remain at, unless your address scheme is different. Say your network is, then this would be the device IP address.

Chose a subnet mask to fit your network. The default and mine is And explanation of ip addresses and subnets can be found here. After, you can add multiple subnets. I have one added, though it is not in use. If you don’t know what this is, you don’t need to change it ūüôā

In the bottom tables, you have settings for your WAN ports. I only use WAN2, so I will leave WAN1 set to automatically obtain IP address, which is nothing in this case. I will also leave DMZ alone, as I do not use a DMZ. Click edit for each of these items if you wish to use them.

Click Edit on WAN2, and we will configure this ports settings.

WAN2 IP Setup

WAN2 IP Setup

Select Static IP.

Enter in the WAN IP address provided by your ISP. this is your internet IP.

Provide the subnet mask and default gateway they they provide. This should all be on the pink slip you got when the internet was installed.

DNS server are your external ISP’s DNS servers. For most cases, leave MTU to auto- we can alweays adjust it later if necessary. Save and click on password subtab.

Change the router password. Use complex strong passwords, and change them every couple of months. I have a string that I remember because it rhymes, but it is very complex with all the trimmings. I would suggest doing the same, and NOT writing it down.

If I was a burglar, and I broke into your server room, the first thing I would do would be to check drawers, under the keyboard and calendar, and notebooks for written down passwords (then I would probably pry open the case to steal your HDD’s, but that’s for later).

Save and move on to Time. Leave this as default, unless you need to change it. DMS Host- we dont need to change this with no DMZ.

Forwarding- this is a BIG one! In order for your network to even work, there are certain things that you need to forward to the server. This is telling certain types of communication coming into your network via the external IP address that they need to report to the server, who then forwards them on to their destination (ther server is the internal DNS server).

I will list the things you need to forward to your DNS server. Bold text is necessary, underlined is probably necessary, and regular text is optional depending upon services.

Setup Forwarding

Setup Forwarding

  • SMTP– TCP25, allows mail to come in, dependent upon your email configuration
  • HTTP– TCP80- web browsing, and a lot of default services
  • HTTPS– TCP443- Secure HTTP, used for Remote Companyweb/RWW/etc
  • Companyweb– TCPxxx- this is the port that you set up remote Sharepoint access on, which is changed in IIS Manager
  • PPTP- TCP1723- if you dont know what this is leave it alone, but this allows VPN connection
  • Hostmonster- TCP26, my remote mail provider does not operate on port 25, we use 26 instead
  • RWW– TCP4125, for Remote Web Workplace access
  • HTTPS Secondary- TCP8443, default secondary HTTPS port, used for multiple secure sites. I use mine for a private database site
  • FTP- TCP21, use this if your network has any FTP sites or servers
  • TELNET- TCP23, use this if you have any need to telnet into the server. I use this for mail troubleshooting, and disable it when not needed
  • L2TP- UDP1701, this is used for VPN tunneling protocol. DO NOT enable this unless you use L2TP VPN
  • RD– TCP3389, Remote Desktop port. This can be defined through your network access policy

You can of course add to this list. If you need a port open for a particular application, then open that port and forward it to the server. Do not open spare ports for the heck of it. Remember that this router supports UPnP. You can also run UPnP, and then run the Connect to the Internet Wizard. I prefer not to do this, personally.

One to the one-to-one nat tab; you probably don’t need this enabled for a simple network. MAC Clone, DDNS, and Advanced Routing you will most likely leave alone.


You will only enable this if your router is handling DHCP, which provides IP addresses for connected devices. A typical server setup will have the server providing DHCP. There are configurations using both server and router DHCP in case of server failure or vice versa- but typically you will leave this setting alone. The status tab tells you the status of the router DHCP if it is enabled.


I was surfing through my server manager, and I noticed a whole lot of yellow exclamation points on my server roles. After browsing them, I realized most were caused by the server reboot this morning, and can safely be deleted as 1 time events. I did notice an informational item under File Services.

Log Name:      System
Source:        volsnap
Date:          10/13/2010 12:00:34 PM
Event ID:      33
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      SOLACESERVER.solace.local
The oldest shadow copy of volume C: was deleted to keep disk space usage for shadow copies of volume C: below the user defined limit.

Server Manager and VSS Error Event ID 33

Server Manager and VSS Error Event ID 33

Configure Shadow Copies

Configure Shadow Copies

User defined limit? Did I set that? Oh well, let’s explore and see what it is set at, and how to gauge what the best settings are for a system. Navigate to Start>My Computer. Right click on the C: Drive and select Configure Shadow Copies.

I see four entries.





The first two are disabled. A:\ is my backup drive, and I do not it want Shadowed. The first is the¬†volumename for my backup drive, which is also not Shadowed- why would you make copies of the drive that you store copies on, after all. If it WAS enabled, you could change it’s scheduling under scheduled tasks, Volume Shadow Copy. Were going to ignore those two for now- let’s focus on our two logical drives, C:\ and D:\. We do want these Shadowed- to provide previous version support for files, as well as for use in Windows Server Backup, which uses VSS.

These drives were both backed up today, they both have 10 shares, though the used size is different: 2088 for C:\, and 8921 on D:\. You will notice that both drives keep their own Shadow Copies. I at one time thought that this would be a good thing to change, so I put them both on a backup drive. Well, after that Windows Server Backup worked 50% of the time, and I could not change them back- exception error. So I suggest leaving them there.

Shadow Copies

Shadow Copies


But what about the size? Why are they different? Why does C:\ only have two copies while D:\ has 5? These settings are all set by Windows depending upon the drive size. My C: is 60Gb while D: is 90Gb. Also, D: has more content, and about the same free disk space. Proportionally the settings are correct- a large space for Shadow Copies on a larger drive. But C:\ is only keep two Shadow Copies, which gives you 2 previous version. You need more? Then increase the size by clicking settings and changing it.

You will notice in the settings menu that the limit is actually larger than the used- this is of course true. You can change it to no limit if you wish and have the space, or increase the limit to include many more copies. You can also change the schedule here- the default is twice a day. I like to leave mine here, though I change the times to make sure they do not run at the same time as other major things such as an Exchange backup.

In windows Server 2003 you had to keep the sizes as multiples of 300Mb, but this is no longer the case. As for the correct size- default is good. If you need it larger increase it untill you can keep the number of copies you wish. If you need it small, I suggest making it small incrementally, and make sure you can keep at lease 2 Shadow Copies. Making it too small might restrict Shadow Copies too much and interfere with Windows Server Backup.

You can also manage space and copies with the command line tool VSSADMIN, which is documented here at TechNet.

So after upgrading my install of SBS 2008 on my HP Proliant ML150 G5, I decided to upgrade the BIOS. The HP website offers an online ROM upgrade- meaning that you install it in windows and reboot. I thought i would try it out. I went to the site, and downloaded cp012032.exe (1.6 MB) which is for Windows Server 2008 x64. It is revision date 10/30/2009. 


To install it, you simply double click the file download, and reboot when prompted. I did this, rebooted, and let the configuration run. On the second boot I turned off the server and removed the small battery inside (AFTER unplugging the server). This reset the CMOS. Then I booted up, and it prompted me to set up some BIOS settings. I set the correct date and time, boot order, RAID, etc, then rebooted again. I got into Windows, and noticed that the server was loud. I mean REALLY loud.

Opening it up, I noticed the HDD System Fan (The large one in the front) was jamming away. So I rebooted again and looked through the BIOS for a fan speed setting. Nothing. I then installed an earlier revision of the BIOS, again resetting the CMOS. Still loud.

Alright, I called HP Support. Get the Serial Number and Product Number off the back of the server case near the rear ports. I got someone on the phone (less than 10 minutes, not bad), and they explained to me that my warranty expired. They could not open a case for me, but the tech continued to help me on the phone for over 20 minutes, which was surprising. they informed me to install Integrated Lights Out Management FW Upgrade, which is USB-Key Media. He sent me a custom link, and I set about doing this.

I was unaware what iLO was, so I Googled it. It is a card that you install in a HP Proliant that allows you to manage the server remotely, even when the server is off. I don’t have the card, so why did the tech tell me to install it? i called back, and after trying a bunch of things, the tech could not help me, and recommended that I DID NOT install the FW for a card I did not have.

So I researched a bit more, and stumbled across this post in the HP Forums– with the download located here– which does say to install the iLO to fix the fan speed. The server has been running with the fan cranked up for 5 days now. I am seeing no effects other than the obnoxious loud (It is LOUD) noise- though I would guess that running a fan at max significantly decreases it’s lifespan.

To install the USB-Key Media, download and run the MSI file. Then insert your usb drive, it needs to be a maximum of 2Gb. Click prepare my USB Media or equivalent, and it formats and installs the USB key. Then reboot, and keep the USB stick in. when prompted, boot from the key. Hit continue, continue, install. Make sure you don’t stop the install once it starts, or reboot.

I will be installing the iLO FW tomorrow evening, I will post on how it goes.


Woohooo, it worked! I rebooted to apply several Windows updates. i let the server reboot, finishin installing this time (that was how I destroyed my box last time), and logged in. then shut down, unplugged from the network and unplugged all external HDD’s. then I put in the USB, and booted up from it. It gave me a warning that the revision was not newwer than the curren one, and beneath that it said current revision 3.05, selected revision 3.11.

Crossed my fingers, let it bar up, reboot. Removed the drive, let it configure. It started to POST with the fan still screaming away, and about to hit Windows it hummed down. So far down I checked it to see if it was still on- it was. Logged in- everything is working as it should be! Thank God.


This blog is a simple list of changes I make to keep a Microsoft Small Business Server 2008 and accompanying network up and running. While I do not consider Microsoft, nor any of their software to be actually “stupid”, anyone who has ever worked on anything Microsoft certainly understand the ease with which a person can break their functionality. This is my specialty. Through out this blog I will document many system changes¬†both custom and necessary out of the box changes. It will include OS, software, hardware, and workstation changes. These changes should and will encompass a wide variety of topics to include:

  • DNS
  • DHCP
  • Active Directory
  • Exchange 2007
  • WSUS
  • Windows Backup
  • WSS 3.0 on IIS 7.0
  • Sharepoint Customization
  • SQL Server Express 2005
  • Windows 7, Vista, and XP
  • Network peripherals such as printers, routers, and switches

    Not only will these posts document my troubleshoot and error correcting process, but they will provide links to other sites with answers, or useful posts on help forums. while I do not promise that any of these posts will be accurate, I can assure you that to the best of my ability I am solving common and complex errors that might affect any user of any Microsoft product.Please allow credit where credit is due. I publish references and links to this site as a means of spreading information, without intent to infringe or harm. Feel free to contact me with any problems.

  • %d bloggers like this: