NetBT

  • Thread starter Thread starter akpud
  • Start date Start date
A

akpud

Hello,

I have 2 laptops and one desktop connecting wirelessly to the Internet.

One is a Gateway Tablet PC (XP SP2). Every once in awhile (yesterday 4
times) it freezes and must be rebooted. Once rebooted it is back to normal.

The Event Viewer shows an Error NetBT and says "The name MSHOME......1d
could not be registered on the Interface with IP address XXXXXX. The machine
with IP address XXXXX did not allow the name to eb claimed by this machine".

This PC is one of three computers that access the Internet wirelessly
through the router - with no issues from the other two at all.

Any idea how to deal with this issue? Last night I changed the name of the
computer from MSHOME to MYHOME. Not sure if this is relevant or not.

Please advise.
 
Hello,

I have 2 laptops and one desktop connecting wirelessly to the Internet.

One is a Gateway Tablet PC (XP SP2). Every once in awhile (yesterday 4
times) it freezes and must be rebooted. Once rebooted it is back to normal.

The Event Viewer shows an Error NetBT and says "The name MSHOME......1d
could not be registered on the Interface with IP address XXXXXX. The machine
with IP address XXXXX did not allow the name to eb claimed by this machine".

This PC is one of three computers that access the Internet wirelessly
through the router - with no issues from the other two at all.

Any idea how to deal with this issue? Last night I changed the name of the
computer from MSHOME to MYHOME. Not sure if this is relevant or not.

Please advise.
Click to expand...

Please note: MSHOME is usually used in Microsoft's Workgroup settings
for the "Network Wizard." Microsoft's networking does not normally
"permit" a user anme, workgroup or computer name to be the "same." I

Example:
Workgroup: MSHOME
Computer: MyPC
User: User
 
Update:

It just froze again - but this time the Error Log shows no error messages.

Any advice would be greatly appreciated!
 
Can I disable NetBT?

Is there a more detailed error log that I can refer to for troubleshooting
purposes?

Is it possible that Zone Alarm is causing this behavior?

Thanks for your help!
 
Back
Top