Home RDP Sales Contact Us Training  
RDP Support  

     Open a Web Support Ticket
RDPWin
Knowledge Base		 RDP-DOS
Knowledge Base		 IRM and IRM.Net
Knowledge Base		 Crystal
Knowledge Base
         

Updated: 7/03/08 SS per KW

RDP Windows 2003 Data Server Installation

Update:  6/11/08 Microsoft Windows Server 2003 and 2008 for 32 bit are supported by RDP.  Feel free to call RDP Support at 970- 845-7108 with any hardware questions.  Please see the current hardware requirements.

Note:  Microsoft's Windows Server 2003 with SP1 x64-based version (released 10/11/2007) has not been tested by RDP and therefore is not supported.  RDPWin only supports Windows 2003 R2 Standard Edition and Server 2008 for 32-bit programs.  RDP no longer supports Windows 95, 98, ME, or 2000.

Links to RDP Data Server and Internet Reservation Module (IRM.net) documents

This document is intended for use by Certified Microsoft Installers and outlines the steps for installing the RDP system on a Windows 2003/2008 data server.  The document is organized into the following sections.

RDP Windows 2003 Data Server
Configuration Overview

RDP uses the Pervasive database, which is located on a data server.  The data server can use Windows 2003 standard edition or 2008 32 bit server, or could be installed peer-to-peer on an XP Professional workstation.  The preferred operating system is Windows 2008, as it's faster than 2003.  Any new server purchased for a RDP Data Server or Internet Reservation Module Server should be Windows 2008 for 32 bits.  Existing customers with a Windows 2003 servers do not need to upgrade to 2008.  Before starting the installation process, it is critical to verify if the proper equipment is in place.   Please click here to review the RDP hardware requirements.

This document serves as an overview to the RDP Windows 2003 Data Server installation process.  It is designed for use by a Microsoft Certified Installer and is not intended as the sole reference for installing and configuring a Windows 2003 Server and a Pervasive.SQL database.  If you are looking for the installation procedure for RDP's Internet Reservation Module, please click here.

RDP strongly recommends installing the property management software on a Windows 2003 or 2008 Server dedicated to running the RDP software.  All other network applications (back-office accounting software, sales and marketing applications, etc.) should be installed on another server.  This configuration guarantees maximum performance and reliability for the RDP property management software.  It also eliminates the risk of application conflicts between RDP and/or the Pervasive.SQL database.

Diagram of Data Server,  IRM Server, and Workstations
Warning:  Microsoft Small Business Server can not be used for the Internet Reservation Module (IRM), because Small Business Server installs Microsoft Exchange which does not work with the IRM. 
</
Item Explanation
Anti-Virus Software Anti-virus software should be installed on the RDP data server, IRM server, and all workstations.  It is critical to configure the auto-protected mode of all anti-virus software to scan local drives only.  If anti-virus software is set to scan network drives, all network based software such as RDP will run slowly.

See Do Not Scan Network Drives with Anti-virus Software.
Router  A router connects your firewall to the Internet.  For security reasons, it is critical to always connect the router to a firewall and not directly to a network card in any server or workstation.
Firewall A firewall provides security when an internal network is connected to the Internet. The firewall must be a physically separate device (a "stand alone" firewall).  RDP software does not work with firewall software installed on the RDP data server or the IRM Bridge Server.  The firewall must be capable of "address redirection."  For example, the external IP address of 65.38.150.5 will be redirected to the internal address of the IRM server (10.0.0.4 in this example).

See Linking Options From Your Marketing Website to the IRM and IRM.net.
Firewall Ports
to Open

DMZ setup for IRM

Ports for Netmeeting		 A physical firewall is required to secure the IRM from viruses and other attacks. The external IP address must be redirected to the internal address of the IRM Bridge for Ports 80, 443, and 3389.  Additionally, the firewall must be open to allow outgoing e-mail from the SMTP server installed on the IRM bridge on Port 25.  Do not, under any conditions, assign the external IP address directly to the IRM, as this creates a security loophole and also prevents proper communication from the IRM to the data server.

Ports Reason
25 E-mails are sent out to guests from the IRM bridge server using Port 25.  See Installation of Outgoing SMTP E-mail Server
80 Internet traffic (HTTP) is required for all IRM systems.
443  Secure Internet (HTTPs) is required if IRM has Security Certificate.
3389  Terminal services are required for RDP support to access server.
DMZ Only

1583
3351		 Some customers want to set up the IRM in a Demilitarized Zone (DMZ).  RDP uses the Pervasive.SQL database, which uses two TCP ports when communicating from the client to the server, which are: 1583 and 3351. These ports will have to be open on the firewall, as all other ports required by Microsoft for the Windows 2003 IRM server to communicate with the Windows 2003 Data Server. Please contact Microsoft for details on what ports are required.
522, 389
1503, 1720
1731		 Any workstation that connects to RDP with NetMeeting must open various ports.  For instructions on how to configure your firewall to allow workstations to connect to RDP using Net Meeting, see Microsoft article ID# 158623 How to Establish Net Meeting Connections Through a Firewall.
Switch or Hub All workstations are connected to a hub or switch which must be a minimum of 100 megabits.  The RDP data server and IRM bridge server must be connected to the same hub or switch.  Ideally, all workstations that access RDP should be connected to the same hub or switch as the data server.  Multiple hubs or switches may be installed for larger installations.  Regardless of how many hubs or switches are used, all workstations that access the RDP data server must be on the same subnet.