## Common Security Exceptions

This table displays some security exceptions that many LANs use. They are specified using the Security Exceptions tab of the Intel® Packet Protect control panel. Contact your administrator if you have any questions about adding security exceptions.

### Exception for DHCP

The following security exception is created by default when Intel Packet Protect is installed.

Protocol | Local Port | Remote Port | Security Action | Used for
UDP | 68 | 67 | Allow Communication without Security | Dynamic Host Configuration Protocol (DHCP)

If you have a DHCP server which is using Intel Packet Protect, then you must modify the security exception (shown above) only on the DHCP server, as follows:

Protocol | Local Port | Remote Port | Security Action | Used for
UDP | 67 | 68 | Allow Communication without Security | Dynamic Host Configuration Protocol (DHCP)

### Exceptions for DNS

In order for a client machine running Intel Packet Protect to communicate with a Domain Name Server (DNS), you must use the following security exceptions at each client machine (these are created by default when Intel Packet Protect is installed):

Protocol | Local Port | Remote Port | Security Action | Used for
TCP | Any | 53 | Allow Communication without Security | DNS name resolution
UDP | Any | 53 | Allow Communication without Security | DNS name resolution

If you have a DNS which is using Intel Packet Protect, then you must modify the security exception (shown above) only on the DNS, as follows:

Protocol | Local Port | Remote Port | Security Action | Used for
TCP | 53 | Any | Allow Communication without Security | DNS name resolution
UDP | 53 | Any | Allow Communication without Security | DNS name resolution

### Exceptions for WINS and NetBIOS

In order for a client machine running Intel Packet Protect to communicate with a Windows Internet Naming Service (WINS), you must use this security exceptions at each client machine (these are created by default when Intel Packet Protect is installed). This is also required if you are mapping remote drives through Intel Packet Protect.

Protocol | Local Port | Remote Port | Security Action | Used for
UDP | 137 | 137 | Allow Communication without Security | WINS/NetBIOS name resolution

If the WINS server is also running Intel Packet Protect, it must also have this security exception defined.

### Exceptions for Entrust Certificates

If you are using Entrust certificates, you will need to have the following two security exceptions (these are added automatically when Intel Packet Protect Certificate support is installed):

Protocol | Local Port | Remote Port | Security Action | Used for
TCP | Any | 389 | Allow Communication without Security | Lightweight Directory Access Protocol (LDAP)
TCP | Any | 709 | Allow Communication without Security | Entrust* Client-Server Communication

Copyright © 2002 Intel Corporation. Legal Information