Duplicate Name on the network - SMB access hangs

I have a Win2008 SP2 fully patched and running on a DELL PE 2950 with 4 NICs
(2 integrated broadcoms and 2 intel "off-board")

Sometimes the server "hangs" and all SMB connections (only SMB/CIFS
connections are affected) stops. TS works well and in the EWvent Viewer apper
a messages informing duplicate name on the network (event id 4319 and 4343)
but there is no machine with the same name or the name of the domain.

Is a DC and the 2 broadcom as enabled with diff. IP addressess and the 2
Intel are "disabled" (via device manager)

DNS and WINS are Ok. I can access the share (\\servername) in the server
itself, but none of the machines in the network can access the mapped letter,
the \\servername share. The only solution is to reboot

what else i can do?

"FB" <> wrote in message
news:B98EF8E1-B60D-4250-BAEB-...
>
> I have a Win2008 SP2 fully patched and running on a DELL PE 2950 with 4
> NICs
> (2 integrated broadcoms and 2 intel "off-board")
>
> Sometimes the server "hangs" and all SMB connections (only SMB/CIFS
> connections are affected) stops. TS works well and in the EWvent Viewer
> apper
> a messages informing duplicate name on the network (event id 4319 and
> 4343)
> but there is no machine with the same name or the name of the domain.
>
> Is a DC and the 2 broadcom as enabled with diff. IP addressess and the 2
> Intel are "disabled" (via device manager)
>
> DNS and WINS are Ok. I can access the share (\\servername) in the server
> itself, but none of the machines in the network can access the mapped
> letter,
> the \\servername share. The only solution is to reboot
>
> what else i can do?


You are saying this is a DC. Multihomed DCs cause problems. Also, multihomed
DC cause problems with NetBIOS because of the multiple names for one IP,
same with SMB.

Follow the guideline in the following link to configure the domain
controller. Otherwise, I would suggest to make it a single NIC or team the
NICs, and make a member server multihomed to do whatever task you are trying
to do with this DC and multiple NICs or IPs. I prefer to move it to another
server instead of making all of these changes, including the registry
changes.

Multihomed DCs with DNS, RRAS, and/or PPPoE adapters:
http://blogs.dirteam.com/blogs/acefe...-adapters.aspx

--
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, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer

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

No, both NICs are internal... i can´t why the problem is ocurring since the
internals IPs registered with the same name. The clients can connecto with
both adapters and i don´t see no sense in "confusing" the DC with tow
internal valid address and relation with NetBIOS names in conflict with
itself.

IF Teaming is not possibel, maybe disabling on of the adapters, solve the
problem?

"Ace Fekay [MCT]" wrote:

> "FB" <> wrote in message
> news:B98EF8E1-B60D-4250-BAEB-...
> >
> > I have a Win2008 SP2 fully patched and running on a DELL PE 2950 with 4
> > NICs
> > (2 integrated broadcoms and 2 intel "off-board")
> >
> > Sometimes the server "hangs" and all SMB connections (only SMB/CIFS
> > connections are affected) stops. TS works well and in the EWvent Viewer
> > apper
> > a messages informing duplicate name on the network (event id 4319 and
> > 4343)
> > but there is no machine with the same name or the name of the domain.
> >
> > Is a DC and the 2 broadcom as enabled with diff. IP addressess and the 2
> > Intel are "disabled" (via device manager)
> >
> > DNS and WINS are Ok. I can access the share (\\servername) in the server
> > itself, but none of the machines in the network can access the mapped
> > letter,
> > the \\servername share. The only solution is to reboot
> >
> > what else i can do?
>
>
> You are saying this is a DC. Multihomed DCs cause problems. Also, multihomed
> DC cause problems with NetBIOS because of the multiple names for one IP,
> same with SMB.
>
> Follow the guideline in the following link to configure the domain
> controller. Otherwise, I would suggest to make it a single NIC or team the
> NICs, and make a member server multihomed to do whatever task you are trying
> to do with this DC and multiple NICs or IPs. I prefer to move it to another
> server instead of making all of these changes, including the registry
> changes.
>
> Multihomed DCs with DNS, RRAS, and/or PPPoE adapters:
> http://blogs.dirteam.com/blogs/acefe...-adapters.aspx
>
> --
> 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, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
> Microsoft Certified Trainer
>
> For urgent issues, please contact Microsoft PSS directly. Please check
> http://support.microsoft.com for regional support phone numbers.
>
>
>
>

"FB" <> wrote in message
news:87D3CDA8-4845-4AF9-876C-...
> No, both NICs are internal... i can´t why the problem is ocurring since
> the
> internals IPs registered with the same name. The clients can connecto with
> both adapters and i don´t see no sense in "confusing" the DC with tow
> internal valid address and relation with NetBIOS names in conflict with
> itself.
>
> IF Teaming is not possibel, maybe disabling on of the adapters, solve the
> problem?


Yes, disabling one of them is your best bet.

What brand and model NICs are they? If you find the driver from the vendor's
site, and if they are both of the same name brand and model, the
downloadable drivers will allow you to team them. Teaming provides the
ability to combine the two so they act as one with one IP address, as well
as load balance and fault tolerance if one of them were to go down.

Ace