Cannot Connect to Instance

Ok, I can connect to the sql server instances using
tcp:ServerName,PortNumber. However; I still cannot connect using
ServerName\InstanceName. This would not be a big deal, if I could get
Enterprise Manager on a remote machine to register the instance using the
tcp:ServerName,PortNumber format. I would still like to be able to register
the server in Enterprise Manager on a remote computer.sounds like a DNS issue...can you register using IPaddress\instance name?
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Travis Lingenfelder" <TravisLingenfelder@.discussions.microsoft.com> wrote
in message news:DE60DF84-A796-4219-A2CE-86B7F99D4B0A@.microsoft.com...
> Ok, I can connect to the sql server instances using
> tcp:ServerName,PortNumber. However; I still cannot connect using
> ServerName\InstanceName. This would not be a big deal, if I could get
> Enterprise Manager on a remote machine to register the instance using the
> tcp:ServerName,PortNumber format. I would still like to be able to
> register
> the server in Enterprise Manager on a remote computer.
>|||Or...could be trying to use named pipes (or some other protocol) when you
are not specifying tcp...what protocols is theSQL server listening on?
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Travis Lingenfelder" <TravisLingenfelder@.discussions.microsoft.com> wrote
in message news:DE60DF84-A796-4219-A2CE-86B7F99D4B0A@.microsoft.com...
> Ok, I can connect to the sql server instances using
> tcp:ServerName,PortNumber. However; I still cannot connect using
> ServerName\InstanceName. This would not be a big deal, if I could get
> Enterprise Manager on a remote machine to register the instance using the
> tcp:ServerName,PortNumber format. I would still like to be able to
> register
> the server in Enterprise Manager on a remote computer.
>|||I'm having the exact same problem. I can connect using this in my connectio
n
string:
Source=tcp:ServerName,1130
I know to use port 1130 because that's what the ERRORLOG file for that named
instance says it's currently listening on, but I don't think it's a good ide
a
to specify the port when it can change the next time the server is rebooted.
I know it's not a DNS issue, I can ping myDBserver.acme.com, or even just
myDBserver and get replies. Not only that, the the above source parameter
obviously resolves properly to the right IP address.
The server is listening on TCP/IP and Named Pipe.
Trying to connect using the following do not work:
Source=ServerName\InstanceName,1130
Source=ServerName\InstanceName
Source=192.168.10.4\InstanceName
Source=192.168.10.4\InstanceName,1130
I'm trying to connect to SQL Server 2000 SP4 from a web server (classic ASP
on IIS 5.0). The strange thing is that I can run Query Analyzer from the we
b
server and connect using ServerName\InstanceName. The web site can't.
According to MDAC component checker, the web server is running MDAC 2.7 SP1.
I'll run the SQL Server SP4 on the web server to update the SQL Tools.
Unless I'm mistaken, that should also update MDAC to 2.8. We'll see if that
fixes it.
Anyone can add to this? Any ideas as to what else I can do to troubleshoot
this?
Thanks,
Francois
"Kevin3NF" wrote:

> Or...could be trying to use named pipes (or some other protocol) when you
> are not specifying tcp...what protocols is theSQL server listening on?
> --
> Kevin Hill
> President
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
> "Travis Lingenfelder" <TravisLingenfelder@.discussions.microsoft.com> wrote
> in message news:DE60DF84-A796-4219-A2CE-86B7F99D4B0A@.microsoft.com...
>
>|||Well, updating MDAC to the latest, by applying SQL Server SP4, didn't change
anything.
What else can I do to troubleshoot this?
Any help would be greatly appreciated...
Francois
"Francois" wrote:
[vbcol=seagreen]
> I'm having the exact same problem. I can connect using this in my connect
ion
> string:
> Source=tcp:ServerName,1130
> I know to use port 1130 because that's what the ERRORLOG file for that nam
ed
> instance says it's currently listening on, but I don't think it's a good i
dea
> to specify the port when it can change the next time the server is reboote
d.
> I know it's not a DNS issue, I can ping myDBserver.acme.com, or even just
> myDBserver and get replies. Not only that, the the above source parameter
> obviously resolves properly to the right IP address.
> The server is listening on TCP/IP and Named Pipe.
> Trying to connect using the following do not work:
> Source=ServerName\InstanceName,1130
> Source=ServerName\InstanceName
> Source=192.168.10.4\InstanceName
> Source=192.168.10.4\InstanceName,1130
> I'm trying to connect to SQL Server 2000 SP4 from a web server (classic AS
P
> on IIS 5.0). The strange thing is that I can run Query Analyzer from the
web
> server and connect using ServerName\InstanceName. The web site can't.
> According to MDAC component checker, the web server is running MDAC 2.7 SP
1.
> I'll run the SQL Server SP4 on the web server to update the SQL Tools.
> Unless I'm mistaken, that should also update MDAC to 2.8. We'll see if th
at
> fixes it.
> Anyone can add to this? Any ideas as to what else I can do to troubleshoo
t
> this?
> Thanks,
> Francois
>
> "Kevin3NF" wrote:
>