ping to local machine name with 2 network cards

  • Thread starter Thread starter Daniel
  • Start date Start date
D

Daniel

Hello

I've a Win2000 Server with 2 Networkcards, lets call them Interface 1
and Interface 2. Interface 1 has static IP and Interface 2 has DHCP. The
name of the machine is XY and is in domain workgroup.
to ping the machine from both interfaces i can call "ping XY" and i got
answer vom the responsiple interface with his IP.
When I now call "ping XY" from the command line of the server i get
always response from Interface 1. Why I get answer from this one and not
from the other one? And how can I change the Interface which answers?

thanx
 
Netbios can only bind to 1 interface at a time and this will never be
consistent. That is why you do not want to multihome(multiple NICs) your
WINS servers. What are trying to do? What is the reason for the 2 nics? Is
this machine a router?

--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

scrockel@***No_SPAM***hotmail.com
 
What are trying to do? What is the reason for the 2 nics? Is
this machine a router?

yes this machine acts as router. on nic2 is a "normal" entrprise lan and
on nic1 is a lan of a bigger machine. On win2k server a server
application is running where a local DNS (by CORBA) gives access to the
server application.
if now a client from the internal lan (nic1) tries to acces to the
server application its possible because the returned IP is thisone of
nic1. If a client tries to acces to the server application the returned
IP is also thisone of nic1 but it should be the IP of nic2. because then
the client is on nic2 side and can't use the IP of nic1.
 
In
Daniel said:
yes this machine acts as router. on nic2 is a "normal" entrprise lan
and on nic1 is a lan of a bigger machine. On win2k server a server
application is running where a local DNS (by CORBA) gives access to
the server application.
if now a client from the internal lan (nic1) tries to acces to the
server application its possible because the returned IP is thisone of
nic1. If a client tries to acces to the server application the
returned IP is also thisone of nic1 but it should be the IP of nic2.
because then the client is on nic2 side and can't use the IP of nic1.

DNS does this by default, it is called subnet prioritizing. Look that up in
DNS help for an explanation on how it works. But basically it gives the IP
out based on the closest subnet address match.
To work the most effectively you two subnets should be in completely
different subnet ranges, i.e. 192.168.x.x, 172.16.x.x and 10.x.x.x.
 
Kevin said:
DNS does this by default, it is called subnet prioritizing. Look that up in
DNS help for an explanation on how it works. But basically it gives the IP
out based on the closest subnet address match.
To work the most effectively you two subnets should be in completely
different subnet ranges, i.e. 192.168.x.x, 172.16.x.x and 10.x.x.x.

on nic1 we have 10.128.x.x/255.255.0.0 (thisone is always returned) and
on nic2 10.10.x.x/255.255.192.0.
To the inquiry from the 10.10.x.x side, the answer is 10.128.x.x. But I
think the subnet mask on nic1 should be 255.255.192.0 too.

thanx a lot, i know now where to search for the error.
 
Change the binding order of the NICs may do this but is not guaranteed to do so. To do this, right click on My Network Places
and choose properties. Click on the Advanced Menu and choose Advanced Settings. In the Binding order section, put the NIC
you'd like to respond at the top of the list.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.
 
Daniel said:
on nic1 we have 10.128.x.x/255.255.0.0 (thisone is always returned) and
on nic2 10.10.x.x/255.255.192.0.
To the inquiry from the 10.10.x.x side, the answer is 10.128.x.x. But I
think the subnet mask on nic1 should be 255.255.192.0 too.

thanx a lot, i know now where to search for the error.

Yes, it seems that both NICs are on the same subnet due to the mask. If you
change it to 255.255.192.0, it may work. It may also not work, I have to
work out the bits to see, but pretty sure it will work. If it doesn't work,
try changing the second subnet to 192.168.5.0/255.255.255.0. That will
guarantee to work. ALso make sure routing is enabled between the NICs.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Michael said:
Change the binding order of the NICs may do this but is not guaranteed to do so. To do this, right click on My Network Places
and choose properties. Click on the Advanced Menu and choose Advanced Settings. In the Binding order section, put the NIC
you'd like to respond at the top of the list.

this helped and was finally the only thing that we had to change.
thanks a lot.
Regards,
Daniel
 
Back
Top