Network naming error by my predecessor wreaks havoc on my life!

[AceHigh1234]

OK, I took over at an office last august for the old computer guy right after a major system crash. The person who set up the new server was trying to recreate the domain ABC2000.local for some? reason he couldn't get the old domain name to work at first. At some point, he tried using ABC20000. Now, everything in DNS is ABC2000.local, all the computers are amachine@ABC2000.local, when I add a mcahine, I add it to ABC2000.local, all my users are auser@ABC2000.local, I can pink amachine@allen2000.local and get a response etc. When my users log on to their workstations, however, the select ABC20000.local from the drop down box. When I go to network places on my server, and view entire network, I see ABC20000 as the network name. When ever I go to the properties for any item in AD, the network name is listed properly as ABC2000.local almost everwhere except for any security tabs, and for my User Log on name (pre WIn2000). We've been having some VERY strange problems around here lately with an accounting application that is hosted on one of our servers, and with a Pervasive.SQL database used with the accounting program. I check my server event logs daily, but never check my users logs unless they have a problem. Well, I've been working on this for a while now, and I started checking my users even logs for once, and almost all of them have this error:

*****Just tried to connect to a remote users event log from the server, and it will not connect. Yet that user is accessing the accounting application and a shared data folder on the serverI am using right now*****

Something about group policy could not be processed because the domain ABC20000.local could not be contacted. The specified domain is offline or does not exist.

I am at a loss to even guess at how this was done, or how to correct it, and I've been working on it off and on for months now.

ANY help or input would be GREATLY appreciated!!

-Mark Vickroy, Jr.

 

[JBruyet]

AceHigh1234,

You might try running dcdiag and see if everything is cool in your AD structure. Running that helped me fix an issue I was having with workstations not being able to join the domain. AND, if it finds an error (if I'm remembering this correctly) running dcdiag /fix will correct the issue.

HTH,

Joe Brouillette

 

[pgaliardo]

For more info on dcdiag and other Domain Controller troubleshooting options check out this link:

http://support.microsoft.com/kb/247811/en-us

 

[AceHigh1234]

Here's the ipconfig /all from the main server:



Windows 2000 IP Configuration



Host Name . . . . . . . . . . . . : ASERVER
Primary DNS Suffix . . . . . . . : ABC2000.COM
Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : ABC2000.COM

Ethernet adapter Local Area Connection 10-1000:



Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 XT Server Adapter
Physical Address. . . . . . . . . : 00-0E-0C-6C-6D-EB

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.1.32

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 192.168.1.32
192.168.1.5


And here's from an effected workstation:



Windows IP Configuration



Host Name . . . . . . . . . . . . : Manger

Primary Dns Suffix . . . . . . . : ABC2000.COM

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : ABC2000.COM



Ethernet adapter Local Area Connection 2:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection

Physical Address. . . . . . . . . : 00-13-20-01-89-D6

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.1.152

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 192.168.1.32

192.168.1.5


My DCDiag looks OK, except for the following:

Starting test: kccevent
An Warning Event occured. EventID: 0x8000062D
Time Generated: 06/23/2006 16:11:04
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x8000043D
Time Generated: 06/23/2006 16:11:04
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x80000425
Time Generated: 06/23/2006 16:11:04
(Event String could not be retrieved)
......................... ASERVER failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0xC004000F
Time Generated: 06/23/2006 15:59:09
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC004000F
Time Generated: 06/23/2006 15:59:25
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC004000F
Time Generated: 06/23/2006 15:59:25
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0040011
Time Generated: 06/23/2006 15:59:26
Event String: RSM cannot manage library Tape0. It encountered

An Error Event occured. EventID: 0xC004000F
Time Generated: 06/23/2006 16:00:07
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC004000F
Time Generated: 06/23/2006 16:00:22
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC004000F
Time Generated: 06/23/2006 16:00:23
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0040011
Time Generated: 06/23/2006 16:00:23
Event String: RSM cannot manage library Tape0. It encountered

An Error Event occured. EventID: 0x0000041B
Time Generated: 06/23/2006 16:11:49
Event String: The DHCP/BINL service has determined that it is

......................... ASERVER failed test systemlog


the systemlog error is b/c of a problem we are having with the tape drive. I'm not sure exactly what the kccevent
error is all about though...

 

[JBruyet]

AceHigh1234,

Do you get the same results from dcdiag on all three of your domain controllers?

Thanks,

Joe Brouillette

 

[markdmac]

Sounds to me like the Bozo in the position befor eyou messed up AD and somehow added a second site or domain to your network.

Take a loot at this KB and see if it helps any.

http://support.microsoft.com/kb/214745/EN-US/

Ideally I think what you need to do is look at each DC for domain membership. It might be necessary to demote all but one DC. You might then opt to use the Domain Rename Tool to change the netBIOS Domain Name if you want. Then DCPROMO the other servers back as DCs.

Thoroughly look through ALL records of DNS to see what internal DNs lists as DC, GS etc. You should be looking for sources of the 'extra zero' domain name.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

 

[AceHigh1234]

There was only 1 DC when I got here, another one was created when I created a terminal server, and the third DC is just a backup, and hosts some files and printers..

I just logged in to the terminal server via TS, and got this message when trying to run dcdiag:

dcdiag.exe Entry Point Not Found

The procedure entry point DsIsMangledDnW could not be located in the dynamic link library NTDSAPI.dll


I'm gonna run down there and run it locally in a second here..

 

[pgaliardo]

This might be off the subject of your original post, but if you created a terminal server that runs in application mode and also made that server a DC, you might want to remove one or the other. You really don't want users logging onto a TS that is also your DC. If it is only running in Admin mode, that's different.

 

[markdmac]

I agree, you should not have a TS also be a DC.

So from what I gather here you have 3 current DCs. I would DCPROMO 2 of them to remove AD then working with just a single server you can use the domain rename tool to get this straightened out then promote just the File Server back as a second DC.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

 

[AceHigh1234]

OK, I'll give that a try tomarrow

 

[AceHigh1234]

err.. where do I get the domain rename tool?

 

[markdmac]

Ace my apologies I did not realize the tool was only for 2003.

http://www.microsoft.com/technet/downloads/winsrvr/domainrename.mspx

So let's see if we can't figure this out with what you have.

I still believe your best bet is to first get down to a single DC. that way you are not dealing with multiple copies of DNS or dealing with AD replication.

Once you have a single DC, then I would very meticulously look for any entries in DNS that show the wrong name and remove/repair them.

It will be important to see what the AD Sites and Services and AD Users and Computers have to say as well.

Make sure before you demote your other DCs that you get all the FSMO roles on whatever server you are going to keep.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript