Re: one way or two way

"Ramon Niese" <ramon@xxxxxxxxxxx> wrote in message
news:u0$xkrDVIHA.5508@xxxxxxxxxxxxxxxxxxxxxxx
Can anyone explain me this error?

A packet generated on the local host was rejected because its source IP
address is assigned to one network adapter and its destination IP address
is reachable through another network adapter.

If a machine has two nics in two different subnets and a packet is destined
for a particular destination,...then the Routing Table is used to determine
the proper Source Nic (source IP#) to have the packet "leave from" in order
to be routed correctly.

If you somehow "force" the Source Nic to be the other Nic then it will fail.
That is what the error says is happening. The Source Nic (source IP#) must
be allowed to be "dynamically" chosen based on the routing table (not
"forced"). For example: a packet destined for a subnet that is not a subnet
that the source machine is a member of will always be assigned the source
IP# of the Primary IP# of the Nic that posseses the Default Gateway,...hence
only one Default Gateway is allowed per machine.

Additional Gateways can be added but they need to all be within the same
subnet and all be listed on the same Nic which allows the same Source IP# to
be used no matter what. These will be used in a Dead Gateway Detection
situation.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/download/9/1/8/918ed2d3-71d0-40ed-8e6d-fd6eeb6cfa07/ts_rules.doc

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Microsoft ISA Server Partners: Partner Hardware Solutions
http://www.microsoft.com/forefront/edgesecurity/partners/hardwarepartners.mspx
-----------------------------------------------------


.

Relevant Pages

  • Re: FC1 multiple ethernet interface issue
    ... >> addressing you are using and says the new interface has the same ... Look at the packet stats ifconfig ... All of the systems I have used that had multiple NICs were configured ... Since both NICs are in the same subnet you are going to end up with a ...
    (Fedora)
  • RE: Transfer a sending packet to upper TCP/IP protocol layer in IM
    ... source and destination MAC addresses are the same for both IP versions. ... the destination NIC of IPv6 packet is the same as the destination NIC of my ... encapped IPv4 packet. ...
    (microsoft.public.development.device.drivers)
  • Re: TOE brain dump
    ... primarily over ATMish core networks. ... "if you can't find header address ... the flow, if you can find a VC from cache, send the packet there" ... destination node address selector bits in header, ...
    (Linux-Kernel)
  • RE: Transfer a sending packet to upper TCP/IP protocol layer in IM
    ... the destination NIC of IPv6 packet is the same as the destination NIC of my ... encapped IPv4 packet. ... you should clearly realize that emulating non-existent IPv6 ...
    (microsoft.public.development.device.drivers)
  • Re: [SLE] Looking for info on setting up a packet sniffer
    ... > I have a SuSE 9.0 Pro machine set up with a pair of NICs that I need to ... > Firebox sitting on RoadRunner's residential cable network. ... > also open to suggestions on what other packet sniffing utilities might ...
    (SuSE)