Cannot Register Remote Server

Dear all,
I've installed SQL2005 on my local machine. And there is another SERVER whic
h has install both SQL2000 and SQL2005. I can use my local Management Studio
to register the SERVER\SQL2000 instance but I cannot register SERVER\SQL200
5 instance.
How can I register and connect to the SERVER\SQL2005 server?
The SERVER\SQL2005 has been configured to enable the protocols of shared mem
ory, namepipe and tcpip already.
The SERVER has installed SQL2000 first and then install SQL2005 server.
Thanks a lot.
Regards,
Alex AUHi Alex
Can you conncet to this server using SQLCMD? If not check that Remote
Connections have been set in the surface area configuration tool.
John
"Alex AU" wrote:

> Dear all,
> I've installed SQL2005 on my local machine. And there is another SERVER wh
ich has install both SQL2000 and SQL2005. I can use my local Management Stud
io to register the SERVER\SQL2000 instance but I cannot register SERVER\SQL2
005 instance.
> How can I register and connect to the SERVER\SQL2005 server?
> The SERVER\SQL2005 has been configured to enable the protocols of shared m
emory, namepipe and tcpip already.
> The SERVER has installed SQL2000 first and then install SQL2005 server.
> Thanks a lot.
>
> Regards,
> Alex AU|||Alex AU wrote:
> Dear all,
> I've installed SQL2005 on my local machine. And there is another
> SERVER which has install both SQL2000 and SQL2005. I can use my local
> Management Studio to register the SERVER\SQL2000 instance but I cannot
> register SERVER\SQL2005 instance.
> How can I register and connect to the SERVER\SQL2005 server?
> The SERVER\SQL2005 has been configured to enable the protocols
> of shared memory, namepipe and tcpip already.
> The SERVER has installed SQL2000 first and then install SQL2005 server.
> Thanks a lot.
>
> Regards,
> Alex AU
Are both SQL2000 and SQL2005 installed as named instances on the server?
It could be that SQL2000 is installed as a default instance (hence you
can connect to it just with the servername) and SQL2005 is installed as
a named instance so you need to use that instance name to connect.
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator|||Dear John,
I've already setup the remote connections to accept namepine and tcpip conne
ction in the surface area configuration tool.
I can use ODBC to establish connection from my workstation to the SERVER\SQL
2005 but just cannot register the server in the Management Studio on my work
station.
Thanks.
Regards,
Alex AU
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message news:3238D38E-5324
-49BB-A188-43078C16F3A1@.microsoft.com...
Hi Alex
Can you conncet to this server using SQLCMD? If not check that Remote
Connections have been set in the surface area configuration tool.
John
"Alex AU" wrote:

> Dear all,
>
> I've installed SQL2005 on my local machine. And there is another SERVER wh
ich has install both SQL2000 and SQL2005. I can use my local Management Stud
io to register the SERVER\SQL2000 instance but I cannot register SERVER\SQL2
005 instance.
>
> How can I register and connect to the SERVER\SQL2005 server?
>
> The SERVER\SQL2005 has been configured to enable the protocols of shared m
emory, namepipe and tcpip already.
>
> The SERVER has installed SQL2000 first and then install SQL2005 server.
>
> Thanks a lot.
>
>
>
> Regards,
>
> Alex AU|||Dear Steen,
The SQL2000 is the default instance and SQL2005 is a named instance. When I
register the SQL2005 on my workstation's Management Studio, I've already use
d the name instance to try connect but it failed.
I've already set the remote connection with namepipe and tcpip in the servic
e area configuration on the server. When I try to use ODBC on my workstation
to connect to the SERVER\SQL2005, I can successfully establish the connecti
on. I just cannot register the SERVER\SQL2005 on my workstation's management
studio.
Thanks
Regards,
Alex AU
"Steen Persson (DK)" <spe@.REMOVEdatea.dk> wrote in message news:u0NxbpJrGHA.
2256@.TK2MSFTNGP03.phx.gbl...
Alex AU wrote:
Dear all,
I've installed SQL2005 on my local machine. And there is another SERVER whic
h has install both SQL2000 and SQL2005. I can use my local Management Studio
to register the SERVER\SQL2000 instance but I cannot register SERVER\SQL200
5 instance.
How can I register and connect to the SERVER\SQL2005 server?
The SERVER\SQL2005 has been configured to enable the protocols of shared mem
ory, namepipe and tcpip already.
The SERVER has installed SQL2000 first and then install SQL2005 server.
Thanks a lot.
Regards,
Alex AU
Are both SQL2000 and SQL2005 installed as named instances on the server? It
could be that SQL2000 is installed as a default instance (hence you can conn
ect to it just with the servername) and SQL2005 is installed as a named inst
ance so you need to use that instance name to connect.
--
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator|||Hi Alex
And SQLCMD allows you to connect?
John
"Alex AU" wrote:

> Dear John,
> I've already setup the remote connections to accept namepine and tcpip
> connection in the surface area configuration tool.
> I can use ODBC to establish connection from my workstation to the
> SERVER\SQL2005 but just cannot register the server in the Management
> Studio on my workstation.
> Thanks.
>
> Regards,
> Alex AU
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:3238D38E-5324-49BB-A188-43078C16F3A1@.microsoft.com...
> Hi Alex
> Can you conncet to this server using SQLCMD? If not check that Remote
> Connections have been set in the surface area configuration tool.
> John
> "Alex AU" wrote:
>
> SERVER which has install both SQL2000 and SQL2005. I can use my local
> Management Studio to register the SERVER\SQL2000 instance but I cannot
> register SERVER\SQL2005 instance.
> shared memory, namepipe and tcpip already.
> server.
>|||Dear John,
I've tried sqlcmd, it also failed. The command I used and error as follow:
sqlcmd -S SERVER\SQL2005
HResult 0xFFFFFFFF, Level 16, State 1
SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFF
FFF].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while est
abli
shing a connection to the server. When connecting to SQL Server 2005, this f
ailu
re may be caused by the fact that under the default settings SQL Server does
not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
Thanks a lot.
Regards,
Alex AU
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message news:342A5195-A4E1
-4477-AFDF-F592B3809BDC@.microsoft.com...
Hi Alex
And SQLCMD allows you to connect?
John
"Alex AU" wrote:

> Dear John,
>
> I've already setup the remote connections to accept namepine and tcpip
> connection in the surface area configuration tool.
>
> I can use ODBC to establish connection from my workstation to the
> SERVER\SQL2005 but just cannot register the server in the Management
> Studio on my workstation.
>
> Thanks.
>
>
>
> Regards,
>
> Alex AU
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:3238D38E-5324-49BB-A188-43078C16F3A1@.microsoft.com...
> Hi Alex
>
> Can you conncet to this server using SQLCMD? If not check that Remote
> Connections have been set in the surface area configuration tool.
>
> John
>
> "Alex AU" wrote:
>
> SERVER which has install both SQL2000 and SQL2005. I can use my local
> Management Studio to register the SERVER\SQL2000 instance but I cannot
> register SERVER\SQL2005 instance.
> shared memory, namepipe and tcpip already.
> server.
>|||Hi Alex
This is indicating that the remote connections setting are not set on the
protocols. What does the SQLServer 2005 Configuration Manager tool say (i.e.
not SAC!). Also make sure that you can resolve the server name correctly.
You may also want to look at SQLPing to to see to search for servers
http://www.sqlsecurity.com/Tools/Fr...65/Default.aspx
John
"Alex AU" wrote:

> Dear John,
> I've tried sqlcmd, it also failed. The command I used and error as follow:
> sqlcmd -S SERVER\SQL2005
> HResult 0xFFFFFFFF, Level 16, State 1
> SQL Network Interfaces: Error Locating Server/Instance Specified
> [xFFFFFFFF].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server
> does not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> Thanks a lot.
>
> Regards,
> Alex AU
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:342A5195-A4E1-4477-AFDF-F592B3809BDC@.microsoft.com...
> Hi Alex
> And SQLCMD allows you to connect?
> John
> "Alex AU" wrote:
>
> Remote
>|||Thanks John,
I've used the tools on that SERVER and I've found that the port number for S
QL2005 using is 1025. (SQL2000 use 1433).
I finally figure out what causing the connection issue, it's the firewall se
ttings. I use a Windows XP with SP2 as a server and the firewall has turned
on. It only allow SQL connection from port 1433 and that's the reason why I
cannot connect with SQL Management Studio with port 1025 (SQL2005). When I s
hut down the firewall, it works.
Sorry for the chaos that I've made. But I really appreciate for your kindly
help.
I've got one more question related to this. I've tried to add exception rule
in the XP firewall settings for port 1025, but I still cannot connect. I ca
n only connect when the firewall is off. Can anyone help with this? (or shou
ld I post in other newsgroup for this issue?)
Thanks.
Regards,
Alex AU
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message news:E4A5B93E-6A03
-4406-87B6-399E4A150D02@.microsoft.com...
Hi Alex
This is indicating that the remote connections setting are not set on the
protocols. What does the SQLServer 2005 Configuration Manager tool say (i.e.
not SAC!). Also make sure that you can resolve the server name correctly.
You may also want to look at SQLPing to to see to search for servers
http://www.sqlsecurity.com/Tools/Fr...65/Default.aspx
John
"Alex AU" wrote:

> Dear John,
>
> I've tried sqlcmd, it also failed. The command I used and error as follow:
>
> sqlcmd -S SERVER\SQL2005
>
> HResult 0xFFFFFFFF, Level 16, State 1
> SQL Network Interfaces: Error Locating Server/Instance Specified
> [xFFFFFFFF].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server
> does not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
>
> Thanks a lot.
>
>
>
> Regards,
>
> Alex AU
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:342A5195-A4E1-4477-AFDF-F592B3809BDC@.microsoft.com...
> Hi Alex
>
> And SQLCMD allows you to connect?
>
> John
>
> "Alex AU" wrote:
>
> Remote
>|||Hi
I don't know the intricacies of the XP firewall as I have always used a
third party one. The following describes what you should need to set up in
terms of rules, change this for the port you are using and it should be ok.
http://support.microsoft.com/kb/287932
John
"Alex AU" wrote:

> Thanks John,
> I've used the tools on that SERVER and I've found that the port number for
> SQL2005 using is 1025. (SQL2000 use 1433).
> I finally figure out what causing the connection issue, it's the firewall
> settings. I use a Windows XP with SP2 as a server and the firewall has
> turned on. It only allow SQL connection from port 1433 and that's the
> reason why I cannot connect with SQL Management Studio with port 1025
> (SQL2005). When I shut down the firewall, it works.
> Sorry for the chaos that I've made. But I really appreciate for your
> kindly help.
> I've got one more question related to this. I've tried to add exception
> rule in the XP firewall settings for port 1025, but I still cannot
> connect. I can only connect when the firewall is off. Can anyone help with
> this? (or should I post in other newsgroup for this issue?)
> Thanks.
>
> Regards,
> Alex AU
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:E4A5B93E-6A03-4406-87B6-399E4A150D02@.microsoft.com...
> Hi Alex
> This is indicating that the remote connections setting are not set on
> the
> protocols. What does the SQLServer 2005 Configuration Manager tool say
> (i.e.
> not SAC!). Also make sure that you can resolve the server name
> correctly.
> You may also want to look at SQLPing to to see to search for servers
> http://www.sqlsecurity.com/Tools/Fr...65/Default.aspx
> John
> "Alex AU" wrote:
>
> follow:
> while
> this
> Server
> tcpip
> Management
> tool.
> another
> local
> cannot
> of
> SQL2005
>