Re: Remote Desktop to Internal Clients
From: Phillip Windell (_at_.)
Date: 10/21/04
- Previous message: Jack Pea***: "Re: Remote Desktop to Internal Clients"
- In reply to: Jack Pea***: "Re: Remote Desktop to Internal Clients"
- Next in thread: Phillip Windell: "Re: Remote Desktop to Internal Clients"
- Reply: Phillip Windell: "Re: Remote Desktop to Internal Clients"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 21 Oct 2004 14:53:01 -0500
Ok, <g>,...I understand, and agree...
It has been a real "soap box" of mine when it comes to complaining how the
whole SOHO/DSL/Cable/ISPs mess has butchered the dictionary over the last
couple years with thier terminology that has created an environment where
nobody knows what anybody means by what they say anymore.
It all began with the marketing choice to call these Cable/DSL boxes
"routers" instead of calling them [lightweight] Firewalls when they actually
more closely parallel the function of the more expensive NAT-based Hardware
Firewalls than they ever resemble a "real" router.
I remember when "IP Forwarding" meant enabling the "routing" function in
NT4.0 within the properties of TCP/IP on an interface, but now....when
somebody uses that term you have to ask them 15 questions before you think
you know what they think they might mean by it.
-- Phillip Windell [MCP, MVP, CCNA] www.wandtv.com "Jack Pea***" <pea***@simconv.com> wrote in message news:%23NL87A6tEHA.3392@TK2MSFTNGP10.phx.gbl... > "Phillip Windell" <@.> wrote in message > news:%23kEnA$2tEHA.376@TK2MSFTNGP09.phx.gbl... > > "Jack Pea***" <pea***@simconv.com> wrote in message > > news:eZRtsQvtEHA.3320@TK2MSFTNGP15.phx.gbl... > >> on the modem contact your ISP to change it to "bridge mode" (that's > > routing > >> only, no NAT) and have them give you the real IP address. > > > > Bridging is not routing. > > > No it isn't but when dealing with an ISP install tech they typically do not > distinguish between the two. The router option is often either NAT or > "bridge" on their installation order, so if you tell the ISP you want the > router to route they won't have a clue as to what you mean...so you get the > default setting of NAT. Sometimes it does not pay to be too precise. > > Yes in an ideal world the IP address is assigned to the firewall, not the > modem, but it can be very difficult to communicate that concept to the ISP. > > The local telephone company only supplies T1 lines with a router that is set > as a bridge (2 internet IPs if bridged, 1 internet and NAT if not). Nnless > you specifically request "bridging" you will get NAT, regardless of anything > else you tell the sales order drone. > Jack Pea*** > (who has just had a really bad day trying to explain to the *senior* ISP > tech the difference between synchronous and asynchronous serial, and that > two devices cannot communicate if the bit rates do not match...trying > unsuccessfully so far) > >
- Previous message: Jack Pea***: "Re: Remote Desktop to Internal Clients"
- In reply to: Jack Pea***: "Re: Remote Desktop to Internal Clients"
- Next in thread: Phillip Windell: "Re: Remote Desktop to Internal Clients"
- Reply: Phillip Windell: "Re: Remote Desktop to Internal Clients"
- Messages sorted by: [ date ] [ thread ]