10 replies
by downrighttired Accepted solution
by p.j.hutchison Accepted solution
by downrighttired Accepted solution
by p.j.hutchison Accepted solution
You need to install the Windows Internet
Naming Service on your Windows server and
change DHCP server options to point to wins
server. This will store the netbios names
in a database and will allow netbios name
resolution, unless you are using 'Netbios
over TCPIP' option on your DHCP scopes.
You can install it via Add/Remove Windows
Products in the Networking section.
by downrighttired Accepted solution
by cg it Accepted solution
normally you don't want your AD DC appearing in my network places. Its not necessary for users to see the DC to logon. It's just necessary for the sysvol and netlogon share to be accessible to users via permissions. They don't actually have to see the shared folder.
However, if you are sharing a resource on your DC for users and it's listed in AD, users can browse AD for the resource.
by downrighttired Accepted solution
by p.j.hutchison Accepted solution
Computer browsing uses Netbios names, not dns. For it to work, if all computers are on the same subnet, then you should be able to see all computers on the same subnet as it will be using ARP.
Computers and servers need the Computer Browser, Server and Workstation services running otherwise no computers will be available to browse or it will not be available to browse for.
WINS is useful for multi-subnet networks and multiple domains and workgroups and for short name resolution.
USeful tools: BROWSTAT.EXE, NBTSTAT.EXE
(you may have to download browstat as its not a tool provided in XP).
by cg it Accepted solution
domain controller [DC] intimates that you have a domain based network. Active Directory Services are the base concept of a Windows domain.
A workgroup isn't a domain based network nor does it have a domain controller.
so, using a DC and the term workgroup together doesn't quite make sense.
WINS server is really used for finding and resolving machine names to addresses for pre W2K and non Windows hosts. Operates like a Hosts file. In a pure TCP/IP environment using W2K or above O/Ss NetBios over TCP/IP isn't necessary [nor is a WINS server]. DNS with forward and reverse lookup zones takes the place of a WINS server.
need more information on your basic network setup. If this a Active Directory domain or just a plain workgroup [peer to peer]. do you run DHCP and DNS? how are those configured? what client O/Ss are there on the network[preW2K]?
by downrighttired Accepted solution
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending