Exchange Server 2003

Exchange Server 2003 may be run on the Windows 2000 Server if the fourth service pack has already been installed. It may also be run on 32 bit Windows Server 2003. There is a new disaster recovery feature that is even better than before. It allows the server to experience less downtime. The Exchange Server 2003 received some features form Microsoft Mobile Information server as well. These include Outlook Mobile Access as well as ActiveSync. Improved versions of anti-spam and anti-virus were also included. Management tools for mailboxes and messages have been improved and Instant Messaging and Exchange Conferencing Server are now separate products. There are two versions available of Exchange Server 2003. These include the Enterprise edition and the Standard edition. There are many other features that are available on Exchange Server 2003.

Exchange Server 2007

When Exchange Server 2003 was released there were no immediate plans as to what would happen to the product. A 2005 edition was dropped and it was not until the end of 2006 that the new version was released. Some of the new features included integration of voicemail, improved filtering, Web service support, and Outlook Web Access interface. The new edition was run on a 64 bit x 64 version of Windows Server. This increases the performance significantly. There are quite a few improvements to Exchange Server 2007. These include better calendaring, improved web access, unified messages, and better mobility. From a system protection standpoint there is more clustering, antivirus, anti spam, and compliance included. The IT experience is improved overall with a 64-bit performance. Deployment is better; routing is simplified as well as the command line shell and GUI.

There have been many changes and improvements to the Exchange Server 2007 and it is better than ever. There are no definite plans as to what Microsoft has in store for Exchange Server but the next version will certainly be better than ever.

What is the Difference between Exchange 2003 and 2007?

Exchange 2003 and 2007 difference

· 2003 is 32 bit
· Single server base, No roles base
· Outlook Mobile Access (or OMA)
· Active sync
· Up-To-Date Notifications

Exchange 2003 with SP2

· Direct Push
· Global Address List lookup
· Mobile Admin

2007 exchange server Enhanced and Newly added features

· Has Power full command line Power shell for configuration
· Most of configuration is done through power shell
· Fast message retrieval
· Follow-up flags
· Meeting attendee information
· Enhanced Exchange Search
· Windows Share Point and file share document access
· Reset PIN/Password
· Enhanced PPC security
· Autodiscover for over the air (OTA) provisioning
· Out of Office
· Support for HTML messages

Missing/ Removed features in 2007 RTM due to stability Issue but available in SP1

· Information Rights Management (IRM)
· Support for S/MIME

Completely Removed Feature

· Outlook Mobile Access (OMA)

Exchange 2007 has Role base Infrastructure. These are:

Mailbox Role

· Stores Mailboxes and Public folder
. Client Access Client request for mail are fetched by this Role
· Browser-based clients using either the full-featured Outlook Web Access (OWA) or a new OWA Light client
· Mobile devices via Exchange ActiveSync (EAS)
· Phone devices via Outlook by Phone
· POP3 or IMAP4 clients, such as Outlook Express and Eudora

Hub Transport
Responsible for all internal mail flow

Inbound mail are accepted by Edge Transport and passed on to Mailbox server and all outbound mail is relayed from the Hub Transport to the Edge Transport and out to the Internet.

Edge transport

Edge Transport server handles all Internet-facing mail flow, which provides Simple Mail Transfer Protocol (SMTP) relay and smart host services for the Exchange organization.

Unified Messaging

Unified Messaging combines email, voicemail and fax into the Exchange Server databases, and makes this data available to mailbox users via both telephone and computer.

Exchange 2007 System Requirements

PROCESSER

· x64 architecture-based computer with Intel processor that supports Intel 64 architecture
· AMD processor that supports the AMD64 platform
· Intel Itanium IA64 processors not supported
· Intel Pentium or compatible 800-megahertz (MHz) or faster 32-bit processor (for testing and training purposes only; not supported in production)

Memory

· Minimum: 2 gigabytes (GB) of RAM for Single Roles
· 5 GB of RAM. if Roles are installed on single server.
· 8 megabytes (MB) of RAM per mailbox
· Minimum based on number of storage groups

Disk space

· At least 2.5 GB on the drive on which you install Exchange
· An additional 500 MB of available disk space for each Unified Messaging (UM) language pack that you plan to install
· 200 MB of available disk space on the system drive
· In Exchange 2007 RTM, a hard disk drive that stores the message queue database on an Edge Transport server or Hub Transport server with at least 4 GB of free space
· In Exchange 2007 SP1, a hard disk drive that stores the message queue database on an Edge Transport server or Hub Transport server with at least 500 MB of free space
· Disk partitions formatted as NTFS file systems.

Upgrade Tip

· It is not supported to upgrade Exchange 2007 RTM to Exchange 2007 SP1, and then upgrade your operating system to Windows Server 2008.
· Complete Fresh Installation of Ex-2007-SP1 on 2008 is supported

Protocol Numbers

• 0 HOPOPT IPv6 Hop-by-Hop Option
• 1 ICMP Internet Control Message
• 2 IGMP Internet Group Management
• 3 GGP Gateway-to-Gateway
• 4 IP IP in IP (encapsulation)
• 5 ST Stream
• 6 TCP Transmission Control
• 7 CBT CBT
• 8 EGP Exterior Gateway Protocol
• 9 IGP any private interior gateway (used by Cisco for their IGRP)
• 10 BBN-RCC-MON BBN RCC Monitoring
• 11 NVP-II Network Voice Protocol
• 12 PUP PUP
• 13 ARGUS ARGUS
• 14 EMCON EMCON
• 15 XNET Cross Net Debugger
• 16 CHAOS Chaos
• 17 UDP User Datagram
• 18 MUX Multiplexing
• 19 DCN-MEAS DCN Measurement Subsystems
• 20 HMP Host Monitoring
• 21 PRM Packet Radio Measurement
• 22 XNS-IDP XEROX NS IDP
• 23 TRUNK-1 Trunk-1
• 24 TRUNK-2 Trunk-2
• 25 LEAF-1 Leaf-1
• 26 LEAF-2 Leaf-2
• 27 RDP Reliable Data Protocol
• 28 IRTP Internet Reliable Transaction
• 29 ISO-TP4 ISO Transport Protocol Class 4
• 30 NETBLT Bulk Data Transfer Protocol
• 31 MFE-NSP MFE Network Services Protocol
• 32 MERIT-INP MERIT Internodal Protocol
• 33 SEP Sequential Exchange Protocol
• 34 3PC Third Party Connect Protocol
• 35 IDPR Inter-Domain Policy Routing Protocol
• 36 XTP XTP
• 37 DDP Datagram Delivery Protocol
• 38 IDPR-CMTP IDPR Control Message Transport Protocol
• 39 TP++ TP++ Transport Protocol
• 40 IL IL Transport Protocol
• 41 IPv6 Ipv6
• 42 SDRP Source Demand Routing Protocol
• 43 IPv6-Route Routing Header for IPv6
• 44 IPv6-Frag Fragment Header for IPv6
• 45 IDRP Inter-Domain Routing Protocol
• 46 RSVP Reservation Protocol
• 47 GRE General Routing Encapsulation
• 48 MHRP Mobile Host Routing Protocol
• 49 BNA BNA
• 50 ESP Encapsulating Security Payload
• 51 AH Authentication Header
• 52 I-NLSP Integrated Net Layer Security TUBA
• 53 SWIPE IP with Encryption
• 54 NARP NBMA Address Resolution Protocol
• 55 MOBILE IP Mobility
• 56 TLSP Transport Layer Security Protocol using Kryptonet key management
• 57 SKIP SKIP
• 58 IPv6-ICMP ICMP for IPv6
• 59 IPv6-NoNxt No Next Header for IPv6
• 60 IPv6-Opts Destination Options for IPv6
• 61 any host internal protocol
• 62 CFTP CFTP
• 63 any local network
• 64 SAT-EXPAK SATNET and Backroom EXPAK
• 65 KRYPTOLAN Kryptolan
• 66 RVD MIT Remote Virtual Disk Protocol
• 67 IPPC Internet Pluribus Packet Core
• 68 any distributed file system
• 69 SAT-MON SATNET Monitoring
• 70 VISA VISA Protocol
• 71 IPCV Internet Packet Core Utility
• 72 CPNX Computer Protocol Network Executive
• 73 CPHB Computer Protocol Heart Beat
• 74 WSN Wang Span Network
• 75 PVP Packet Video Protocol
• 76 BR-SAT-MON Backroom SATNET Monitoring
• 77 SUN-ND SUN ND PROTOCOL-Temporary
• 78 WB-MON WIDEBAND Monitoring
• 79 WB-EXPAK WIDEBAND EXPAK
• 80 ISO-IP ISO Internet Protocol
• 81 VMTP VMTP
• 82 SECURE-VMTP SECURE-VMTP
• 83 VINES VINES
• 84 TTP TTP
• 85 NSFNET-IGP NSFNET-IGP
• 86 DGP Dissimilar Gateway Protocol
• 87 TCF TCF
• 88 EIGRP EIGRP
• 89 OSPFIGP OSPFIGP
• 90 Sprite-RPC Sprite RPC Protocol
• 91 LARP Locus Address Resolution Protocol
• 92 MTP Multicast Transport Protocol
• 93 AX.25 AX.25 Frames
• 94 IPIP IP-within-IP Encapsulation Protocol
• 95 MICP Mobile Internetworking Control Protocol
• 96 SCC-SP Semaphore Communications Sec. Protocol
• 97 ETHERIP Ethernet-within-IP Encapsulation
• 98 ENCAP Encapsulation Header
• 99 any private encryption scheme
• 100 GMTP GMTP
• 101 IFMP Ipsilon Flow Management Protocol
• 102 PNNI PNNI over IP
• 103 PIM Protocol Independent Multicast
• 104 ARIS ARIS
• 105 SCPS SCPS
• 106 QNX QNX
• 107 A/N Active Networks
• 108 IPComp IP Payload Compression Protocol
• 109 SNP Sitara Networks Protocol
• 110 Compaq-Peer Compaq Peer Protocol
• 111 IPX-in-IP IPX in IP
• 112 VRRP Virtual Router Redundancy Protocol
• 113 PGM PGM Reliable Transport Protocol
• 114 any 0-hop protocol
• 115 L2TP Layer Two Tunneling Protocol
• 116 DDX D-II Data Exchange (DDX)
• 117 IATP Interactive Agent Transfer Protocol
• 118 STP Schedule Transfer Protocol
• 119 SRP SpectraLink Radio Protocol
• 120 UTI UTI
• 121 SMP Simple Message Protocol
• 122 SM SM
• 123 PTP Performance Transparency Protocol
• 124 ISIS over IPv4
• 125 FIRE
• 126 CRTP Combat Radio Transport Protocol
• 127 CRUDP Combat Radio User Datagram
• 128 SSCOPMCE
• 129 IPLT
• 130 SPS Secure Packet Shield
• 131 PIPE Private IP Encapsulation within IP
• 132 SCTP Stream Control Transmission Protocol
• 133 FC Fibre Channel
• 134 RSVP-E2E-IGNORE
• 135-254 Unassigned
• 255 Reserved

Installing and Configuring VPN on Windows Server 2003

What is Virtual Private Network (VPN)?

A virtual private network (VPN) is a network that uses a public telecommunication infrastructure, such as the Internet, to provide remote offices or individual users with secure access to their organization's network. A virtual private network can be contrasted with an expensive system of owned or leased lines that can only be used by one organization. The goal of a VPN is to provide the organization with the same capabilities, but at a much lower cost.

A VPN works by using the shared public infrastructure while maintaining privacy through security procedures and tunneling protocols such as the Layer Two Tunneling Protocol (L2TP). In effect, the protocols, by encrypting data at the sending end and decrypting it at the receiving end, send the data through a "tunnel" that cannot be "entered" by data that is not properly encrypted. An additional level of security involves encrypting not only the data, but also the originating and receiving network addresses.

Components of VPN

A VPN in servers running Windows Server 2003 is made up of a VPN server, a VPN client, a VPN connection (that portion of the connection in which the data is encrypted), and the tunnel (that portion of the connection in which the data is encapsulated). The tunneling is completed through one of the tunneling protocols included with servers running Windows Server 2003, both of which are installed with Routing and Remote Access. The Routing and Remote Access service is installed automatically during the installation of Windows Server 2003. By default, however, the Routing and Remote Access service is turned off.

The two tunneling protocols included with Windows are:

Point-to-Point Tunneling Protocol (PPTP): Provides data encryption using Microsoft Point-to-Point Encryption.

Layer Two Tunneling Protocol (L2TP): Provides data encryption, authentication, and integrity using IPSec.

Your connection to the Internet must use a dedicated line such as T1, Fractional T1, or Frame Relay. The WAN adapter must be configured with the IP address and subnet mask assigned for your domain or supplied by an Internet service provider (ISP). The WAN adapter must also be configured as the default gateway of the ISP router.

NOTE: To turn on VPN, you must be logged on using an account that has administrative rights.

VPN Installation

To install and turn on a VPN server, follow these steps:

1. Click Start, point to Administrative Tools, and then click Routing and Remote Access.
2. Click the server icon that matches the local server name in the left pane of the console. If the icon has a red circle in the lower-left corner, the Routing and Remote Access service has not been turned on. If the icon has a green arrow pointing up in the lower-left corner, the Routing and Remote Access service has been turned on. If the Routing and Remote Access service was previously turn on, you may want to reconfigure the server. To reconfigure the server:
   1. Right-click the server object, and then click Disable Routing and Remote Access. Click Yes to continue when you are prompted with an informational message.
   2. Right-click the server icon, and then click Configure and Enable Routing and Remote Access to start the Routing and Remote Access Server Setup Wizard. Click Next to continue.
   3. Click Remote access (dial-up or VPN) to turn on remote computers to dial in or connect to this network through the Internet. Click Next to continue.
3. Click to select VPN or Dial-up depending on the role that you intend to assign to this server.
4. In the VPN Connection window, click the network interface which is connected to the Internet, and then click Next.
5. In the IP Address Assignment window, click Automatically if a DHCP server will be used to assign addresses to remote clients, or click From a specified range of addresses if remote clients must only be given an address from a pre-defined pool. In most cases, the DHCP option is simpler to administer. However, if DHCP is not available, you must specify a range of static addresses. Click Next to continue.
6. If you clicked From a specified range of addresses, the Address Range Assignment dialog box opens. Click New. Type the first IP address in the range of addresses that you want to use in the Start IP address box. Type the last IP address in the range in the End IP address box. Windows calculates the number of addresses automatically. Click OK to return to the Address Range Assignment window. ClickNext to continue.
7. Accept the default setting of No, use Routing and Remote Access to authenticate connection requests, and then click Next to continue. Click Finish to turn on the Routing and Remote Access service and to configure the server as a Remote Access server.

The Routing and Remote Access Wizard Component

Like most wizards, the first screen of the Routing and Remote Access wizard is purely informational and you can just click Next.

The second screen in this wizard is a lot meatier and asks you to decide what kind of remote access connection you want to provide. Since the goal here is to set up a PPTP-based VPN, select the "Virtual Private Network VPN and NAT" selection and click Next.

Select the VPN option and click Next

The next screen of the wizard, entitled VPN Connection, asks you to determine which network adapter is used to connect the system to the Internet. For VPN servers, you should install and use a separate network adapter for VPN applications. Network adapters are really cheap and separation makes the connections easier to secure. In this example, I've selected the second local area network connection , a separate NIC from the one that connects this server to the network. Notice the checkbox labeled "Enable security on the selected interface by setting up Basic Firewall" underneath the list of network interfaces. It's a good idea to enable since option it helps to protect your server from outside attack. A hardware firewall is still a good idea, too.

Select the network adapter that connects your server to the Internet

With the selection of the Internet-connected NIC out of the way, you need to tell the RRAS wizard which network external clients should connect to in order to access resources. Notice that the adapter selected for Internet access is not an option here.

Select the network containing resources needed by external clients

Just like every other client out there, your external VPN clients will need IP addresses that are local to the VPN server so that the clients can access the appropriate resources. You have two options (really three â€" I'll explain in a minute) for handling the doling out of IP addresses.

First, you can leave the work up to your DHCP server and make the right configuration changes on your network equipment for DHCP packets to get from your DHCP server to your clients. Second, you can have your VPN server handle the distribution of IP addresses for any clients that connect to the server. To make this option work, you give your VPN server a range of available IP addresses that it can use. This is the method I prefer since I can tell at a glance exactly from where a client is connecting. If they're in the VPN "pool" of addresses, I know they're remote, for example. So, for this setting, as shown in below, I prefer to use the "From a specified range of addresses" option. Make your selection and click Next.

Your choice on this one! I prefer to provide a range of addresses

If you select the "From a specified range of addresses" option on the previous screen, you now have to tell the RRAS wizard exactly which addresses should be reserved for distribution to VPN clients. To do this, click the New button on the Address Range Assignment screen. Type in the starting and ending IP addresses for the new range and click OK. The "Number of addresses" field will be filled in automatically based on your entry. You can also just enter the starting IP address and the number if IP addresses you want in the pool. If you do so, the wizard automatically calculates the ending IP address. Click OK in the New Address Range window; your entry appears in the Address Range Assignment window. Click Next to continue.

You can have multiple address ranges, as long as they are all accessible

The next screen asks you to identify the network that has shared access to the Internet. This is generally the same network that your VPN users will use to access shared resources.

Pick the network adapter that gives you access to the Internet

Authenticating users to your network is vital to the security of your VPN infrastructure. The Windows VPN service provides two means for handling this chore. First, you can use RADIUS, which is particularly useful if you have other services already using RADIUS. Or, you can just let the RRAS service handle the authentication duties itself. Give users access to the VPN services by enabling dial-in permissions in the user's profile (explained below). For this example, I will not be using RADIUS, but will allow RRAS to directly authenticate incoming connection requests.

Decide what means of authentication you want to provide

That's it for the RRAS wizard! You're provided with a summary screen that details the selections you made.

The RRAS wizard summary window

This also completes the installation of the Remote Access/VPN Server role.

User Configuration

By default, users are not granted access to the services offered by the VPN; you need to grant these rights to each user that you want to allow remote access to your network. To do this, open Active Directory Users and Computers (for domains) or Computer Management (for stand alone networks), and open the properties page for a user to whom you'd like to grant access to the VPN. Select that user's Dial-In properties page. On this page, under Remote Access Permissions, select "Allow access". Note that there are a lot of different ways to "dial in to" a Windows Server 2003 system; a VPN is but one method. Other methods include wireless networks, 802.1x, and dial-up. This article assumes that you're not using the Windows features for these other types of networks. If you are, and you specify "Allow access", a user will be able to use multiple methods to gain access to your system. I can't go over all of the various permutations in a single article, however.

Allow the user access to the VPN

Up and Running

These are the steps needed on the server to get a VPN up and running.

How to Configure a VPN Connection from a Client Computer

1. On the client computer, confirm that the connection to the Internet is correctly configured.
2. Click Start, click Control Panel, and then click Network Connections. Click Create a new connection under Network Tasks, and then click Next.
3. Click Connect to the network at my workplace to create the dial-up connection. Click Next to continue.
4. Click Virtual Private Network connection, and then click Next.
5. Type a descriptive name for this connection in the Company name dialog box, and then click Next.
6. Click Do not dial the initial connection if the computer is permanently connected to the Internet. If the computer connects to the Internet through an Internet Service Provider (ISP), click Automatically dial this initial connection, and then click the name of the connection to the ISP. Click Next.
7. Type the IP address or the host name of the VPN server computer (for example, VPNServer.SampleDomain.com).
8. Click Anyone's use if you want to permit any user who logs on to the workstation to have access to this dial-up connection. Click My use only if you want this connection to be available only to the currently logged-on user. Click Next.
9. Click Finish to save the connection.
10. Click Start, click Control Panel, and then click Network Connections.
11. Double-click the new connection.
12. Click Properties to continue to configure options for the connection. To continue to configure options for the connection, follow these steps:
    
    • If you are connecting to a domain, click the Options tab, and then click to select the Include Windows logon domain check box to specify whether to request Windows Server 2003 logon domain information before trying to connect.
    • If you want the connection to be redialed if the line is dropped, click theOptions tab, and then click to select the Redial if line is dropped check box.

To use the connection, follow these steps:

1. Click Start, point to Connect to, and then click the new connection.
2. If you do not currently have a connection to the Internet, Windows offers to connect to the Internet.
3. When the connection to the Internet is made, the VPN server prompts you for your user name and password. Type your user name and password, and then clickConnect.
   Your network resources must be available to you in the same way they are when you connect directly to the network.NOTE: To disconnect from the VPN, right-click the connection icon, and then click Disconnect.

Troubleshooting

Troubleshooting Remote Access VPNs

Cannot Establish a Remote Access VPN Connection

• Cause: The name of the client computer is the same as the name of another computer on the network.
  
  Solution: Verify that the names of all computers on the network and computers connecting to the network are using unique computer names.

• Cause: The Routing and Remote Access service is not started on the VPN server.
  
  Solution: Verify the state of the Routing and Remote Access service on the VPN server.
  
  
  
• Cause: Remote access is not turned on on the VPN server.
  
  Solution: Turn on remote access on the VPN server.
  
  
  
• Cause: PPTP or L2TP ports are not turned on for inbound remote access requests.
  
  Solution: Turn on PPTP or L2TP ports, or both, for inbound remote access requests.
  
  
  
• Cause: The LAN protocols used by the VPN clients are not turned on for remote access on the VPN server.
  
  Solution: Turn on the LAN protocols used by the VPN clients for remote access on the VPN server.
  
  
  
• Cause: All of the PPTP or L2TP ports on the VPN server are already being used by currently connected remote access clients or demand-dial routers.
  
  Solution: Verify that all of the PPTP or L2TP ports on the VPN server are already being used. To do so, click Ports in Routing and Remote Access. If the number of PPTP or L2TP ports permitted is not high enough, change the number of PPTP or L2TP ports to permit more concurrent connections.
  
  
  

.

• Cause: The VPN server does not support the tunneling protocol of the VPN client.
  
  By default, Windows Server 2003 remote access VPN clients use the Automaticserver type option, which means that they try to establish an L2TP over IPSec-based VPN connection first, and then they try to establish a PPTP-based VPN connection. If VPN clients use either the Point-to-Point Tunneling Protocol (PPTP) or Layer-2 Tunneling Protocol (L2TP) server type option, verify that the selected tunneling protocol is supported by the VPN server.
  
  By default, a computer running Windows Server 2003 Server and the Routing and Remote Access service is a PPTP and L2TP server with five L2TP ports and five PPTP ports. To create a PPTP-only server, set the number of L2TP ports to zero. To create an L2TP-only server, set the number of PPTP ports to zero.
  
  Solution: Verify that the appropriate number of PPTP or L2TP ports is configured.
  
  
  

• Cause: The VPN client and the VPN server in conjunction with a remote access policy are not configured to use at least one common authentication method.
  
  Solution: Configure the VPN client and the VPN server in conjunction with a remote access policy to use at least one common authentication method.
  
  
  

• Cause: The VPN client and the VPN server in conjunction with a remote access policy are not configured to use at least one common encryption method.
  
  Solution: Configure the VPN client and the VPN server in conjunction with a remote access policy to use at least one common encryption method.
  
  
  

• Cause: The VPN connection does not have the appropriate permissions through dial-in properties of the user account and remote access policies.
  
  Solution: Verify that the VPN connection has the appropriate permissions through dial-in properties of the user account and remote access policies. For the connection to be established, the settings of the connection attempt must:
  • Match all of the conditions of at least one remote access policy.
  • Be granted remote access permission through the user account (set to Allow access) or through the user account (set to Control access through Remote Access Policy) and the remote access permission of the matching remote access policy (set to Grant remote access permission).
  • Match all the settings of the profile.
  • Match all the settings of the dial-in properties of the user account.
  See the Windows Server 2003 Help and Support Center for an introduction to remote access policies, and for more information about how to accept a connection attempt. Click Start to access the Windows Server 2003 Help and Support Center.

• Cause: The settings of the remote access policy profile are in conflict with properties of the VPN server.
  
  The properties of the remote access policy profile and the properties of the VPN server both contain settings for:
  • Multilink.
  • Bandwidth allocation protocol (BAP).
  • Authentication protocols.
  If the settings of the profile of the matching remote access policy are in conflict with the settings of the VPN server, the connection attempt is rejected. For example, if the matching remote access policy profile specifies that the Extensible Authentication Protocol - Transport Level Security (EAP-TLS) authentication protocol must be used and EAP is not enabled on the VPN server, the connection attempt is rejected.
  
  Solution: Verify that the settings of the remote access policy profile are not in conflict with properties of the VPN server.
  
  See the Windows Server 2003 Help and Support Center for more information about additional information about multilink, BAP and authentication protocols. Click Start to access the Windows Server 2003 Help and Support Center.

• Cause: The answering router cannot validate the credentials of the calling router (user name, password, and domain name).
  
  Solution: Verify that the credentials of the VPN client (user name, password, and domain name) are correct and can be validated by the VPN server.

• Cause: There are not enough addresses in the static IP address pool.
  
  Solution: If the VPN server is configured with a static IP address pool, verify that there are enough addresses in the pool. If all of the addresses in the static pool have been allocated to connected VPN clients, the VPN server cannot allocate an IP address, and the connection attempt is rejected. If all of the addresses in the static pool have been allocated, modify the pool. See the Windows Server 2003 Help and Support Center for more information about TCP/IP and remote access, and how to create a static IP address pool.

• Cause: The VPN client is configured to request its own IPX node number and the VPN server is not configured to permit IPX clients to request their own IPX node number.
  
  Solution: Configure the VPN server to permit IPX clients to request their own IPX node number.
  
  

• Cause: The VPN server is configured with a range of IPX network numbers that are being used elsewhere on your IPX network.
  
  Solution: Configure the VPN server with a range of IPX network numbers that is unique to your IPX network.
  
  

• Cause: The authentication provider of the VPN server is improperly configured.
  
  Solution: Verify the configuration of the authentication provider. You can configure the VPN server to use either Windows Server 2003 or Remote Authentication Dial-In User Service (RADIUS) to authenticate the credentials of the VPN client.
  
  

• Cause: The VPN server cannot access Active Directory.
  
  Solution: For a VPN server that is a member server in a mixed-mode or native-mode Windows Server 2003 domain that is configured for Windows Server 2003 authentication, verify that:
  • The RAS and IAS Servers security group exists. If not, create the group and set the group type to Security and the group scope to Domain local.
  • The RAS and IAS Servers security group has Read permission to the RAS and IAS Servers Access Check object.
  • The computer account of the VPN server computer is a member of the RAS and IAS Servers security group. You can use the netsh ras show registeredserver command to view the current registration. You can use thenetsh ras add registeredserver command to register the server in a specified domain.
    
    If you add (or remove) the VPN server computer to the RAS and IAS Serverssecurity group, the change does not take effect immediately (because of the way that Windows Server 2003 caches Active Directory information). To immediately effect this change, restart the VPN server computer.
  • The VPN server is a member of the domain.

• Cause: A Windows NT 4.0-based VPN server cannot validate connection requests.
  
  Solution: If VPN clients are dialing in to a VPN server running Windows NT 4.0 that is a member of a Windows Server 2003 mixed-mode domain, verify that the Everyone group is added to the Pre-Windows 2000 Compatible Access group with the following command:
  "net localgroup "Pre-Windows 2000 Compatible Access""
  If not, type the following command at a command prompt on a domain controller computer, and then restart the domain controller computer:
  net localgroup "Pre-Windows 2000 Compatible Access" everyone /add

• Cause: The VPN server cannot communicate with the configured RADIUS server.
  
  Solution: If you can reach your RADIUS server only through your Internet interface, do one of the following:
  • Add an input filter and an output filter to the Internet interface for UDP port 1812 (based on RFC 2138, "Remote Authentication Dial-In User Service (RADIUS)"). –or-
  • Add an input filter and an output filter to the Internet interface for UDP port 1645 (for older RADIUS servers), for RADIUS authentication and UDP port 1813 (based on RFC 2139, "RADIUS Accounting"). -or-
    
    
  • -or- Add an input filter and an output filter to the Internet interface for UDP port 1646 (for older RADIUS servers) for RADIUS accounting.

• Cause: Cannot connect to the VPN server over the Internet using the Ping.exe utility.
  
  Solution: Because of the PPTP and L2TP over IPSec packet filtering that is configured on the Internet interface of the VPN server, Internet Control Message Protocol (ICMP) packets used by the ping command are filtered out. To turn on the VPN server to respond to ICMP (ping) packets, add an input filter and an output filter that permit traffic for IP protocol 1 (ICMP traffic).
  
  

Cannot Send and Receive Data

• Cause: The appropriate demand-dial interface has not been added to the protocol being routed.
  
  Solution: Add the appropriate demand-dial interface to the protocol being routed.
  
  

• Cause: There are no routes on both sides of the router-to-router VPN connection that support the two-way exchange of traffic.
  
  Solution: Unlike a remote access VPN connection, a router-to-router VPN connection does not automatically create a default route. Create routes on both sides of the router-to-router VPN connection so that traffic can be routed to and from the other side of the router-to-router VPN connection.
  
  You can manually add static routes to the routing table, or you can add static routes through routing protocols. For persistent VPN connections, you can turn on Open Shortest Path First (OSPF) or Routing Information Protocol (RIP) across the VPN connection. For on-demand VPN connections, you can automatically update routes through an auto-static RIP update. See Windows Server 2003 online Help for more information about how to add an IP routing protocol, how to add a static route, and how to perform auto-static updates.

• Cause: A two-way initiated, the answering router as a remote access connection is interpreting router-to-router VPN connection.
• 
  Solution: If the user name in the credentials of the calling router appears under Dial-In Clients in Routing and Remote Access, the answering router may interpret the calling router as a remote access client. Verify that the user name in the credentials of the calling router matches the name of a demand-dial interface on the answering router. If the incoming caller is a router, the port on which the call was received shows a status of Active and the corresponding demand-dial interface is in a Connectedstate.
  
  

• Cause: Packet filters on the demand-dial interfaces of the calling router and answering router are preventing the flow of traffic.
  
  Solution: Verify that there are no packet filters on the demand-dial interfaces of the calling router and answering router that prevent the sending or receiving of traffic. You can configure each demand-dial interface with IP and IPX input and output filters to control the exact nature of TCP/IP and IPX traffic that is permitted into and out of the demand-dial interface.
  
  

• Cause: Packet filters on the remote access policy profile are preventing the flow of IP traffic.
  
  Solution: Verify that there are no configured TCP/IP packet filters on the profile properties of the remote access policies on the VPN server (or the RADIUS server if Internet Authentication Service is used) that are preventing the sending or receiving of TCP/IP traffic. You can use remote access policies to configure TCP/IP input and output packet filters that control the exact nature of TCP/IP traffic permitted on the VPN connection. Verify that the profile TCP/IP packet filters are not preventing the flow of traffic.