Re: rpc over http problem
From: VanPelt (eplu_at_not-blue.com)
Date: 04/13/04
- Next message: Jerry Bryant [MSFT]: "Microsoft Security Bulletins for April 2004"
- Previous message: Verizon: "Relaying denied. IP name possibly forged"
- In reply to: Jason Gallas: "Re: rpc over http problem"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 13 Apr 2004 13:01:26 -0400
I am getting the exact same problem. I had the server [on SBS 2003] and
client Outlook 2003 working perfectly until a server shutdown that was not
clean. After that, this stopped to function. I can get through the
mail.myserver.com/rpc with the login and so forth. I get the right error
message via teh web, but cannot hook in via Outlook 2003.
Any more help out there?
"Jason Gallas" <jgallas@usa.nospam.net> wrote in message
news:%23VDErXKIEHA.1528@TK2MSFTNGP09.phx.gbl...
> Yes, I do get prompted for credentials after the server certificate
prompts
> me to accept it. I also get that error message, but for some reason when
I
> try using Outlook 2003 to connect it just times out with that message.
> Could it be that mail.mydomain.com and mail.mydomain.com/rpc are behaving
> differently?
>
> "James Burrage [MSFT]" <jburrage@online.microsoft.com> wrote in message
> news:eHLnBunHEHA.3528@TK2MSFTNGP09.phx.gbl...
> : Hi Jason,
> :
> : Can you connect to https://myserver.mydomain.com/rpc and get prompted
for
> : credentials? If it is setup properly, you should get prompted for
> : credentials. Once you enter your credentials you should get a page with
> : error 403.2 Read Access is Denied. If you don't get this, then it is not
> : setup properly.
> :
> : --
> : Thanks,
> : James Burrage
> :
> : This posting is provided "AS IS" with no warranties, and confers no
> rights.
> : Please do not send email to this address, post a reply to this
newsgroup.
> :
> : Use of included script samples are subject to the terms specified at
> : http://www.microsoft.com/info/cpyright.htm
> :
> : "Jason Gallas" <jgallas@usa.nospam.net> wrote in message
> : news:e$p2bnlHEHA.308@tk2msftngp13.phx.gbl...
> : > I'm having a problem connecting to my Exchange 2003 SBS at home from
the
> : > office. I have it setup as per the instructions in KB833401. I have
a
> : > Linksys Router/Gateway at home. I have Outlook setup as follows:
> : >
> : > -----------------------------
> : >
> : > Exchange Server Settings
> : >
> : > Microsoft Exchange Server: mail.mydomain.com (alias, real server name
is
> : > onyx.mydomain.com; I've tried both)
> : >
> : > Use Cached Exchange Mode (unchecked)
> : >
> : > User Name: my username
> : >
> : > -----------------------------
> : >
> : > Exchange Proxy Settings
> : >
> : > https:// mail.mydomain.com (internet alias given by no-ip.com dynamic
> dns
> : > service)
> : >
> : > Basic Authentication
> : >
> : > -----------------------------
> : >
> : > When I attempt a connection with outlook /rpcdiag I am prompted for a
> : > username password. I type in as follows:
> : >
> : > User: domain name\username
> : > Password: my password
> : >
> : > Then I get the following message:
> : >
> : > Outlook could not log on. Check to make sure you are connected to the
> : > network and are using the proper server and mailbox name. The
> connection
> : to
> : > Microsoft Exchange Server is unavailable. Outlook must be online or
> : > connected to complete this action.
> : >
> : > Anyone have an idea why I cannot connect? When I connect via OWA at
> : > http://mydomain.com/exchange/ everything works beautifully.
> : >
> : >
> :
> :
>
>
- Next message: Jerry Bryant [MSFT]: "Microsoft Security Bulletins for April 2004"
- Previous message: Verizon: "Relaying denied. IP name possibly forged"
- In reply to: Jason Gallas: "Re: rpc over http problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
