| Author |
Message |
Richard
Guest
|
Posted:
Wed Jan 26, 2005 9:23 pm Post subject:
RCP over HTTP Problem |
|
|
Hello
I've setup rpc over http and it seems to work, however outlook seems to hang
for a good 3-4 minutes before it logs into the mailboxes.
The exchange 2003 server is named server1.domain.com however in dns I use
mail.domain.com
When I configure outlook to use mail.domain.com it freezes and changes that
to server1.domain.com. I've set the exchange proxy settings to use
https://mail.domain.com however when I open outlook it takes ages to make
the https connection, it hangs trying to connect to server1.domain.com.
Interestingly enough, when I connect using the same configuration using a
different computer on a different network it actually does work even though
both computers are configured identcally.
Any ideas where to start troubleshooting this?
Thanks for any advice.
Richard
|
|
| Back to top |
|
 |
Mark Arnold [MVP]
Guest
|
Posted:
Wed Jan 26, 2005 11:02 pm Post subject:
Re: RCP over HTTP Problem |
|
|
On Wed, 26 Jan 2005 10:23:03 -0500, "Richard"
<rcowell%nospam%@britainusa.com> wrote:
| Quote: | Hello
I've setup rpc over http and it seems to work, however outlook seems to hang
for a good 3-4 minutes before it logs into the mailboxes.
The exchange 2003 server is named server1.domain.com however in dns I use
mail.domain.com
When I configure outlook to use mail.domain.com it freezes and changes that
to server1.domain.com.
|
That's right, the server name in the server / user name box needs to
be the actual mailbox server.
| Quote: | I've set the exchange proxy settings to use
https://mail.domain.com however when I open outlook it takes ages to make
the https connection, it hangs trying to connect to server1.domain.com.
|
Is it actually hanging or does it just take a while to connect? I do
this from work to my home systems and it does take a few minutes to
reach "connected" and then a few more to update the mail.
When you configure it to run RPC over HTTPS even on fast networks
(both ticks) do you get that same delay?
| Quote: |
Interestingly enough, when I connect using the same configuration using a
different computer on a different network it actually does work even though
both computers are configured identcally.
Any ideas where to start troubleshooting this?
Thanks for any advice.
Richard
|
|
|
| Back to top |
|
 |
Richard
Guest
|
Posted:
Thu Jan 27, 2005 2:21 am Post subject:
Re: RCP over HTTP Problem |
|
|
Hi Mark
Both boxes are checked, and like you it takes a few minutes to connect fully
and sync up.. Was just strange because if I connect using my work computer
it is really quick, like less than a minute. (work is T1, home is cable 5
meg down/384 up)
Just wondered if this was something to be expected or if there was something
wrong somewhere. It just ran alarm bells with me that it kept looking for
server1.domain.com and not mail.domain.com
Thanks for any further advice.
Richard
"Mark Arnold [MVP]" <mark@mvps.org> wrote in message
news:n5jfv0d3snlerhkcf9iqim1cu80bvqg6q6@4ax.com...
| Quote: | On Wed, 26 Jan 2005 10:23:03 -0500, "Richard"
rcowell%nospam%@britainusa.com> wrote:
Hello
I've setup rpc over http and it seems to work, however outlook seems to
hang
for a good 3-4 minutes before it logs into the mailboxes.
The exchange 2003 server is named server1.domain.com however in dns I use
mail.domain.com
When I configure outlook to use mail.domain.com it freezes and changes
that
to server1.domain.com.
That's right, the server name in the server / user name box needs to
be the actual mailbox server.
I've set the exchange proxy settings to use
https://mail.domain.com however when I open outlook it takes ages to make
the https connection, it hangs trying to connect to server1.domain.com.
Is it actually hanging or does it just take a while to connect? I do
this from work to my home systems and it does take a few minutes to
reach "connected" and then a few more to update the mail.
When you configure it to run RPC over HTTPS even on fast networks
(both ticks) do you get that same delay?
Interestingly enough, when I connect using the same configuration using a
different computer on a different network it actually does work even
though
both computers are configured identcally.
Any ideas where to start troubleshooting this?
Thanks for any advice.
Richard
|
|
|
| Back to top |
|
 |
|
|
|
|