Tag Archives: protocol

Mozilla Release Firefox 13.0.1 Browser Update

19/06/2012 Stuart Davey

Firefox 13.0.1 introduces the following new features, security updates and fixes

FIXED – Windows Messenger did not load in Hotmail, and the Hotmail inbox did not auto-update (764546, fixed in 13.0.1)
FIXED – Hebrew text sometimes rendered incorrectly (756850, fixed in 13.0.1)
FIXED – Flash 11.3 sometimes caused a crash on quit (747683, fixed in 13.0.1)
NEW – When opening a new tab, users are now presented with their most visited pages
NEW – The default home page now has quicker access to bookmarks, history, settings, and more
CHANGED – SPDY protocol now enabled by default for faster browsing on supported sites
CHANGED – Restored background tabs are not loaded by default for faster startup
CHANGED – Smooth scrolling is now enabled by default
DEVELOPER – 72 total improvements to Page Inspector, HTML panel, Style Inspector, Scratchpad and Style Editor
DEVELOPER – The column-fill CSS property has been implemented
DEVELOPER – Experimental support for ECMAScript 6 Map and Set objects has been implemented
DEVELOPER – Support for the CSS3 background-position property extended syntax has been added
DEVELOPER – The :invalidpseudo-class can now be applied to the element
DEVELOPER – The CSS turn <angle> unit is now supported
SECURITY FIX – MFSA 2012-40 Buffer overflow and use-after-free issues found using Address Sanitizer
SECURITY FIX – MFSA 2012-39 NSS parsing errors with zero length items
SECURITY FIX – MFSA 2012-38 Use-after-free while replacing/inserting a node in a document
SECURITY FIX – MFSA 2012-37 Information disclosure though Windows file shares and shortcut files
SECURITY FIX – MFSA 2012-36 Content Security Policy inline-script bypass
SECURITY FIX – MFSA 2012-35 Privilege escalation through Mozilla Updater and Windows Updater Service
SECURITY FIX – MFSA 2012-34 Miscellaneous memory safety hazards

Microsoft, SBS 2011, Service Pack 1, Service Pack 1, Service Pack 1, Service Pack 1, Small Business Server 2011, Windows, Windows 7, Windows Server 2008 R2

Http.sys – Pre Service Pack 2 Revision History for Windows Server 2008 R2 SP1, Windows 7 SP1 and Windows Small Business Server 2011 (SBS 2011)

23/03/2012 Stuart Davey

Http.sys – Pre Service Pack 2 Revision History for Windows Server 2008 R2 SP1, Windows 7 SP1 and Windows Small Business Server 2011 (SBS 2011)

05-Oct-2012 – 6.1.7601.22126 – Http.sys – x64 – http://support.microsoft.com/kb/2768523 – “0x0000007E” Stop error after you configure a computer to host a web service in Windows Server 2008 R2

24-Nov-2011 – 6.1.7601.21866 – Http.sys – x86/x64 – http://support.microsoft.com/kb/2634328 – Increased latency occurs on an HTTP connection to a computer that is running Windows Vista, Windows 7, Windows Server 2008 or Windows Server 2008 R2 if the connection is through a load balancer

17-Sep-2011 – 6.1.7601.21822 – Http.sys – x86/x64 – http://support.microsoft.com/kb/2618425 – “0xC0000010” error and Http.sys intermittently ends TCP/IP connections in Windows 7 or in Windows Server 2008 R2

31-Aug-2011 – 6.1.7601.21805 – Http.sys – x86/x64 – http://support.microsoft.com/kb/2607930 – Slow performance when an application retrieves a file on an SMB share by using the HTTP protocol in Windows 7 or in Windows Server 2008 R2

Microsoft, SBS 2008, Service Pack 2, Service Pack 2, Service Pack 2, Service Pack 2, Small Business Server 2008, Windows, Windows Server 2008, Windows Vista

Ntfs.sys – Pre Service Pack 3 Revision History for Windows Server 2008 SP2, Windows Vista SP2 and Windows Small Business Server 2008 (SBS 2008)

23/03/2012 Stuart Davey

Ntfs.sys – Pre Service Pack 3 Revision History for Windows Server 2008 SP2, Windows Vista SP2 and Windows Small Business Server 2008 (SBS 2008)

04-Apr-2012 – 6.0.6002.22833 – Ntfs.sys – x86/x64 – http://support.microsoft.com/kb/2698155 – An application does not read or access a file correctly in Windows Server 2008 R2, Windows Server 2008, Windows 7, or Windows Vista

03-Mar-2013 – 6.0.6002.23070 – Ntfs.sys – x86/x64 – http://support.microsoft.com/kb/2840149 – MS13-036: Description of the security update for the Windows file system kernel-mode driver (ntfs.sys): April 9, 2013

03-Mar-2013 – 6.0.6002.18799 – Ntfs.sys – x86/x64 – http://support.microsoft.com/kb/2840149 – MS13-036: Description of the security update for the Windows file system kernel-mode driver (ntfs.sys): April 9, 2013

05-Apr-2012 – 6.0.6002.22833 – Ntfs.sys – x86/x64 – http://support.microsoft.com/kb/2698155 – On-demand antivirus scans do not work as expected in Windows Vista, in Windows 7, in Windows Server 2008, or in Windows Server 2008 R2

05-Mar-2012 – 6.0.6002.22811 – Ntfs.sys – x86/x64 – http://support.microsoft.com/kb/967351 – A heavily fragmented file in an NTFS volume may not grow beyond a certain size

27-Feb-2012 – 6.0.6002.22804 – Ntfs.sys – x86/x64 – http://support.microsoft.com/kb/2673320 – Computer stops responding when you perform a file operation on a directory in Windows Vista SP2 or in Windows Server 2008 SP2

24-May-2011 – 6.0.6002.22650 – Ntfs.sys – x86/x64 – http://support.microsoft.com/kb/2550862 – FSExtend tool fails to extend a LUN in Windows Server 2008

28-Apr-2011 – 6.0.6002.22632 – Ntfs.sys – x86/x64 – http://support.microsoft.com/kb/2535094 – Server stops responding when you lock or unlock files on a network by using the SMB2 protocol in Windows Vista or in Windows Server 2008

18-Mar-2011 – 6.0.6002.22616 – Ntfs.sys – x86/x64 – http://support.microsoft.com/kb/2525064 – Ntfs.sys driver takes a long time to mount a large volume in Windows Vista or in Windows Server 2008

10-Dec-2010 – 6.0.6002.22544 – Ntfs.sys – x86/x64 – http://support.microsoft.com/kb/2471430 – You cannot restore large files in the NTFS file system when all the data streams that have sparse attributes are deleted in Windows Server 2008 or in Windows Vista

13-Sep-2010 – 6.0.6002.22486 – Ntfs.sys – x86/x64 – http://support.microsoft.com/kb/980382 – The computer stops responding when you rename a folder in Windows Server 2008, in Windows Vista, in Windows 7 and in Windows Server 2008 R2

07-Jul-2010 – 6.0.6002.22441 – Ntfs.sys – x86/x64 – http://support.microsoft.com/kb/981891 – Disk Manager reports incorrect disk usage a while after the operating system starts in Windows Server 2008 or in Windows Vista

19-Mar-2010 – 6.0.6002.22368 – Ntfs.sys – x86/x64 – http://support.microsoft.com/kb/981166 – Some data is corrupted when cached and noncached I/O operations occur by using the same NTFS file handle

11-Mar-2010 – 6.0.6002.22360 – Ntfs.sys – x86/x64 – http://support.microsoft.com/kb/976538 – File corruption may occur if you run a program that uses a file system filter driver in Windows 7, Windows Server 2008 R2, Windows Vista, or Windows Server 2008

08-Dec-2009 – 6.0.6002.22283 – Ntfs.sys – x86/x64 – http://support.microsoft.com/kb/977675 – A computer that is running Windows Vista or Windows Server 2008 stops responding at a black screen early in the startup process

14-Oct-2009 – 6.0.6002.22245 – Ntfs.sys – x86/x64 – http://support.microsoft.com/kb/975663 – Stop error message on a computer that is running Windows Server 2008 SP2 or Windows Vista SP2: “0x00000024 NTFS_FILE_SYSTEM”

17-Aug-2009 – 6.0.6002.22201 – Ntfs.sys – x86/x64 – http://support.microsoft.com/kb/974646/EN-US – A computer that is running Windows Server 2008 SP2 or Windows Vista SP2 stops responding when an application uses the NTFS sparse files

14-Aug-2009 – 6.0.6002.22200 – Ntfs.sys – x86/x64 – http://support.microsoft.com/kb/974127 – An ERROR_ACCESS_DENIED error is returned in Windows Server 2003, in Windows Vista, or in Windows Server 2008 when you call the DeviceIoControl function together with the FSCTL_LOCK_VOLUME control code

15-Jun-2009 – 6.0.6002.22152 – Ntfs.sys – x86/x64 – http://support.microsoft.com/kb/972135 – Backups fail and Event ID 12293 is logged on a computer that is running Windows Vista or Windows Server 2008

19-May-2009 – 6.0.6002.22138 – Ntfs.sys – x86/x64 – http://support.microsoft.com/kb/971279 – The first attempt to eject a removable cartridge disk drive fails on a computer that is running Windows Vista or Windows Server 2008

18-May-2009 – 6.0.6002.22138 – Ntfs.sys – x86/x64 – http://support.microsoft.com/kb/965497 – You receive the Stop error 0x00000050 and then the computer restarts automatically if the OpenFileById function opens a folder and then the handle returned is used to rename files on a computer that is running Windows Server 2008 or Windows Vista

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

02/11/2011 Stuart Davey

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”.

Aid In IT

Tag Archives: protocol

Ntfs.sys – Pre Service Pack 3 Revision History for Windows Server 2008 SP2, Windows Vista SP2 and Windows Small Business Server 2008 (SBS 2008)

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

IT – Software and Hardware Support Resources