Re: ISA Is Driving Me Insane!
- From: "Asher_N" <ashernat@xxxxxxxxx>
- Date: Tue, 02 Jan 2007 07:30:06 -0800
Not a whole lot of difference. It's still PPP protocol, but runs on ATM
instead of Ethernet. Is about 0.5% less overhead that PPPoE. It's still
an authenticated 'home' type of setup. You really want a non-
authenticated, true fixed IP setup.
"AndyJ" <andyjones99@xxxxxxxxxxxxx> wrote in
news:1167473973.975575.194320@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:
I juts checked my router/modem and I am using PPPoA not PPPoE
AJ
AndyJ wrote:
Interesting, so what about PPPoA? is that the same. I just spoke to
another ISP in my area and they only provide PPPoA connections.
Regarding timeouts I have had no problems that I have noticed to date
regarding this and I host my own website and Exchange email servers -
I guess thats not to say I wont have though!
Thanks for your input regarding this
AJ
Asher_N wrote:
"Lei Hu" <lei@xxxxxxxxxx> wrote in
news:uRfsCDdKHHA.420@xxxxxxxxxxxxxxxxxxxx:
Why should we avoid PPPoE like plague? What problems will it
cause? From memory, isa does support PPPoE auto dial, so they
should work together well. I've read some of your replies in this
group, but failed to find any detailed explanation. Can you give
a bit more detailed explanation for newbies like me? Thanks.
For starters, PPPoE was designed to allow ISP to switch to
broadband with no changes to their network and Radius
authentication schemes. There is a 5-10% overhead associated with
PPPoE.
Because it was designed with the dial-up home user infrastructure
in mind, it is also implemented with inactivity timeouts. For a
home user, that is not a problem as the 'dial-up' and
authentication usually takes only a few seconds, and in a home user
situation, the user ALWAYS initiates the connection. Most SOHO NAT
devices will send a regular 'keep-alive' packet to the ISP to
simulate activity and prevent the disconnect. It is only somewhat
effective.
In a business environment, you need that connection open all the
time to receive inbound requests (e-mail, published web sites,
etc.) For that reason, the 'keep alive' failing even once in a
while is not an acceptable solution.
"Phillip Windell" <@.> wrote in message
news:OrbqTJbJHHA.1252@xxxxxxxxxxxxxxxxxxxxxxx
You could start saving yourself a bunch of greif by ditching the
ADSL "router".
Plug the ADSL Modem directly into the External Nic of the ISA.
Make sure the Public IP# is static and the ISA's nic simply
takes over the IP Specs that the external side of the "router"
used to have. If the ISP does not have a static IP for you then
get one from them. You're paying them for a service, make them
earn it, don't let them give you any crap about it.
Also avoid PPPoE like the Plague,...PPPoE is for Home
Users,...it is not meant for commercial environments.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
The views expressed are my own (as annoying as they are), and
not those of my employer or anyone else associated with me.
-----------------------------------------------------
"AndyJ" <andyjones99@xxxxxxxxxxxxx> wrote in message
news:1166735436.665206.260110@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
All working again. Don't ask me how though!!!
AndyJ wrote:
I have been trying to solve this issue for ages now and I am
failing miserably, its driving me insane. One minute I have it
working and I make a change for something else and it breaks
again!
Here is my problem.
I have an ISA server configured in a 3 legged configuration so
I have an external NIC which plugs into a ADSL Router, a
perimeter network and my internal network. All network
segments have a private address range and the router does my
natting. I am trying to get all my published servers on the
perimeter network.
So far I have OWA and EAS working via a web publishing rule, I
publish the Front-End server in the perimeter network. However
I cannot seem to get my server publishing rule working which
publishes the front end server for SMTP.
I have an access rule which allows SMTP traffic from the
perimeter network into the internal network and a rule which
lets SMTP traffic from the external network into the
perimeter. However whatever I try I still see SMTP traffic
getting denied by the default rule.
I thought I solved this earlier on by adding some network
rules, but since I don't really understand exactly what I did
I am back to square one.
Can someone please help me out here!
Thanks
AJ
.
- Follow-Ups:
- Re: ISA Is Driving Me Insane!
- From: AndyJ
- Re: ISA Is Driving Me Insane!
- Next by Date: Re: ISA Is Driving Me Insane!
- Next by thread: Re: ISA Is Driving Me Insane!
- Index(es):
Relevant Pages
|
