Duplicate name on network

I have an NT 4.0, service pack 5 machine that I added a new modem to and then set up the Remote Access service.  After doing this I rebooted the computer and the following services failed to start:  Workstation, Alerter, Computer Browser, Messenger, Net Logon, RPC Locator.

In Event Viewer, the Workstation service terminated with the following error:  A duplicate name exists on the network.  The other services probably failed to start because the Workstation service did not start.

I can start the Workstation service and all of the other services manually after the computer boots and everything works fine.  Also, I changed the name of the computer and it booted without any errors.

As a test, I shut down the NT machine and changed the name of a Win98 machine to be the same name as the NT server machine name that reported a duplicate name on the network.  The Win98 computer booted without any errors and worked fine.  I then shut the Win98 machine down and renamed the NT machine back to the problem name and I got a duplicate name error.

I reinstalled service pack 5 but this didn't help.

Any ideas as to why I would get a duplicate name error on the NT machine and not on the Windows 98 machine?  I really don't want to change the name of the NT machine.
rosscAsked:
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.

rosscAuthor Commented:
Edited text of question.
0
spreemanCommented:
Check your network properties... unbind NetBEUI from the modem if you're not sure it's going to be needed and see if that lets you boot up okay. Probably both your network card and modem are trying to register the same NETBIOS name with the WINS service on your network, causing the error.
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
rosscAuthor Commented:
I removed the remote access service and the computer booted up without any errors.  When I re-installed remote access with only TCP/IP checked, I got the same error.

Is it possible to run RAS on an NT server maching that is not a PDC or BDC?
0
spreemanCommented:
I am running an NT server which is used for validating users dialing into our system, and it is running RAS - but it isn't a domain controller. So, if I understand the scenario correctly, my answer is that it's possible.
0
rosscAuthor Commented:
I had a spare com port on my BDC so I moved the modem to that machine.  I'll try again later, maybe with Windows 2000.


Thanks 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 OS

From novice to tech pro — start learning today.