Re: SOT: name resultion

2011-04-19 Thread Al Rose
In that case sounds like you may need to use RPC over https and open port 80
on your firewall for the front-end server

On Mon, Apr 18, 2011 at 7:32 PM, Jean-Paul natola jnat...@hotmail.comwrote:


 Hi all,

 I feel i'm overlooking the obvious but my brain just went into lock, how do
 I go about having a client connect to an alternate server ip?

 Scenario;

 Remote office is connected to HQ via VPN, they open outlook or owa and it
 resolves to the internal IP of exchange,
 now the tunnel is broken for  whatever reason , so now when they attempt to
 connect to exchange (with out the VPN tunnel in place) they obviously
 cannot.

 So is the solution  as sample as ONLY using the the external IP in the
 remote offces, and what impact will this have on bandwidth?

 Some offices are on VSAT and only have 256k

 TIA




 ---
 To manage subscriptions click here:
 http://lyris.sunbelt-software.com/read/my_forums/
 or send an email to listmana...@lyris.sunbeltsoftware.com
 with the body: unsubscribe exchangelist


---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

RE: SOT: name resultion

2011-04-19 Thread Jean-Paul natola

So basically  , if i am understanding correctly, you are saying to delete the 
DNS record at the remote offices for the internal IP of the exchange server, 
and recreate the record with the public IP, so that the clients will ALWAYS go 
outside the network to access exchange using outlook anywhere (rpc over https) 
as opposed to having them connect as LAN  clients?
 
The reason I was trying to avoid this is because bandwidth is very limited in 
some offices and I was trying to conserve as much as possible, that being said  
, are there any stats on using outlook in LAN mode, vs RPC?



 


Date: Tue, 19 Apr 2011 13:06:38 +0200
Subject: Re: SOT: name resultion
From: arose...@gmail.com
To: exchangelist@lyris.sunbelt-software.com

In that case sounds like you may need to use RPC over https and open port 80 on 
your firewall for the front-end server


On Mon, Apr 18, 2011 at 7:32 PM, Jean-Paul natola jnat...@hotmail.com wrote:



Hi all,
 
I feel i'm overlooking the obvious but my brain just went into lock, how do I 
go about having a client connect to an alternate server ip?
 
Scenario;
 
Remote office is connected to HQ via VPN, they open outlook or owa and it 
resolves to the internal IP of exchange,
now the tunnel is broken for  whatever reason , so now when they attempt to 
connect to exchange (with out the VPN tunnel in place) they obviously cannot.
 
So is the solution  as sample as ONLY using the the external IP in the remote 
offces, and what impact will this have on bandwidth?
 
Some offices are on VSAT and only have 256k
 
TIA 
 




---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist 
  
---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

Re: SOT: name resultion

2011-04-19 Thread Kurt Buff
443

On Tue, Apr 19, 2011 at 04:06, Al Rose arose...@gmail.com wrote:
 In that case sounds like you may need to use RPC over https and open port 80
 on your firewall for the front-end server

 On Mon, Apr 18, 2011 at 7:32 PM, Jean-Paul natola jnat...@hotmail.com
 wrote:

 Hi all,

 I feel i'm overlooking the obvious but my brain just went into lock, how
 do I go about having a client connect to an alternate server ip?

 Scenario;

 Remote office is connected to HQ via VPN, they open outlook or owa and it
 resolves to the internal IP of exchange,
 now the tunnel is broken for  whatever reason , so now when they attempt
 to connect to exchange (with out the VPN tunnel in place) they obviously
 cannot.

 So is the solution  as sample as ONLY using the the external IP in the
 remote offces, and what impact will this have on bandwidth?

 Some offices are on VSAT and only have 256k

 TIA




 ---
 To manage subscriptions click here:
 http://lyris.sunbelt-software.com/read/my_forums/
 or send an email to listmana...@lyris.sunbeltsoftware.com
 with the body: unsubscribe exchangelist

 ---
 To manage subscriptions click here:
 http://lyris.sunbelt-software.com/read/my_forums/
 or send an email to listmana...@lyris.sunbeltsoftware.com
 with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist