Resolving NetBIOS Names

On a private lan of about 50 clients, each client is able to be referenced by their computer names (I think NetBIOS name is more technically correct). So at the command prompt I can run "ping fileserver" and it resolves the name fileserver to an address.

1. What service on the network is responsible for this?

I think it has to do with WINS and NetBIOS but I'd like some clarification. The reason I am asking is because there is one client on the network that it *doesn't* work for. If you type "ping client", it responds "Pinging client.domain.local [192.168.0.30] with 32 bytes of data:", then gives a series of timeouts (because nothing is at that ip). When I log onto that client's computer, the client has a completely different IP address. It's actually 192.168.0.45.

2. What could cause this to happen and how do I "update" the information?

The domain is a SBS2000 domain with mixed 2k/xp clients.
LVL 20
DVation191Asked:
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.

NetoMeter ScreencastsCommented:
Hi!

Check the forward lookup DNZ zone for domain.local on your domain controller.
There is a record for host "client.domain.local" with ip 192.168.0.30. Delete this entry and reboot the client.
Instead of reboot you can type in dos prompt on the client machine ipconfig /registerdns.

The ip address for this client has been changed and the old stale record hasnot been removed.

NetoMeter
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
DVation191Author Commented:
Well you were right about the forward lookup zone...that client had the wrong ip in the zone. I deleted the entry

However after both rebooting the client and also running ipconfig /registerdns, the entry has not been rebuilt, nor can any reference be made to this client by name on the network at all.
0
DVation191Author Commented:
By the way, shouldn't all this happen automatically?
0
DVation191Author Commented:
scratch that. it worked. thanks.
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
Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.