gerpaqit
asked on
RPC over http
Hi
i have to learn how to connect my remote employees to connect to exchange using rpc over http using outlook 2003quickly!
i have followed (i think!) the steps on the microsft site but am not having any success.... a quick summary of where i'm at...
i am running SBS 2003 server with sp1 (exchange sp2)
my local domain is called "domain.local) and my server is called "server"....... i was feeling very original the time!
i use a single nic in my server and use a sonicwall firewall to protect it....
**assume my internet domain name is abcd.com**
i can outlook on the web from anywhere using https://remote.abcd.com/exchange...so these ports are setup on the sonicwall corectly..
i have enter the settings on my outlook client to access exchange using rpc....
under "use this url to connect to my proxy server for exchange" i have sinply entered remote.abcd.com
however when i try t open outlook it askes me for my network password...the username is already there in the form of server\ger
it does not acceppt my password....
what silly thing am i overlooking???
any help greatly appreciated...
regards
ger
i have to learn how to connect my remote employees to connect to exchange using rpc over http using outlook 2003quickly!
i have followed (i think!) the steps on the microsft site but am not having any success.... a quick summary of where i'm at...
i am running SBS 2003 server with sp1 (exchange sp2)
my local domain is called "domain.local) and my server is called "server"....... i was feeling very original the time!
i use a single nic in my server and use a sonicwall firewall to protect it....
**assume my internet domain name is abcd.com**
i can outlook on the web from anywhere using https://remote.abcd.com/exchange...so these ports are setup on the sonicwall corectly..
i have enter the settings on my outlook client to access exchange using rpc....
under "use this url to connect to my proxy server for exchange" i have sinply entered remote.abcd.com
however when i try t open outlook it askes me for my network password...the username is already there in the form of server\ger
it does not acceppt my password....
what silly thing am i overlooking???
any help greatly appreciated...
regards
ger
Take IIS manager >>exchange website properties >>Directory Security >>Authentication and access controller >>edit >> in authentication methods tab specify the correct Domain
in Default domain and realm field
in Default domain and realm field
by the way have you tried username as Domain/usermane or username@domain.com Inserted of server\username
http://www.msexchange.org/tutorials/Outlook_2003_Connect_Exchange_2003.html
http://www.msexchange.org/tutorials/Outlook_2003_Connect_Exchange_2003.html
Domain\username
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thank u again jeff!.... i could have sworn i did all this already! did it again and it worked straight away
ger
ger
No problem... you should really post any SBS related question in the SBS Topic Area... otherwise you end up with advice that isn't applicable to SBS.
Jeff
TechSoEasy
Jeff
TechSoEasy
ASKER
noted....thanks again
When you ran the wizard, it would have asked you to give the server a domain name - you need to use the external FQDN (remote.abcd.com) for the proxy name, the mutual authentication name (in the format msstd:remote.abcd.com) AND the certificate name must match or it will keep prompting for the password.
A quick check - when you open the webmail on HTTPS, do you get prompted to accept the certificate? If so, do you get three green ticks? One for it being from a trusted provider (either a commercial mob, the domain the PC belongs to or having the root manually installed on the PC), one for it being the same name as the FQDN you are accessing and one for the ceritificate date being valid. If any one of those fails you have the problem there.
Fixing the name is easy - just request a new certificate with the IIS certificate wizard under the security settings for the web root, and put in the correct name.
Fixing the trusting is easy - download the server.domain.local\certsr
Fixing the date is easy, but I'll let you work that out.