Access 2003

So, click Ports in Routing and Remote Access. If the number of PPTP or L2TP ports permitted isn't high enough, change the number of PPTP or L2TP ports to permit more concurrent connections.For more information about how to add PPTP or L2TP ports, see the Windows Server 2003 Help and Support Center. Click Start to access the Windows Server 2003 Help and Support Center.Cause: The VPN server doesn't support the tunneling protocol of the VPN client.By default, Windows Server 2003 remote access VPN clients use the Automatic server 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.For more information about how to add PPTP or L2TP ports, see the Windows Server 2003 Help and Support Center. Click Start to access the Windows Server 2003 Help and Support Center.Cause: The VPN client and the VPN server in conjunction with a remote access policy aren't 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.For more information about how to configure authentication, see the Windows Server 2003 Help and Support Center. Click Start to access the Windows Server 2003 Help and Support Center.Cause: The VPN client and the VPN server in conjunction with a remote access policy aren't 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.For more information about how to configure encryption, see the Windows Server 2003 Help and Support Center. Click Start to access the Windows Server 2003 Help and Support Center.Cause: The VPN connection doesn't have the appropriate permissions

Connection attempt is rejected. If all of the addresses in the static pool have been allocated, modify the pool.For more information about TCP/IP and remote access, and how to create a static IP address pool, see the Windows Server 2003 Help and Support Center. Click Start to access the Windows Server 2003 Help and Support Center.Cause: The VPN client is configured to request its own IPX node number and the VPN server isn't 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.For more information about IPX and remote access, see the Windows Server 2003 Help and Support Center. Click Start to access the Windows Server 2003 Help and Support Center.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.For more information about IPX and remote access, see the Windows Server 2003 Help and Support Center. Click Start to access the Windows Server 2003 Help and Support Center.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.For more information about authentication and accounting providers, see the Windows Server 2003 Help and Support Center, and how to use RADIUS authentication. Click Start to access the Windows Server 2003 Help and Support Center.Cause: The VPN server can't 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 the netsh ras add registeredserver command to register the server in a specified

Windows offers to connect to the Internet.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 click Connect. Your network resources must be available to you in the same way they're when you connect directly to the network.NoteTo disconnect from the VPN, right-click the connection icon, and then click Disconnect.TroubleshootingTroubleshooting remote access VPNsCan't establish a remote access VPN connectionCause: 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 isn't started on the VPN server.Solution: Verify the state of the Routing and Remote Access service on the VPN server.For more information about how to monitor the Routing and Remote Access service, and how to start and stop the Routing and Remote Access service, see Windows Server 2003 Help and Support Center. Click Start to access the Windows Server 2003 Help and Support Center.Cause: Remote access isn't turned on the VPN server.Solution: Turn on remote access on the VPN server.For more information about how to turn on the remote access server, see the Windows Server 2003 Help and Support Center. Click Start to access the Windows Server 2003 Help and Support Center.Cause: PPTP or L2TP ports aren't turned on for inbound remote access requests.Solution: Turn on PPTP or L2TP ports, or both, for inbound remote access requests.For more information about how to configure ports for remote access, see the Windows Server 2003 Help and Support Center. Click Start to access the Windows Server 2003 Help and Support Center.Cause: The LAN protocols used by the VPN clients aren't 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.For more information about how to view properties of the remote access server, see the Windows Server 2003 Help and Support Center. Click Start to access the Windows Server 2003 Help and Support Center.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

Microsoft Office Web Components are a collection of Component Object Model (COM) controls for publishing spreadsheets, charts, and databases to the Web. They are also used to view these items when published and to view data access pages.If you have Microsoft Office FrontPage 2003, Microsoft Office Access 2003, and Microsoft Office Excel 2003 installed, Office Web Components allow you to publish interactive data as part of a Web page. Used with Microsoft Internet Explorer version 5.01 or later, Office Web Components allow you to view a published control (Spreadsheet, chart, or database) on a Web page and to view data access pages.By installing The Office Web Components tool, users can view published components and data access pages on the Web without having to install Office 2003. Note: If you do not own an Office 2003 license, the Office Web Components are licensed to be used in Static, non-interactive, client-side, view-only mode. If you do own an Office 2003 license, the Office Web Components are licensed to be used in interactive mode.Fixed some bugs.