Hi,
Hope y'all can help...
I've tried to get it to fire from a specific error # as
well as from a severity level. I have also done all the
troubleshooting tips on BOL. Still no dice. The job
itself executes, this I've checked. I turn the service on
& off, and that registers on the event log, so that's
working.
Thanks!Is the error you are defining the alert on appearing in the event log? =If not you will need to define the error to write to the log - see =sp_addmessage for details.
Mike John
"Ian" <anonymous@.discussions.microsoft.com> wrote in message =news:0c9801c3a0d6$c470acf0$a001280a@.phx.gbl...
> Hi,
> > Hope y'all can help...
> > I've tried to get it to fire from a specific error # as > well as from a severity level. I have also done all the > troubleshooting tips on BOL. Still no dice. The job > itself executes, this I've checked. I turn the service on > & off, and that registers on the event log, so that's > working.
> > Thanks!
Showing posts with label specific. Show all posts
Showing posts with label specific. Show all posts
Sunday, March 25, 2012
Sunday, February 12, 2012
Can't connect to instance name - need explaination rather than ans
I'm really looking for an explaination rather than an answer...
I can't connect to sql instances on a specific server using the normal
structure of <servername>\<instancename> but I can connect to
<servername>,<portnumber>.
I've tried many different connection tests (OSQL, udl file, Ent Mngr) and
instance name doesn't work unless I configure the Client Net Utility to use a
specific port number for this instance.
What I don't understand is whats failing? Is this the server failing to
resolve inbound traffic for a instance name to the port number used? If so
what actually performs this name-to-port-number resolution?
My dev team are particularly technical & when I tell them they have to
connect using <servername>,<portnumber> they'll want to know why I can't fix
it on the server...
Thnx
Steve
Steve Morgan
MCDBA
Snr Production DBA
Well...it's a bit difficult to give an explanation for a
problem when the problem hasn't been identified. But here is
an explanation of connecting to named instances: If you try
to connect to YourServer\YourNamedInstance and that's what
you specify for the connection, it hits UDP 1434 to use the
SQL Server Resolution Service to find what port number
YourServer\YourNamedInstance is listening on. You can
bypass that by specifying the port yourself and then there
is no need to go through UDP 1434.
At a high level, that's one of the primary connection
difference with name instances and when you specify a port
number and when you don't.
-Sue
On Tue, 30 Nov 2004 08:49:03 -0800, Steve Morgan
<SteveMorgan@.discussions.microsoft.com> wrote:
>I'm really looking for an explaination rather than an answer...
>I can't connect to sql instances on a specific server using the normal
>structure of <servername>\<instancename> but I can connect to
><servername>,<portnumber>.
>I've tried many different connection tests (OSQL, udl file, Ent Mngr) and
>instance name doesn't work unless I configure the Client Net Utility to use a
>specific port number for this instance.
>What I don't understand is whats failing? Is this the server failing to
>resolve inbound traffic for a instance name to the port number used? If so
>what actually performs this name-to-port-number resolution?
>My dev team are particularly technical & when I tell them they have to
>connect using <servername>,<portnumber> they'll want to know why I can't fix
>it on the server...
>Thnx
>Steve
I can't connect to sql instances on a specific server using the normal
structure of <servername>\<instancename> but I can connect to
<servername>,<portnumber>.
I've tried many different connection tests (OSQL, udl file, Ent Mngr) and
instance name doesn't work unless I configure the Client Net Utility to use a
specific port number for this instance.
What I don't understand is whats failing? Is this the server failing to
resolve inbound traffic for a instance name to the port number used? If so
what actually performs this name-to-port-number resolution?
My dev team are particularly technical & when I tell them they have to
connect using <servername>,<portnumber> they'll want to know why I can't fix
it on the server...
Thnx
Steve
Steve Morgan
MCDBA
Snr Production DBA
Well...it's a bit difficult to give an explanation for a
problem when the problem hasn't been identified. But here is
an explanation of connecting to named instances: If you try
to connect to YourServer\YourNamedInstance and that's what
you specify for the connection, it hits UDP 1434 to use the
SQL Server Resolution Service to find what port number
YourServer\YourNamedInstance is listening on. You can
bypass that by specifying the port yourself and then there
is no need to go through UDP 1434.
At a high level, that's one of the primary connection
difference with name instances and when you specify a port
number and when you don't.
-Sue
On Tue, 30 Nov 2004 08:49:03 -0800, Steve Morgan
<SteveMorgan@.discussions.microsoft.com> wrote:
>I'm really looking for an explaination rather than an answer...
>I can't connect to sql instances on a specific server using the normal
>structure of <servername>\<instancename> but I can connect to
><servername>,<portnumber>.
>I've tried many different connection tests (OSQL, udl file, Ent Mngr) and
>instance name doesn't work unless I configure the Client Net Utility to use a
>specific port number for this instance.
>What I don't understand is whats failing? Is this the server failing to
>resolve inbound traffic for a instance name to the port number used? If so
>what actually performs this name-to-port-number resolution?
>My dev team are particularly technical & when I tell them they have to
>connect using <servername>,<portnumber> they'll want to know why I can't fix
>it on the server...
>Thnx
>Steve
Can't connect to instance name - need explaination rather than ans
I'm really looking for an explaination rather than an answer...
I can't connect to sql instances on a specific server using the normal
structure of <servername>\<instancename> but I can connect to
<servername>,<portnumber>.
I've tried many different connection tests (OSQL, udl file, Ent Mngr) and
instance name doesn't work unless I configure the Client Net Utility to use
a
specific port number for this instance.
What I don't understand is whats failing? Is this the server failing to
resolve inbound traffic for a instance name to the port number used? If so
what actually performs this name-to-port-number resolution?
My dev team are particularly technical & when I tell them they have to
connect using <servername>,<portnumber> they'll want to know why I can't fix
it on the server...
Thnx
Steve
Steve Morgan
MCDBA
Snr Production DBAWell...it's a bit difficult to give an explanation for a
problem when the problem hasn't been identified. But here is
an explanation of connecting to named instances: If you try
to connect to YourServer\YourNamedInstance and that's what
you specify for the connection, it hits UDP 1434 to use the
SQL Server Resolution Service to find what port number
YourServer\YourNamedInstance is listening on. You can
bypass that by specifying the port yourself and then there
is no need to go through UDP 1434.
At a high level, that's one of the primary connection
difference with name instances and when you specify a port
number and when you don't.
-Sue
On Tue, 30 Nov 2004 08:49:03 -0800, Steve Morgan
<SteveMorgan@.discussions.microsoft.com> wrote:
>I'm really looking for an explaination rather than an answer...
>I can't connect to sql instances on a specific server using the normal
>structure of <servername>\<instancename> but I can connect to
><servername>,<portnumber>.
>I've tried many different connection tests (OSQL, udl file, Ent Mngr) and
>instance name doesn't work unless I configure the Client Net Utility to use
a
>specific port number for this instance.
>What I don't understand is whats failing? Is this the server failing to
>resolve inbound traffic for a instance name to the port number used? If so
>what actually performs this name-to-port-number resolution?
>My dev team are particularly technical & when I tell them they have to
>connect using <servername>,<portnumber> they'll want to know why I can't fi
x
>it on the server...
>Thnx
>Steve
I can't connect to sql instances on a specific server using the normal
structure of <servername>\<instancename> but I can connect to
<servername>,<portnumber>.
I've tried many different connection tests (OSQL, udl file, Ent Mngr) and
instance name doesn't work unless I configure the Client Net Utility to use
a
specific port number for this instance.
What I don't understand is whats failing? Is this the server failing to
resolve inbound traffic for a instance name to the port number used? If so
what actually performs this name-to-port-number resolution?
My dev team are particularly technical & when I tell them they have to
connect using <servername>,<portnumber> they'll want to know why I can't fix
it on the server...
Thnx
Steve
Steve Morgan
MCDBA
Snr Production DBAWell...it's a bit difficult to give an explanation for a
problem when the problem hasn't been identified. But here is
an explanation of connecting to named instances: If you try
to connect to YourServer\YourNamedInstance and that's what
you specify for the connection, it hits UDP 1434 to use the
SQL Server Resolution Service to find what port number
YourServer\YourNamedInstance is listening on. You can
bypass that by specifying the port yourself and then there
is no need to go through UDP 1434.
At a high level, that's one of the primary connection
difference with name instances and when you specify a port
number and when you don't.
-Sue
On Tue, 30 Nov 2004 08:49:03 -0800, Steve Morgan
<SteveMorgan@.discussions.microsoft.com> wrote:
>I'm really looking for an explaination rather than an answer...
>I can't connect to sql instances on a specific server using the normal
>structure of <servername>\<instancename> but I can connect to
><servername>,<portnumber>.
>I've tried many different connection tests (OSQL, udl file, Ent Mngr) and
>instance name doesn't work unless I configure the Client Net Utility to use
a
>specific port number for this instance.
>What I don't understand is whats failing? Is this the server failing to
>resolve inbound traffic for a instance name to the port number used? If so
>what actually performs this name-to-port-number resolution?
>My dev team are particularly technical & when I tell them they have to
>connect using <servername>,<portnumber> they'll want to know why I can't fi
x
>it on the server...
>Thnx
>Steve
Can't connect to Database Engine from Management Studio
I have found several posts on the internet on similar issues, but none
with this specific problem.
I am unable to connect to a Database Engine from SQL Server 2005
Management Studio when connecting from a WAN connection, but I can
connect remotely when connected to the same LAN as the server that
hosts this SQL Server database. Also, I do not have any problems
connecting to the Analysis Services on the same database [and same
server] from the WAN connection.
On the desktop computer there is no Microsoft firewall and on the
server the Microsoft firewall is also disabled.
I have changed the options on the Surface Area Connection to only
remote with TCP/IP and remote with TCP/IP and Named Pipes - this did
not make a difference.
The SQL Server Browser is running.
Obviously remote connections work, because I can connect to the
database engine when I am remote on the same LAN. Also I can connect
to Analysis Services when I am remote on the WAN.
The specific error message is:
Cannot connect to <Server>\<Instance Name>
Additional information:
An error has occured while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified) ( Microsoft SQL Server)
Blake wrote:
> I have found several posts on the internet on similar issues, but none
> with this specific problem.
> I am unable to connect to a Database Engine from SQL Server 2005
> Management Studio when connecting from a WAN connection, but I can
> connect remotely when connected to the same LAN as the server that
> hosts this SQL Server database. Also, I do not have any problems
> connecting to the Analysis Services on the same database [and same
> server] from the WAN connection.
> On the desktop computer there is no Microsoft firewall and on the
> server the Microsoft firewall is also disabled.
> I have changed the options on the Surface Area Connection to only
> remote with TCP/IP and remote with TCP/IP and Named Pipes - this did
> not make a difference.
> The SQL Server Browser is running.
> Obviously remote connections work, because I can connect to the
> database engine when I am remote on the same LAN. Also I can connect
> to Analysis Services when I am remote on the WAN.
> The specific error message is:
> Cannot connect to <Server>\<Instance Name>
> Additional information:
> An error has occured while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under default settings SQL Server does not allow remote
> connections. (provider: SQL Network Interfaces, error: 26 - Error
> Locating Server/Instance Specified) ( Microsoft SQL Server)
>
When connecting over the WAN, are you able to PING the server? Have you
tried connecting by specifying the IP address instead of the hostname?
This sounds like a network issue, possible name resolution.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Tracy McKibben wrote:
> Blake wrote:
> When connecting over the WAN, are you able to PING the server? Have you
> tried connecting by specifying the IP address instead of the hostname?
> This sounds like a network issue, possible name resolution.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Thanks for your comments. Yes I can ping the server, I can connect
with a remote control software package to the same server and can use
Management Studio to connect to SQL Server Analysis Services. I don't
think this is a network [or firewall] issue because I can connect to
the server from every other method, unless there is something specific
network method that is used for Database Engine connections that are
blocked. I have presumed that when I set the connection to be TCP/IP
only it used a TCP connection and when the connection is set to TCP/IP
and Named Pipes it used Named Pipes. I see in the Registered Server
window you can specify the type of connection. This is very
confusing...
|||MS SQL-Server talks on ports when using TCP/IP. So, you need to make sure the
port itself is open. I beleive it uses 1433/tcp for accessing the server
(might be 1434, I can't remember).
Can you telnet to that port? Does Management Studio use a different port?
"Blake" wrote:
> Tracy McKibben wrote:
> Thanks for your comments. Yes I can ping the server, I can connect
> with a remote control software package to the same server and can use
> Management Studio to connect to SQL Server Analysis Services. I don't
> think this is a network [or firewall] issue because I can connect to
> the server from every other method, unless there is something specific
> network method that is used for Database Engine connections that are
> blocked. I have presumed that when I set the connection to be TCP/IP
> only it used a TCP connection and when the connection is set to TCP/IP
> and Named Pipes it used Named Pipes. I see in the Registered Server
> window you can specify the type of connection. This is very
> confusing...
>
|||On Jan 4, 2:48 pm, JayKon <Jay...@.discussions.microsoft.com> wrote:[vbcol=seagreen]
> MS SQL-Server talks on ports when using TCP/IP. So, you need to make sure the
> port itself is open. I beleive it uses 1433/tcp for accessing the server
> (might be 1434, I can't remember).
> Can you telnet to that port? Does Management Studio use a different port?
> "Blake" wrote:
>
>
>
Based on a comment from my customer on this database, I created a SQL
Server installation without using a named instance. Using the default
instance name - I am able to connect via Management Studio from a WAN
connection. I have since deleted the original NAMED instance,
recreated on the same computer as a DEFAULT instance and connecting
with Management Studio is a breeze.
Does anyone know how to report this to Microsoft, this is a but that
should be fixed?
|||Blake wrote:
> Based on a comment from my customer on this database, I created a SQL
> Server installation without using a named instance. Using the default
> instance name - I am able to connect via Management Studio from a WAN
> connection. I have since deleted the original NAMED instance,
> recreated on the same computer as a DEFAULT instance and connecting
> with Management Studio is a breeze.
> Does anyone know how to report this to Microsoft, this is a but that
> should be fixed?
>
If I understand this correctly, you had the following:
Machine named SERVER
SQL instance named SERVER\MYINSTANCE
When you were attempting to connect, what were you specifying as a
server name? To connect to SERVER\MYINSTANCE, you wouldn't specify
SERVER\MYINSTANCE as the server name, unless you have defined that as an
alias in the client configuration tool. You would specify a server name
of "SERVER,1433", replacing 1433 with the port number that the instance
is listening on. The name "SERVER\MYINSTANCE" isn't a valid hostname,
and won't be resolvable by your client tools.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||I had same problem...at leat I think so..
Have you tryed to add server name and IP to your host file?
Because that resolved my problem.
Information about host file
http://accs-net.com/hosts/how_to_use_hosts.html
Juha Sinkkonen
Agenteq Consulting Oy
sinkkonen22(at)hotmail.com
"Blake" wrote:
>
> On Jan 4, 2:48 pm, JayKon <Jay...@.discussions.microsoft.com> wrote:
> Based on a comment from my customer on this database, I created a SQL
> Server installation without using a named instance. Using the default
> instance name - I am able to connect via Management Studio from a WAN
> connection. I have since deleted the original NAMED instance,
> recreated on the same computer as a DEFAULT instance and connecting
> with Management Studio is a breeze.
> Does anyone know how to report this to Microsoft, this is a but that
> should be fixed?
>
with this specific problem.
I am unable to connect to a Database Engine from SQL Server 2005
Management Studio when connecting from a WAN connection, but I can
connect remotely when connected to the same LAN as the server that
hosts this SQL Server database. Also, I do not have any problems
connecting to the Analysis Services on the same database [and same
server] from the WAN connection.
On the desktop computer there is no Microsoft firewall and on the
server the Microsoft firewall is also disabled.
I have changed the options on the Surface Area Connection to only
remote with TCP/IP and remote with TCP/IP and Named Pipes - this did
not make a difference.
The SQL Server Browser is running.
Obviously remote connections work, because I can connect to the
database engine when I am remote on the same LAN. Also I can connect
to Analysis Services when I am remote on the WAN.
The specific error message is:
Cannot connect to <Server>\<Instance Name>
Additional information:
An error has occured while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified) ( Microsoft SQL Server)
Blake wrote:
> I have found several posts on the internet on similar issues, but none
> with this specific problem.
> I am unable to connect to a Database Engine from SQL Server 2005
> Management Studio when connecting from a WAN connection, but I can
> connect remotely when connected to the same LAN as the server that
> hosts this SQL Server database. Also, I do not have any problems
> connecting to the Analysis Services on the same database [and same
> server] from the WAN connection.
> On the desktop computer there is no Microsoft firewall and on the
> server the Microsoft firewall is also disabled.
> I have changed the options on the Surface Area Connection to only
> remote with TCP/IP and remote with TCP/IP and Named Pipes - this did
> not make a difference.
> The SQL Server Browser is running.
> Obviously remote connections work, because I can connect to the
> database engine when I am remote on the same LAN. Also I can connect
> to Analysis Services when I am remote on the WAN.
> The specific error message is:
> Cannot connect to <Server>\<Instance Name>
> Additional information:
> An error has occured while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under default settings SQL Server does not allow remote
> connections. (provider: SQL Network Interfaces, error: 26 - Error
> Locating Server/Instance Specified) ( Microsoft SQL Server)
>
When connecting over the WAN, are you able to PING the server? Have you
tried connecting by specifying the IP address instead of the hostname?
This sounds like a network issue, possible name resolution.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Tracy McKibben wrote:
> Blake wrote:
> When connecting over the WAN, are you able to PING the server? Have you
> tried connecting by specifying the IP address instead of the hostname?
> This sounds like a network issue, possible name resolution.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Thanks for your comments. Yes I can ping the server, I can connect
with a remote control software package to the same server and can use
Management Studio to connect to SQL Server Analysis Services. I don't
think this is a network [or firewall] issue because I can connect to
the server from every other method, unless there is something specific
network method that is used for Database Engine connections that are
blocked. I have presumed that when I set the connection to be TCP/IP
only it used a TCP connection and when the connection is set to TCP/IP
and Named Pipes it used Named Pipes. I see in the Registered Server
window you can specify the type of connection. This is very
confusing...
|||MS SQL-Server talks on ports when using TCP/IP. So, you need to make sure the
port itself is open. I beleive it uses 1433/tcp for accessing the server
(might be 1434, I can't remember).
Can you telnet to that port? Does Management Studio use a different port?
"Blake" wrote:
> Tracy McKibben wrote:
> Thanks for your comments. Yes I can ping the server, I can connect
> with a remote control software package to the same server and can use
> Management Studio to connect to SQL Server Analysis Services. I don't
> think this is a network [or firewall] issue because I can connect to
> the server from every other method, unless there is something specific
> network method that is used for Database Engine connections that are
> blocked. I have presumed that when I set the connection to be TCP/IP
> only it used a TCP connection and when the connection is set to TCP/IP
> and Named Pipes it used Named Pipes. I see in the Registered Server
> window you can specify the type of connection. This is very
> confusing...
>
|||On Jan 4, 2:48 pm, JayKon <Jay...@.discussions.microsoft.com> wrote:[vbcol=seagreen]
> MS SQL-Server talks on ports when using TCP/IP. So, you need to make sure the
> port itself is open. I beleive it uses 1433/tcp for accessing the server
> (might be 1434, I can't remember).
> Can you telnet to that port? Does Management Studio use a different port?
> "Blake" wrote:
>
>
>
Based on a comment from my customer on this database, I created a SQL
Server installation without using a named instance. Using the default
instance name - I am able to connect via Management Studio from a WAN
connection. I have since deleted the original NAMED instance,
recreated on the same computer as a DEFAULT instance and connecting
with Management Studio is a breeze.
Does anyone know how to report this to Microsoft, this is a but that
should be fixed?
|||Blake wrote:
> Based on a comment from my customer on this database, I created a SQL
> Server installation without using a named instance. Using the default
> instance name - I am able to connect via Management Studio from a WAN
> connection. I have since deleted the original NAMED instance,
> recreated on the same computer as a DEFAULT instance and connecting
> with Management Studio is a breeze.
> Does anyone know how to report this to Microsoft, this is a but that
> should be fixed?
>
If I understand this correctly, you had the following:
Machine named SERVER
SQL instance named SERVER\MYINSTANCE
When you were attempting to connect, what were you specifying as a
server name? To connect to SERVER\MYINSTANCE, you wouldn't specify
SERVER\MYINSTANCE as the server name, unless you have defined that as an
alias in the client configuration tool. You would specify a server name
of "SERVER,1433", replacing 1433 with the port number that the instance
is listening on. The name "SERVER\MYINSTANCE" isn't a valid hostname,
and won't be resolvable by your client tools.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||I had same problem...at leat I think so..
Have you tryed to add server name and IP to your host file?
Because that resolved my problem.
Information about host file
http://accs-net.com/hosts/how_to_use_hosts.html
Juha Sinkkonen
Agenteq Consulting Oy
sinkkonen22(at)hotmail.com
"Blake" wrote:
>
> On Jan 4, 2:48 pm, JayKon <Jay...@.discussions.microsoft.com> wrote:
> Based on a comment from my customer on this database, I created a SQL
> Server installation without using a named instance. Using the default
> instance name - I am able to connect via Management Studio from a WAN
> connection. I have since deleted the original NAMED instance,
> recreated on the same computer as a DEFAULT instance and connecting
> with Management Studio is a breeze.
> Does anyone know how to report this to Microsoft, this is a but that
> should be fixed?
>
Can't connect to Database Engine from Management Studio
I have found several posts on the internet on similar issues, but none
with this specific problem.
I am unable to connect to a Database Engine from SQL Server 2005
Management Studio when connecting from a WAN connection, but I can
connect remotely when connected to the same LAN as the server that
hosts this SQL Server database. Also, I do not have any problems
connecting to the Analysis Services on the same database [and same
server] from the WAN connection.
On the desktop computer there is no Microsoft firewall and on the
server the Microsoft firewall is also disabled.
I have changed the options on the Surface Area Connection to only
remote with TCP/IP and remote with TCP/IP and Named Pipes - this did
not make a difference.
The SQL Server Browser is running.
Obviously remote connections work, because I can connect to the
database engine when I am remote on the same LAN. Also I can connect
to Analysis Services when I am remote on the WAN.
The specific error message is:
Cannot connect to <Server>\<Instance Name>
Additional information:
An error has occured while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified) ( Microsoft SQL Server)Blake wrote:
> I have found several posts on the internet on similar issues, but none
> with this specific problem.
> I am unable to connect to a Database Engine from SQL Server 2005
> Management Studio when connecting from a WAN connection, but I can
> connect remotely when connected to the same LAN as the server that
> hosts this SQL Server database. Also, I do not have any problems
> connecting to the Analysis Services on the same database [and same
> server] from the WAN connection.
> On the desktop computer there is no Microsoft firewall and on the
> server the Microsoft firewall is also disabled.
> I have changed the options on the Surface Area Connection to only
> remote with TCP/IP and remote with TCP/IP and Named Pipes - this did
> not make a difference.
> The SQL Server Browser is running.
> Obviously remote connections work, because I can connect to the
> database engine when I am remote on the same LAN. Also I can connect
> to Analysis Services when I am remote on the WAN.
> The specific error message is:
> Cannot connect to <Server>\<Instance Name>
> Additional information:
> An error has occured while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under default settings SQL Server does not allow remote
> connections. (provider: SQL Network Interfaces, error: 26 - Error
> Locating Server/Instance Specified) ( Microsoft SQL Server)
>
When connecting over the WAN, are you able to PING the server? Have you
tried connecting by specifying the IP address instead of the hostname?
This sounds like a network issue, possible name resolution.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy McKibben wrote:
> Blake wrote:
> When connecting over the WAN, are you able to PING the server? Have you
> tried connecting by specifying the IP address instead of the hostname?
> This sounds like a network issue, possible name resolution.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Thanks for your comments. Yes I can ping the server, I can connect
with a remote control software package to the same server and can use
Management Studio to connect to SQL Server Analysis Services. I don't
think this is a network [or firewall] issue because I can connect to
the server from every other method, unless there is something specific
network method that is used for Database Engine connections that are
blocked. I have presumed that when I set the connection to be TCP/IP
only it used a TCP connection and when the connection is set to TCP/IP
and Named Pipes it used Named Pipes. I see in the Registered Server
window you can specify the type of connection. This is very
confusing...|||MS SQL-Server talks on ports when using TCP/IP. So, you need to make sure th
e
port itself is open. I beleive it uses 1433/tcp for accessing the server
(might be 1434, I can't remember).
Can you telnet to that port? Does Management Studio use a different port?
"Blake" wrote:
> Tracy McKibben wrote:
> Thanks for your comments. Yes I can ping the server, I can connect
> with a remote control software package to the same server and can use
> Management Studio to connect to SQL Server Analysis Services. I don't
> think this is a network [or firewall] issue because I can connect to
> the server from every other method, unless there is something specific
> network method that is used for Database Engine connections that are
> blocked. I have presumed that when I set the connection to be TCP/IP
> only it used a TCP connection and when the connection is set to TCP/IP
> and Named Pipes it used Named Pipes. I see in the Registered Server
> window you can specify the type of connection. This is very
> confusing...
>|||On Jan 4, 2:48 pm, JayKon <Jay...@.discussions.microsoft.com> wrote:[vbcol=seagreen]
> MS SQL-Server talks on ports when using TCP/IP. So, you need to make sure
the
> port itself is open. I beleive it uses 1433/tcp for accessing the server
> (might be 1434, I can't remember).
> Can you telnet to that port? Does Management Studio use a different port?
> "Blake" wrote:
>
>
>
>
>
>
>
Based on a comment from my customer on this database, I created a SQL
Server installation without using a named instance. Using the default
instance name - I am able to connect via Management Studio from a WAN
connection. I have since deleted the original NAMED instance,
recreated on the same computer as a DEFAULT instance and connecting
with Management Studio is a breeze.
Does anyone know how to report this to Microsoft, this is a but that
should be fixed?|||Blake wrote:
> Based on a comment from my customer on this database, I created a SQL
> Server installation without using a named instance. Using the default
> instance name - I am able to connect via Management Studio from a WAN
> connection. I have since deleted the original NAMED instance,
> recreated on the same computer as a DEFAULT instance and connecting
> with Management Studio is a breeze.
> Does anyone know how to report this to Microsoft, this is a but that
> should be fixed?
>
If I understand this correctly, you had the following:
Machine named SERVER
SQL instance named SERVER\MYINSTANCE
When you were attempting to connect, what were you specifying as a
server name? To connect to SERVER\MYINSTANCE, you wouldn't specify
SERVER\MYINSTANCE as the server name, unless you have defined that as an
alias in the client configuration tool. You would specify a server name
of "SERVER,1433", replacing 1433 with the port number that the instance
is listening on. The name "SERVER\MYINSTANCE" isn't a valid hostname,
and won't be resolvable by your client tools.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I had same problem...at leat I think so..
Have you tryed to add server name and IP to your host file?
Because that resolved my problem.
Information about host file
http://accs-net.com/hosts/how_to_use_hosts.html
Juha Sinkkonen
Agenteq Consulting Oy
sinkkonen22(at)hotmail.com
"Blake" wrote:
>
> On Jan 4, 2:48 pm, JayKon <Jay...@.discussions.microsoft.com> wrote:
> Based on a comment from my customer on this database, I created a SQL
> Server installation without using a named instance. Using the default
> instance name - I am able to connect via Management Studio from a WAN
> connection. I have since deleted the original NAMED instance,
> recreated on the same computer as a DEFAULT instance and connecting
> with Management Studio is a breeze.
> Does anyone know how to report this to Microsoft, this is a but that
> should be fixed?
>
with this specific problem.
I am unable to connect to a Database Engine from SQL Server 2005
Management Studio when connecting from a WAN connection, but I can
connect remotely when connected to the same LAN as the server that
hosts this SQL Server database. Also, I do not have any problems
connecting to the Analysis Services on the same database [and same
server] from the WAN connection.
On the desktop computer there is no Microsoft firewall and on the
server the Microsoft firewall is also disabled.
I have changed the options on the Surface Area Connection to only
remote with TCP/IP and remote with TCP/IP and Named Pipes - this did
not make a difference.
The SQL Server Browser is running.
Obviously remote connections work, because I can connect to the
database engine when I am remote on the same LAN. Also I can connect
to Analysis Services when I am remote on the WAN.
The specific error message is:
Cannot connect to <Server>\<Instance Name>
Additional information:
An error has occured while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified) ( Microsoft SQL Server)Blake wrote:
> I have found several posts on the internet on similar issues, but none
> with this specific problem.
> I am unable to connect to a Database Engine from SQL Server 2005
> Management Studio when connecting from a WAN connection, but I can
> connect remotely when connected to the same LAN as the server that
> hosts this SQL Server database. Also, I do not have any problems
> connecting to the Analysis Services on the same database [and same
> server] from the WAN connection.
> On the desktop computer there is no Microsoft firewall and on the
> server the Microsoft firewall is also disabled.
> I have changed the options on the Surface Area Connection to only
> remote with TCP/IP and remote with TCP/IP and Named Pipes - this did
> not make a difference.
> The SQL Server Browser is running.
> Obviously remote connections work, because I can connect to the
> database engine when I am remote on the same LAN. Also I can connect
> to Analysis Services when I am remote on the WAN.
> The specific error message is:
> Cannot connect to <Server>\<Instance Name>
> Additional information:
> An error has occured while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under default settings SQL Server does not allow remote
> connections. (provider: SQL Network Interfaces, error: 26 - Error
> Locating Server/Instance Specified) ( Microsoft SQL Server)
>
When connecting over the WAN, are you able to PING the server? Have you
tried connecting by specifying the IP address instead of the hostname?
This sounds like a network issue, possible name resolution.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy McKibben wrote:
> Blake wrote:
> When connecting over the WAN, are you able to PING the server? Have you
> tried connecting by specifying the IP address instead of the hostname?
> This sounds like a network issue, possible name resolution.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Thanks for your comments. Yes I can ping the server, I can connect
with a remote control software package to the same server and can use
Management Studio to connect to SQL Server Analysis Services. I don't
think this is a network [or firewall] issue because I can connect to
the server from every other method, unless there is something specific
network method that is used for Database Engine connections that are
blocked. I have presumed that when I set the connection to be TCP/IP
only it used a TCP connection and when the connection is set to TCP/IP
and Named Pipes it used Named Pipes. I see in the Registered Server
window you can specify the type of connection. This is very
confusing...|||MS SQL-Server talks on ports when using TCP/IP. So, you need to make sure th
e
port itself is open. I beleive it uses 1433/tcp for accessing the server
(might be 1434, I can't remember).
Can you telnet to that port? Does Management Studio use a different port?
"Blake" wrote:
> Tracy McKibben wrote:
> Thanks for your comments. Yes I can ping the server, I can connect
> with a remote control software package to the same server and can use
> Management Studio to connect to SQL Server Analysis Services. I don't
> think this is a network [or firewall] issue because I can connect to
> the server from every other method, unless there is something specific
> network method that is used for Database Engine connections that are
> blocked. I have presumed that when I set the connection to be TCP/IP
> only it used a TCP connection and when the connection is set to TCP/IP
> and Named Pipes it used Named Pipes. I see in the Registered Server
> window you can specify the type of connection. This is very
> confusing...
>|||On Jan 4, 2:48 pm, JayKon <Jay...@.discussions.microsoft.com> wrote:[vbcol=seagreen]
> MS SQL-Server talks on ports when using TCP/IP. So, you need to make sure
the
> port itself is open. I beleive it uses 1433/tcp for accessing the server
> (might be 1434, I can't remember).
> Can you telnet to that port? Does Management Studio use a different port?
> "Blake" wrote:
>
>
>
>
>
>
>
Based on a comment from my customer on this database, I created a SQL
Server installation without using a named instance. Using the default
instance name - I am able to connect via Management Studio from a WAN
connection. I have since deleted the original NAMED instance,
recreated on the same computer as a DEFAULT instance and connecting
with Management Studio is a breeze.
Does anyone know how to report this to Microsoft, this is a but that
should be fixed?|||Blake wrote:
> Based on a comment from my customer on this database, I created a SQL
> Server installation without using a named instance. Using the default
> instance name - I am able to connect via Management Studio from a WAN
> connection. I have since deleted the original NAMED instance,
> recreated on the same computer as a DEFAULT instance and connecting
> with Management Studio is a breeze.
> Does anyone know how to report this to Microsoft, this is a but that
> should be fixed?
>
If I understand this correctly, you had the following:
Machine named SERVER
SQL instance named SERVER\MYINSTANCE
When you were attempting to connect, what were you specifying as a
server name? To connect to SERVER\MYINSTANCE, you wouldn't specify
SERVER\MYINSTANCE as the server name, unless you have defined that as an
alias in the client configuration tool. You would specify a server name
of "SERVER,1433", replacing 1433 with the port number that the instance
is listening on. The name "SERVER\MYINSTANCE" isn't a valid hostname,
and won't be resolvable by your client tools.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I had same problem...at leat I think so..
Have you tryed to add server name and IP to your host file?
Because that resolved my problem.
Information about host file
http://accs-net.com/hosts/how_to_use_hosts.html
Juha Sinkkonen
Agenteq Consulting Oy
sinkkonen22(at)hotmail.com
"Blake" wrote:
>
> On Jan 4, 2:48 pm, JayKon <Jay...@.discussions.microsoft.com> wrote:
> Based on a comment from my customer on this database, I created a SQL
> Server installation without using a named instance. Using the default
> instance name - I am able to connect via Management Studio from a WAN
> connection. I have since deleted the original NAMED instance,
> recreated on the same computer as a DEFAULT instance and connecting
> with Management Studio is a breeze.
> Does anyone know how to report this to Microsoft, this is a but that
> should be fixed?
>
Can't connect to Database Engine from Management Studio
I have found several posts on the internet on similar issues, but none
with this specific problem.
I am unable to connect to a Database Engine from SQL Server 2005
Management Studio when connecting from a WAN connection, but I can
connect remotely when connected to the same LAN as the server that
hosts this SQL Server database. Also, I do not have any problems
connecting to the Analysis Services on the same database [and same
server] from the WAN connection.
On the desktop computer there is no Microsoft firewall and on the
server the Microsoft firewall is also disabled.
I have changed the options on the Surface Area Connection to only
remote with TCP/IP and remote with TCP/IP and Named Pipes - this did
not make a difference.
The SQL Server Browser is running.
Obviously remote connections work, because I can connect to the
database engine when I am remote on the same LAN. Also I can connect
to Analysis Services when I am remote on the WAN.
The specific error message is:
Cannot connect to <Server>\<Instance Name>
Additional information:
An error has occured while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified) ( Microsoft SQL Server)Blake wrote:
> I have found several posts on the internet on similar issues, but none
> with this specific problem.
> I am unable to connect to a Database Engine from SQL Server 2005
> Management Studio when connecting from a WAN connection, but I can
> connect remotely when connected to the same LAN as the server that
> hosts this SQL Server database. Also, I do not have any problems
> connecting to the Analysis Services on the same database [and same
> server] from the WAN connection.
> On the desktop computer there is no Microsoft firewall and on the
> server the Microsoft firewall is also disabled.
> I have changed the options on the Surface Area Connection to only
> remote with TCP/IP and remote with TCP/IP and Named Pipes - this did
> not make a difference.
> The SQL Server Browser is running.
> Obviously remote connections work, because I can connect to the
> database engine when I am remote on the same LAN. Also I can connect
> to Analysis Services when I am remote on the WAN.
> The specific error message is:
> Cannot connect to <Server>\<Instance Name>
> Additional information:
> An error has occured while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under default settings SQL Server does not allow remote
> connections. (provider: SQL Network Interfaces, error: 26 - Error
> Locating Server/Instance Specified) ( Microsoft SQL Server)
>
When connecting over the WAN, are you able to PING the server? Have you
tried connecting by specifying the IP address instead of the hostname?
This sounds like a network issue, possible name resolution.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy McKibben wrote:
> Blake wrote:
> > I have found several posts on the internet on similar issues, but none
> > with this specific problem.
> >
> > I am unable to connect to a Database Engine from SQL Server 2005
> > Management Studio when connecting from a WAN connection, but I can
> > connect remotely when connected to the same LAN as the server that
> > hosts this SQL Server database. Also, I do not have any problems
> > connecting to the Analysis Services on the same database [and same
> > server] from the WAN connection.
> > On the desktop computer there is no Microsoft firewall and on the
> > server the Microsoft firewall is also disabled.
> > I have changed the options on the Surface Area Connection to only
> > remote with TCP/IP and remote with TCP/IP and Named Pipes - this did
> > not make a difference.
> > The SQL Server Browser is running.
> >
> > Obviously remote connections work, because I can connect to the
> > database engine when I am remote on the same LAN. Also I can connect
> > to Analysis Services when I am remote on the WAN.
> >
> > The specific error message is:
> > Cannot connect to <Server>\<Instance Name>
> > Additional information:
> > An error has occured while establishing a connection to the server.
> > When connecting to SQL Server 2005, this failure may be caused by the
> > fact that under default settings SQL Server does not allow remote
> > connections. (provider: SQL Network Interfaces, error: 26 - Error
> > Locating Server/Instance Specified) ( Microsoft SQL Server)
> >
> When connecting over the WAN, are you able to PING the server? Have you
> tried connecting by specifying the IP address instead of the hostname?
> This sounds like a network issue, possible name resolution.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Thanks for your comments. Yes I can ping the server, I can connect
with a remote control software package to the same server and can use
Management Studio to connect to SQL Server Analysis Services. I don't
think this is a network [or firewall] issue because I can connect to
the server from every other method, unless there is something specific
network method that is used for Database Engine connections that are
blocked. I have presumed that when I set the connection to be TCP/IP
only it used a TCP connection and when the connection is set to TCP/IP
and Named Pipes it used Named Pipes. I see in the Registered Server
window you can specify the type of connection. This is very
confusing...|||On Jan 4, 2:48 pm, JayKon <Jay...@.discussions.microsoft.com> wrote:
> MS SQL-Server talks on ports when using TCP/IP. So, you need to make sure the
> port itself is open. I beleive it uses 1433/tcp for accessing the server
> (might be 1434, I can't remember).
> Can you telnet to that port? Does Management Studio use a different port?
> "Blake" wrote:
> > Tracy McKibben wrote:
> > > Blake wrote:
> > > > I have found several posts on the internet on similar issues, but none
> > > > with this specific problem.
> > > > I am unable to connect to a Database Engine from SQL Server 2005
> > > > Management Studio when connecting from a WAN connection, but I can
> > > > connect remotely when connected to the same LAN as the server that
> > > > hosts this SQL Server database. Also, I do not have any problems
> > > > connecting to the Analysis Services on the same database [and same
> > > > server] from the WAN connection.
> > > > On the desktop computer there is no Microsoft firewall and on the
> > > > server the Microsoft firewall is also disabled.
> > > > I have changed the options on the Surface Area Connection to only
> > > > remote with TCP/IP and remote with TCP/IP and Named Pipes - this did
> > > > not make a difference.
> > > > The SQL Server Browser is running.
> > > > Obviously remote connections work, because I can connect to the
> > > > database engine when I am remote on the same LAN. Also I can connect
> > > > to Analysis Services when I am remote on the WAN.
> > > > The specific error message is:
> > > > Cannot connect to <Server>\<Instance Name>
> > > > Additional information:
> > > > An error has occured while establishing a connection to the server.
> > > > When connecting to SQL Server 2005, this failure may be caused by the
> > > > fact that under default settings SQL Server does not allow remote
> > > > connections. (provider: SQL Network Interfaces, error: 26 - Error
> > > > Locating Server/Instance Specified) ( Microsoft SQL Server)
> > > When connecting over the WAN, are you able to PING the server? Have you
> > > tried connecting by specifying the IP address instead of the hostname?
> > > This sounds like a network issue, possible name resolution.
> > > --
> > > Tracy McKibben
> > > MCDBA
> > >http://www.realsqlguy.com
> > Thanks for your comments. Yes I can ping the server, I can connect
> > with a remote control software package to the same server and can use
> > Management Studio to connect to SQL Server Analysis Services. I don't
> > think this is a network [or firewall] issue because I can connect to
> > the server from every other method, unless there is something specific
> > network method that is used for Database Engine connections that are
> > blocked. I have presumed that when I set the connection to be TCP/IP
> > only it used a TCP connection and when the connection is set to TCP/IP
> > and Named Pipes it used Named Pipes. I see in the Registered Server
> > window you can specify the type of connection. This is very
> > confusing...
Based on a comment from my customer on this database, I created a SQL
Server installation without using a named instance. Using the default
instance name - I am able to connect via Management Studio from a WAN
connection. I have since deleted the original NAMED instance,
recreated on the same computer as a DEFAULT instance and connecting
with Management Studio is a breeze.
Does anyone know how to report this to Microsoft, this is a but that
should be fixed?|||Blake wrote:
> Based on a comment from my customer on this database, I created a SQL
> Server installation without using a named instance. Using the default
> instance name - I am able to connect via Management Studio from a WAN
> connection. I have since deleted the original NAMED instance,
> recreated on the same computer as a DEFAULT instance and connecting
> with Management Studio is a breeze.
> Does anyone know how to report this to Microsoft, this is a but that
> should be fixed?
>
If I understand this correctly, you had the following:
Machine named SERVER
SQL instance named SERVER\MYINSTANCE
When you were attempting to connect, what were you specifying as a
server name? To connect to SERVER\MYINSTANCE, you wouldn't specify
SERVER\MYINSTANCE as the server name, unless you have defined that as an
alias in the client configuration tool. You would specify a server name
of "SERVER,1433", replacing 1433 with the port number that the instance
is listening on. The name "SERVER\MYINSTANCE" isn't a valid hostname,
and won't be resolvable by your client tools.
--
Tracy McKibben
MCDBA
http://www.realsqlguy.com
with this specific problem.
I am unable to connect to a Database Engine from SQL Server 2005
Management Studio when connecting from a WAN connection, but I can
connect remotely when connected to the same LAN as the server that
hosts this SQL Server database. Also, I do not have any problems
connecting to the Analysis Services on the same database [and same
server] from the WAN connection.
On the desktop computer there is no Microsoft firewall and on the
server the Microsoft firewall is also disabled.
I have changed the options on the Surface Area Connection to only
remote with TCP/IP and remote with TCP/IP and Named Pipes - this did
not make a difference.
The SQL Server Browser is running.
Obviously remote connections work, because I can connect to the
database engine when I am remote on the same LAN. Also I can connect
to Analysis Services when I am remote on the WAN.
The specific error message is:
Cannot connect to <Server>\<Instance Name>
Additional information:
An error has occured while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified) ( Microsoft SQL Server)Blake wrote:
> I have found several posts on the internet on similar issues, but none
> with this specific problem.
> I am unable to connect to a Database Engine from SQL Server 2005
> Management Studio when connecting from a WAN connection, but I can
> connect remotely when connected to the same LAN as the server that
> hosts this SQL Server database. Also, I do not have any problems
> connecting to the Analysis Services on the same database [and same
> server] from the WAN connection.
> On the desktop computer there is no Microsoft firewall and on the
> server the Microsoft firewall is also disabled.
> I have changed the options on the Surface Area Connection to only
> remote with TCP/IP and remote with TCP/IP and Named Pipes - this did
> not make a difference.
> The SQL Server Browser is running.
> Obviously remote connections work, because I can connect to the
> database engine when I am remote on the same LAN. Also I can connect
> to Analysis Services when I am remote on the WAN.
> The specific error message is:
> Cannot connect to <Server>\<Instance Name>
> Additional information:
> An error has occured while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under default settings SQL Server does not allow remote
> connections. (provider: SQL Network Interfaces, error: 26 - Error
> Locating Server/Instance Specified) ( Microsoft SQL Server)
>
When connecting over the WAN, are you able to PING the server? Have you
tried connecting by specifying the IP address instead of the hostname?
This sounds like a network issue, possible name resolution.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy McKibben wrote:
> Blake wrote:
> > I have found several posts on the internet on similar issues, but none
> > with this specific problem.
> >
> > I am unable to connect to a Database Engine from SQL Server 2005
> > Management Studio when connecting from a WAN connection, but I can
> > connect remotely when connected to the same LAN as the server that
> > hosts this SQL Server database. Also, I do not have any problems
> > connecting to the Analysis Services on the same database [and same
> > server] from the WAN connection.
> > On the desktop computer there is no Microsoft firewall and on the
> > server the Microsoft firewall is also disabled.
> > I have changed the options on the Surface Area Connection to only
> > remote with TCP/IP and remote with TCP/IP and Named Pipes - this did
> > not make a difference.
> > The SQL Server Browser is running.
> >
> > Obviously remote connections work, because I can connect to the
> > database engine when I am remote on the same LAN. Also I can connect
> > to Analysis Services when I am remote on the WAN.
> >
> > The specific error message is:
> > Cannot connect to <Server>\<Instance Name>
> > Additional information:
> > An error has occured while establishing a connection to the server.
> > When connecting to SQL Server 2005, this failure may be caused by the
> > fact that under default settings SQL Server does not allow remote
> > connections. (provider: SQL Network Interfaces, error: 26 - Error
> > Locating Server/Instance Specified) ( Microsoft SQL Server)
> >
> When connecting over the WAN, are you able to PING the server? Have you
> tried connecting by specifying the IP address instead of the hostname?
> This sounds like a network issue, possible name resolution.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Thanks for your comments. Yes I can ping the server, I can connect
with a remote control software package to the same server and can use
Management Studio to connect to SQL Server Analysis Services. I don't
think this is a network [or firewall] issue because I can connect to
the server from every other method, unless there is something specific
network method that is used for Database Engine connections that are
blocked. I have presumed that when I set the connection to be TCP/IP
only it used a TCP connection and when the connection is set to TCP/IP
and Named Pipes it used Named Pipes. I see in the Registered Server
window you can specify the type of connection. This is very
confusing...|||On Jan 4, 2:48 pm, JayKon <Jay...@.discussions.microsoft.com> wrote:
> MS SQL-Server talks on ports when using TCP/IP. So, you need to make sure the
> port itself is open. I beleive it uses 1433/tcp for accessing the server
> (might be 1434, I can't remember).
> Can you telnet to that port? Does Management Studio use a different port?
> "Blake" wrote:
> > Tracy McKibben wrote:
> > > Blake wrote:
> > > > I have found several posts on the internet on similar issues, but none
> > > > with this specific problem.
> > > > I am unable to connect to a Database Engine from SQL Server 2005
> > > > Management Studio when connecting from a WAN connection, but I can
> > > > connect remotely when connected to the same LAN as the server that
> > > > hosts this SQL Server database. Also, I do not have any problems
> > > > connecting to the Analysis Services on the same database [and same
> > > > server] from the WAN connection.
> > > > On the desktop computer there is no Microsoft firewall and on the
> > > > server the Microsoft firewall is also disabled.
> > > > I have changed the options on the Surface Area Connection to only
> > > > remote with TCP/IP and remote with TCP/IP and Named Pipes - this did
> > > > not make a difference.
> > > > The SQL Server Browser is running.
> > > > Obviously remote connections work, because I can connect to the
> > > > database engine when I am remote on the same LAN. Also I can connect
> > > > to Analysis Services when I am remote on the WAN.
> > > > The specific error message is:
> > > > Cannot connect to <Server>\<Instance Name>
> > > > Additional information:
> > > > An error has occured while establishing a connection to the server.
> > > > When connecting to SQL Server 2005, this failure may be caused by the
> > > > fact that under default settings SQL Server does not allow remote
> > > > connections. (provider: SQL Network Interfaces, error: 26 - Error
> > > > Locating Server/Instance Specified) ( Microsoft SQL Server)
> > > When connecting over the WAN, are you able to PING the server? Have you
> > > tried connecting by specifying the IP address instead of the hostname?
> > > This sounds like a network issue, possible name resolution.
> > > --
> > > Tracy McKibben
> > > MCDBA
> > >http://www.realsqlguy.com
> > Thanks for your comments. Yes I can ping the server, I can connect
> > with a remote control software package to the same server and can use
> > Management Studio to connect to SQL Server Analysis Services. I don't
> > think this is a network [or firewall] issue because I can connect to
> > the server from every other method, unless there is something specific
> > network method that is used for Database Engine connections that are
> > blocked. I have presumed that when I set the connection to be TCP/IP
> > only it used a TCP connection and when the connection is set to TCP/IP
> > and Named Pipes it used Named Pipes. I see in the Registered Server
> > window you can specify the type of connection. This is very
> > confusing...
Based on a comment from my customer on this database, I created a SQL
Server installation without using a named instance. Using the default
instance name - I am able to connect via Management Studio from a WAN
connection. I have since deleted the original NAMED instance,
recreated on the same computer as a DEFAULT instance and connecting
with Management Studio is a breeze.
Does anyone know how to report this to Microsoft, this is a but that
should be fixed?|||Blake wrote:
> Based on a comment from my customer on this database, I created a SQL
> Server installation without using a named instance. Using the default
> instance name - I am able to connect via Management Studio from a WAN
> connection. I have since deleted the original NAMED instance,
> recreated on the same computer as a DEFAULT instance and connecting
> with Management Studio is a breeze.
> Does anyone know how to report this to Microsoft, this is a but that
> should be fixed?
>
If I understand this correctly, you had the following:
Machine named SERVER
SQL instance named SERVER\MYINSTANCE
When you were attempting to connect, what were you specifying as a
server name? To connect to SERVER\MYINSTANCE, you wouldn't specify
SERVER\MYINSTANCE as the server name, unless you have defined that as an
alias in the client configuration tool. You would specify a server name
of "SERVER,1433", replacing 1433 with the port number that the instance
is listening on. The name "SERVER\MYINSTANCE" isn't a valid hostname,
and won't be resolvable by your client tools.
--
Tracy McKibben
MCDBA
http://www.realsqlguy.com
Subscribe to:
Posts (Atom)