WINS Resolution Problem

We are runnint Windows NT 4.0 with Exchange Server 5.0.  Our Network Protocols are TCP/IP and NetBEUI.
We previously had two subnets (we'll cal them Alpha and Beta) communicating across an ISDN line.
Network Alpha's IP block was:
Network Beta's IP block was:
The subnet mask for both networks was:

We moved network (Beta) to the same physical network (Alpha) and reassigned DHCP to issue addresses between with a subnet mask of

We seem to be able to ping any workstation on the local subnet without problems by using the IP address.  However, when we try to ping using NetBios names, many of the workstations don't respond.  More importantly, many workstations cannot get their e-mail because their e-mail client registers with Exchange Server using a NetBios name.

By the way, we deleted the WINS server database and added a new one so that it would reconstruct itself.  

I cannot figure this out.
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.

Tim HolmanCommented:
Test NetBIOS name resolution using NBTSTAT from the workstations.
What IP address does the WINS server have - post up its IPCONFIG /ALL.
What does IPCONFIG /ALL from a failing client say ?
When you say 'PING' using NetBIOS names, what do you mean ?
PING will search for a DNS hostname, not NetBIOS name, althought these can be exactly the same !
Your subnet mask is hopefully and not (which could definitely be a reason for the above behavior).
Also, assign addresses from to 126 (127 is broadcast for that subnet and 128 is the subnet address for the next subnet).
Exchange uses IP name resolution same as PING. If you want it to use NetBIOS name resolution (wins) you will have to change the RPC_Binding_Order key on each clients registry so that netbios comes first.

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
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 Networking

From novice to tech pro — start learning today.