Multihome Server


B

Brian

I have a multihome w2k server. Is there anyway to stop the logging of the
following message in the system log? Sure there is a duplicate name both nic
cards are in the same machine.

Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4319
Date: 6/30/2004
Time: 2:13:06 PM
User: N/A
Computer: SVR_DC2
Description:
A duplicate name has been detected on the TCP network. The IP address of
the machine that sent the message is in the data. Use nbtstat -n in a
command window to see which name is in the Conflict state.
 
Ad

Advertisements

P

Phillip Windell

The second Nic cannot be the same IP and should not be the same subnet in
most cases. Why does it have two Nics? What are you doing that requires it?

I'm about to leave for the day so I may not reply till tomorrow.
 
B

Brian

Each nic does have an different ip. One nic is set up for local traffic and
the other for vpn traffic.

Phillip Windell said:
The second Nic cannot be the same IP and should not be the same subnet in
most cases. Why does it have two Nics? What are you doing that requires it?

I'm about to leave for the day so I may not reply till tomorrow.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Brian said:
I have a multihome w2k server. Is there anyway to stop the logging of the
following message in the system log? Sure there is a duplicate name both nic
cards are in the same machine.

Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4319
Date: 6/30/2004
Time: 2:13:06 PM
User: N/A
Computer: SVR_DC2
Description:
A duplicate name has been detected on the TCP network. The IP address of
the machine that sent the message is in the data. Use nbtstat -n in a
command window to see which name is in the Conflict state.
 
P

Phillip Windell

Brian said:
Each nic does have an different ip. One nic is set up for local traffic and
the other for vpn traffic.

But are they different subnets? That won't cause the Dupe IP error, but it
still matters.

The error could be caused by a machine connecting by VPN that is being given
an IP# that is the same as one used on the LAN by another machine.

You need to verify exactly what IP# is in conflict here or we are just
shooting in the dark. Paste the "data" portion of the error in your reply.
It probably looks like a bunch of HEX numbers. If I am still here when you
reply, I'll try to respond once more before leaving for the day. I'll be
here for a few more minutes.
 
S

Steven L Umbach

Damn part timers. --- Steve

Phillip Windell said:
The second Nic cannot be the same IP and should not be the same subnet in
most cases. Why does it have two Nics? What are you doing that requires it?

I'm about to leave for the day so I may not reply till tomorrow.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Brian said:
I have a multihome w2k server. Is there anyway to stop the logging of the
following message in the system log? Sure there is a duplicate name both nic
cards are in the same machine.

Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4319
Date: 6/30/2004
Time: 2:13:06 PM
User: N/A
Computer: SVR_DC2
Description:
A duplicate name has been detected on the TCP network. The IP address of
the machine that sent the message is in the data. Use nbtstat -n in a
command window to see which name is in the Conflict state.
 
S

Steven L Umbach

Damn part timers. --- Steve

Phillip Windell said:
The second Nic cannot be the same IP and should not be the same subnet in
most cases. Why does it have two Nics? What are you doing that requires it?

I'm about to leave for the day so I may not reply till tomorrow.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Brian said:
I have a multihome w2k server. Is there anyway to stop the logging of the
following message in the system log? Sure there is a duplicate name both nic
cards are in the same machine.

Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4319
Date: 6/30/2004
Time: 2:13:06 PM
User: N/A
Computer: SVR_DC2
Description:
A duplicate name has been detected on the TCP network. The IP address of
the machine that sent the message is in the data. Use nbtstat -n in a
command window to see which name is in the Conflict state.
 
Ad

Advertisements

S

Steven L Umbach

Damn part timers. --- Steve

Phillip Windell said:
The second Nic cannot be the same IP and should not be the same subnet in
most cases. Why does it have two Nics? What are you doing that requires it?

I'm about to leave for the day so I may not reply till tomorrow.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Brian said:
I have a multihome w2k server. Is there anyway to stop the logging of the
following message in the system log? Sure there is a duplicate name both nic
cards are in the same machine.

Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4319
Date: 6/30/2004
Time: 2:13:06 PM
User: N/A
Computer: SVR_DC2
Description:
A duplicate name has been detected on the TCP network. The IP address of
the machine that sent the message is in the data. Use nbtstat -n in a
command window to see which name is in the Conflict state.
 
S

Steven L Umbach

Damn part timers. --- Steve

Phillip Windell said:
The second Nic cannot be the same IP and should not be the same subnet in
most cases. Why does it have two Nics? What are you doing that requires it?

I'm about to leave for the day so I may not reply till tomorrow.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Brian said:
I have a multihome w2k server. Is there anyway to stop the logging of the
following message in the system log? Sure there is a duplicate name both nic
cards are in the same machine.

Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4319
Date: 6/30/2004
Time: 2:13:06 PM
User: N/A
Computer: SVR_DC2
Description:
A duplicate name has been detected on the TCP network. The IP address of
the machine that sent the message is in the data. Use nbtstat -n in a
command window to see which name is in the Conflict state.
 
S

Steven L Umbach

Damn part timers. --- Steve

Phillip Windell said:
The second Nic cannot be the same IP and should not be the same subnet in
most cases. Why does it have two Nics? What are you doing that requires it?

I'm about to leave for the day so I may not reply till tomorrow.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Brian said:
I have a multihome w2k server. Is there anyway to stop the logging of the
following message in the system log? Sure there is a duplicate name both nic
cards are in the same machine.

Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4319
Date: 6/30/2004
Time: 2:13:06 PM
User: N/A
Computer: SVR_DC2
Description:
A duplicate name has been detected on the TCP network. The IP address of
the machine that sent the message is in the data. Use nbtstat -n in a
command window to see which name is in the Conflict state.
 
S

Steven L Umbach

Damn part timers. --- Steve

Phillip Windell said:
The second Nic cannot be the same IP and should not be the same subnet in
most cases. Why does it have two Nics? What are you doing that requires it?

I'm about to leave for the day so I may not reply till tomorrow.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Brian said:
I have a multihome w2k server. Is there anyway to stop the logging of the
following message in the system log? Sure there is a duplicate name both nic
cards are in the same machine.

Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4319
Date: 6/30/2004
Time: 2:13:06 PM
User: N/A
Computer: SVR_DC2
Description:
A duplicate name has been detected on the TCP network. The IP address of
the machine that sent the message is in the data. Use nbtstat -n in a
command window to see which name is in the Conflict state.
 
S

Steven L Umbach

Damn part timers. --- Steve

Phillip Windell said:
The second Nic cannot be the same IP and should not be the same subnet in
most cases. Why does it have two Nics? What are you doing that requires it?

I'm about to leave for the day so I may not reply till tomorrow.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Brian said:
I have a multihome w2k server. Is there anyway to stop the logging of the
following message in the system log? Sure there is a duplicate name both nic
cards are in the same machine.

Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4319
Date: 6/30/2004
Time: 2:13:06 PM
User: N/A
Computer: SVR_DC2
Description:
A duplicate name has been detected on the TCP network. The IP address of
the machine that sent the message is in the data. Use nbtstat -n in a
command window to see which name is in the Conflict state.
 
Ad

Advertisements

S

Steven L Umbach

Sorry about multi posts. Had a problem with OE with repeatedly sending posts claiming
failure to find server. --- Steve

Steven L Umbach said:
Damn part timers. --- Steve

The second Nic cannot be the same IP and should not be the same subnet in
most cases. Why does it have two Nics? What are you doing that requires it?

I'm about to leave for the day so I may not reply till tomorrow.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Brian said:
I have a multihome w2k server. Is there anyway to stop the logging of the
following message in the system log? Sure there is a duplicate name both nic
cards are in the same machine.

Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4319
Date: 6/30/2004
Time: 2:13:06 PM
User: N/A
Computer: SVR_DC2
Description:
A duplicate name has been detected on the TCP network. The IP address of
the machine that sent the message is in the data. Use nbtstat -n in a
command window to see which name is in the Conflict state.
 
S

Steven L Umbach

Damn part timers. --- Steve

Phillip Windell said:
The second Nic cannot be the same IP and should not be the same subnet in
most cases. Why does it have two Nics? What are you doing that requires it?

I'm about to leave for the day so I may not reply till tomorrow.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Brian said:
I have a multihome w2k server. Is there anyway to stop the logging of the
following message in the system log? Sure there is a duplicate name both nic
cards are in the same machine.

Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4319
Date: 6/30/2004
Time: 2:13:06 PM
User: N/A
Computer: SVR_DC2
Description:
A duplicate name has been detected on the TCP network. The IP address of
the machine that sent the message is in the data. Use nbtstat -n in a
command window to see which name is in the Conflict state.
 
S

Steven L Umbach

Damn part timers. --- Steve

Phillip Windell said:
The second Nic cannot be the same IP and should not be the same subnet in
most cases. Why does it have two Nics? What are you doing that requires it?

I'm about to leave for the day so I may not reply till tomorrow.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Brian said:
I have a multihome w2k server. Is there anyway to stop the logging of the
following message in the system log? Sure there is a duplicate name both nic
cards are in the same machine.

Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4319
Date: 6/30/2004
Time: 2:13:06 PM
User: N/A
Computer: SVR_DC2
Description:
A duplicate name has been detected on the TCP network. The IP address of
the machine that sent the message is in the data. Use nbtstat -n in a
command window to see which name is in the Conflict state.
 
S

Steven L Umbach

Damn part timers. --- Steve

Phillip Windell said:
The second Nic cannot be the same IP and should not be the same subnet in
most cases. Why does it have two Nics? What are you doing that requires it?

I'm about to leave for the day so I may not reply till tomorrow.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Brian said:
I have a multihome w2k server. Is there anyway to stop the logging of the
following message in the system log? Sure there is a duplicate name both nic
cards are in the same machine.

Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4319
Date: 6/30/2004
Time: 2:13:06 PM
User: N/A
Computer: SVR_DC2
Description:
A duplicate name has been detected on the TCP network. The IP address of
the machine that sent the message is in the data. Use nbtstat -n in a
command window to see which name is in the Conflict state.
 
P

Phillip Windell

Yea, blame it on the software! Likely
storey..story..storey..storey..storey..Opps! sorry the keyboard must have
stuck :)


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Steven L Umbach said:
Sorry about multi posts. Had a problem with OE with repeatedly sending posts claiming
failure to find server. --- Steve

Steven L Umbach said:
Damn part timers. --- Steve

The second Nic cannot be the same IP and should not be the same subnet in
most cases. Why does it have two Nics? What are you doing that requires it?

I'm about to leave for the day so I may not reply till tomorrow.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


I have a multihome w2k server. Is there anyway to stop the logging of the
following message in the system log? Sure there is a duplicate name both
nic
cards are in the same machine.

Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4319
Date: 6/30/2004
Time: 2:13:06 PM
User: N/A
Computer: SVR_DC2
Description:
A duplicate name has been detected on the TCP network. The IP address of
the machine that sent the message is in the data. Use nbtstat -n in a
command window to see which name is in the Conflict state.
 
Ad

Advertisements

J

Jeff Whitehead

This is not a Dupe IP issue though... merely a dupe machine name problem
(unless I've misread).

I had a similar problem with WINS registering both adapters on the same WINS
server... someone configured the NICs incorrectly, pointing them both to the
same WINS server on one of the subnets. (Actually they then compounded it by
adding a static mapping in the WINS DB too). This gave us the same message.

Not sure if this applies to you?
 
P

Phillip Windell

Yea, it did say duplicate name and not IP#, I did miss that. Yes, I have
seen the same issue with WINS. But I thought I have had duel-homed machine
using the same WINS from both interfaces and didn't have a problem as long
as I didn't screw around with it, but I don't have any like that now to test
with and so I not sure if I remember the situation properly.

But anyway, the IP# of the offending machine is still encoded in the Data of
the error if he ever sends us that. With the IP# he will know what to look
at.
 
Ad

Advertisements

L

Leythos

Sorry about multi posts. Had a problem with OE with repeatedly sending posts claiming
failure to find server. --- Steve

Steve, get something like Gravity news reader, it's a real news reader
and you won't have those problems. OE has been a pain for Usenet since
it came out.

Now, don't get the wrong idea, I spec only MS systems, but I've been on
Usenet since the early 80's and in all the time I've never found
anything better than Gravity for Usenet.
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top