Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1771
  • Last Modified:

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
0
mattstannard
Asked:
mattstannard
  • 13
  • 13
  • +1
1 Solution
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
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.
0
 
Alan HardistyCommented:
Are you using a 3rd party SSL certificate or the SBS self-issued one?
0
 
mattstannardAuthor Commented:
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.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
Alan HardistyCommented:
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
0
 
mattstannardAuthor Commented:
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.




0
 
Alan HardistyCommented:
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?
0
 
mattstannardAuthor Commented:
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!
0
 
Alan HardistyCommented:
Who issued the SSL certificate and does the client you are having problems have them as a trusted provider?
0
 
mattstannardAuthor Commented:
Godaddy.com

https://exchange.mydomain.org/

0
 
Alan HardistyCommented:
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?
 
0
 
mattstannardAuthor Commented:
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.


0
 
Alan HardistyCommented:
Can you just put in the server name not servername.domain.local as the servername please and try again.
0
 
mattstannardAuthor Commented:
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.
0
 
Alan HardistyCommented:
When entering the server / username - please enter just server, not server.domain.local e.g., server01 instead of server01.internaldomain.local
When entering the HTTPS part, you need to use exchange.yourdomain.com plus msstd:exchange.yourdomain.com
Hopefully that should work.
When entering username / password when prompted, enter domain\username and password.
Domain\username is not internaldomain.local\username, just domain\username.
Sorry if this is teaching you to suck eggs here : )
0
 
mattstannardAuthor Commented:
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
0
 
Alan HardistyCommented:
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?
0
 
ksksilvaCommented:
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
0
 
mattstannardAuthor Commented:
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.
0
 
Alan HardistyCommented:
Is your laptop up-to-date with Windows Updates etc?  Manual check - not just automatic check.
0
 
mattstannardAuthor Commented:
Hi Alan,

Yep - there is one Office update I'll try that.
0
 
Alan HardistyCommented:
What about my Firewall / Anti-virus question earlier?  Anything installed?
0
 
mattstannardAuthor Commented:
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
0
 
Alan HardistyCommented:
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.
0
 
mattstannardAuthor Commented:
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
0
 
Alan HardistyCommented:
Okay - that's a valid point!
Do you know that it is setup properly on the server you can't reach?
Can you run the RPC over HTTP test at https://testexchangeconnectivity.com and see what results you get.
0
 
mattstannardAuthor Commented:
Ohhh! That's a great tool!!

I got:

Testing Http Authentication Methods for URL https://exchange.mydomain.org/rpc/rpcproxy.dll
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
0
 
mattstannardAuthor Commented:
Yep, permissions issue on the RPC directory, followed the instructions worked like a charm thanks!!!!
0
 
Alan HardistyCommented:
Excellent - well done.
I also obscured your domain name in your last post but one.
Alan
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 13
  • 13
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now