WINS is realy needed

Hello Group,

I am using network environment that consist win2k srv ,win2k pro ,win2k3 ,xp
for name resolving using DNS only, now for the question.
we are using applications that relays lots of NetBIOS names convection like
UNC path and calling computers by there NetBIOS name.
is it preferred to use any way WINS even when using UNC its still works does
it resolve the NetBIOS name by broadcast or resolving it from DNS?.

Thanks in Advanced.

"Tal Bar-Or" <(E-Mail Removed)> wrote in
news:(E-Mail Removed):

> Hello Group,
>
> I am using network environment that consist win2k srv ,win2k pro
> ,win2k3 ,xp for name resolving using DNS only, now for the question.
> we are using applications that relays lots of NetBIOS names convection
> like UNC path and calling computers by there NetBIOS name.
> is it preferred to use any way WINS even when using UNC its still
> works does it resolve the NetBIOS name by broadcast or resolving it
> from DNS?.
>
> Thanks in Advanced.
>
>
>

Yes, you do need WINS -- so many applications and even server components
still use WINS that it is recommended that you deploy it.

--
James McIllece, Microsoft

Please do not send email directly to this alias. This is my online account
name for newsgroup participation only.

This posting is provided "AS IS" with no warranties, and confers no rights.

If its still working without WINS for example (\\computername\share) do you
think the name resolving is done by broadcast or by ths DNS?
Thanks.

"James McIllece [MS]" <(E-Mail Removed)> wrote in message
news:Xns96F5939B3CF9Cjamesmcionlinemicros@207.46.2 48.16...
> "Tal Bar-Or" <(E-Mail Removed)> wrote in
> news:(E-Mail Removed):
>
>> Hello Group,
>>
>> I am using network environment that consist win2k srv ,win2k pro
>> ,win2k3 ,xp for name resolving using DNS only, now for the question.
>> we are using applications that relays lots of NetBIOS names convection
>> like UNC path and calling computers by there NetBIOS name.
>> is it preferred to use any way WINS even when using UNC its still
>> works does it resolve the NetBIOS name by broadcast or resolving it
>> from DNS?.
>>
>> Thanks in Advanced.
>>
>>
>>
>
> Yes, you do need WINS -- so many applications and even server components
> still use WINS that it is recommended that you deploy it.
>
> --
> James McIllece, Microsoft
>
> Please do not send email directly to this alias. This is my online
> account
> name for newsgroup participation only.
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.

It is hard to tell. W2k and later machines try DNS and Netbios name
resolution together and use whichever replies first. The only way to know
for sure would be to monitor the network traffic. (Or disable Netbios over
TCP/IP and see what stops working).

DNS will resolve a simple name like machinename as long as the machine
has the correct DNS suffix set up. The resolver adds the suffix to form the
FQDN.

msnews.microsoft.com wrote:
> If its still working without WINS for example (\\computername\share) do
> you think the name resolving is done by broadcast or by ths DNS?
> Thanks.
>
> "James McIllece [MS]" <(E-Mail Removed)> wrote in message
> news:Xns96F5939B3CF9Cjamesmcionlinemicros@207.46.2 48.16...
>> "Tal Bar-Or" <(E-Mail Removed)> wrote in
>> news:(E-Mail Removed):
>>
>>> Hello Group,
>>>
>>> I am using network environment that consist win2k srv ,win2k pro
>>> ,win2k3 ,xp for name resolving using DNS only, now for the question.
>>> we are using applications that relays lots of NetBIOS names
>>> convection like UNC path and calling computers by there NetBIOS
>>> name. is it preferred to use any way WINS even when using UNC its still
>>> works does it resolve the NetBIOS name by broadcast or resolving it
>>> from DNS?.
>>>
>>> Thanks in Advanced.
>>>
>>>
>>>
>>
>> Yes, you do need WINS -- so many applications and even server
>> components still use WINS that it is recommended that you deploy it.
>>
>> --
>> James McIllece, Microsoft
>>
>> Please do not send email directly to this alias. This is my online
>> account
>> name for newsgroup participation only.
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.