Re: OK..I get it...no STATIC NAT....so please help me

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

You are correct about the Voip traffic (it is SIP). That server is located
on the same segment as the ISA server. It appears the the phone installers
have the VOIP traveling over the T1's, so no problem there. I'm still not
sure how to "assign" a public IP address to our AS400 (at our Indiana site)to
allow our remote offices access. Is an additional ISA server necessary since
it appears the VOIP traffic is being handled?
Thanks for your assistance
John

"Phillip Windell" wrote:

Looking back over your post, a "quickie" response would be that you would:
1. place an ISA at each site.
2. Set up a Site-to-Site VPN (aka Router-to-Router VPN) between the two
ISAs
3. Do anything and everything you want to do over the VPN which would be a
sheltered private link.

The VPN is about the only way VoIP is going to work between the two offices.
VoIP most likely uses SIP and SIP cannot be "proxied", but should be fine
over the VPN which is a normal "routed" connection.

Access Rules on the two ISAs will control Access between the two sites. It
will not be "wide open" to start with,...you will have to specifically allow
the traffic you want. I'm not quite sure about the VoIP concerning Access
Rules.

I can't say more without knowing more details,...I'm kinda "pushing it" now.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com




"Phillip Windell" <@.> wrote in message
news:O6zxBS%236GHA.4304@xxxxxxxxxxxxxxxxxxxxxxx
Need more clarification.

If only the Chicago Office has internet access,...then how are you going
to connect the two offices together? Are there private Leased Lines that
have nothing to do with the Internet connecting the two sites?


--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------



"John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9338CD82-4CAD-47F1-840E-39BE7559DABC@xxxxxxxxxxxxxxxx
We are currently changing servce providers. The new service will give us
a
6Mb connection in our chicago office with a 3Mb connection to our Indiana
office. The chicago office is the only one with internet access, so all
traffic will be routed through Chicago. VOIP will also be running over
these
connections. We have an ISA 2004 SP2 server we want to use on the border
of
the chicago office and the internet. My problems are:
1. I have an IBM AS400 in our Indiana office that remote offices
need
access to. In the past, we just configured a static route on our cisco
router. I'm not sure how to do this now. I'm sort of new with ISA so
this
may be an easy question.
2. Our Exchange Server is located in the Indiana office. With this
cause a problem since it is not on the same segment as the ISA server?
3. Will the ISA server need any special configuration for VOIP??
Any help would be appreciated!!

Thanks
John





.

Relevant Pages

  • Re: H.323 Gatekeeper errors
    ... aren't using telephony I would disable the 323 filter in ISA. ... >> Are you trying to run VOIP through an ISA server? ... >> Frank McCallister ...
    (microsoft.public.windows.server.sbs)
  • Re: CEICW fails - several errors
    ... On the WAN NIC of your server the DNS has to point to the LAN IP. ... Ethernet adapter Internet Connection: ... I immediately checked and ISA Server ... Management said that Web Proxy, Firewall and ...
    (microsoft.public.windows.server.sbs)
  • Re: Help with ISA 2000 / Load balancing router requested - Thanks.
    ... I have a load balancing router that will load balance two connections quite ... happily but then I have two different proxy servers that I ... connection that the load balancing router is using. ... My understanding is that ISA server 2000 Standard Edition won't load balance ...
    (microsoft.public.isa)
  • Re: Site to site VPN failure > LinkSys DSL Gateway AG241 to ISA 2004 S
    ... > Also, this doesn't look like an IPSec/L2TP connection, rather a PPTP ... >> Application logs on the ISA Server ... you can view details in the packet filter log. ... >> 202.89.62.82 External Local Host Establish 0x0 Allow VPN client traffic ...
    (microsoft.public.isa.vpn)
  • RE: Site to site VPN failure > LinkSys DSL Gateway AG241 to ISA 2004 S
    ... Also, this doesn't look like an IPSec/L2TP connection, rather a PPTP ... > Application logs on the ISA Server ... you can view details in the packet filter log. ... > 202.89.62.82 External Local Host Establish 0x0 Allow VPN client traffic to ...
    (microsoft.public.isa.vpn)