--=_NextPart_000_0038_01C6ACCB.8D05BD60
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
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
--=_NextPart_000_0038_01C6ACCB.8D05BD60
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
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
--=_NextPart_000_0038_01C6ACCB.8D05BD60--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 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|||This is a multi-part message in MIME format.
--000100040600010001030705
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
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
--000100040600010001030705
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Alex AU wrote:
<blockquote cite="mid%234kVSiIrGHA.3680@.TK2MSFTNGP02.phx.gbl"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<style></style>
<meta content="MSHTML 6.00.2900.2912" name="GENERATOR">
<div><font face="Times New Roman">Dear all,</font></div>
<div>Â </div>
<div><font face="Times New Roman">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.</font></div>
<div>Â </div>
<div><font face="Times New Roman">How can IÂ register and connect to
the SERVER\SQL2005 server? </font></div>
<div>Â </div>
<div><font face="Times New Roman">The SERVER\SQL2005 has been
configured to enable the protocols of shared memory, namepipe and tcpip
already.</font></div>
<div>Â </div>
<div><font face="Times New Roman">The SERVER has installed SQL2000
first and then install SQL2005 server.</font></div>
<div>Â </div>
<div><font face="Times New Roman">Thanks a lot.</font></div>
<div>Â </div>
<div>
<div>
<div>
<div>Â </div>
<div>Â </div>
<div><font face="Times New Roman">Regards,</font></div>
<div>Â </div>
<div><font face="Times New Roman">Alex AU</font></div>
</div>
</div>
</div>
</blockquote>
<font size="-1"><font face="Arial">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.</font></font><br>
<br>
<br>
-- <br>
Regards<br>
Steen Schlüter Persson<br>
Databaseadministrator / Systemadministrator<br>
</body>
</html>
--000100040600010001030705--|||This is a multi-part message in MIME format.
--=_NextPart_000_002F_01C6ADE7.6B1D97F0
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
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:
> 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
--=_NextPart_000_002F_01C6ADE7.6B1D97F0
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
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"
--=_NextPart_000_002F_01C6ADE7.6B1D97F0--|||This is a multi-part message in MIME format.
--=_NextPart_000_0041_01C6ADE7.D964CB70
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
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 used the name instance to try connect but it failed.
I've already set the remote connection with namepipe and tcpip in the =service 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 connection. 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 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=C3=BCter Persson
Databaseadministrator / Systemadministrator
--=_NextPart_000_0041_01C6ADE7.D964CB70
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
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 used the name instance to try connect =but it failed.
I've already set the remote =connection with namepipe and tcpip in the service 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 connection. I just cannot register the =SERVER\SQL2005 on my workstation's management studio.
Thanks
Regards,
Alex AU
"Steen Persson (DK)"
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 AUAre 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.-- RegardsSteen =Schl=C3=BCter PerssonDatabaseadministrator / Systemadministrator
--=_NextPart_000_0041_01C6ADE7.D964CB70--|||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:
> > 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
>|||This is a multi-part message in MIME format.
--=_NextPart_000_0103_01C6AF00.EB2418B0
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
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:
> 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:
> > > 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
>
--=_NextPart_000_0103_01C6AF00.EB2418B0
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
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 =1SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].Sqlcmd: Error: Microsoft SQL Native Client : An error =has occurred while establishing a connection to the server. When =connecting to SQL Server 2005, this failure 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"
--=_NextPart_000_0103_01C6AF00.EB2418B0--|||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/FreeTools/tabid/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:
> > 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:
> >
> > > 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
> >
>|||This is a multi-part message in MIME format.
--=_NextPart_000_0017_01C6AF40.AEAD7990
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
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/FreeTools/tabid/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:
> > > 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:
> >
> > > 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
> >
>
--=_NextPart_000_0017_01C6AF40.AEAD7990
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
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"
--=_NextPart_000_0017_01C6AF40.AEAD7990--|||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/FreeTools/tabid/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:
> >
> > > 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:
> > >
> > > > 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
> > >
> >
>|||This is a multi-part message in MIME format.
--=_NextPart_000_000F_01C6AF97.8BFAF4C0
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Dear John,
Thanks for your great help. With your information, I found another =article that detailed the settings needed for XP firewall settings for =SQL2005 and would like to share here.
http://support.microsoft.com/kb/914277/en-us
Now I can connect to the SQL2005 instance on the XP workstation.
Thanks again.
Regards,
Alex AU
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message =news:844977CE-C5D2-4A3A-A29D-5DA1613C476C@.microsoft.com...
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/FreeTools/tabid/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:
> >
> > > 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:
> > >
> > > > 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
> > >
> >
>
--=_NextPart_000_000F_01C6AF97.8BFAF4C0
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Dear John,
Thanks for your great help. With =your information, I found another article that =detailed the settings needed for XP firewall settings for SQL2005 and would like =to share here.
http://support.microsoft.com/kb/914277/en-us">http://support.micr=osoft.com/kb/914277/en-us
Now I can connect to the SQL2005 =instance on the XP workstation.
Thanks again.
Regards,
Alex AU
"John Bell"
--=_NextPart_000_000F_01C6AF97.8BFAF4C0--|||Here is another one: http://www.sqlserver2005.de > Screencasts > Enable
Remote Connections.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--|||Hi Jens
You may want to add a new screen cast for enabling the XP firewall to allow
SQL Server traffic as described in the lower half of the link Alex provided!
John
"Jens" wrote:
> Here is another one: http://www.sqlserver2005.de > Screencasts > Enable
> Remote Connections.
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
No comments:
Post a Comment