Archive for the '64-Bit' Category

11
Feb
10

Is a 64-bit ipsec client enough?

We’ve been seeing a lot of discussion in the forums about Cisco’s IPsec VPN client (welcome to the party—you’re four years late).  In 2010, a 64-bit client isn’t enough.  Perhaps four years ago this would work, but not today.  In today’s mobile world, users are constantly on-the-go and purchasing the latest and best devices—they need more than just a VPN client.

NCPs client was developed with both the user and administrator in mind.  When an employee is away on business, they need to connect and remain connected to the network hassle-free.  They need to be reassured that their desired device, whether it be a laptop, mobile phone, etc., will work with their VPN client and have access to the appropriate files, email, folders, etc. they need.

Overlapping subnets, roaming across networks and connections dropping shouldn’t be an issue.  Users should be able to use important features, such as two-factor authentication, end-point security software and personal firewalls without any IT knowledge or help desk support.  It should be a matter of a one-click and get connected.  Will a 64-bit IPsec VPN client be enough to meet customers’ remote access needs?  No, and we think you’ll agree.

Follow this discussion on Twitter @VPNHaus

10
Nov
09

Options for 64-bit Windows 7 VPN

Big news today from Cisco as reported by Network World:

Cisco (NASDAQ: CSCO) is warning customers of its unified communicationsWindows 7 will be supported. Products that support for Windows 7 won’t be forthcoming until the product’s 8.0 release scheduled for the first quarter of 2010. About a dozen more UC products will not support Windows 7 until version 8.5, in the third quarter of 2010 and at that time, only the 32-bit version of.

For customers who need IPsec 64-bit support, NCP engineering can help you out. The “beta” version of the client is scheduled to go release candidate any day now too.

17
Sep
09

YES to VPN

NCP has recently been selected to provide end-point security solutions for Texas-based YES Prep Public Schools.  The school’s IT manager needed a secure VPN solution that would not only allow staff access to the Intranet, but also flexibility to integrate the solution to existing and future devices and operating systems.  NCP Secure Entry Client provided 64-bit support to gain access to the network and prepared the school’s migration to Windows 7.

As we’ve blogged in the past, the need for end-point security is critical for school systems.  Security breaches do affect this market, and hackers gain access to student’s personal records, school internal documents and other confidential data.   Education institutions need to be ware and take action to protect their network, and the most effective way to this is with a VPN.

NCPs universal client provides YES’ teachers with secure and constant communications to the Intranet, where they can access lesson plans and student files immediately.  It also enables YES staff to be in contact with each other in the seven different locations.  This access is important to YES because it grants students with the quality education they deserve.  The entry client saved YES from downgrading their 64-bit machines to 32-bit; and the client will work on new operating system, Windows 7.

For more information on this issue, check out a recent article published in Processor.

04
Aug
09

Do you have a King Kong VPN client?

Can your 64-bit VPN client meet the enterprise challenge? Take King Kong – a single person brought him to the base of the Enterprise State Building but it was his inherent strength and stability that allowed him to conquer. Apes are not our passion; scalable VPN clients drive us.

We know about Cisco moving to SSL and Microsoft pushing IPSec through Windows 7 and their server. 64-bit VPN users were being left out in the cold until NCP and a few freeware alternatives came along.

The connection to the King of Apes? Ability to take on tough challenges (read: scale the enterprise). Central policy control, NAC enforcement, change management and technical support are what drive an enterprise VPN client choice. 64-bit systems are here to stay and companies need VPN (and vendor) support that can conquer the tough enterprise problems.

07
Jul
09

Forcing IPSec or SSL on a Market is Wrong

Read an interesting post on Cisco and its lack of support of the 64-bit IPSec VPN client. What was more interesting to us though, was a reader’s comment listed below the post—Robert, comment no. 7.

Robert disagrees with blogger, Greg Ferro’s post, and believes Cisco is going in the right direction with its support of SSL. “IPSec was never designed to be a user VPN solution,” says Robert. “Anyone [who] has to deal with multiple VPN clients, [knows] it’s a pain because of where IPSec is inserted into the stack.”

We disagree! IPSec’s historic downside has been the complexity created by so much flexibility (Robert’s point). But this has been fixed. However, the bigger picture here is that supporting solely SSL or IPSec is not good enough. Arguments for both SSL and IPSec have been an on-going debate for some time now, and there is a clear argument for the use of both, under different situations. One or the other does not apply.

Regardless of a user’s access, an enterprise solution should support both SSL and IPSec. It is necessary to build VPN systems around mobility, productivity and policy needs, rather than limit these with a biased technology choice.