I am setting up a migration upgrade from SBS 4.5 to 2000.
On our current server, I am running Win NT 4.0 and SQL
Server 2000 without problems. On a seperate switch, I
have set up a new server with SBS 2000 running SQL Server
2000 and cannot get a client computer to connect to the
the SQL server database using Enterprise Manager.
Enterprise Manager works fine on the server console.

ODBC connections fail in the same manner giving an ODBC
Timeout error.

Server Connection is set to use TCP/IP on port 1433,
clients are set to use TCP/IP and dynamic port acquisition.

Client logs in to server without problems, and exchange
works fine too.

Any ideas on what could cause the communication problem?

Thanks,
Steve

It could just be that you need to increase the login timeout
in Enterprise Manager. In Enterprise Manager, go to the menu
to Tools and select Options. In the Properties Window,
select the Advanced tab. Increase the Connections login
timeout to something greater than the default 4 seconds.

-Sue

On Sun, 5 Oct 2003 20:32:27 -0700, "Steve"
<stevebermes@hotmail.com> wrote:

>I am setting up a migration upgrade from SBS 4.5 to 2000.
>On our current server, I am running Win NT 4.0 and SQL
>Server 2000 without problems. On a seperate switch, I
>have set up a new server with SBS 2000 running SQL Server
>2000 and cannot get a client computer to connect to the
>the SQL server database using Enterprise Manager.
>Enterprise Manager works fine on the server console.
>
>ODBC connections fail in the same manner giving an ODBC
>Timeout error.
>
>Server Connection is set to use TCP/IP on port 1433,
>clients are set to use TCP/IP and dynamic port acquisition.
>
>Client logs in to server without problems, and exchange
>works fine too.
>
>Any ideas on what could cause the communication problem?
>
>Thanks,
>Steve