Re: Multihomed Terminal Server
"nhance" <nhance@discussions.microsoft.com> wrote in message
news:CFC6189E-0F99-465A-A302-22E8671DC82B@microsoft.com...
> The thing with posting on these sites is to request some support and draw
> on
> the collective knowlege of all contributors. Many times the concept is
> know
> but the details fuzzy, out of the replies i am still not getting a result.
> Can somone please confirm my steps and advise if i am wrong as i am 12hrs
> difference and i need to get this resolved asap.
I'm sorry, ...you're getting the results of your post, I'm afraid it just
isn't what you want to hear.
You can *NOT* have two "Internet" nics,...period. The Internet, by the very
fact of what it is,..is an "unknown" destination (0.0.0.0),...therefore is
handled only by the Default Gateway and there can be only *one* functioning
Default Gateway at a time.
Concering the nic it "comes from"....
Traffic always shows comming from the Primary IP# of the Nic that matches
the Route found in the Routing table which is determined by the Destination.
For the Internet this is always the 0.0.0.0 Route (the Default Route) and
will always show comming from the Nic with the Default Gateway and if that
nic has more than one IP# then it will always be the Primary IP#. The IP#
(and/or Nic) that the traffic was originally received on is completely and
totally irrelevant.
You have a flawed network design based on flawed theory. In a correct
design this server would have only one nic.
Concerning other routing matters,... You get more bandwidth by getting a
faster line,...you don't get more bandwidth by adding another Line, that is
one of the flaws in your theory. The second flaw might be that this is
RDP,..which has very *low* bandwidth requirements and doesn't need a new
line just for it. What a second Line gets you is more Routes or more Routing
Options,...or more often just more Routing Confusion. The only gain in
Bandwith comes from moving some of the traffic over to the second Line to
free up bandwidth on the first,...*BUT* that only works when the environment
and the topology have been properly designed for it and,...this is very
important,...you approach it with the right expectations for the right
reasons. It typically does not work for inbound traffic, or at least is a
whole lot more complicated and limited in options because of the "response"
to the traffic not following the same path (which appears to be your
problem).
I am speaking from experience.
At our place we have:
2 DSL lines
1 CableTV internet line
1 commercial grade connection built from 2 T1 lines that are "merged"
These all have different purposes, but they all work with the same company
LAN, and they all work perfectly with no problems.
My Terminal Server has only one Nic.
We are a TV Station with equipment that causes heavy bandwith usage to the
outside. So I divide up that equipment into groups of similar or related
purposes and configure each "group" to use a particular "internet
connection". In most cases the Destination is "specific" so the Routing can
be handled by our LAN Router to move the traffic to the correct connection.
If the desitnation is "not specific" then the equipment must be in the
correct subnet to use the chosen "internet connection" as its default
gateway (that's the correct topology stuff I mentioned) while using local
static routes to deal with the rest of the LAN's segments.
So now when I get to the Terminal Server, I have it just use the "normal"
main internet connection for the LAN because I have plenty of bandwidth due
to how I moved the other equipment to use specific dedicated connections for
what they do.
--
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.
-----------------------------------------------------