Have you ever run across the following:
I re-did the PDC at “Site 1” a few weeks back (wiped it completely) did the usual re-install without any issues until the end when I installed RAS (remote access). The error coming up after re-boot in the event viewer was “Not a valid computer name” and it wouldn’t start the netlogon service, thus couldn’t connect to the network. If I un-installed RAS and re-booted, the problem went away. Searching Technet, it is a known problem. So I removed the listing for the server in WINS as instructed and the problem went away. Problem solved.
Putting in “Site 2’s” new server last week, I had the exact same problem. I have never seen this before, and I have “re-done” a number of servers the same way as I did there. Did I miss something along the way?
We have all of our servers listed in the WINS static mappings, and this has never come up before. This time there were both domain controllers with RAS service loaded and re-using the same server name. I removed the server from server manager long before bringing it on-line and sync’ed the domain.
I am re-doing the server here in “Site 3” today and will have to load RAS, and am concerned that having an entry in WINS will cause the same problem. Note even if I remove the entry from WINS prior to bringing the new server on-line and putting it back in the database after the fact, the error comes up.
I know not having the WINS entry is not a big deal since DNS will take care of the resolution, but it concerns me that I might have missed something, I would like to know how to get around the problem, and if the DNS server is ever down for a period of time, then it may become a issue.
Any thoughts, comments?
Thanks,
Tom Morris
