> Charles,
> Try increasing the login timeout used by Enterprise Manager.
> In Enterprise Manager, go to the menu to Tools, then select
> Options. Click on the Advanced tab and increase the login
> timeout from the default 4 seconds. Try 10 or 15 seconds
> instead and see if that helps.
>
> -Sue
>
> On Sat, 17 Apr 2004 12:14:30 +0200, "Charles"
> <ccolell@softeng.es> wrote:
>
> >Hello,
> >
> >I try to register a remote SQL Server 2000 installed in a W2003, but it
> >doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
> >
> >In that network , there is not any firewall and port 1433 is open in the
> >router. What it really surpises me, is that
> >I can connect via ODBC to any database of that remote SQL Server2000 and
> >work wuth tables fine !!!
> >
> >Using the Enterprise Manager from the W2003 server, we have checked
> >the following:
> > -Network Configuration button on the General tab
> > Is TCP/IP enabled?
> > -In the Connections tab, the Query time-out value is not set too low
(600
> >seconds)
> > -There is not a maximum concurrent user connections value set
> >(unlimited).
> >
> >Also, we can register others remote servers and work fine.
> >
> >Any idea ?
> >
> >Thank you very much !
> >
> >Charles.
> >
>