On Mar 22, 10:03*pm, Ace Fekay [MVP-DS, MCT]
<ace...@newsgroup> wrote:
> > On Mar 22, 11:27*am, "SteveB" <newsgr...@newsgroup> wrote:
> >> Outlook Anywhere is pretty easy to setup. There is a link on the RWW home
> >> page that gives you specific directions. >
> >> "Dean K" <d...@newsgroup> wrote in message >
> >>news:0bf260d1-1e83-4a46-abc0-ef8cc8244f87@newsgroup
> >> On Mar 22, 9:45 am, "SteveB" <newsgr...@newsgroup> wrote: >
> >>> Outlook Anywhere does not require VPN at all and works very well for
> >>> e-mail
> >>> access. Is there a specific reason why you need to use VPN?
> >>> "Dean K" <d...@newsgroup> wrote in message
> >>>news:a2339528-7e33-4228-8407-751bd8d68c97@newsgroup
> >>> On Mar 22, 8:27 am, "Ace Fekay [MVP-DS, MCT]"
> >>> <ace...@newsgroup> wrote:
> >>>> "Dean K" <d...@newsgroup> wrote in
> >>>> messagenews:a98b246b-e173-49cf-9141-2190ba758f10@newsgroup
> >>>>> Hi All, >
> >>>>> I was hoping you could assist me in troubleshooting a problem I am
> >>>>> having accessing Exchange through a laptop computer. Here are some
> >>>>> details - I'm sure you will have additional questions regarding my
> >>>>> setup but I will try to be as thorough as possible:
> >>>>> 1. The laptop computer is part of the SBS domain. The SBS is the mail
> >>>>> host and all email is sent/received via SMTP.
> >>>>> 2. All emails can be retrieved on the laptop if the laptop is
> >>>>> physically connected onto the network.
> >>>>> 3. When the laptop is connected remotely (via "Connect to Small
> >>>>> Business Server"), the laptop VPNs into the network but email is not
> >>>>> synchronized with Outlook.
> >>>>> 4. Email can be retrieved via OWA.
> >>>>> Please note that email synchronization between Outlook and Exchange
> >>>>> was working previously on this laptop.
> >>>>> Thanks in advance for all of your assistance.
> >>>> What version of Outlook? >
> >>>> What changed if it was working previously?
> >>>> In #1, are you saying the laptop is configured as a POP3 account, orthe
> >>>> SMTP reference is just the server?
> >>>> Is Outlook configured to use Outlook Anywhere (also known as RPC/HTTPS)?
> >>>> If the laptop is configured for RPC/HTTPS, and it's not working outside
> >>>> of
> >>>> the office, then it's telling me there is a mis-config on the serveror
> >>>> the laptop. To rule out a server mis-config, visit the following site to
> >>>> test the server's config first >
> >>>> Microsoft Exchange Server Remote Connectivity
> >>>> Analyzerhttps://www.testexchangeconnectivity.com
> >>>> --
> >>>> Ace >
> >>>> This posting is provided "AS-IS" with no warranties or guarantees and
> >>>> confers no rights. >
> >>>> Please reply back to the newsgroup or forum for collaboration benefit
> >>>> among responding engineers, and to help others benefit from your
> >>>> resolution. >
> >>>> Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
> >>>> MCSA 2003/2000, MCSA Messaging 2003
> >>>> Microsoft Certified Trainer
> >>>> Microsoft MVP - Directory Services
> >>>> If you feel this is an urgent issue and require immediate assistance,
> >>>> please contact Microsoft PSS directly. Please
> >>>> checkhttp://support.microsoft.comforregionalsupportphone numbers.
> >>> Hi Ace, >
> >>> I just checked the Outlook settings and discovered that Outlook
> >>> Anywhere is not configured. Is this necessary if the laptop is
> >>> connected to the network via VPN (Connect to Small Business Server)?
> >>> Thanks for all of your assistance. >
> >>> Regards,
> >>> Dean >>
> >> No particular reason why I am using VPN - it was just the way we were
> >> accessing Exchange outside of the office in the past. I will try
> >> configuring Outlook Anywhere to see if I can access mail from outside
> >> of the LAN. >>>
> > Thanks for the pointer to the RWW homepage. It was very helpful. I
> > made the adjustments and will test when I get home. >>
> Hi Dean,
>
> Glad to see you are on the right track. As other have stated, VPNs are
> not required if the sole purpose is for email connectivity when Outlook
> Anywhere is an option.
>
> Check that site I gave you to make sure the server is configured
> properly for Outlook Anywhere - HTTPS/RPC, which I don't see why it
> wouldn't be, unless the correct ports are not mapped. If you get an
> error at the site about the autodiscover record missing or incorrect,
> you can ignore it since that is an Exchange 2007 feature on SBS 2008.
> Also ignore any error about the certificate not being from a publicly
> recognized authority because SBS configures a self-signed cert and
> automatically deploys it to the workstations once joined to the domain.
> This way you will know that if you have a problem configuring Outlook,
> you can eliminate the server as the issue.
>
> Ace Hi Ace & All,
Thank you very much for all of your kind assistance in helping me
troubleshoot my Exchange issues.
Here is what I have tried so far:
1. I reran CECEIW (sp?) and issued a new self-signed certificate. I
installed this certificate on the laptop.
2. I followed the instructions on the RWW website to set up Outlook
anywhere on the laptop
3. I verified the directory setttings in IIS, including enabling
"Basic Authentication" and enabling the "Require secure channel" and
"Require 128 bit encryption" checkboxes.
4. I checked ISA 2004 and found that ports 80 and 443 are opened for a
rule entitled "Outlook over the internet". I made certain that the
certificate that is referenced in ISA was changed to the new one
generated during step 1.
5. I can access exchange through OMA and OWA.
I can VPN into the network and have confirmed access to all of the
network resources. The only thing I can't do is connect to Exchange.
I need help. I'm at my wits end with this problem. I just ran the
Microsoft Server Exchange Connectivity Analyzer and tested Outlook
Anywhere. Here are the results:
[[Testing RPC/HTTP connectivity
RPC/HTTP test failed
Test Steps
Attempting to test Autodiscover for dean@newsgroup
Testing Autodiscover failed
Test Steps
Attempting each method of contacting the AutoDiscover Service
Failed to contact the AutoDiscover service successfully by any
method
Test Steps
Attempting to test potential AutoDiscover URL
https://tmcpower.com/AutoDiscover/AutoDiscover.xml
Failed testing this potential AutoDiscover URL
Test Steps
Attempting to resolve the host name tmcpower.com in DNS.
Host successfully resolved
Additional Details
IP(s) returned: 67.199.19.86
Testing TCP Port 443 on host tmcpower.com to ensure it is listening
and open.
The port was opened successfully.
Testing SSL Certificate for validity.
The SSL Certificate failed one or more certificate validation
checks.
Tell me more about this issue and how to resolve it
Additional Details
A network error occurred while communicating with remote host
Exception Details:
Message: Authentication failed because the remote party has closed the
transport stream.
Type: System.IO.IOException
Stack Trace:
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32
readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer,
AsyncProtocolRequest asyncRequest)
at
System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken
message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32
count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean
receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult
lazyResult)
at System.Net.Security.SslStream.AuthenticateAsClient(String
targetHost, X509CertificateCollection clientCertificates, SslProtocols
enabledSslProtocols, Boolean checkCertificateRevocation)
at System.Net.Security.SslStream.AuthenticateAsClient(String
targetHost)
at
Microsoft.Exchange.Tools.ExRca.Tests.SSLCertificateTest.PerformTestReally()
Attempting to test potential AutoDiscover URL
https://autodiscover.tmcpower.com/Au...toDiscover.xml
Failed testing this potential AutoDiscover URL
Test Steps
Attempting to resolve the host name autodiscover.tmcpower.com in DNS.
Host successfully resolved
Additional Details
IP(s) returned: 66.215.31.154
Testing TCP Port 443 on host autodiscover.tmcpower.com to ensure it
is listening and open.
The port was opened successfully.
Testing SSL Certificate for validity.
The SSL Certificate failed one or more certificate validation
checks.
Test Steps
Validating certificate name
Certificate name validation failed
Tell me more about this issue and how to resolve it
Additional Details
Host name autodiscover.tmcpower.com does not match any name found on
the server certificate CN=tmcsbs.tmcpower.com
Attempting to contact the AutoDiscover service using the HTTP
redirect method.
Failed to contact AutoDiscover using the HTTP Redirect method
Test Steps
Attempting to resolve the host name autodiscover.tmcpower.com in DNS.
Host successfully resolved
Additional Details
IP(s) returned: 66.215.31.154
Testing TCP Port 80 on host autodiscover.tmcpower.com to ensure it is
listening and open.
The specified port is either blocked, not listening, or not
producing the expected response.
Tell me more about this issue and how to resolve it
Additional Details
A network error occurred while communicating with remote host
Exception Details:
Message: No connection could be made because the target machine
actively refused it 66.215.31.154:80
Type: System.Net.Sockets.SocketException
Stack Trace:
at System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port)
at
Microsoft.Exchange.Tools.ExRca.Tests.TcpPortTest.PerformTestReally()
Attempting to contact the AutoDiscover service using the DNS SRV
redirect method.
Failed to contact AutoDiscover using the DNS SRV redirect method.
Test Steps
Attempting to locate SRV record _autodiscover._tcp.tmcpower.com in
DNS.
Failed to find AutoDiscover SRV record in DNS.
Tell me more about this issue and how to resolve it]]
In addition, when I tried verifying the RPC Virtual Directory
Configuration in the MS technet document, after entering my
credentials at the login prompt the first time and clicking "OK" on
prompts 2 and 3, I get the following error, instead of the anticipated
403.2 or 401.3 errors:
HTTP Error 401.1 - Unauthorized: Access is denied due to invalid
credentials.
Internet Information Services (IIS)
Your continued support is greatly appreciated. I hope that I will be
able to resolve this issue soon. Pretty soon I will either have all
white hair or no hair at all!
Thanks again,
Dean