The name could not be registered

Hi,

I see this error in the logs of some of my XP systems on a 2003 domain
and sometimes they are disconnected from the network when it appears.

The name "LCS072225223004:35" could not be registered on the Interface
with IP address 192.168.n.a
The machine with the IP address 192.168.n.b did not allow the name to
be claimed by this machine

192.168.n.a is the client and 192.168.n.b is our WINS server.

Commeon advice says just make sure there's no system with the same name
and you'll be fine but there's no host name even close to
LCS072225223004 on our network - where is it coming from ??? The WINS
server has around 50 records with similar host names with record type
30h through 39h (other).

Thanks

"£Jim" <> wrote in message news:...
> Hi,
>
> I see this error in the logs of some of my XP systems on a 2003 domain
> and sometimes they are disconnected from the network when it appears.
>
> The name "LCS072225223004:35" could not be registered on the Interface
> with IP address 192.168.n.a
> The machine with the IP address 192.168.n.b did not allow the name to
> be claimed by this machine
>
> 192.168.n.a is the client and 192.168.n.b is our WINS server.
>
> Commeon advice says just make sure there's no system with the same name
> and you'll be fine but there's no host name even close to
> LCS072225223004 on our network - where is it coming from ??? The WINS
> server has around 50 records with similar host names with record type
> 30h through 39h (other).
>
> Thanks


LCSxxxxxx sounds like a printer or some other device that is getting a DHCP address with your WINS settings and trying to register. The error could be based on the name being longer than 15 bytes. Do you have an inventory of all IP devices? Run an IP scan, such as with SuperScan or more elaborate, eEye's Retina scanner. You can also check your switch ports, as well, to find this device.


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

Please reply back to the newsgroup or forum to benefit from collaboration among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer

http://twitter.com/acefekay

For urgent issues, you may want to contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.

Hi,
Thanks for the reply. That is my problem, there are no hosts with
anything close to that name on my network. It's almost as if the client
PC is trying to register a second name but I have no idea where the
names are coming from, nor why they exhibit the strange record type
numbers (other).

Ace Fekay [MCT] wrote:

> "£Jim" <> wrote in message
> news:...
> > Hi,
> >
> > I see this error in the logs of some of my XP systems on a 2003
> > domain and sometimes they are disconnected from the network when it
> > appears.
> >
> > The name "LCS072225223004:35" could not be registered on the
> > Interface with IP address 192.168.n.a
> > The machine with the IP address 192.168.n.b did not allow the name
> > to be claimed by this machine
> >
> > 192.168.n.a is the client and 192.168.n.b is our WINS server.
> >
> > Commeon advice says just make sure there's no system with the same
> > name and you'll be fine but there's no host name even close to
> > LCS072225223004 on our network - where is it coming from ??? The
> > WINS server has around 50 records with similar host names with
> > record type 30h through 39h (other).
> >
> > Thanks
>
>
> LCSxxxxxx sounds like a printer or some other device that is getting
> a DHCP address with your WINS settings and trying to register. The
> error could be based on the name being longer than 15 bytes. Do you
> have an inventory of all IP devices? Run an IP scan, such as with
> SuperScan or more elaborate, eEye's Retina scanner. You can also
> check your switch ports, as well, to find this device.

"£Jim" <> wrote in message news:...
> Hi,
> Thanks for the reply. That is my problem, there are no hosts with
> anything close to that name on my network. It's almost as if the client
> PC is trying to register a second name but I have no idea where the
> names are coming from, nor why they exhibit the strange record type
> numbers (other).


Researching it a bit more, I figured out that you're getting an EventID 4321.

See if the following link helps:
http://www.eventid.net/display.asp?e...=NetBT&phase=1

I still have a feeling it's a device causing it, but see if any of the scenarios posted match or seem to possibly apply to your scenario.

Ace

Ace