SQL Server Performance

Is WINS needed for #domain SQL2K virtual instance

Discussion in 'SQL Server Clustering' started by alzdba, Jul 15, 2004.

  1. alzdba Member

    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 [?]

  2. bradmcgehee New Member

    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
  3. Adriaan New Member

    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.
  4. Vinny New Member

    One can also add a DNS record for the SQL virtual server name on the DNS server in the new domain.
  5. alzdba Member

    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.
  6. alzdba Member

    FYI MS has confirmed this to be a problem. [<img src='/community/emoticons/emotion-6.gif' alt=':(' />]<br />Because the are a number of workarounds (which we described) and we appeared to be the first [?] to report this, no corrective hotfix will be assembled.[B)]<br /><br />The problem is that it all is still designed to be used with netbios (nt4).<br /><br />We had already described some workarounds : [<img src='/community/emoticons/emotion-3.gif' alt=':eek:' />)]<br /><br />- add the old domain in network settings domain-suffixes<br /><br />- add the old wins-server<br /><br />

Share This Page