Re: WINS needed in 2003?


"study" <study@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EA2B935E-EC04-43AC-80D0-1FC4975AA335@xxxxxxxxxxxxxxxx
Thank you for your response.
I've never published shared folders in active directory before. The
instructions in doing so seems to be straight forward but the problem is
we
have hundreds of shard folders.
We do have multiple subnets. All our clients are XP or later. So without
WINS and without publishing the shared folders in AD, would we have isseus
because we're not using WINS?

In general you STILL need NetBIOS in Win2003 (if you wish to support
easy browsing and few other minor things).

IF you need NetBIOS (above) AND you have more than one subnet, i.e.,
a routed network, then you also have a practical requirement for WINS
Server and for every computer, esp. DCs and other servers, to be a
WINS Client.


"Kevin D. Goodknecht Sr. [MVP]" wrote:

Read inline please.

In news:213A6EBE-2C9A-49D4-A381-5F7147A2CD80@xxxxxxxxxxxxx,
study <study@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Is WINS still needed in 2003 domain when there's no MS exchange
server? Drive mapping seems to work without WINS using the flat name
since the DNS suffix will take care of the domain name.
Any of you don't run WINS in your 2003 domain?

The only need for WINS in Active Directory is if you want to browse
Network
Places across multiple subnets. If you have only one subnet and no NT4 or
9x
clients there is no real need for WINS. You can get by without WINS even
in
multiple subnets if you have only Win2k and later clients and all your
shares are Published in Active Directory because Win2k, XP and Vista
clients
can search Active Directory for your published shares.


--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================





.

Relevant Pages

  • Re: WINS needed in 2003?
    ... I've never published shared folders in active directory before. ... All our clients are XP or later. ... WINS and without publishing the shared folders in AD, ... The only need for WINS in Active Directory is if you want to browse Network ...
    (microsoft.public.windows.server.dns)
  • Re: WINS needed in 2003?
    ... I've never published shared folders in active directory before. ... Publishing shares in Active Directory is still the best way to go because XP ...
    (microsoft.public.windows.server.dns)
  • Re: Ports required for Internal Firewall between client and DC
    ... When an application requests access to Active Directory an Active Directory ... server (domain controller is located by a mechanism called the domain ... If we fix the port in one DC, can i make this DC as the one the clients ... Exchange, the Exchange MTA service stopped responding. ...
    (microsoft.public.windows.server.active_directory)
  • Re: My own Site unavailable to the clients
    ... > I have the site hosted with Yahoo and not on the PDC ... > clients I receive an immediate error "Unable to resolve ... The Active Directory domain name _must_ resolve to the IP address ... If the site is accessable from the server then you must also be using the ...
    (microsoft.public.win2000.dns)
  • Re: Rollback to NT4 domain from 2000 mixed mode
    ... There are corrupt tables in ntds.dit. ... They have all XP&2000 clients so trick ... > This is more of an Active Directory question than Group Policy so I ... Also if you applied any security templates, ...
    (microsoft.public.win2000.group_policy)
Loading