Remote Support Software

Provide instant remote support to customers and employees:

Click here for a free trial

System Log Event ID 4321 every 30 seconds, system name conflict for a name not in use

-- Symptom --
System event log shows an error with event ID 4321 every 30 seconds:
The name "pac-1 :2d" could not be registered on the interface with IP address 172.20.51.206. The computer with the IP address 172.20.21.2 did not allow the name to be claimed by this computer.
-- Environment --
OS: Windows 7 x64 Enterprise
Network: Enterprise domain
DHCP: Yes
WINS: via DHCP

-- Additional information --
This computer was set up from an image. The image was built with the system being named 'pac-1'. This system's name was changed to 'pac-11' before (or possibly shortly after) joining the domain and now has a completely different name, and there
is no system on the network with the name 'pac-1' (there are 'pac-3', and other numbers, but no 'pac-1')
I have renamed the system with no change to the frequency of the error, and I cannot find 'pac-1' in the registry anywhere except for strings located in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LANDesk\Inventory\LogonHistory\Logons that list prior logons.
I've done my google research and have found great information for plenty of other people's situations, just not this one. Any helpful advice is welcome.
Thank you!

Need to support users over the internet? click here try our remote control online beta






June 13th, 2012 9:44am
c0lorless wrote:

-- Symptom --


System event log shows an error with event ID 4321 every 30 seconds:
The name "pac-1          :2d" could not be registered on the
interface with IP address 172.20.51.206. The computer with the IP
address 172.20.21.2 did not allow the name to be claimed by this
computer.

-- Environment -- OS:  Windows 7 x64 Enterprise
Network:  Enterprise domain
DHCP:  Yes
WINS:  via DHCP


-- Additional information -- This computer was set up from an image.  The image was built with the
system being named 'pac-1'.  This system's name was changed to
'pac-11' before (or possibly shortly after) joining the domain and
now has a completely different name, and there is no system on the
network with the name 'pac-1' (there are 'pac-3', and other numbers,
but no 'pac-1')

I have renamed the system with no change to the frequency of the
error, and I cannot find 'pac-1' in the registry anywhere except for
strings located in
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LANDesk\Inventory\LogonHistory
\Logons that list prior logons.

I've done my google research and have found great information for
plenty of other people's situations, just not this one.  Any helpful
advice is welcome.

Thank you!

I'd check my WINS server's registration entries, if they contain an
entry with that NETBIOS name. If the machine with the ip-address
172.20.21.2 is not your WINS server you need to check, what services
etc. are running on that machine. Also look if the domain/workgroup
name, which is used by this machine is correct and identical to all
other machines.
Wolfgang

Need to support users over the internet? click here try our remote control online beta






June 13th, 2012 12:30pm
c0lorless wrote:

-- Symptom --


System event log shows an error with event ID 4321 every 30 seconds:
The name "pac-1          :2d" could not be registered on the
interface with IP address 172.20.51.206. The computer with the IP
address 172.20.21.2 did not allow the name to be claimed by this
computer.

-- Environment -- OS:  Windows 7 x64 Enterprise
Network:  Enterprise domain
DHCP:  Yes
WINS:  via DHCP


-- Additional information -- This computer was set up from an image.  The image was built with the
system being named 'pac-1'.  This system's name was changed to
'pac-11' before (or possibly shortly after) joining the domain and
now has a completely different name, and there is no system on the
network with the name 'pac-1' (there are 'pac-3', and other numbers,
but no 'pac-1')

I have renamed the system with no change to the frequency of the
error, and I cannot find 'pac-1' in the registry anywhere except for
strings located in
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LANDesk\Inventory\LogonHistory
\Logons that list prior logons.

I've done my google research and have found great information for
plenty of other people's situations, just not this one.  Any helpful
advice is welcome.

Thank you!

I'd check my WINS server's registration entries, if they contain an
entry with that NETBIOS name. If the machine with the ip-address
172.20.21.2 is not your WINS server you need to check, what services
etc. are running on that machine. Also look if the domain/workgroup
name, which is used by this machine is correct and identical to all
other machines.
Wolfgang

Need to support users over the internet? click here try our remote control online beta






June 13th, 2012 12:41pm
Thanks, Wolfgang. Your assumption that 172.20.21.2 is a WINS server is correct - we have a primary (21.1) and an alternate (21.2).
Also look if the domain/workgroup name, which is used by this machine is correct and identical to all other machines.
I have confirmed that my machine's domain name is correct and identical to all other machines. Or were you saying to check this on the WINS server?
I don't administer the WINS server, so I'll have to get back to you on the items to check from there.
Thanks!

Need to support users over the internet? click here try our remote control online beta






June 13th, 2012 12:49pm
Hi,


I agree with Wolfp. The issue may be related to the NetBIOS Name. Please consider to contact your Domain Administrator to double check it on Server site.


Please refer to this.

http://technet.microsoft.com/en-us/library/cc738412(v=ws.10).aspx



If the issue persists or encounter any problem during changing NetBIOS Name, please post your problem on Server Forum. You will get the more solid suggestion.

http://social.technet.microsoft.com/Forums/en/category/windowsserver/Kim
Zhou

TechNet Community Support

Need to support users over the internet? click here try our remote control online beta






June 15th, 2012 3:03am
This is a pretty low-priority for our network admins, so they haven't gotten back to me on this yet. I'll let you know what I find out once they do.
Thank you!

Need to support users over the internet? click here try our remote control online beta






June 26th, 2012 8:07am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics