SQL Server Performance Forum – Threads Archive
Is WINS needed for #domain SQL2K virtual instance
We are moving to a new domain.The old ones will still be active for a (long) while.
When I want to connect to a normal sqlserver it works.
When I want to connect to a virtual sqlserver (clustered or non-clustered),
it does not work, unless I add our old WINS server to the client-settings
WINS definitions.[B)]
Using SMSnetworksniffer we’ve detected that a normal server returns its
servername with FQDN (fully qualified domain name) whereas the virtual
servers don’t. ! [xx(] [V] Is this a bug [?]
I don’t know if this is a bug or not, but, yes you need WINS or DNS to access the virtual server name. —————————–
Brad M. McGehee, MVP
Webmaster
SQL-Server-Performance.Com
I’ve seen installations where the client computer was in a different domain than the server, and we had to use the FQDN. Client computers in the same domain as the server could also connect using the FQDN, so we made sure we used the FQDN in the client application.
One can also add a DNS record for the SQL virtual server name on the DNS server in the new domain.
Thanks for your replies. The problem is that only dns-replication does not work ! [V]
Servers are addressed with FQDN, but with the virtual ones it does not work.
(mynormalsql2k.myolddomain.old works, [^]
myvirtualsql2k.myolddomain.oldmyvirtualinstance does not work unless our old WINS is added ) [xx(] We might indeed add an alias to the new domain, but that would be a workaround and I’m afraid it would bite us in the back at moments we wouldn’t expect it.
FYI MS has confirmed this to be a problem. [<img src=’/community/emoticons/emotion-6.gif’ alt=’


]]>