SS 2000 not allow remote connections

GaryDean

I'm trying to connect to a SQL Server 2000 (not 2005) database on another
server and I'm getting the error that SQL Server 2005 does not allow remote
connections by default.

But I'm running 2000. Why am I getting an error about 2005?

All of the stuff in the internet about this problem is in regards to 2005
where it tells you go to go into the surface areas utility etc.

Can anyone enlighten me?

--
Regards,
Gary Blakely

Rick Sawtell

"GaryDean" <GaryDean@newsgroups.nospam> wrote in message
news:.gbl...
> I'm trying to connect to a SQL Server 2000 (not 2005) database on another
> server and I'm getting the error that SQL Server 2005 does not allow
> remote connections by default.
>
> But I'm running 2000. Why am I getting an error about 2005?
>
> All of the stuff in the internet about this problem is in regards to 2005
> where it tells you go to go into the surface areas utility etc.
>
> Can anyone enlighten me?
>
> --
> Regards,
> Gary Blakely
>
>\

Open enterprise manager and connect to the 2k SS in question.

Right-click on the Server and choose Properties.

In the properties window, click the Connections tab.

On the bottom half of the connection tab, there is a section called "Remote
server connections"

Click the appropriate check-boxes.


Rick Sawtell

GaryDean

Sorry, I should have mentioned that I already had verified that the Allow
other SQL Servers to connect remotely to this SQL Server using RPC was
checked.

--
Regards,
Gary Blakely
Dean Blakely & Associates

"Rick Sawtell" <> wrote in message
news:.gbl...
>
> "GaryDean" <GaryDean@newsgroups.nospam> wrote in message
> news:.gbl...
>> I'm trying to connect to a SQL Server 2000 (not 2005) database on another
>> server and I'm getting the error that SQL Server 2005 does not allow
>> remote connections by default.
>>
>> But I'm running 2000. Why am I getting an error about 2005?
>>
>> All of the stuff in the internet about this problem is in regards to 2005
>> where it tells you go to go into the surface areas utility etc.
>>
>> Can anyone enlighten me?
>>
>> --
>> Regards,
>> Gary Blakely
>>
>>\
>
> Open enterprise manager and connect to the 2k SS in question.
>
> Right-click on the Server and choose Properties.
>
> In the properties window, click the Connections tab.
>
> On the bottom half of the connection tab, there is a section called
> "Remote server connections"
>
> Click the appropriate check-boxes.
>
>
> Rick Sawtell
>
>

Jason Massie

Hi Gary,
You have probably already done this but I would start at the bottom and work
my way up. Telnet by name to verify name resolution, connectivity and it is
listening.

telnet YourServer 1433(or the port)

If that is good, try creating an alias forcing tcp and the hard coded port.


--
Jason Massie
Web:
RSS:

"GaryDean" <GaryDean@newsgroups.nospam> wrote in message
news:.gbl...
> I'm trying to connect to a SQL Server 2000 (not 2005) database on another
> server and I'm getting the error that SQL Server 2005 does not allow
> remote connections by default.
>
> But I'm running 2000. Why am I getting an error about 2005?
>
> All of the stuff in the internet about this problem is in regards to 2005
> where it tells you go to go into the surface areas utility etc.
>
> Can anyone enlighten me?
>
> --
> Regards,
> Gary Blakely
>
>

Jason Massie

Hi Gary,
You have probably already done this but I would start at the bottom and work
my way up. Telnet by name to verify name resolution, connectivity and it is
listening.

telnet YourServer 1433(or the port)

If that is good, try creating an alias forcing tcp and the hard coded port.


--
Jason Massie
Web:
RSS:

"GaryDean" <GaryDean@newsgroups.nospam> wrote in message
news:.gbl...
> I'm trying to connect to a SQL Server 2000 (not 2005) database on another
> server and I'm getting the error that SQL Server 2005 does not allow
> remote connections by default.
>
> But I'm running 2000. Why am I getting an error about 2005?
>
> All of the stuff in the internet about this problem is in regards to 2005
> where it tells you go to go into the surface areas utility etc.
>
> Can anyone enlighten me?
>
> --
> Regards,
> Gary Blakely
>
>

Wei Lu [MSFT]

Hello Gary,

I would like to suggest you first check whether you have connect to the
right instance.

Then, you may follow this KB article to troubleshoot.

827422 How to troubleshoot connectivity issues in SQL Server 2000


Sincerely,

Wei Lu
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Wei Lu [MSFT]

Hello Gary,

I would like to suggest you first check whether you have connect to the
right instance.

Then, you may follow this KB article to troubleshoot.

827422 How to troubleshoot connectivity issues in SQL Server 2000


Sincerely,

Wei Lu
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Jason Massie

Hi Gary,
You have probably already done this but I would start at the bottom and work
my way up. Telnet by name to verify name resolution, connectivity and it is
listening.

telnet YourServer 1433(or the port)

If that is good, try creating an alias forcing tcp and the hard coded port.


--
Jason Massie
Web:
RSS:

"GaryDean" <GaryDean@newsgroups.nospam> wrote in message
news:.gbl...
> I'm trying to connect to a SQL Server 2000 (not 2005) database on another
> server and I'm getting the error that SQL Server 2005 does not allow
> remote connections by default.
>
> But I'm running 2000. Why am I getting an error about 2005?
>
> All of the stuff in the internet about this problem is in regards to 2005
> where it tells you go to go into the surface areas utility etc.
>
> Can anyone enlighten me?
>
> --
> Regards,
> Gary Blakely
>
>

Jason Massie

Hi Gary,
You have probably already done this but I would start at the bottom and work
my way up. Telnet by name to verify name resolution, connectivity and it is
listening.

telnet YourServer 1433(or the port)

If that is good, try creating an alias forcing tcp and the hard coded port.


--
Jason Massie
Web:
RSS:

"GaryDean" <GaryDean@newsgroups.nospam> wrote in message
news:.gbl...
> I'm trying to connect to a SQL Server 2000 (not 2005) database on another
> server and I'm getting the error that SQL Server 2005 does not allow
> remote connections by default.
>
> But I'm running 2000. Why am I getting an error about 2005?
>
> All of the stuff in the internet about this problem is in regards to 2005
> where it tells you go to go into the surface areas utility etc.
>
> Can anyone enlighten me?
>
> --
> Regards,
> Gary Blakely
>
>

Wei Lu [MSFT]

Hello Gary,

I would like to suggest you first check whether you have connect to the
right instance.

Then, you may follow this KB article to troubleshoot.

827422 How to troubleshoot connectivity issues in SQL Server 2000


Sincerely,

Wei Lu
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.