Re: Hey Jim! Need to find an article on "isaserver.org" but can find it

From: Phillip Windell (_at_.)
Date: 03/05/04 

Date: Fri, 5 Mar 2004 09:10:55 -0600

It was the MAC address that became the problem, not the IP address. Both the
source MAC and the destination MAC were identical in the packet header
causing it to fail. The article is over a year old. The last time I lost it
Jim Harrison gave the link in a heartbeat and knew exactly what I was asking
about with very little description. I used it in posts several times,
.....and appearantly lost it an equal number of times. I had a list of links
to ISA articles stored in a text file that was lost during a machine
rebuild.

It had to do with internal users accessing internal resources by trying to
go through the publishing of the proxy (effectively a "u-turn") to get there
rather than just going directly to the resource as they should have done. It
created a situation where the MAC address of the ISA's external NIC was
listed in both the Source and Destination field of the Layer2 (not 3) Header
in the packet. That is as specific as I can be. 

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"Tony Su" <anonymous@discussions.microsoft.com> wrote in message
news:73ac01c4026d$39ed4b80$a501280a@phx.gbl...
> FYI -  I have not had any problem connecting to a
> published resource through ISA with the resource on the
> same Host machine, thereby the source and destination have
> the same IP address... so I doubt there is an issue
> without possibly more parameters. Maybe if you were more
> specific about a situation, the problem can be replicated.

Relevant Pages

  • Re: Problem with etherchannel between 2 3550 FXs
    ... :I have a 3550's in different buildings with ~2km of multimode fiber between ... and destination MAC addresses. ... of the final bits of each of the source and destination ... You get to choose which logical operation you want, ...
    (comp.dcom.sys.cisco)
  • Re: Problem with etherchannel between 2 3550 FXs
    ... > and destination MAC addresses. ... > of the final bits of each of the source and destination ... > You get to choose which logical operation you want, ... > provided you aren't fragmenting packets; ...
    (comp.dcom.sys.cisco)
  • Re: A lesson on why Windows dominates computing...
    ... >> Still no documentation from you about how long the Mac used DLLs, ... > Not to mention AmigaOS had resource management inherent it's design ... "If you raise the ceiling 4 feet, move the fireplace from that wall ...
    (comp.sys.mac.advocacy)
  • Re: ARP requests on my net?
    ... But my machine is not configured to be a router, bridge, or gateway. ... But why would it need the MAC for the router? ... my machine is the destination IP. ... only for passing along to another device closer to the destination ...
    (Fedora)
  • Re: Ip forwarding
    ... Packets that are meant to be forwarded by a router must be sent to its MAC address on the link. ... The gateway column optionnally contains the address of the next hop router if the destination is not directly reachable on the network attached to the output interface. ... In both cases the packet is sent on the link to the next hop MAC address. ...
    (comp.os.linux.networking)
Quantcast