Report Forge 3.0.11.5

Establishing a connection from ENT Report Forge is much the same as establishing a connection from Enterprise Server. About the only reason why you might be able to configure Enteprise Server to use a database that you werent able to configure ENT Report Forge to use would be if Enterprise Server was installed on the same machine as your MSDE/SQL Server and ENT Report Forge was not.

If ENT Report Forge is running on the same machine as the MSDE or SQL Server, then you probably shouldnt use the ip address or machine name... instead use the address (local) (without the quotes) - this will force ENT Report Forge to establish a connection using the SQL Server Shared Memory protocol which, apart from being more efficient than TCP or RPC, is ALWAYS installed and enabled.

If you are using ENT Report Forge to connect to a database on an SQL Server which is running on a separate machine from ENT Report Forge, then you will need to ensure that
a) The SQL Server that you are connecting to has the TCP/IP network libraries installed and enabled
b) The SQL Server is configured to use a static port
c) If the SQL Server is running on Windows XP SP2 or Windows 2003 that you have configured an exception for port 1433 in the windows firewall (this is the port that SQL Server uses by default to accept requests over the network)