Fax, Microsoft, SBS 2008, SBS 2011, Small Business Server 2008, Small Business Server 2011, Windows, Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows Vista

The Microsoft Fax Service crashes when you receive a fax on Windows Server 2008 – SP2, SBS 2008 – SP2 or Windows Server 2008 R2 – SP1, SBS 2011 – SP1

You may find that the Microsoft Windows fax service randomly crashes when your server is receiving a fax, this will be evident in the Windows Application Event Log where you will find Event ID 32083 and 32089.  These Events will contain the following errors/warnings:

The Fax Service failed to execute a specific routing method. The service will retry to route the fax according to the retries configuration. If the retries fail, verify routing method configuration.

and/or

Unable to route fax FileName to the requested e-mail address. The following error occurred: 0x80040211 This error code indicates the cause of the error. Check the SMTP server configuration, and correct any anomalies.

The error is related to two classes not being unregistered each time the Inetcomm.dll module is unloaded, next time it is loaded to route a fax a function still tries to point to the old address and causes the Fax Service to Crash.

The issue can be resolved by installing the Microsoft Hotfix from KB 973640 http://support.microsoft.com/kb/973640 this hotfix contains updated versions of Inetcomm.dll and Inetres.dll for Server 2008/Vista/SBS 2008 and just a new version of Inetcomm.dll for Server 2008 R2/Windows 7/SBS 2011

Fujitsu, HP, Internet Explorer, Internet Explorer 8, Internet Explorer 9, Microsoft, ML110 G5, ML350 G5, ML350 G6, Office, Outlook 2010, Primergy, ProLiant, Uncategorized, Windows, Windows 7, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP

Remote Desktop Sessions Pause Or Exhibit Unresponsiveness – Lag Whilst Typing And Session Will Not Accept Mouse Inputs

Remote Desktop Services can be extremely useful, allowing users to access a terminal server or their company desktop computer from another location.  One very common complaint with RDP sessions is screen refresh delays and a delay when typing or trying to click on items using the mouse cursor.  It will appear to most that the session has become unresponsive for a period of 5-20 seconds, after this delay the session will return to normal for a period of several minutes before once again becoming unresponsive.  You may find that this issue becomes more apparent as more users connect to the specific terminal server in question and if all these users utilise several applications (i.e. Outlook, Word and Excel) together.

Causes for poor user experience when connected via RDP are varied but one of the most common is resource exhaustion or contention.  This in turn causes a delay in processing that appears as a pause or unresponsiveness.

Check that your computer or terminal server has sufficient Memory to cope with the current load.

The next thing to verify by using performance monitor is that the PhysicalDisk\% Idle Time is consistently high, that’s correct this should be 90-100% when the server is not very busy.

It is worth running performance monitor using the PhysicalDisk\% Idle Time counter whilst you are seeing the slowdowns, this will help identify if your hard disk or controller are causing contention and in turn the pausing or unresponsiveness.

If you do find that the “%Idle Time” keeps going very low then it’s time to consider some of the options below to help resolve the issue

  • Install a second drive or mirror set, move the Windows Page File to this second disk/array to reduce the load on the drive/array holding your operating system
  • Install additional memory into the computer or server, this will reduce paging to disk and will generally improve overall system performance
  • Migrate to or upgrade your existing RAID controller to a unit that had a Battery Backed Cache (Fast) or Flash Backed Cache (Newer – Faster) to significantly improve performance and alleviate the system
  • Migrate to faster hard disk drives, 7200, 10,000 or 15,000 RPM drives are amongst the fastest.  The SATA interface is slower than the SAS interface but is cheaper.  Try to invest in the fastest drives that you can to future proof the system and avoid future performance issues if you have to scale for more users.
  • Ensure that you have at least 20-25% free disk space on all partitions/drives
  • Defragment all drives on a regular basis to optimise read and write operations
  • A cheap solution for improving disk performance may be to turn on the Hard Disk Cache using “Device Manager” or in the event that you are using a RAID controller without a battery backed Cache module you will need to open the RAID Array Management Software and then enable Disk Cache within the management software as this feature will not be available within “Device Manager” in this instance.  Please note that this does have some risks and should be used with caution, you may loose data in the event of a sudden/unexpected loss of power to the system.  Consider using this option with a UPS and redundant power supplies to reduce the risk of power loss to the system.  As always ensure you have a reliable backup that is carried out at regular intervals.

Example – HP RAID Array Configuration Utility:

Example – Windows Device Manager:

FireBox, Microsoft, SBS 2008, SBS 2011, Small Business Server 2008, Small Business Server 2011, SSL VPN, Watchguard, Windows, Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows Vista, XTM

Watchguard – SSL VPN clients cannot resolve internal host names despite DNS servers being configured for the connection

You may find that when you configure your Watchguard XTM Firewall to accept SSL VPN connections that clients can connect to

the VPN and ping IP addresses of internal resources, however you cannot resolve internal hosts even via FQDN using DNS.  You

may also find that when you run NSLOOKUP on the SSL VPN connected client that the  result is your Internet Service Providers

DNS servers rather than the DNS servers assigned via the VPN connection.

 

To resolve the issue you can change your SSL VPN configuration from a “Routed VPN” to a “Bridge VPN”, the routed VPN uses a

virtual IP address pool (192.168.113.0/24) which does not match your internal IP range or the address range of the internal

DNS Servers.  When a Windows client connects to the “Routed VPN” it appears that due to the DNS server mismatch they are not

utilised by the client.

 

When you configure the VPN in “Bridge VPN” mode you can work around this issue, the Bridge VPN configuration allows you to

exclude some addresses from your Windows DHCP Server Pool and add the into them “Start” and “End” IP addresses on your

Watchguard SSL VPN Configuration Page. The Watchguard will now become responsible for assigning these internal IPs to VPN

clients as they connect rather than the Windows DHCP Server.

 

You should now find that when your SSL VPN clients connect that they are assigned an IP address and DNS server that are all

within the existing internal IP range of your network.  An NSLOOKUP should now return your internal DNS server address and

you should be able to ping hostnames and FQDNs that reside within your internal network.

 

Examples:

ping windowsserver

ping windowsserver.exampledomain.local

 

Please remember that the only down side with this configuration is that a “Bridge VPN” bridges to the “Trusted” interface,

this means that the client computer can access any internal resources that they have permissions for by default. A “Routed

VPN” allows you to offer traffic to Optional/secondary networks and gives you more control by letting you lock down access

using “Specify allowed resources”.

Microsoft, SBS 2011, Small Business Server 2011, Windows, Windows 7, Windows Server 2008 R2

The Startup Process in Windows 7 – SP1 or Windows Server 2008 R2 – SP1 may be slower than expected

An issue that was identifed a few months ago is slow system startup with your Windows 7 Desktop/Laptop or Windows Server 2008 R2 Server.  This is related to a delay in the initilisation of the Microsoft Software Shadow Copy Provider (Deals with Shadow Copy, System Restore and Backup).

All is not lost as this issue can be fixed by applying the latest version of Volsnap.sys to your operating system

Currently the latest version can be found in the following Microsoft Hotfix (KB 2548124) and applies to Windows 7 and Server 2008 R2 – RTM or Service Pack 1 installs.

http://support.microsoft.com/kb/2548124

IT – Software and Hardware Support Resources