Cisco 3002 - VPN Hardware Client Spezifikationen PDF herunterladen (Seite 13)

Release Notes for Cisco VPN 3002 Hardware Client Release 3.1

78-13771-01

Caveats

• CSCdt21080

Unable to unlock a locked configuration

If you are managing a device and do not log out properly, the configuration

file is locked by any other IP Address of the managing device until that

session expires.

For a VPN 30xx Concentrator, you can physically log out this admin user, but

with a VPN 3002, the problem persists until the session expires (the default

is 10 minutes) or you reboot the unit.

• CSCdt28156

Using Port Address Translation (PAT) and non-compliant FTP shareware

applications can cause a problem. For example, with both Sambar and TSoft

FTP shareware, the Server changes the source port to something other than

"20" (which is the FTP-Data port outlined in the RFC). To work around this

problem, use passive mode FTP instead of active.

• CSCdt38841

The VPN 3002 DHCP server may at times assign addresses that are not in

sequence, skipping addresses that are free for use.

• CSCdt42173

The VPN Concentrator family of products does not support SSH connections

from TeraTerm SSH version: TTSSH v1.2/TTPRO v2.3. If you plan to use

SSH from TeraTerm, and are currently running this version, visit the

following site and upgrade your SSH software:

http://www.zip.com.au/~roca/ttssh.html

• CSCdt42408

The MS Exchange/Outlook auto-update feature doesn’t work in Client (PAT)

mode. There is an open Microsoft bug for this problem.

• CSCdt42421, CSCdu57252

The Traceroute debugging tool does not work from a device on the private

LAN of a VPN 3002.

• CSCdt48908

When changing IP addresses (from static to DHCP mode and vice-versa) on

the VPN 3002 public interface, data starts passing approximately 30 seconds

after the tunnel to the central-site VPN 3000 has been established.

1 2 ... 8 9 10 11 12 13 14 15 16 17 18 19 20

Keine Kommentare

Cisco 3002 - VPN Hardware Client Spezifikationen Seite 13