We're running SonicWall Enforced Client on a Windows 7 64 bit machine. Upon bootup, the system hangs for 7-10 minutes while the McAfee agent updates. During this time the PC is not usable. If the user manually updates McAfee upon bootup, the process takes 1-2 minutes and then the system is fine. Why do all apps not respond while the update is running? How can we resolve this issue? Thanks,

Set the AnyConnect client to issue keep-alive messages, and bump the TCP timeout to 10 minutes on the TX210. More info is available at Cisco's site: http://www.cisco.com/en/US/docs/security/vpn_client/anyconnect/anyconnect30/administration/guide/ac12managemonitortbs.html#wp1058576

This may sounds obvious but have you forwarded the correct ports through sonicwall for your VPN?
If you have, do you have any QoS running, it could be worth checking that VPN has priority over VoIP etc.
Do you get disconnects all the time or is it only during busy periods? You may be overloading your server, perhaps it's time for more RAM.

To use hardware-enforced DEP, you must meet all the following conditions:

1. The computer's processor must support hardware-enforced DEP.
   
   Many recent processors support hardware-enforced DEP. Both Advanced Micro Devices (AMD) and Intel Corporation have defined and shipped Windows-compatible architectures that are compatible with DEP. This processor support may be known as NX (no-execute) or XD (execute disable) technology. To determine whether your computer's processor supports hardware-enforced DEP, contact the manufacturer of your computer.
2. Hardware-enforced DEP must be enabled in the BIOS.
   
   On some computers, you can disable processor support for hardware-enforced DEP in the BIOS. You must not disable this support. Depending on your computer manufacturer, the option to disable this support may be labeled "Data Execution Prevention," "XD," "Execute Disable," or "NX."
3. The computer must have Windows XP with Service Pack 2 or Windows Server 2003 with Service Pack 1 installed.
   
   Note Both 32-bit versions and 64-bit versions of Windows support hardware-enforced DEP. Windows XP Media Center Edition 2005 and Microsoft Windows XP Tablet PC Edition 2005 include all the features and components of Windows XP SP2.
4. Hardware-enforced DEP must be enabled for programs on the computer.
   
   In 64-bit versions of Windows, hardware-enforced DEP is always enabled for 64-bit native programs. However, depending on your configuration, hardware-enforced DEP may be disabled for 32-bit programs.

For more information about DEP, about DEP configuration, and for a list of Windows Operating Systems that support hardware DEP, click the following article number to view the article in the Microsoft Knowledge Base:875352 A detailed description of the Data Execution Prevention (DEP) feature in Windows XP Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows Server 2003For information about how to configure memory protection in Windows XP with Service Pack 2, visit the following Microsoft Web site:

http://technet.microsoft.com/en-us/library/cc700810.aspx

To confirm that hardware DEP is working in WindowsTo confirm that hardware DEP is working in Windows, use one of the following methods.Method 1: Use the Wmic command-line toolYou can use the Wmic command-line tool to examine the DEP settings. To determine whether hardware-enforced DEP is available, follow these steps:

1. Click Start, click Run, type cmd in the Open box, and then click OK.
2. At the command prompt, type the following command, and then press ENTER:wmic OS Get DataExecutionPrevention_AvailableIf the output is "TRUE," hardware-enforced DEP is available.

To determine the current DEP support policy, follow these steps.

1. Click Start, click Run, type cmd in the Open box, and then click OK.
2. At the command prompt, type the following command, and then press ENTER:wmic OS Get DataExecutionPrevention_SupportPolicyThe value returned will be 0, 1, 2 or 3. This value corresponds to one of the DEP support policies that are described in the following table.

DataExecutionPrevention_SupportPolicy property valuePolicy LevelDescription2OptIn (default configuration)Only Windows system components and services have DEP applied3OptOutDEP is enabled for all processes. Administrators can manually create a list of specific applications which do not have DEP applied1AlwaysOnDEP is enabled for all processes0AlwaysOffDEP is not enabled for any processesNote To verify that Windows is running with hardware DEP enabled, examine the DataExecutionPrevention_Driversproperty of the Win32_OperatingSystem class. In some system configurations, hardware DEP may be disabled by using the /nopae or /execute switches in the Boot.ini file. To examine this property, type the following command at a command prompt:wmic OS Get DataExecutionPrevention_DriversMethod 2: Use the graphical user interfaceTo use the graphical user interface to determine whether DEP is available, follow these steps:

1. Click Start, click Run, type wbemtest in the Open box, and then click OK.
2. In the Windows Management Instrumentation Tester dialog box, click Connect.
3. In the box at the top of the Connect dialog box, type root\cimv2, and then click Connect.
4. Click Enum Instances.
5. In the Class Info dialog box, type Win32_OperatingSystem in the Enter superclass name box, and then click OK.
6. In the Query Result dialog box, double-click the top item.
   
   Note This item starts with "Win32_OperatingSystem.Name=Microsoft..."
7. In the Object editor dialog box, locate the DataExecutionPrevention_Available property in the Properties area.
8. Double-click DataExecutionPrevention_Available.
9. In the Property Editor dialog box, note the value in the Value box.

If the value is TRUE, hardware DEP is available.Notes

• To determine the mode in which DEP is running, examine the DataExecutionPrevention_SupportPolicy property of the Win32_OperatingSystem class. The table at the end of Method 1 describes each support policy value.
• To verify that hardware DEP is enabled in Windows, examine the DataExecutionPrevention_Drivers property of the Win32_OperatingSystem class. In some system configurations, hardware DEP may be disabled by using the/nopae or /execute switches in the Boot.ini file.

The inability of a client running Windows Vista to connect with a SonicPoint or any SonicWALL firewall (UTM) appliance running SonicOS Standard firmware is caused by a lack of a correct association on the SonicWALL between the computer running Windows Vista and its assigned IP address. Follow these steps to work around the issue by editing the System Registry:

WARNING: Exercise extreme caution when modifying the System Registry. Incorrect modifications could lead to an inability to boot your system. It may become necessary to completely reinstall your operating system.

1. Click the Start button.
2. Select All Programs > Accessories.
3. Right click Command Prompt and click Run as administrator.
4. Type regedit.exe and press enter.
5. Go to the following location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
6. Right click this entry and select New Dword.
7. Rename the new entry ArpRetryCount (leave it set to 0 by default).
8. Restart the computer.
9. Reassociate with the SonicWALL. You should notice a successful connection.

Please print this out if possible, you may want to take your computer to a local repair shop to make this change if your not comfortable.

Cisco VPN Client for Windows Vista, release 5.0.0.340, does not support the following:

•Microsoft Windows NT, 98, and ME.

•System upgraded from Windows XP or earlier Windows operating systems to Vista. (Clean OS installation required.)

•Combination of Cisco Unified Video Advantage 2.1.2 and McAfee HIPS Patch 4 Build 688. To avoid system failures, uninstall either of these two applications, upgrade McAfee to the latest version, or use VPN Client 4.6.x.

•Start Before Logon.

•SmartCard authentication.

•Integrated firewall

•InstallShield.

•Auto Update.

•Translated Online Help. Online Help is provided only in English.

•64-bit Windows operating systems. For x-64 support, customers should explore with their Cisco sales representative the use of the next-generation Cisco AnyConnect VPN Client.

sir, i have a window7 in all in one hp but there is a software called mstar which run on oracle 8i when i install the oracle 8i there is a problem and show dll file corrupted. Pls tell me the solution because my client want it very urgently and i am not able to install and run the programm.

Hi,
The"svchost.exe" is a normall windows system files.
It does not cause any harm to your pc.
It's only a running process.
Regards
Uttam

The default VPN policy rules prevent LAN access, also known as split-tunneling, since this creates a security risk (the ability of the VPN session to be hijacked or compromised through a covert channel).

If you are not the system admin, you need to talk to your system admin. If you are the system admin, then you need to review the documentation with respect to

http://www.sonicwall.com/us/support/kb.asp?kbsk=policy+allow+lan

Here's a link to the cleanup tool located on SonicWALL's FTP site:
ftp://ftp.sonicwall.com/pub/techSupport/SWVPNClientClean.zip

If you are still having problems after using the cleanup util, try downloading the DNE demo here:
http://www.deterministicnetworks.com/Downloads/downloads.asp

Use the cleanup util again, then install the DNE demo first and Global client after that. The DNE demo is the virtual adapter piece that Global client uses anyway, you will just be installing it separately.
<<

I got the clean up tool, ran it, rebooted, then ran the DNE demo installer then installed the VPN client and it worked fine.

Hope that helps!

Are you behind a firewall performing some kind of deep packet inspection/AV/Spyware removal? It may be corrupting your HTTP Range headers during BITS transfers on the client.
I experienced a similar error through a SonicWall with GatewayAV (no proxy, just the Sonic) and had to enable HTTP byte-range requests. This can happen to both server and client BITS downloads...