Autodiscover... Still...

[HPlum78]

take it the serviceDNSName is set to the NetBIOS name of your mail server?

[GRitchie]

Correct (CPS-MSX)

[HPlum78]

What is the keywords attribute look like?

[HPlum78]

Right so the thing is outlook on domain joined workstations use the SRV method as the last option to find the auto discover service. The SCP is the first (LDAP to AD looking for the SCP) these will be sorted as in-site or out-of-site lists outlook then tries these in order. if that fails outlook then connects to some predefined URL's so you should also have in your DNS some A's that point to autodiscover.cartmelprioryschool.co.uk after that it's the SRV's.

[GRitchie]

Keywords:

 

The information about DNS there taken on board, what would I need to add/change then?

[HPlum78]

That looks good, so from an internal workstation can you browse to https://mail.cartmelprioryschool.co.uk/autodiscover/autodiscover.xls do you get prompted for credentials or do you get the invalid request response?

 

H

[GRitchie]

If you meant .xml rather than .xls, I receive the error 600 (after logging in). Which apparently is the right message?

[HPlum78]

yeah xml looking at xls files! :-P right so I think we have your problem you should not be prompted for a username and password if you are accessing the autodiscover from inside your network. Need to take a look at the Auth methods / do you proxy all your http/https traffic? if so have you got exclusions for your mail server?

[GRitchie]

Slow progress is good progress...!

 

There is a proxy in place yes. I'm not too sure how to exclude the mail server.

Where would I check the auth methods?

[HPlum78]

I seem to think in a screen shot you posted a build number of 8 so exchange 2010? so something like get-autodiscovervirtualdirectory | select internalAuthenticationMethods I think! post the output back if you will

 

H

[GRitchie]

Exchange 2013 here. The command worked and showed this:

[HPlum78]

That's how I would expect it to look so this is looking more and more like a proxy getting involved! Can you bypass your proxy?

[GRitchie]

Eughr, I don't think so.

It's a new network to me...

Without installing Outlook ON the server, which I see is strongly advised against....

[HPlum78]

Can you put a workstation on your server vLAN and run the test from there? and yeah office on servers not what I would be doing!

[GRitchie]

I would, if I knew how... Is there any other way I can test without the need for configuring a vLAN?

[GRitchie]

bump out of desperation

[GRitchie]

@HPlum78 any more ideas?

[HPlum78]

Can we be absolutely sure with what's happening to the traffic when you start outlook up, something as simple as netstat maybe able to tell us if we are hitting a proxy. If you can wireshark or tcp view would give a deeper dive into what's happening to the traffic as it leaves your clients. I am almost certain that the issue is a proxy getting in the way, do your servers hit a proxy? Who is the isp? Do you maintain your own proxy box? Let me know your thoughts.

 

H

[GRitchie]

Lots of questions, here we go:

 

Netstat isn't showing the MSX server at all (from the client).

We DO use a proxy (at the moment). The client and the exchange server are both connected to the same proxy server.

ISP is LUNS, proxies are internal IPFire/Smoothwall (soon to be changed) and an external local authority (soon to be changed).

 

Not too sure how to use Wireshark, any insight on this?

 

 

UPDATE: if I do a manual netstat -ano 1 | find "exchange_ip" I receive an 'established' message.

Edited September 23, 2015 by GRitchie