RE: pinging servers

[Brad DeHart]

From the Advanced tab of Network Connections, choose Advanced Settings and 
compare the order in the Connections pane.  I'm betting they are swapped on 
your servers.


Brad DeHart
Senior Network Systems Administrator
Kern Health Systems

-Original Message-
From: DAVID SMITH [mailto:davidsm...@dritz.com]
Sent: Wednesday, August 18, 2010 11:11 AM
To: NT System Admin Issues
Subject: pinging servers

I have 2 servers that are identical that has 2 network ports.  Both of the 
servers have their local connection plugged into port 1 and their back network 
plugged into port 2.  When you ping the server name on these servers, one 
server replies back with the local area connection and the other replies back 
with the back network.  Why is this?
~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
  ~

Kern Health Systems Confidentiality Statement:

This email and any attachments are legally privileged and can contain business 
proprietary and/or confidential information intended for a specific individual 
and purpose. This information is intended only for the use of the individual or 
entity named above. The authorized recipient of this information is prohibited 
from disclosing this information to any other party unless required to do so by 
law or regulation and is required to destroy the information after its stated 
need has been fulfilled.

If you are not the intended recipient, you are hereby notified that any 
disclosure, copying, distribution, or action taken in reliance on the contents 
of these documents is strictly prohibited. If you have received this 
information in error, please notify the sender immediately and arrange for the 
return or destruction of these documents.

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

Re: pinging servers

[Ben Scott]

On Wed, Aug 18, 2010 at 5:52 PM, Ziots, Edward  wrote:
> Local Network is the Public facing network taking the traffic
> from the users, and the Back network ( is setup for backups
> and other system administration to happen on).

  My assumption was something along those lines, but we all know about
assumptions.  Better to get the idea explicitly.

-- Ben

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

RE: pinging servers

[Ziots, Edward]

Local Network is the Public facing network taking the traffic from the users, 
and the Back network ( is setup for backups and other system administration to 
happen on). 

I have done this type of stuff in the past for those that want to have certain 
traffic go over 1 NIC ( or set of NIC's) and access for general users over 
another NIC. 

Usually don't register the Private ( Back Network NIC's IP) in DNS or WINS 
accordingly. We would put static entries in DNS accordingly in a special zone 
which the backup software was to look at for resolution accordingly. That and 
tight ACL's that only the backup server IP could even talk to that port, and 
the appropriate firewall rules set on the server to allow the backup software 
and only that to run. 

Z

Edward E. Ziots
CISSP, Network +, Security +
Network Engineer
Lifespan Organization
Email:ezi...@lifespan.org
Cell:401-639-3505


-Original Message-
From: Ben Scott [mailto:mailvor...@gmail.com] 
Sent: Wednesday, August 18, 2010 4:40 PM
To: NT System Admin Issues
Subject: Re: pinging servers

On Wed, Aug 18, 2010 at 2:11 PM, DAVID SMITH  wrote:
> I have 2 servers that are identical that has 2 network ports.

  As ASB points out, they're obviously not identical, or you'd be
getting identical results.

>  Both of the servers have their local connection plugged
> into port 1 and their back network plugged into port 2.

  What do you mean by "local connection" and "back network"?

> When you ping the server name on these servers, one
> server replies back with the local area connection and
> the other replies back with the back network.

  You can't really ping a name, only an IP address.  If you give ping
a name, it looks up an IP address.  The first thing to do is to see
which IP address ping is lookup up.  That will tell you if the
difference is in name resolution or some network layer thing.

  A comment on name resolution that may be applicable: In general, if
a name has multiple IP addresses associated with it, you shouldn't
depend on those IP addresses being given in any particular order.

-- Ben

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Re: pinging servers

[Ben Scott]

On Wed, Aug 18, 2010 at 2:11 PM, DAVID SMITH  wrote:
> I have 2 servers that are identical that has 2 network ports.

  As ASB points out, they're obviously not identical, or you'd be
getting identical results.

>  Both of the servers have their local connection plugged
> into port 1 and their back network plugged into port 2.

  What do you mean by "local connection" and "back network"?

> When you ping the server name on these servers, one
> server replies back with the local area connection and
> the other replies back with the back network.

  You can't really ping a name, only an IP address.  If you give ping
a name, it looks up an IP address.  The first thing to do is to see
which IP address ping is lookup up.  That will tell you if the
difference is in name resolution or some network layer thing.

  A comment on name resolution that may be applicable: In general, if
a name has multiple IP addresses associated with it, you shouldn't
depend on those IP addresses being given in any particular order.

-- Ben

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

RE: pinging servers

[Erik Goldoff]

Bet you'll find different default gateways, try a ROUTE PRINT and see what you 
can see ...
Or worse, maybe you have a default gateway set on BOTH adapters 


Erik Goldoff
IT  Consultant
Systems, Networks, & Security 

'  Security is an ongoing process, not a one time event ! '



-Original Message-
From: DAVID SMITH [mailto:davidsm...@dritz.com] 
Sent: Wednesday, August 18, 2010 2:11 PM
To: NT System Admin Issues
Subject: pinging servers

I have 2 servers that are identical that has 2 network ports.  Both of the 
servers have their local connection plugged into port 1 and their back network 
plugged into port 2.  When you ping the server name on these servers, one 
server replies back with the local area connection and the other replies back 
with the back network.  Why is this?
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

Re: pinging servers

[Andrew S. Baker]

I'l bet that they're not really as identical as you think.

Where are you pinging from?

Are both addresses in AD/DNS?   What are the bindings for both NICs on both
servers?



*ASB *(My XeeSM Profile) 
*Exploiting Technology for Business Advantage...*
* *
Signature powered by WiseStamp 


On Wed, Aug 18, 2010 at 2:11 PM, DAVID SMITH  wrote:

> I have 2 servers that are identical that has 2 network ports.  Both of the
> servers have their local connection plugged into port 1 and their back
> network plugged into port 2.  When you ping the server name on these
> servers, one server replies back with the local area connection and the
> other replies back with the back network.  Why is this?
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~