Hello,
We have 3 SQL servers.
Server01 Win 2003 w/SQL 2000 192.168.1.1
Server02 Win 2003 w/SQL 2000 192.168.1.2
Server03 Win 2003 w/SQL 2005 192.168.1.3
Server02 can see Server01 and Server03.
Server01 and Server03 can find each other but can not see Server02.
I add 192.168.1.2 in Server03 SQL native client configuration.
The server03 error message said 'the SQL does not allow remote connection'
Whe I check Server02 SQL property, the remote connection is checked.
How can I fix this problem?
Thanks
It's more than just visibility. As I discuss in Chapter 9, you'll need to
enable the protocols and (in the case of SQL Server 2005) the SQL Browser
service to expose SQL Server to the network.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Newbie" <Newbie@.discussions.microsoft.com> wrote in message
news:1F8BFB61-5920-4087-B020-273471DA6163@.microsoft.com...
> Hello,
> We have 3 SQL servers.
> Server01 Win 2003 w/SQL 2000 192.168.1.1
> Server02 Win 2003 w/SQL 2000 192.168.1.2
> Server03 Win 2003 w/SQL 2005 192.168.1.3
> Server02 can see Server01 and Server03.
> Server01 and Server03 can find each other but can not see Server02.
> I add 192.168.1.2 in Server03 SQL native client configuration.
> The server03 error message said 'the SQL does not allow remote connection'
> Whe I check Server02 SQL property, the remote connection is checked.
> How can I fix this problem?
> Thanks
|||Hello,
My question is both SQL2000 can see SQL2005, but SQL2005 can not connect one
of SQL2000.
Thanks
"William (Bill) Vaughn" wrote:
> It's more than just visibility. As I discuss in Chapter 9, you'll need to
> enable the protocols and (in the case of SQL Server 2005) the SQL Browser
> service to expose SQL Server to the network.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Newbie" <Newbie@.discussions.microsoft.com> wrote in message
> news:1F8BFB61-5920-4087-B020-273471DA6163@.microsoft.com...
>
>
Showing posts with label 1server02. Show all posts
Showing posts with label 1server02. Show all posts
Friday, February 10, 2012
can not remote connect SQL 2000
Hello,
We have 3 SQL servers.
Server01 Win 2003 w/SQL 2000 192.168.1.1
Server02 Win 2003 w/SQL 2000 192.168.1.2
Server03 Win 2003 w/SQL 2005 192.168.1.3
Server02 can see Server01 and Server03.
Server01 and Server03 can find each other but can not see Server02.
I add 192.168.1.2 in Server03 SQL native client configuration.
The server03 error message said 'the SQL does not allow remote connection'
Whe I check Server02 SQL property, the remote connection is checked.
How can I fix this problem?
ThanksIt's more than just visibility. As I discuss in Chapter 9, you'll need to
enable the protocols and (in the case of SQL Server 2005) the SQL Browser
service to expose SQL Server to the network.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Newbie" <Newbie@.discussions.microsoft.com> wrote in message
news:1F8BFB61-5920-4087-B020-273471DA6163@.microsoft.com...
> Hello,
> We have 3 SQL servers.
> Server01 Win 2003 w/SQL 2000 192.168.1.1
> Server02 Win 2003 w/SQL 2000 192.168.1.2
> Server03 Win 2003 w/SQL 2005 192.168.1.3
> Server02 can see Server01 and Server03.
> Server01 and Server03 can find each other but can not see Server02.
> I add 192.168.1.2 in Server03 SQL native client configuration.
> The server03 error message said 'the SQL does not allow remote connection'
> Whe I check Server02 SQL property, the remote connection is checked.
> How can I fix this problem?
> Thanks|||Hello,
My question is both SQL2000 can see SQL2005, but SQL2005 can not connect one
of SQL2000.
Thanks
"William (Bill) Vaughn" wrote:
> It's more than just visibility. As I discuss in Chapter 9, you'll need to
> enable the protocols and (in the case of SQL Server 2005) the SQL Browser
> service to expose SQL Server to the network.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Newbie" <Newbie@.discussions.microsoft.com> wrote in message
> news:1F8BFB61-5920-4087-B020-273471DA6163@.microsoft.com...
>
>
We have 3 SQL servers.
Server01 Win 2003 w/SQL 2000 192.168.1.1
Server02 Win 2003 w/SQL 2000 192.168.1.2
Server03 Win 2003 w/SQL 2005 192.168.1.3
Server02 can see Server01 and Server03.
Server01 and Server03 can find each other but can not see Server02.
I add 192.168.1.2 in Server03 SQL native client configuration.
The server03 error message said 'the SQL does not allow remote connection'
Whe I check Server02 SQL property, the remote connection is checked.
How can I fix this problem?
ThanksIt's more than just visibility. As I discuss in Chapter 9, you'll need to
enable the protocols and (in the case of SQL Server 2005) the SQL Browser
service to expose SQL Server to the network.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Newbie" <Newbie@.discussions.microsoft.com> wrote in message
news:1F8BFB61-5920-4087-B020-273471DA6163@.microsoft.com...
> Hello,
> We have 3 SQL servers.
> Server01 Win 2003 w/SQL 2000 192.168.1.1
> Server02 Win 2003 w/SQL 2000 192.168.1.2
> Server03 Win 2003 w/SQL 2005 192.168.1.3
> Server02 can see Server01 and Server03.
> Server01 and Server03 can find each other but can not see Server02.
> I add 192.168.1.2 in Server03 SQL native client configuration.
> The server03 error message said 'the SQL does not allow remote connection'
> Whe I check Server02 SQL property, the remote connection is checked.
> How can I fix this problem?
> Thanks|||Hello,
My question is both SQL2000 can see SQL2005, but SQL2005 can not connect one
of SQL2000.
Thanks
"William (Bill) Vaughn" wrote:
> It's more than just visibility. As I discuss in Chapter 9, you'll need to
> enable the protocols and (in the case of SQL Server 2005) the SQL Browser
> service to expose SQL Server to the network.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Newbie" <Newbie@.discussions.microsoft.com> wrote in message
> news:1F8BFB61-5920-4087-B020-273471DA6163@.microsoft.com...
>
>
Subscribe to:
Posts (Atom)