Allied Telesis AR450S Manuel d'utilisateur télécharger pdf (Page 4)

Configure Microsoft® Windows XP** Virtual Private Network (VPN) client interoperability with NAT-T support 4

Other solution requirements and things to consider

• Other utilities sometimes conflict with the Windows IPSec policy agent, and may need

uninstalling—such as another VPN Client installation, or perhaps a firewall utility. In some cases

the uninstall of these utilities may not properly restore the Windows IPSec policy agent, in which

case you may need to check your Windows services listing to see that the agent is in 'automatic'

mode.

• If your office VPN router is behind an external gateway that does not use NAT—perhaps a firewall

or IP filtering device—then the external gateway will need a protocol 50 permit rule in addition

to the UDP 500 and UDP 4500 permit rules. This will allow NAT-T to work in all situations.

• Your ISAKMP pre-shared key needs to be alphanumeric only, not hexadecimal, to ensure

interoperation with Windows.

• Users will need to define a PPP DNS server address on the router that will be assigned to the

incoming VPN users. The DNS address needs to be valid for the network being connected to via

VPN.

• Internet Explorer browser users may need to define a proxy definition against the VPN dial up

link, valid for the network being connected to via VPN.

• If you have the customised "ProhibitIPSec" registry entry or a customised MMC IP Security Policy

defined in Windows—you should remove these and reboot, i.e. from a previous attempt to use

Windows IPSec client.

• Using Secure Shell for remote management is encouraged. Telnet should not be used to a secure

gateway.

1 2 3 4 5 6 7 8 9 ... 21 22

Pas de commentaire

Allied Telesis AR450S Manuel d'utilisateur Page 4