Vista Ultimate x64 netbt error 4321

I have a small Windows 2003 domain with two domain controllers, 5 othe
servers, and 4 workstations. All of ther servers are 2003, 4 of th
workstations are XP, and the other workstation is Vista Ultimate x6
SP1. The Vista workstation is new to the network (just came from Dell)
There were no issues on the network before the Vista machine was added

About every 7 minutes and 40 seconds the Vista computer will have 1
errors in the System Windows Log. The errors are all netbt Event I
4321. Here is an example

the name \"prg-ssss :0\" could not be registered on the interface wit
ip address 192.168.1.227. the computer with the ip address 192.168.1.23
did not allow the name to be claimed by this computer

the name of the vista machine is workstation08 and it has a dhc
assigned address of 192.168.1.227. each of the errors is the sam
except for the name of the computer trying to be registered on the vist
machine, and of course its ip address

There is no duplicate name on the network. None of the othe
computers, including the DC's, has an error. The network is operatin
fine. The Vista machine is able to reach all network resources that i
should

Why on Earth would this computer be trying to register to its interfac
the name of every other computer on the network? On the Wins tab of th
TCP/IP Settgins dialog, NetBIOS is set for 'Enable NetBIOS over TCP/IP'
This is the same setting for all of the machines. Also, WINS is no
being used

The DHCP scope also provides the router and DNS servers

--
ohiovista64

I am having the same problem with my fairly new Dell Studio 17.

My girlfriend bought a 32-bit Vista Dell at the same time and does not
have the problems.

I shut off NetBios and the errors went away, but I couldn't see any
shared resourvces (printers, drives, etc.) any more on either XP or
Vista machines.

Turning NetBios back on brought everything back, including the errors.

It's April 18th here, I don't know how far back the Event Viewer
actually keeps log entries but the earliest dated entry is March 22nd -
does that date ring a bell with anyone?

Anyone else have an success at fixing this?


drc


--
dragonstar