mattstannard
asked on
Exchange over HTTP on SBS 2003
Hi there,
I currently use Exchange over HTTP for a number of businesses which work fine. I'm trying to set it up for another account and it refuses to connect.
What I do is enter the server name i.e. server.domain.local, enter my username, then in connection enter the URL of the OWA (i.e. https://domain.domain.com) and select basic authentication.
I get prompted for a username and password but whatever I put the machine doesn't recognise, I know the username / password are correct as if I login to OWA https://domain.domain.com/exchange it works fine!
Any help much appreciated!!
M
I currently use Exchange over HTTP for a number of businesses which work fine. I'm trying to set it up for another account and it refuses to connect.
What I do is enter the server name i.e. server.domain.local, enter my username, then in connection enter the URL of the OWA (i.e. https://domain.domain.com) and select basic authentication.
I get prompted for a username and password but whatever I put the machine doesn't recognise, I know the username / password are correct as if I login to OWA https://domain.domain.com/exchange it works fine!
Any help much appreciated!!
M
Lee W, MVP
Make sure you have the correct web address - RPC of HTTP is different from RPC over HTTPS - you say you're using HTTP but you're specifying HTTPS.
Are you using a 3rd party SSL certificate or the SBS self-issued one?
ASKER
Hi,
Thank you both.
I am trying to connect to the https:// service, I know it works as if I go there in my browser and login with my domain username / password I get in fine.
On the default website, what should the directory security / ip restrictions be?
I am using a 3rd party SSL certificate, again that works fine with OWA.
Thank you both.
I am trying to connect to the https:// service, I know it works as if I go there in my browser and login with my domain username / password I get in fine.
On the default website, what should the directory security / ip restrictions be?
I am using a 3rd party SSL certificate, again that works fine with OWA.
In Outlook are you typing in https:// or just name.domain.com? It should just be name.domain.com for the RPC part.
RPC Virtual Directory:
Auth = Integrated & Basic
IP Restrictions = Granted Access
SSL = Require Secure Channel & Require 128-bit
Exchange Virtual Directory:
Auth = Integrated & Basic
IP Restrictions = Granted Access
SSL = Require Secure Channel & Require 128-bit
RPC Virtual Directory:
Auth = Integrated & Basic
IP Restrictions = Granted Access
SSL = Require Secure Channel & Require 128-bit
Exchange Virtual Directory:
Auth = Integrated & Basic
IP Restrictions = Granted Access
SSL = Require Secure Channel & Require 128-bit
ASKER
Thanks you,
What I put is as follows:
Server: servername.domain.local
Username: Matt Stannard
Click More Settings, Connection, Tick to connect to Microsoft Exchange using HTTP
in the https:// box I put the servers external domain name (if I go to it and login I see the Welcome to Windows SBS 2003 website)
Select the "Basic Authentication" and tick Slow / Fast Networks as I always want HTTP.
I get a logon prompt, I enter my username mstannard and password doesn't work, so I try domain\mstannard and password doesnt work.
What I put is as follows:
Server: servername.domain.local
Username: Matt Stannard
Click More Settings, Connection, Tick to connect to Microsoft Exchange using HTTP
in the https:// box I put the servers external domain name (if I go to it and login I see the Welcome to Windows SBS 2003 website)
Select the "Basic Authentication" and tick Slow / Fast Networks as I always want HTTP.
I get a logon prompt, I enter my username mstannard and password doesn't work, so I try domain\mstannard and password doesnt work.
Have you tried with NTL authentication?
Are you filling in the "Only connect to proxy server that have the principal name in their certificate" and entering "msstd:name.domain.com" in that box?
Are you filling in the "Only connect to proxy server that have the principal name in their certificate" and entering "msstd:name.domain.com" in that box?
ASKER
Hi Alan,
Just did, didn't seem to make any difference whatsoever.
So strange as on my other HTTP exchange accounts they all work fine!
Just did, didn't seem to make any difference whatsoever.
So strange as on my other HTTP exchange accounts they all work fine!
Who issued the SSL certificate and does the client you are having problems have them as a trusted provider?
ASKER
Godaddy.com
https://exchange.mydomain.
https://exchange.mydomain.
Cert looks fine.
If you browse to the URL via IE that you posted on the client with the problem - does it trust the site?
If you browse to the URL via IE that you posted on the client with the problem - does it trust the site?
ASKER
Thanks Alan,
Yes - its my own laptop lol! But any machine I try and setup this way has had this issue and I can't figure out why its any different.
Yes - its my own laptop lol! But any machine I try and setup this way has had this issue and I can't figure out why its any different.
Can you just put in the server name not servername.domain.local as the servername please and try again.
ASKER
Just to get this right, use server.domain.com in the server in the Mail Account setup, just tried that still doesn't like it.
When entering the server / username - please enter just server, not server.domain.local e.g., server01 instead of server01.internaldomain.lo
When entering the HTTPS part, you need to use exchange.yourdomain.com plus msstd:exchange.yourdomain.
Hopefully that should work.
When entering username / password when prompted, enter domain\username and password.
Domain\username is not internaldomain.local\usern
Sorry if this is teaching you to suck eggs here : )
When entering the HTTPS part, you need to use exchange.yourdomain.com plus msstd:exchange.yourdomain.
Hopefully that should work.
When entering username / password when prompted, enter domain\username and password.
Domain\username is not internaldomain.local\usern
Sorry if this is teaching you to suck eggs here : )
ASKER
Hey,
You're not at all, if anything you are proving my own sanity.
Just tried that, made no difference, is there a way to reset the IIS setup, i.e. remove it an reinstall it to see if that helps?
M
You're not at all, if anything you are proving my own sanity.
Just tried that, made no difference, is there a way to reset the IIS setup, i.e. remove it an reinstall it to see if that helps?
M
Click on Start, Run {type} inetcpl.cpl {press enter}
Click on the Advanced Tab and click on the Restore Advanced Settings and Reset buttons.
That should take IE back to default settings.
Do you have Firewall / Anti-Virus software on your laptop that might be blocking the comms?
Click on the Advanced Tab and click on the Restore Advanced Settings and Reset buttons.
That should take IE back to default settings.
Do you have Firewall / Anti-Virus software on your laptop that might be blocking the comms?
This is similar to a issue I had when I tried to setup RWW over HTTPS through TMG. OWA seems working fine but but Remote Desktop over the web never work out. Assuming you're accessing the SBS through a firewall (Eg: ISA or TMG) I do hope attached file will be useful for you.
Please note attached articles is written by different person and being published in the Technet.
Deploying-ISA-2006-with-Windows-.doc
Please note attached articles is written by different person and being published in the Technet.
Deploying-ISA-2006-with-Windows-.doc
ASKER
Thank you for this, I can connect to Remote Web Workplace, can use RDP.
The machine isn't running ISA but I'll have a read.
The machine isn't running ISA but I'll have a read.
Is your laptop up-to-date with Windows Updates etc? Manual check - not just automatic check.
ASKER
Hi Alan,
Yep - there is one Office update I'll try that.
Yep - there is one Office update I'll try that.
What about my Firewall / Anti-virus question earlier? Anything installed?
ASKER
Hi Alan,
On my machine I've got AVG, although as I said I have three other MS Exchange setups on my laptop all of those work fine.
The server which doesn't work is behind a DrayTek 2820, port forwarding 443 / 80 to that box, perhaps it needs to forward some other ports although can't think what.
Just checked Exchange Version to, looks like its SP2 - 6.5.7638.1
M
On my machine I've got AVG, although as I said I have three other MS Exchange setups on my laptop all of those work fine.
The server which doesn't work is behind a DrayTek 2820, port forwarding 443 / 80 to that box, perhaps it needs to forward some other ports although can't think what.
Just checked Exchange Version to, looks like its SP2 - 6.5.7638.1
M
Only HTTPS is required.
Does the Draytek use HTTPS management remotely for the router?
You might want to check that it isn't and that HTTPS isn't going to the Router and not being passed through it as you are expecting.
Does the Draytek use HTTPS management remotely for the router?
You might want to check that it isn't and that HTTPS isn't going to the Router and not being passed through it as you are expecting.
ASKER
Hi Alan,
A good point, but OWA works fine https://exchange.mydomain.org/exchange and https://exchange.mydomain.org/ both go to the server :-(
M
A good point, but OWA works fine https://exchange.mydomain.org/exchange and https://exchange.mydomain.org/ both go to the server :-(
M
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ohhh! That's a great tool!!
I got:
Testing Http Authentication Methods for URL https://exchange.mydomain.
The HTTP authentication test failed.
Tell me more about this issue and how to resolve it
Additional Details
Initial Anonymous HTTP(s) request did not fail but Anonymous is not a supported Authentication Method for this scenario
I got:
Testing Http Authentication Methods for URL https://exchange.mydomain.
The HTTP authentication test failed.
Tell me more about this issue and how to resolve it
Additional Details
Initial Anonymous HTTP(s) request did not fail but Anonymous is not a supported Authentication Method for this scenario
ASKER
Yep, permissions issue on the RPC directory, followed the instructions worked like a charm thanks!!!!
Excellent - well done.
I also obscured your domain name in your last post but one.
Alan
I also obscured your domain name in your last post but one.
Alan