Showing posts with label dns. Show all posts
Showing posts with label dns. Show all posts

Tuesday, February 14, 2012

Connecting to SQLServer 2000 using DNS alias

Hi all,

I have to move my SQlServer 2000 instance from one server
'actual_server' to another server 'new_server'.
But, the different applications connecting to the actual server can't
easily change their connections address. i.e it connect to
'actual_server' server only.

Is there a risk to declare a DNS alias 'actual_server' pointing to
'new_server' ?
So I could move my databases from 'actual_server' to 'new_server'.
Is the modification transparent to the client ?
I especially thinking about wins...

TYIA
Cordially
RJP"rjp" <rjp.l@.laposte.net> wrote in message
news:9b7a7215.0410130818.317ad44b@.posting.google.c om...
> Hi all,
> I have to move my SQlServer 2000 instance from one server
> 'actual_server' to another server 'new_server'.
> But, the different applications connecting to the actual server can't
> easily change their connections address. i.e it connect to
> 'actual_server' server only.
> Is there a risk to declare a DNS alias 'actual_server' pointing to
> 'new_server' ?
> So I could move my databases from 'actual_server' to 'new_server'.
> Is the modification transparent to the client ?
> I especially thinking about wins...
> TYIA
> Cordially
> RJP

I don't see any big problem, if you're simply adding an alias to an existing
host. It probably isn't a good long-term solution, though, as it may create
management and troubleshooting problems at some point. I don't know about
WINS, as I haven't used it in a while (it's not necessary on an all-Win2K
TCP/IP network) - you might want to check with your network administrators
(if that's not you, of course), or in a networking newsgroup.

Simon|||> I don't see any big problem, if you're simply adding an alias to an
existing
> host. It probably isn't a good long-term solution, though, as it may
create
> management and troubleshooting problems at some point. I don't know about
> WINS, as I haven't used it in a while (it's not necessary on an all-Win2K
> TCP/IP network) - you might want to check with your network administrators
> (if that's not you, of course), or in a networking newsgroup.
> Simon

Thanks Simon.
:)

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.

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.

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.