Do I need WINS?

Installed new 2008 R2 DC's and demoted 2003 DC's. We were running WINS, but decided to not use ti anymore as I have been told we don't need it anymore. Problem I am now facing is client software looking for license server. It requires you to find the server, but can only find computers ont he same subnet without WINS. Is there any way to see computers accross subnets through "My Network Places" or whatever these client software packages use?
Greg27Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Darius GhassemCommented:
Some softwares still need WINS so you would need to keep it on the network. Now WINS won't hurt to have it installed and it allows you to view over subnets in My Network Places.

There are registry hacks that we have done before to make the clients visible across subnets but I don't remember what they are. I started not to do the hacks because of issues when we switched out hardware.
0
rizla7Commented:
you do not need WINS.

you can think of WINS as a DNS server for netbios names. it resolves netbios name requests n behalf of win95/98/me clients usually, as well as some other OSes. or if you win2000/xp/vista/etc are configured for netbios.

if not using WINS, ensure all your machines are capable of Kerberos authentication (win2000 and up) and in network properties disable (use netbios) settings. you can then block ports 135-139 used for file sharing.

DNS must be properly configured.
0
Greg27Author Commented:
What in my DNS might be wrong if I cannot see domain computers/servers across subnets? We used to be able to see it in our Windows 2003 network with WINS installed, but since we moved to 2008 R2 and no WINS we cannot see anything outside each subnet.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Greg27Author Commented:
By the way, We are running Windows 2008 servers and Windows XP workstations. We are not using the Windows firewall on the desktops, so all ports should be accessible.
0
rizla7Commented:
to browse computers in 'network computers' you need netbios/WINS. WINS definately makes things more efficient if you are using a netbios environment.

in an AD only environment tough you should only be using AD to find computers.

you can still use the FQDN to look up an IP using DNS across subnets, as long as both the forward lookup zones are configured and DHCP is configured to update DNS securely.

If you have TWO separate network segments, each should have it's own DHCP server, otherwise you will need a DHCP relay. the relay must be setup on a machine different from the DHCP server. the DHCP server is required in each segment to update DNS records on the client's behalf.

are the records showing up on your DNS server for both subnets?


0
rizla7Commented:
btw, for vista/7 here is the ad search tool

%windir%\system32\rundll32.exe dsquery.dll,OpenQueryWindow

for 2000/xp simply goto start menu -> search
0
rizla7Commented:
oh i should mention, there are also tools like LLDP protocol etc that will allow you to detect clients on the network, but it requires a software installation for XP.

http://www.microsoft.com/downloads/details.aspx?FamilyID=4f01a31d-ee46-481e-ba11-37f485fa34ea&displaylang=en

that is the link for XP. for vista you can enable it in the network control centre option 'enable network discovery'
0
Darius GhassemCommented:
Certain applications still use NetBios for an example My Network places to view computers across subnets need to have WINS.
0
Greg27Author Commented:
I installed WINS on 2 Windows 2008 R2 DC's and setup to replicate both, but one has all of the computers across the subnets and the other shows nothing. Am I missing something?
0
Darius GhassemCommented:
Make sure you have replication setup properly.
0
Greg27Author Commented:
Not sure if I am missing something, but Under Replication Partners for DC "A" I have DC "B" as a replication partner with type "Push/Pull". For DC "B" I have replication partner DC "A" with type "Push/Pull". Is there something else I am missing?
0
Darius GhassemCommented:
No sounds good did you setup any restriction on when they can replicate?
0
Greg27Author Commented:
No restrictions. I just don't understand why one DC sees all of the computers and the other cannot. Even if I didn't replicate, I would think they would find the computers on their own.
0
Darius GhassemCommented:
Check to make sure they are pointing to WINS servers in their TCP\IP settings.
0
Greg27Author Commented:
Looks like after a few days, both are showing all of the computers, but on a Windows 7 PC I am still only seeing the computers that are on the same subnet. No others.
0
Greg27Author Commented:
I am also not seeing any computers on other subnets from a Windows 2003 server.
0
Darius GhassemCommented:
Windows 7 make sure the computer browser service is started; the PC is pointing to WINS server; and the Netbios and TCP\IP is enabled.

Make sure the Windows 2003 server is pointing to the WINS in  the TCP\IP properties.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rizla7Commented:
all this just to see a computer in network places :\ and on a server? i thought this was for your users. lol.... why is netbios enabled on a server... i give up.. /quit question
0
Greg27Author Commented:
I was just testing from those locations. Ultimately, we need for workstations to see the license server, but both are on different subnets. I didn't have access to an XP machine and I wasn't sure if there was a goofy Windows 7 issue, so I tested on a 2003 server that should be able to see everything across subnets. That is why i put that in.
0
Greg27Author Commented:
Looks like the last problem was due to the Computer Browser service on the DC's not being started. We started the service up and now, with WINS running as well, we can see all of the computers on the network. Thanks a ton for the help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.