G
Guest
Guest
Archived from groups: microsoft.public.windowsnt.domain (More info?)
Hi guys, I need your help!
I have a mixed Win 2003 and NT network. On one of the NT BDCs is running the
WINS service and one of the 2003 machine runs the DNS.
Everything was fine when I had the NT machines set to register only with
WINS. The problem began when I did try to register one of the NT machines
with the DNS ( in the Network/ TCP/IP / WINS address tab I checked the box
saying : "Enable DNS for Windows Resolution"). I had to reboot the machine
and after it restarted I got a message saying that at least one Service
didn't Start. When I checked it in Event Viewer, it was Event ID: 7024
described as: " The Messenger service terminated with service-specific error
2270." and the machine didn't appear in the DNS list anyway so, I unchecked
the "Enable DNS for Windows Resolution" ( the single change I did before)
and I rebooted the machine. I got the same error. Why and What can I do?
The Knowledge Base at Microsoft says that this behavior occurs when the
computer's name is not unique on the network ( which shouldn't be the case)
and the solution they give is to rename the machine ( which I don't want).
What can I do?
I would really appreciate your help!
Thanks, Gabi
Hi guys, I need your help!
I have a mixed Win 2003 and NT network. On one of the NT BDCs is running the
WINS service and one of the 2003 machine runs the DNS.
Everything was fine when I had the NT machines set to register only with
WINS. The problem began when I did try to register one of the NT machines
with the DNS ( in the Network/ TCP/IP / WINS address tab I checked the box
saying : "Enable DNS for Windows Resolution"). I had to reboot the machine
and after it restarted I got a message saying that at least one Service
didn't Start. When I checked it in Event Viewer, it was Event ID: 7024
described as: " The Messenger service terminated with service-specific error
2270." and the machine didn't appear in the DNS list anyway so, I unchecked
the "Enable DNS for Windows Resolution" ( the single change I did before)
and I rebooted the machine. I got the same error. Why and What can I do?
The Knowledge Base at Microsoft says that this behavior occurs when the
computer's name is not unique on the network ( which shouldn't be the case)
and the solution they give is to rename the machine ( which I don't want).
What can I do?
I would really appreciate your help!
Thanks, Gabi