Tag Archives: VPN

Microsoft, Realtek, 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

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

Leave a comment

Tcpip.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-Feb-2014 – 6.1.7601.22590 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2918550 – Computer leaks nonpaged pool memory when IPSEC traffic is configured to use AuthIP without encryption in Windows

05-Nov-2013 – 6.1.7601.22502 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2905412 – Stop error 0xD1 on a Windows-based computer with multiple processors

10-Oct-2013 – 6.1.7601.22477 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2896146 – Packet loss occurs when MTU is below 576 and PMTU discovery is enabled on your Windows 7 SP1 or Windows Server 2008 R2 SP1

09-Oct-2013 – 6.1.7601.22476 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2885980 – FIX: A memory leak condition occurs when the FwpsAllocateCloneNetBufferlist() API is called

08-Sep-2013 – 6.1.7601.18254 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2885980 – FIX: A memory leak condition occurs when the FwpsAllocateCloneNetBufferlist() API is called

06-Sep-2013 – 6.1.7601.22443 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2885978 – 0x0000007F Stop error on a Windows-based computer

04-Sep-2013 – 6.1.7601.22441 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2885976 – User application freezes on a Windows-based computer that uses the WFP

04-Sep-2013 – 6.1.7601.18251 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2885976 – User application freezes on a Windows-based computer that uses the WFP

13-Jul-2013 – 6.1.7601.22383 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2871565 – “C000021B” error when you inject an NBL that contains multiple net buffers in Windows 7 SP1 or Windows Server 2008 R2 SP1

13-Jul-2013 – 6.1.7601.18209 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2871565 – “C000021B” error when you inject an NBL that contains multiple net buffers in Windows 7 SP1 or Windows Server 2008 R2 SP1

06-Jul-2013 – 6.1.7601.22378 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2868623 – MS13-065: Vulnerability in ICMPv6 could allow denial of service: August 13, 2013

06-Jul-2013 – 6.1.7601.18203 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2868623 – MS13-065: Vulnerability in ICMPv6 could allow denial of service: August 13, 2013

11-Jan-2013 – 6.1.7601.22215 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2524732 – An IPsec connection to back-end databases from a WTT application times out in Windows 7 or in Windows Server 2008 R2

10-Jan-2013 – 6.1.7601.22214 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2459530 – Event ID 5719 and event ID 1129 may be logged when a non-Microsoft DHCP Relay Agent is used

10-Jan-2013 – 6.1.7601.18048 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2459530 – Event ID 5719 and event ID 1129 may be logged when a non-Microsoft DHCP Relay Agent is used

04-Jan-2013 – 6.1.7601.22209 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2790655 – MS13-018: Vulnerability in TCP/IP could allow denial of service: February 12, 2013

03-Jan-2013 – 6.1.7601.18042 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2790655 – MS13-018: Vulnerability in TCP/IP could allow denial of service: February 12, 2013

30-Nov-2012 – 6.1.7601.22177 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2789968 – “0x000000D1” Stop error after you install the WDK WFP “inspect” sample in Windows 7 or Windows Server 2008 R2

29-Nov-2012 – 6.1.7601.22176 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2789397 – Data corruption and network issues when you run a WFP-based application on a computer that is running Windows

29-Nov-2012 – 6.1.7601.22176 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2789378 – Memory leak when an application uses the FwpsNetBufferListAssociateContext0 function in Windows 7 or Windows Server 2008 R2

29-Nov-2012 – 6.1.7601.22176 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2788573 – “0x00000050” Stop error when you run a WFP-based application to register a callout routine in Windows 7 or Windows Server 2008 R2

29-Nov-2012 – 6.1.7601.22176 – Tcpip.sys – x64 – http://support.microsoft.com/kb/2787847 – “0x000000D1” Stop error when a storage array is attached to a network environment and running Windows Server 2008 R2

29-Nov-2012 – 6.1.7601.18014 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2789397 – Data corruption and network issues when you run a WFP-based application on a computer that is running Windows

29-Nov-2012 – 6.1.7601.18014 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2789378 – Memory leak when an application uses the FwpsNetBufferListAssociateContext0 function in Windows 7 or Windows Server 2008 R2

29-Nov-2012 – 6.1.7601.18014 – Tcpip.sys – x64 – http://support.microsoft.com/kb/2787847 – “0x000000D1” Stop error when a storage array is attached to a network environment and running Windows Server 2008 R2

28-Nov-2012 – 6.1.7601.22175 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2785146 – Data is corrupted when there is insufficient memory on a Windows-based computer

23-Nov-2012 – 6.1.7601.22172 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2741850 – TCP SACK option is always set to “true” after you enable the TCP/IP Offloading feature in Windows 7 or in Windows Server 2008 R2

18-Oct-2012 – 6.1.7601.22137 – Tcpip.sys – x86/x64 – https://support.microsoft.com/kb/2775511 – An enterprise hotfix rollup is available for Windows 7 SP1 and Windows Server 2008 R2 SP1

03-Oct-2012 – 6.1.7601.22124 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2750841 – An IPv6 readiness update is available for Windows 7 and for Windows Server 2008 R2

03-Oct-2012 – 6.1.7601.17964 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2750841 – An IPv6 readiness update is available for Windows 7 and for Windows Server 2008 R2

12-Sep-2012 – 6.1.7601.22112 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2754804 – FTP client does not establish a passive-mode FTP connection to an IPv4 FTP server in Windows 7 or in Windows Server 2008 R2

12-Sep-2012 – 6.1.7601.17954 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2754804 – FTP client does not establish a passive-mode FTP connection to an IPv4 FTP server in Windows 7 or in Windows Server 2008 R2

06-Sep-2012 – 6.1.7601.22108 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2738401 – Raw packet is discarded after a UDP broadcast packet is received on a computer that is running Windows 7 or Windows Server 2008 R2

20-Jul-2012 – 6.1.7601.22067 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2735855 – Network connection is slow when you run a WFP-based application on a computer that is running Windows 7 or Windows Server 2008 R2

20-Jul-2012 – 6.1.7601.17911 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2735855 – Network connection is slow when you run a WFP-based application on a computer that is running Windows 7 or Windows Server 2008 R2

14-Jul-2012 – 6.1.7601.22056 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2727330 – Default gateway is set to 0.0.0.0 if you start a Windows 7-based or Windows Server 2008 R2-based computer from an iSCSI boot device

14-Jul-2012 – 6.1.7601.17900 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2727330 – Default gateway is set to 0.0.0.0 if you start a Windows 7-based or Windows Server 2008 R2-based computer from an iSCSI boot device

09-Jul-2012 – 6.1.7601.22047 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2733445 – Incorrect time is displayed in a device that uses ICMP to synchronize time information with a Windows 7-based or Windows Server 2008 R2-based computer

09-Jun-2012 – 6.1.7601.22015 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2722392 – “0x000000F4” Stop error when you run the Device Fundamental tests in Windows 7 or in Windows Server 2008 R2

30-Mar-2012 – 6.1.7601.21954 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2688338 – MS12-032: Vulnerability in TCP/IP could allow elevation of privilege: May 8, 2012

30-Mar-2012 – 6.1.7601.17802 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2688338 – MS12-032: Vulnerability in TCP/IP could allow elevation of privilege: May 8, 2012

09-Mar-2012 – 6.1.7601.21939 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2665206 – Slow performance when you enable IPsec encryption on a specific TCP port number in Windows 7 or in Windows Server 2008 R2

11-Feb-2012 – 6.1.7601.21921 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2675785 – Data transfer speed is slow in Windows 7 or in Windows Server 2008 R2

01-Feb-2012 – 6.1.7601.21912 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2665809 – You cannot exclude ports by using the ReservedPorts registry key in Windows Server 2008 or in Windows Server 2008 R2

07-Jan-2012 – 6.1.7601.21893 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2553549 – All the TCP/IP ports that are in a TIME_WAIT status are not closed after 497 days from system startup in Windows Vista, in Windows 7, in Windows Server 2008 and in Windows Server 2008 R2

03-Jan-2012 – 6.1.7601.21889 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2661010 – IP packets are not routed through a Windows Server 2008 R2–based LAN router in a VLAN environment

21-Dec-2011 – 6.1.7601.21881 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2639793 – “0x000000C2” Stop error occurs when you use IPsec on a computer that is running Windows Server 2008, Windows Vista, Windows Server 2008 R2 or Windows 7 in a network that uses IPsec NAT-T security

02-Nov-2011 – 6.1.7601.21853 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2639824 – Multicast packets are dropped in Windows 7 or in Windows Server 2008 R2

06-Oct-2011 – 6.1.7601.21833 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2621067 – The first-returned IP address is incorrect when you use the getaddrinfo function on a multi-homed computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2

01-Oct-2011 – 6.1.7601.21830 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2582281 – Slow failover operation if no router exists between the cluster and an application server

29-Sep-2011 – 6.1.7601.21828 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2588516 – MS11-083: Vulnerability in TCP/IP could allow remote code execution: November 8, 2011

13-Aug-2011 – 6.1.7601.21789 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2582284 – New VPN connections establish a session that has a smaller MTU value than expected in Windows Server 2008 R2 or in Windows 7

13-Aug-2011 – 6.1.7601.21789 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2459530 – Event ID 5719 and event ID 1129 may be logged when a non-Microsoft DHCP Relay Agent is used

12-Jul-2011 – 6.1.7601.21768 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2570170 – Performance issue when you enable the AuthNoEncap policy to handle large payloads in a network environment in Windows 7 or in Windows Server 2008 R2

18-Jun-2011 – 6.1.7601.21751 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2569391 – IPv6 DAD state does not switch back to Preferred state from Deprecated state in Windows Vista, in Windows Server 2008, in Windows 7, or in Windows Server 2008 R2

25-May-2011 – 6.1.7601.21734 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2469100 – Manually added route table entries are deleted unexpectedly when you delete an additional IP address in Windows Vista, in Windows 7, in Windows Server 2008 or in Windows Server 2008 R2

10-May-2011 – 6.1.7601.21724 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2523881 – You cannot establish an IPsec tunnel to a computer that is running Windows 7 or Windows Server 2008 R2 through a NAT device

06-May-2011 – 6.1.7601.21722 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2547057 – IP packets are not routed through a Windows Server 2008 R2–based LAN router in a VLAN environment

22-Apr-2011 – 6.1.7601.21710 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2524732 – An IPsec connection to back-end databases from a WTT application times out in Windows 7 or in Windows Server 2008 R2

19-Mar-2011 – 6.1.7601.21687 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2511305 – Network throughput is not scaled up correctly if high-bandwidth PCI Express adapters and four or more processor sockets are used in Windows Server 2008 R2

19-Mar-2011 – 6.1.7601.21687 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2519736 – Stop error message in Windows Server 2008 R2 SP1 or in Windows 7 SP1: “STOP: 0x0000007F”

19-Mar-2011 – 6.1.7601.21687 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2525390 – The SACK option is always set to “true” even if network adapter does not support SACK for offloaded connections in Windows 7 or in Windows Server 2008 R2

17-Mar-2011 – 6.1.7601.21685 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2519644 – Stop code in the tcpip.sys driver on a computer that is running Windows Server 2008 R2: 0x000000D1

05-Mar-2011 – 6.1.7601.21675 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2470853 – IGMP v1 membership report packets are sent to incorrect destinations on a computer that is running Windows Server 2008, Windows Vista, Windows 7 or Windows Server 2008 R2

20-Jan-2011 – 6.1.7601.21645 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2472264 – You cannot customize some TCP configurations by using the netsh command in Windows Server 2008 R2

17-Jan-2011 – 6.1.7601.21643 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2477730 – The TCP Chimney Offload feature fails on all network adapters in Windows Server 2008 R2 or in Windows 7 if you disable or change the properties of a network adapter

15-Jan-2011 – 6.1.7601.21642 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2465772 – An application or service that uses Winsock API or Winsock Kernel API may randomly stop responding in Windows Server 2008 R2 or in Windows 7

18-Dec-2010 – 6.1.7601.21624 – Tcpip.sys – x86/x64 – http://support.microsoft.com/kb/2465408 – Applications or services cannot update their routing tables after they receive route change notifications in Windows Server 2008 R2 or in Windows 7

11.5.1, 11.5.1, 11.5.1, 11.5.1, 11.5.1, 11.5.1, 11.5.1, 11.5.1, 11.5.1, 11.5.1, 11.5.1, 21, 22, 23, 330, 505, 510, 520, 530, 810, 820, 830, CSP4, CSP4, CSP4, CSP4, CSP4, CSP4, CSP4, CSP4, CSP4, CSP4, CSP4, Watchguard, XTM

Watchguard XTM 2 Series, XTM 3 Series, XTM 5 Series, XTM 8 Series – Fireware XTM OS 11.5.1 – CSP4 Build # 335367

Watchguard XTM 2 Series, XTM 3 Series, XTM 5 Series, XTM 8 Series – Fireware XTM OS 11.5.1 – CSP4 Build # 335367

11.5.1 – CSP4 Build # 335367 Resolves the following issues:

BUG64669: Resolved a Firebox crash and reboot when using FireCluster.

BUG63793: Improved proxy debug logging when using FireCluster.

BUG63574: Proxy connections fail with logs showing: “failed to create new traffic spec” and “insert_tspec:XX index inuse?

BUG65026: Iked stack trace eip=0x080c4013 caused by Mobile VPN with IPSec connection.

BUG63860: snmpd memory leak

You can request 11.5.1 – CSP4 Build # 335367 from Watchguard Support by logging a support case online, they should then be able to provide an ftp download link and appropriate credentials.

Please note that Watchguard CSP releases are cumulative so you should only need to apply the latest to ensure that you also have any previous fixes.

Accounts, Microsoft, Payroll, Sage, SBS 2003, SBS 2008, SBS 2011, Small Business Server 2003, Small Business Server 2008, Small Business Server 2011, Windows, Windows 7, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP

Sage Accounts and Sage Payroll – Crashing or Poor Performance

Sage Accounts and Sage Payroll are two very popular accounting products and in general work nicely on a well configured computer/network.

The most common issues that affect Sage Accounts and Payroll are listed below

  • Verify that your computer at least meets the minimum requirements to run your version of Sage Payroll or Sage Accounts (You cannot expect optimum performance from a machine that only just meets these basic requirements or that is below the outlined specs.  You might be able to upgrade the Memory in your existing machine to improve its performance or it may be time to consider a new machine)
  • Consumer Oriented Anti-Virus Products (These are usually bloated and will consume a large percentage of the system resources, the inbuilt software firewall may disrupt or interfere with the accessing of Sage Data files on other machines.  If you have a network strongly consider a corporate anti-virus product that does not bog down your machine and can be centrally configured rather than relying on each user to add exceptions for specific Sage files)
  • Accessing your Sage Data via a Wireless or VPN Connection (Both these type of connection only offer limited throughput and are prone to unexpected disconnections due to external factors, losing connection to your Sage Data whilst you are using it can result in a crash or worse still corruption. Consider having network data cabling installed or if this is not possible in your building/home then Ethernet Over the Mains may offer a suitable alternative)
  • Outdated Network Adapter Drivers (Your network adapter may have drivers installed that date back to 2005 or 2006 when you first purchased your computer, even most new computers do not have the very latest network adapter drivers installed.  Please take a look at my previous article for information on how you can find out if your network adapter driver is upto date and performing optimally)
  • Old Data Cabling and Network Hubs (Consider upgrading your internal cabling to Cat 5e or Cat 6, these both support speeds up to 1000Mbps or 1Gbps, this offers a significant boost over older 10Mbps networks.  You may also find that if your cabling is already suitable that your Network Hub or Switch is only capable of these slower speeds.  The best performance can be achieved by using a Managed Gigabit Switch, this will offer 1000Mbps to any computer/server/laptop that has a suitable network adapter installed or at least 100Mbps to those machines with older network adapters)
  • Unpatched Machine (Your desktop or server may be missing important Service Packs or updates that improve the overall responsiveness of the system or correct issues related to poor network or disk throughput.)
  • Operating System Hotfixes (Sometimes if an issue is not widely acknowledged Microsoft will release a requestable Hotfix rather than post the update to all users, this Hotfix may make it into a subsequent Service Pack but until this is released you may need to request appropriate hotfixes from Microsoft via http://support.microsoft.com )
  • Data Corruption or Repair may be required (If your data has been damaged in the past then a repair may be required to make it consistent, it is also possible that your Sage Data could be compacted to reduce the overall size and thus improve performance when accessing the data)

Hopefully you find this information useful, it does not cover all possible issues but should generally aid most Sage users.  Please always make several backups of your Sage Data before making any changes to your system or Sage.  Ideally you should make sure that at least one of these backups is to external media (USB pen, DVD/CD, External Hard Disk).

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