P. 1
Tcpip Fund

Tcpip Fund

|Views: 6,808|Likes:
Published by mlmcbride33

More info:

Published by: mlmcbride33 on Nov 06, 2009
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

06/10/2014

pdf

text

original

The problem with reaching a destination node might be due to the configuration of Internet Protocol
security (IPsec) or packet filtering on the source node, intermediate routers, or destination node that is
preventing packets from being sent, forwarded, or received.

On the source node, check for the following:

• Active connection security rules with the Windows Firewall with Advanced Security snap-in

• Active IPsec policies with the IP Security Monitor snap-in

• For computers running Windows Server 2008 or Windows Server 2003, Routing and Remote Access
IPv4 packet filters on routing interfaces with the Routing and Remote Access snap-in

On intermediate IPv4 routers that are running Windows Vista or Windows XP, check for the following:

• Active connection security rules with the Windows Firewall with Advanced Security snap-in

• Active IPsec policies with the IP Security Monitor snap-in

On intermediate IPv4 routers that are running Windows Server 2008 or Windows Server 2003 and
Routing and Remote Access, check for the following:

• Active connection security rules with the Windows Firewall with Advanced Security snap-in

• Active IPsec policies with the IP Security Monitor snap-in

• Routing and Remote Access IPv4 packet filters on routing interfaces with the Routing and Remote
Access snap-in

• NAT/Basic Firewall routing protocol component of Routing and Remote Access

On intermediate IPv4 routers or firewalls that are from third-party hardware vendors, check for the
configuration of packet filters—also called access lists—and IPsec policies and filters.

On the destination node that is running Windows, check for the following:

• Active connection security rules with the Windows Firewall with Advanced Security snap-in

• Active IPsec policies with the IP Security Monitor snap-in

• Whether Internet Connection Firewall or Windows Firewall is enabled

• TCP/IP filtering

On the destination node that is running Windows Server 2008 or Windows Server 2003 and Routing
and Remote Access, check for the following:

• Active connection security rules with the Windows Firewall with Advanced Security snap-in

• Active IPsec policies with the IP Security Monitor snap-in

• Routing and Remote Access IPv4 packet filters on routing interfaces with the Routing and Remote
Access snap-in

• NAT/Basic Firewall routing protocol component of Routing and Remote Access

Chapter 16 – Troubleshooting TCP/IP

TCP/IP Fundamentals for Microsoft Windows

Page: 472

• Whether Internet Connection Firewall or Windows Firewall is enabled

• TCP/IP filtering

For more information about IPsec and packet filtering components, see Chapter 13, "Internet Protocol
Security (IPsec) and Packet Filtering."

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->