Hi,
I have a very confusing issue.
I am attempting to connect to a SQL2000 server using Named Pipes and a
DNS Alias without success. I get the sql server does not exist or
access is denied error. I can successfully connect using TCPIP
sockets however.
If I connect to the server using it's own servername I can connect
using Named Pipes or TCPIP sockets.
Any ideas?
Named pipes does not use DNS so a DNS alias will not work with named pipes.
Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS the
connection works.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||rboyd@.onlinemicrosoft.com (Rand Boyd [MSFT]) wrote in message news:<xEV$7$j0EHA.3152@.cpmsftngxa10.phx.gbl>...
> Named pipes does not use DNS so a DNS alias will not work with named pipes.
> Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS the
> connection works.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
Rand
I now have this working after using the DisableStrictNameChecking fix.
I can now use the DNA Alias for the SQL server ver named pipes.
Showing posts with label confusing. Show all posts
Showing posts with label confusing. Show all posts
Tuesday, February 14, 2012
Connecting to SQL2000 using DNS Alias/Named Pipes
Hi,
I have a very confusing issue.
I am attempting to connect to a SQL2000 server using Named Pipes and a
DNS Alias without success. I get the sql server does not exist or
access is denied error. I can successfully connect using TCPIP
sockets however.
If I connect to the server using it's own servername I can connect
using Named Pipes or TCPIP sockets.
Any ideas'Named pipes does not use DNS so a DNS alias will not work with named pipes.
Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS the
connection works.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||rboyd@.onlinemicrosoft.com (Rand Boyd [MSFT]) wrote in message news:<xEV$7$j0EHA.3152@.cpmsftngxa10.phx.gbl>...
> Named pipes does not use DNS so a DNS alias will not work with named pipes.
> Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS the
> connection works.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
Rand
I now have this working after using the DisableStrictNameChecking fix.
I can now use the DNA Alias for the SQL server ver named pipes.
I have a very confusing issue.
I am attempting to connect to a SQL2000 server using Named Pipes and a
DNS Alias without success. I get the sql server does not exist or
access is denied error. I can successfully connect using TCPIP
sockets however.
If I connect to the server using it's own servername I can connect
using Named Pipes or TCPIP sockets.
Any ideas'Named pipes does not use DNS so a DNS alias will not work with named pipes.
Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS the
connection works.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||rboyd@.onlinemicrosoft.com (Rand Boyd [MSFT]) wrote in message news:<xEV$7$j0EHA.3152@.cpmsftngxa10.phx.gbl>...
> Named pipes does not use DNS so a DNS alias will not work with named pipes.
> Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS the
> connection works.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
Rand
I now have this working after using the DisableStrictNameChecking fix.
I can now use the DNA Alias for the SQL server ver named pipes.
Connecting to SQL2000 using DNS Alias/Named Pipes
Hi,
I have a very confusing issue.
I am attempting to connect to a SQL2000 server using Named Pipes and a
DNS Alias without success. I get the sql server does not exist or
access is denied error. I can successfully connect using TCPIP
sockets however.
If I connect to the server using it's own servername I can connect
using Named Pipes or TCPIP sockets.
Any ideas'Named pipes does not use DNS so a DNS alias will not work with named pipes.
Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS the
connection works.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||rboyd@.onlinemicrosoft.com (Rand Boyd [MSFT]) wrote in message news:<xEV$7$j0EHA.3152@.cpm
sftngxa10.phx.gbl>...
> Named pipes does not use DNS so a DNS alias will not work with named pipes
.
> Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS th
e
> connection works.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
Rand
I now have this working after using the DisableStrictNameChecking fix.
I can now use the DNA Alias for the SQL server ver named pipes.
I have a very confusing issue.
I am attempting to connect to a SQL2000 server using Named Pipes and a
DNS Alias without success. I get the sql server does not exist or
access is denied error. I can successfully connect using TCPIP
sockets however.
If I connect to the server using it's own servername I can connect
using Named Pipes or TCPIP sockets.
Any ideas'Named pipes does not use DNS so a DNS alias will not work with named pipes.
Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS the
connection works.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||rboyd@.onlinemicrosoft.com (Rand Boyd [MSFT]) wrote in message news:<xEV$7$j0EHA.3152@.cpm
sftngxa10.phx.gbl>...
> Named pipes does not use DNS so a DNS alias will not work with named pipes
.
> Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS th
e
> connection works.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
Rand
I now have this working after using the DisableStrictNameChecking fix.
I can now use the DNA Alias for the SQL server ver named pipes.
Subscribe to:
Posts (Atom)