Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
WINS+DNS
- Thread starter napoleao
- Start date
WINS can be good if you use Network Peer-to-Peer sharing (Computers sharing files and printers between themselves). If you do not require this, then WINS is not necessary.
WINS purpose is for synchronizing your subnet with different subnets for the computer names. This permits file and print sharing over subnets.
"In space, nobody can hear you click..."
WINS purpose is for synchronizing your subnet with different subnets for the computer names. This permits file and print sharing over subnets.
"In space, nobody can hear you click..."
Actually, Windows 2000 machines and later use DNS for local network name resolution. So, in answer to napoleao's question - if you have any NT4 or earlier, or Windows ME or earlier clients on your network you will want to keep a WINS server around. If all your client machines are Windows 2000 or XP, DNS is all you need.
Marc Creviere
Marc Creviere
NickFerrar
MIS
Some apps can rely on WINS (SMS v2 springs to mind) so I'd be careful, also browsing will be affected.
I completly disagree with Filthpig (I don't disagree often)
You don't need WINS for a LAN. No matter what version of Windows you are running, your Browser Service (if well configured) will do the job for a LAN like a WINS. The "Computer Browser" service was integrated as of Windows for Workgroups 3.11 (for peer to peer networking).
If you have several subnets, you will need WINS if you want people to access machines across the routers via their computer names.
What I think Filthpig means is that you can use a DNS to resolve the IP names across several subnets. For example, let's say computer SERVER2 (a server that is across a router) is in the DNS as IP 192.168.0.4. If you try to attach to a computer across a router without WINS, you will need to use the IP (ex: \\192.168.0.4\<share>). With WINS at both ends and synchronizing, you will be able to type: \\SERVER2\<share>, but if you PING SERVER2, your DNS will answer 192.168.0.4.
"In space, nobody can hear you click..."
You don't need WINS for a LAN. No matter what version of Windows you are running, your Browser Service (if well configured) will do the job for a LAN like a WINS. The "Computer Browser" service was integrated as of Windows for Workgroups 3.11 (for peer to peer networking).
If you have several subnets, you will need WINS if you want people to access machines across the routers via their computer names.
What I think Filthpig means is that you can use a DNS to resolve the IP names across several subnets. For example, let's say computer SERVER2 (a server that is across a router) is in the DNS as IP 192.168.0.4. If you try to attach to a computer across a router without WINS, you will need to use the IP (ex: \\192.168.0.4\<share>). With WINS at both ends and synchronizing, you will be able to type: \\SERVER2\<share>, but if you PING SERVER2, your DNS will answer 192.168.0.4.
"In space, nobody can hear you click..."
- Status
Similar threads
- Locked
- Question