Re: Why can't internal clients access a published TCP server?
- From: "Jim Harrison" <jim@xxxxxxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Sat, 15 Dec 2001 09:26:03 -0800
The problem is that your asking ISA to do something it knows is unnecessary;
something I like to call "isotropic IP bounce".
What's the point of sending a packet from the living room, through the mudroom
and out the front door to reach a kitchen that was only a few steps away?
Proper internal name resolution, LDT and LAT configuration and you don't need
this kind of "functionality".
Here's an article that'll help you 'round the bend, as it were...
http://support.microsoft.com/support/kb/articles/Q288/3/96.ASP
ISA doesn't do anything out of the ordinary where the rules of routing and
TCP/IP are concerned and will complain loudly when it's asked to.
Jim Harrison
MCP(NT4, W2K), A+, Network+, PCG
http://isaserver.org/authors/harrison/
Read the book!
----- Original Message -----
From: Wendell W. Pinegar
To: [ISAserver.org Discussion List]
Sent: Saturday, December 15, 2001 02:44
Subject: [isalist] Why can't internal clients access a published TCP server?
http://www.ISAserver.org
We've configured ISA Server with several published TCP ports to internal
servers. Connections to the published TCP ports works perfectly fine when
connecting from clients on the Internet but if I attempt to connect to the IP
address and TCP port # of the published server from inside the network the
connection always fails.
What gives? Does ISA Server have a problem connecting internal users to
published TCP ports on it's external interface?
(Of course I can connect the internal users to the internal address of the
TCP server and all goes well, but I due to several reasons I would prefer to
connect them to the published IP address on the Internet). Anyone have a clue
what's wrong?
Thanks!
Wendell W. Pinegar
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
jim@xxxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
Other related posts:
