I enabled publishing on the SQL 2000 box so that I can do replication from
2000 to 2005. During the wizard setup, the 2005 subscriber gets this error:
---
Cannot connect to Server1. Additional information: Failed to connection to
server Server1 (Microsoft.SqlServer.ConnectionInfo) An error has occurred
while establishing a connection tot he 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. (provider: Named
Pipes Provider, error 40 - Could not open a connection to SQL Server)
(Microsoft SQL Server, Error: 52).
---
Both boxes are on the same LAN subnet with no firewall between them. I
added an entry to my HOSTS file on the 2005 server so it can see the 2000
server by name (the wizard won't let you type in an IP address). Pinging
that machine works fine.
I don't know why this happens. I've tried windows auth and SQL auth.
What's the trick? Is 2005 using some new communications method that 2000
doesn't understand? I don't even know of a log file that would help but
maybe someone knows the answer or where there is some log info.Open the Surface Area Configuration on the 2005 machine and enable remote
connections. By default a newly installed SQL Server 2005 instance will
only respond to requests sent from the physical machine it was installed on.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"HK" <replywithingroup@.notreal.com> wrote in message
news:ZSbKf.13005$Ou1.8109@.tornado.socal.rr.com...
>I enabled publishing on the SQL 2000 box so that I can do replication from
> 2000 to 2005. During the wizard setup, the 2005 subscriber gets this
> error:
> ---
> Cannot connect to Server1. Additional information: Failed to connection
> to
> server Server1 (Microsoft.SqlServer.ConnectionInfo) An error has occurred
> while establishing a connection tot he 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. (provider: Named
> Pipes Provider, error 40 - Could not open a connection to SQL Server)
> (Microsoft SQL Server, Error: 52).
> ---
> Both boxes are on the same LAN subnet with no firewall between them. I
> added an entry to my HOSTS file on the 2005 server so it can see the 2000
> server by name (the wizard won't let you type in an IP address). Pinging
> that machine works fine.
> I don't know why this happens. I've tried windows auth and SQL auth.
> What's the trick? Is 2005 using some new communications method that 2000
> doesn't understand? I don't even know of a log file that would help but
> maybe someone knows the answer or where there is some log info.
>|||On the subscriber machine? That sounds like something I would do on the
publisher but the publisher is SQL 2000.
"Michael Hotek" <mike@.solidqualitylearning.com> wrote in message
news:uHHA4ZpNGHA.3460@.TK2MSFTNGP15.phx.gbl...
> Open the Surface Area Configuration on the 2005 machine and enable remote
> connections. By default a newly installed SQL Server 2005 instance will
> only respond to requests sent from the physical machine it was installed
on.
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "HK" <replywithingroup@.notreal.com> wrote in message
> news:ZSbKf.13005$Ou1.8109@.tornado.socal.rr.com...
> >I enabled publishing on the SQL 2000 box so that I can do replication
from
> > 2000 to 2005. During the wizard setup, the 2005 subscriber gets this
> > error:
> >
> > ---
> > Cannot connect to Server1. Additional information: Failed to
connection
> > to
> > server Server1 (Microsoft.SqlServer.ConnectionInfo) An error has
occurred
> > while establishing a connection tot he 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. (provider:
Named
> > Pipes Provider, error 40 - Could not open a connection to SQL Server)
> > (Microsoft SQL Server, Error: 52).
> > ---
> >
> > Both boxes are on the same LAN subnet with no firewall between them. I
> > added an entry to my HOSTS file on the 2005 server so it can see the
2000
> > server by name (the wizard won't let you type in an IP address).
Pinging
> > that machine works fine.
> >
> > I don't know why this happens. I've tried windows auth and SQL auth.
> > What's the trick? Is 2005 using some new communications method that
2000
> > doesn't understand? I don't even know of a log file that would help but
> > maybe someone knows the answer or where there is some log info.
> >
> >
>|||The setting Mike told you about is to allow the remote machine (publisher)
to connect to the local (Subscriber - 2005) machine. It is from the
viewpoint of the 2005 machine.
--
Andrew J. Kelly SQL MVP
"HK" <replywithingroup@.notreal.com> wrote in message
news:J9HKf.8983$Jg.197@.tornado.socal.rr.com...
> On the subscriber machine? That sounds like something I would do on the
> publisher but the publisher is SQL 2000.
> "Michael Hotek" <mike@.solidqualitylearning.com> wrote in message
> news:uHHA4ZpNGHA.3460@.TK2MSFTNGP15.phx.gbl...
>> Open the Surface Area Configuration on the 2005 machine and enable remote
>> connections. By default a newly installed SQL Server 2005 instance will
>> only respond to requests sent from the physical machine it was installed
> on.
>> --
>> Mike
>> http://www.solidqualitylearning.com
>> Disclaimer: This communication is an original work and represents my sole
>> views on the subject. It does not represent the views of any other
>> person
>> or entity either by inference or direct reference.
>>
>> "HK" <replywithingroup@.notreal.com> wrote in message
>> news:ZSbKf.13005$Ou1.8109@.tornado.socal.rr.com...
>> >I enabled publishing on the SQL 2000 box so that I can do replication
> from
>> > 2000 to 2005. During the wizard setup, the 2005 subscriber gets this
>> > error:
>> >
>> > ---
>> > Cannot connect to Server1. Additional information: Failed to
> connection
>> > to
>> > server Server1 (Microsoft.SqlServer.ConnectionInfo) An error has
> occurred
>> > while establishing a connection tot he 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. (provider:
> Named
>> > Pipes Provider, error 40 - Could not open a connection to SQL Server)
>> > (Microsoft SQL Server, Error: 52).
>> > ---
>> >
>> > Both boxes are on the same LAN subnet with no firewall between them. I
>> > added an entry to my HOSTS file on the 2005 server so it can see the
> 2000
>> > server by name (the wizard won't let you type in an IP address).
> Pinging
>> > that machine works fine.
>> >
>> > I don't know why this happens. I've tried windows auth and SQL auth.
>> > What's the trick? Is 2005 using some new communications method that
> 2000
>> > doesn't understand? I don't even know of a log file that would help
>> > but
>> > maybe someone knows the answer or where there is some log info.
>> >
>> >
>>
>
