Can not remotely connect to instance of sql server 2000

I had a big problem on connecting sqlserver remotely from other machines on the network .....

From any computer in the network i wanna to register the instance of the sqlserver from the enterprise manager ..... the server instance doesn't appear within the available sqlserver list (the servername which equal to my machine is the only one that appear) ..... when i manualy write the servername\alias manually and i choose the connection type and then i write sqlserver username and password and then finish he give a message to me that access denied or sql server doesn't exist ... !!

by the way from the local machine i registered the local instance of sqlserver successfully and successfully i access the Databases .....

To be noted:

I previously uninstalled this alias and i then i reinstalled it again with the same name and i attached the previously exists Databes.

in the same time i installed on the same machine sqlserver 2005 connectivity clients not the server itself.

Why are you using aliases? Do select @.@.servername, and tell me if this is the exact name you're trying to connect to via enterprise manager.|||

thank you for trying to help me,

I am using an alias from a long time and it was working good until i uninstalled the server and installed it agian .......

when i make "select @.@.servername" it return back "magedsalah\maged" and as i told before it works well on the local machine where i can connect with the enterprise manager to magedsalah\maged without any problems ......

the problem when anybody wanna to register magedsalah\maged in the enterprise manager of another computer the magedsalah\maged doesn't appear in the servers list what appear is magedsalah and it can't be registered and sometimes and some there is nothing appear at all.....

for further details plz refer to original message in the thread.....

thanks

|||Did you ever figure out the solution to this, I'm having the exact same problem, it occured after I installed Sql 2005, and now i'm using named instances.|||

Hi,

After i trapped in solving this problem ..... i removed the existing sql server 2000 where i use the alias and then i installed it again without alias (the default case in setup) ..... then i reattached my databases ......... and it works fine now

|||

I ended up doing the same thing too, and mine works too now. There must be a trick to making it work with alias'/instance names too though, oh well.

Thanks

Can not registre SQL in Enterprise Manager

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.It's the login timeout you want to try increasing. See my
reply to your post in .connect for steps to do this.
-Sue
On Sat, 17 Apr 2004 12:20:44 +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 (60
0
>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.
>

Can not registre SQL in Enterprise Manager

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.
It's the login timeout you want to try increasing. See my
reply to your post in .connect for steps to do this.
-Sue
On Sat, 17 Apr 2004 12:20:44 +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.
>

Can not register SQLServer2000 in Enterprise Manager

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.
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.
>
|||Yes !!!! Thanks a lot Sue.
Have a nice day,
Charles.
"Sue Hoegemeier" <Sue_H@.nomail.please> escribi en el mensaje
news:4eg680hvekta8k50ar1c21fadjcsn7p62i@.4ax.com... [vbcol=seagreen]
> 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:
(600
>

Can not register SQLServer2000 in Enterprise Manager

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.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 (60
0
>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.
>|||Yes !!!! Thanks a lot Sue.
Have a nice day,
Charles.
"Sue Hoegemeier" <Sue_H@.nomail.please> escribi en el mensaje
news:4eg680hvekta8k50ar1c21fadjcsn7p62i@.
4ax.com...
> 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:
>
(600[vbcol=seagreen]
>