sm7725
asked on
Why do end users need to see all the PCs on a Windows network
I am migrating from a Novell NDS to new-from-scratch Windows network with AD over a clean Cisco routed network where all shared services on servers. I remove the netbios over tcp/ip and file&print services from all clients, do not think I have any wins server. Still some of the PCs keep showing up on the Windows network - I would like only DC's and file servers show up. The computer browsing seems so baked into ths OS, is there any risk to removing all the stuff? Is there any guideline for building a secure new windows network when no legacy network exists?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Are their legacy utilities in XP Professional clients that use LMHOSTS instead of DNS?
ASKER
TCP/IP is the only protocol on Windows network. However, whenever I have had occassional replication or problem from windows utility; I was told I need Wins or netbios over tcpip. Are they needed? I usually remove them on new PC's prior to deployment.