E
eljefemus
I am receiving this error as well. I have my remote users setup on TS
to also use Outlook. All clients connected to the LAN are using
Exchange in cache mode. This error is not a problem per-say, but it
is a pain in the ass. I notice that email sends fine and sends rather
quickly, but if I press F9 to send receive all it throws the (subject
line) error at me. I have only noticed this on 2 clients thus far,
but I'm sure others might have it. Is this a normal error being the
fact that I am not technically connected to the LAN. Can someone
please explain if this is normal or how to go about fixing it.
I have been reading on RPC over HTTP/s, but I am unsure of how this
solution works, does it work like let's say I have a connection to the
Interweb and I open Outlook it would pull my Domains Exchange Mail
without initiating some type of secondary connection like a VPN or
through TS.
How would I go about easily setting up a rpc over http topology.
Thanks for any and all help,
Jeff
to also use Outlook. All clients connected to the LAN are using
Exchange in cache mode. This error is not a problem per-say, but it
is a pain in the ass. I notice that email sends fine and sends rather
quickly, but if I press F9 to send receive all it throws the (subject
line) error at me. I have only noticed this on 2 clients thus far,
but I'm sure others might have it. Is this a normal error being the
fact that I am not technically connected to the LAN. Can someone
please explain if this is normal or how to go about fixing it.
I have been reading on RPC over HTTP/s, but I am unsure of how this
solution works, does it work like let's say I have a connection to the
Interweb and I open Outlook it would pull my Domains Exchange Mail
without initiating some type of secondary connection like a VPN or
through TS.
How would I go about easily setting up a rpc over http topology.
Thanks for any and all help,
Jeff