It was the timeout setting. Thanks for your help.
"Simon Hayes" <sq*@hayes.ch> wrote in message news:<40**********@news.bluewin.ch>...
"ffoiii" <fr***@ffoiii.com> wrote in message
news:44**************************@posting.google.c om... I am attempting to connect to a remote default instance of SQL Server
2k on Win2k using Enterprise Manager from my local host but receive a
"SQL Server registration failed, timeout expired" error message each
time.
I am able to connect using Query Analyzer when specifying the IP
address of the server (I am also specifying the IP address in my
Enterprise Manager connection), am able to ping the server from the
command line, and am able to telnet to port 1433. I have tried
connecting both before and after creating an appropriate alias in
Client Network Utilities all to no avail.
I ran SQL Profiler while attempting to connect and do not see the
connection attempt reach the server. What could be preventing
Enterprise Manager from reaching/connecting to the server while all
other utilities (including profiler) are fine?
Thanks in advance.
One possibility is the timeout setting - the default for QA is 15 seconds,
but it's only 4 seconds in EM. You might try increasing the EM login timeout
to 15 also (Tools menu, Options, Advanced) and see if that resolves the
issue. If not, I've seen recommendations to register the server without
using the wizard.
Simon
