Need help wit SBS 2011 and Exchange 2010


Recommended Posts

My problem is 2 fold in a way as it seems to work but not fully

Using the microsoft exchange test utility I get the following 2 errors (the otehr 2 tests are passed green 100% - OWA works fine) ... have tried looking into those 2 errors but unable to get to the bottom of it ...

running the Outlook Anywhere (RPC over HTTP)

Attempting to ping RPC proxy mail.domain.com

RPC Proxy can't be pinged.

Additional Details

An HTTP 401 Unauthorized response was received from the remote Unknown server. This is usually the result of an incorrect username or password. If you are attempting to log onto an Office 365 service, ensure you are using your full User Principal Name (UPN).

running the Exchange ActiveSync

An ActiveSync session is being attempted with the server.

Errors were encountered while testing the Exchange ActiveSync session.

Test Steps

Attempting to send the OPTIONS command to the server.

Testing of the OPTIONS command failed. For more information, see Additional Details.

Additional Details

An HTTP 401 Unauthorized response was received from the remote IIS7 server. This is usually the result of an incorrect username or password. If you are attempting to log onto an Office 365 service, ensure you are using your full User Principal Name (UPN).

My problem is 2 fold in a way as it seems to work but not fully

Using the microsoft exchange test utility I get the following 2 errors (the otehr 2 tests are passed green 100% - OWA works fine) ... have tried looking into those 2 errors but unable to get to the bottom of it ...

running the Outlook Anywhere (RPC over HTTP)

Attempting to ping RPC proxy mail.domain.com

RPC Proxy can't be pinged.

Additional Details

An HTTP 401 Unauthorized response was received from the remote Unknown server. This is usually the result of an incorrect username or password. If you are attempting to log onto an Office 365 service, ensure you are using your full User Principal Name (UPN).

running the Exchange ActiveSync

An ActiveSync session is being attempted with the server.

Errors were encountered while testing the Exchange ActiveSync session.

Test Steps

Attempting to send the OPTIONS command to the server.

Testing of the OPTIONS command failed. For more information, see Additional Details.

Additional Details

An HTTP 401 Unauthorized response was received from the remote IIS7 server. This is usually the result of an incorrect username or password. If you are attempting to log onto an Office 365 service, ensure you are using your full User Principal Name (UPN).

what errors are you seeing ?

can you send or receive mail?

have you set up a "mail.domain.com" in dns

Yes, sending works , receiving works but Outlook 2007 unable to make it work (although I have encountered a domain name where they cannot send/receive to me and I cannot send/receive from them, otehrwise all other domains - hotmail/yahoo/rogers/others seem to work fine

hmmm ... all i can tell you as of this second is that if I go into Server Config - Client Access - Ecp I have the internal and external domains there ...

not sure (have not come upon a tutorial to set that up per say)

Authentication - form based

Yes the port is opened and tested (443) and within the lan/server I get the propr 505/501 error so in essesnce it is working but have no clue why outlook would not budge (could it be because of the form based authentication -- make it basic?)

Edit: have not tried outlook within the lan though, only wan - which is not working

what do you mean? ... a bit more info if it helps

In outlook 2007 (could upgrade if that is the problem) ....

establishing network connection (check - good)

search for user server settings (autodiscovery - check -good)

then logon to server keeps asking for password over and over and over again

so I am assuming that the server or something within IIS or Exchange is blocking the request ... I have no clue what or why or where to even look

I would have to try that once I get home, I can only remote to the server and make config and test from anotehr computer to see if it works ...

So, I should try it within the network to see if it works ...

Now

Case 1: works, then it means something is blocking the protocol to get outside the network

Case2: not working then a bigger problem I would assume

Yes, 443 is open and good to go, exchange has been restarted

What puzzles me the most is that

1. Outlook Anywhere (RPC over HTTP) says cannot ping proxy

2. Exchange ActiveSync says send Option command

I have recreated the virtual directories for ECP and autodiscovery ... yet, manual/automatic setup not working

Edit: which is true. I cannot ping the damn site. IT works fine for mail.domain and domain.com but not ping ....

Can u connect to

Https://server/owa from a local computer? Use the internal server name. First let's test internal. To make life easier get a cert from an authorized certificate provider.

If you want to get this working quickly we can do a join.me session.

I can confirm the following are working from within the lan

OWA / ECP / Autodiscovery

I can also confirm the following are working on WAN

OWA / ECP / Autodiscovery (https://server/OWA (or ecp_

Will do the test for Outlook within LAN today once I get home ... the certificate I hae is recognised and passes the microsoft exchange test for atuodiscovery and activesync

as far as I can look at rpc is installed and configured ... active sync seems to be fine, but just to doublecheck

under server config client access https://mail.domain....rver-ActiveSync can be accessed from WAN just fine (though it gives the error http version not supported) from within LAN same thing (505/501 common error)

for RPC same thing .... I will be running the assumption both services are up and runing and the 505 http version not supported from what I have read mean it works fine ?!

have not tried locally with outlook (did not cross my mind as I wanted it to work from WAN - oversight on my part - will do it once I get home from work) as for logs, have not found anything conclusive in IIS nor exchange though I only looked briefly)

but from what you can deduce from what I have provided, it should work right?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I bought one of these last year. I really hope I won't have to deal with this crap. My drive is in good condition at the moment.
    • Umm, read my answer again! If you have something to add or contribute, feel free. Otherwise my point was that you apparently dont want faster updates... so you want slower updates by process of elimination. If you have something to contribute, meaningful answers are better.
    • These features described above are good, but far from what developers will like the most. The main feature that developers will care and love the most it's called "Bring Your Own Models". It gives us the ability to connect to LOCAL AI models running on Ollama. The feature it's located on GitHub Copilot tab -> On the model picker where you can select "manage models" instead of paid models and then it will show you the "Bring your own models" window where you can now select Ollama and the endpoint of your local server. So if you have a beefy spec machine you can now use your own model 100% local inside Visual Studio 2026 18.7.0
    • Microsoft Teams is getting a controversial location tracking feature that users may hate by Usama Jawad Image generated with Microsoft Copilot Earlier this year, Microsoft planned to roll out a controversial location tracking feature in Teams, but following customer feedback, it decided to delay its release. The bad news is that the company has decided to launch it later this year, but it's based on roughly the same design that was shared earlier, which means that many users still have good reason to worry. Basically, Microsoft Places and Teams have received workplace check-ins via Wi-Fi. The idea is that if an employee arrives at the office and connects to their enterprise network, their profile status indicator will show them as being present in the office. For example, if you arrive at work, open Teams on your PC, and connect to the "Studio B" company Wi-Fi network, your Teams profile will indicate that you are present in "Studio B", as shown below: Microsoft says that this feature is basically a replacement for physical workplace check-in peripherals, it reduces the need to manually update your status, and it also enables co-workers to know that you're at work so that they can coordinate in-person meetings with you. IT admins can enable this workplace check-in capability at a tenant level, and users have the ability to control whether they want to enable it or not. Of course, all of that sounds great on paper, but naturally, many Teams customers may still have concerns, as they did before. This is because it enables your reporting manager and other members of the organization to track if you are at the office, when you arrive at the office, and where you are right now. This could be problematic for people who work in what they consider to be flexible work environments or hybrid setups, and this kind of location tracking could be considered an invasion of privacy. Microsoft has tried to alleviate some of these concerns by letting users know that they can manually set their location easily, which essentially overrides workplace check-in if they feel uncomfortable with it. However, that doesn't really solve the problem because your organization could enforce a workplace policy that mandates that this feature remains enabled. The Redmond tech giant has also assured users that this capability does not store historical data and is only a real-time indicator of location. Finally, it only generates a signal when you connect to a corporate network, which means that if you are working from home and connect your PC to your personal Wi-Fi, it won't broadcast your location to your employer; you will simply be shown as "Remote". Microsoft has encouraged IT admins to prepare for this change and begin informing users so they know what to expect once it begins rolling out later this year.
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      516
    2. 2
      +Edouard
      162
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      82
    5. 5
      ATLien_0
      81
  • Tell a friend

    Love Neowin? Tell a friend!