asked on

Error on DC - "The name could not be registered on the Interface..."

Hi there,

Scenario of our situation:

- We have 2 sites connected via VPN.
- Hub site has 2 DC's running 192.168.11.8 and 192.168.11.9 respectively.
- A 3rd DC was created on the hub site with the IP of 192.168.11.30.
- That 3rd DC was then sent to the branch site and the IP was subsequently changed to 192.168.12.10.

Everything appears to be working fine (replication and etc). I do however keep getting these errors every hour on that 3rd DC ever since it was moved over to the branch site;

System Even Log
Source: NetBT
The name "Domain :1d" could not be registered on the Interface with IP address 192.168.12.10. The machine with the IP address 192.168.11.8 did not allow the name to be claimed by this machine.

I did some digging and most posts pointed the source of the problem to WINS. We don't run WINS so I'm wondering if anyone else has any other suggestions. Again the DC *appears* to be operation but I'd like to find the root of these errors.

Thanks for reading!

DrDave242

I did a little research and found that restarting the Computer Browser service on both machines (the one with the error and the one referenced in the error) fixed the problem for a few people. Give that a shot - it's quick and it might work.

Also, did you follow the recommended procedure for relocating that domain controller? See here for details:
http://technet2.microsoft.com/windowsserver/en/library/80e432f2-10b6-4768-8a3e-54e357e8fc441033.mspx?mfr=true

RHADMIN

ASKER

Hi Dave,

I just restarted the Computer Browser services on both servers. Regarding the IP change I did what was suggested in the document minus the WINS part as we don't use it.

I guess I'll wait for an hour and see if the error still shows. Will report back in then...thanks!

RHADMIN

ASKER

argh i didn't have to wait for an error the errors are still happening. :( I do however see errors on the DC with the IP of 192.168.11.8 such as:

System Event Log
Source: MRxSmb
The master browser has received a server announcement from the computer ******** that believes that it is the master browser for the domain on transport NetBT_Tcpip_{C52C919E-A260-4215. The master browser is stopping or an election is being forced.

If the path you've looked at is the right one then these 2 errors could definitely be related. Thanks again.

oBdA

To start with, since you have NetBIOS over TCP/IP enabled, it would be a good idea to install WINS on at least one server and let your clients use it.
That said: Could it be that you have issues with master browser elections being enforced as well?
Do you have IP Helper addresses or broadcast forwarding configured on your router? If so, disable at least forwarding of the NetBIOS ports (UDP 137 and 138).

RHADMIN

ASKER

sorry for the late reply.

Unfortunately IP helper is turned off as the branch site is running it's own DHCP.

To make it easy should I just (using Regedit) disable the branch office's DC from trying to be the master browser?

Thanks

ASKER CERTIFIED SOLUTION

oBdA

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

RHADMIN

ASKER

Yes you're right. Unfortunately my Sonicwall router's firmware is only "basic" and not the "enhanced" version. I'm missing quite a few of the options that let me configure exactly what's passed through the VPN tunnel. I'll do some further reading on Sonicwall's site to see how I can accomplish this. Thanks for your time.

Error on DC - &quot;The name could not be registered on the Interface...&quot;

Error on DC - "The name could not be registered on the Interface..."