Resovled - RPC over HTTP Issue
|
From: Dean K on 25 Mar 2010 17:56 On Mar 24, 7:27 am, Ace Fekay [MVP-DS, MCT] <ace...(a)mvps.RemoveThisPart.org> wrote: > > On Mar 22, 10:03 pm, Ace Fekay [MVP-DS, MCT] > > > 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 d...(a)tmcpower.com > > 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 > > Create a hostname record called "autodiscover" (without the quotes) > under tmcpower.com at your public DNS server. > > I see down below you've already created it. Good. The problem may be > that the CAS server external Autodiscover record was not set in the CAS > configuration section. > > > > > 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 > > Ignore the "tmepower.com" test. That is usually your website, such ashttp://tmcpower.com, and can be ignored. No big deal. > > > > > > > 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/AutoDiscover/AutoDiscover.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 > > Don't worry about this for Outlook connectivity. If the laptop has been > joined to the domain, and the domain is working and GPOs are applying, > the certificate would have been automatically deployed to the laptop. > Since it is a private cert, it will fail the external test, but for > domain machines, it should be fine. > > > > > > > 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.. > > Ok, when I tried to connect tohttps://tmcsbs.tmcpower.com/owato test > your OWA, it failed to connect. This appears to be a port remap issue > either in your firewall or ISA. > > > > > > > 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 > > I hope that helps. > > -- > 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.comfor regional support phone numbers. Hi Ace and All, Thank you to all of you for your support. I have finally resolved my issues with RPC over HTTP (Outlook Anywhere). Hopefully placing my resolution here will help others experiencing similar problems to get their implementations to work as well. Although I tried virtually everything on every website I could find regarding this issue, I think it all came down to a silly (stupid) mistake that I was making on my end. But here is the combination of things I did to make it work for me: 1. Installed the self-signed certificate in the Trusted Root certificate store on the laptop. Although I'm pretty sure it was stored there via GPO, I also manually installed the certificate there. 2. Enabled RPC over HTTP in Exchange. This was not enabled initially. 3. Modified the RPC registry key to ensure that the NetBios and FQDN were pointed to 6001-6002 and 6004. 4. Lastly, and probably most importantly, when the login box popped up when I launched Outlook, in the user field I placed "DOMAIN\USER". This was the trick for me. In #4 above, I was entering "SERVERNAME \USER" and could not connect. I didn't even think about using "DOMAIN \USER" until I saw it somewhere on the internet. Again, thanks for all of your kind assistance. I now have my sanity back. Regards, Dean
From: Dean K on 25 Mar 2010 18:45 On Mar 25, 2:56 pm, Dean K <d...(a)tmcpower.com> wrote: > On Mar 24, 7:27 am, Ace Fekay [MVP-DS, MCT] > > > > <ace...(a)mvps.RemoveThisPart.org> wrote: > > > On Mar 22, 10:03 pm, Ace Fekay [MVP-DS, MCT] > > > > 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 d...(a)tmcpower.com > > > 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 > > > Create a hostname record called "autodiscover" (without the quotes) > > under tmcpower.com at your public DNS server. > > > I see down below you've already created it. Good. The problem may be > > that the CAS server external Autodiscover record was not set in the CAS > > configuration section. > > > > 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 > > > Ignore the "tmepower.com" test. That is usually your website, such ashttp://tmcpower.com, and can be ignored. No big deal. > > > > 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/AutoDiscover/AutoDiscover.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 > > > Don't worry about this for Outlook connectivity. If the laptop has been > > joined to the domain, and the domain is working and GPOs are applying, > > the certificate would have been automatically deployed to the laptop. > > Since it is a private cert, it will fail the external test, but for > > domain machines, it should be fine. > > > > 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. > > > Ok, when I tried to connect tohttps://tmcsbs.tmcpower.com/owatotest > > your OWA, it failed to connect. This appears to be a port remap issue > > either in your firewall or ISA. > > > > 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 > > > I hope that helps. > > > -- > > 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.comforregional support phone numbers. > > Hi Ace and All, > > Thank you to all of you for your support. I have finally resolved my > issues with RPC over HTTP (Outlook Anywhere). Hopefully placing my > resolution here will help others experiencing similar problems to get > their implementations to work as well. > > Although I tried virtually everything on every website I could find > regarding this issue, I think it all came down to a silly (stupid) > mistake that I was making on my end. But here is the combination of > things I did to make it work for me: > > 1. Installed the self-signed certificate in the Trusted Root > certificate store on the laptop. Although I'm pretty sure it was > stored there via GPO, I also manually installed the certificate there. > 2. Enabled RPC over HTTP in Exchange. This was not enabled initially. > 3. Modified the RPC registry key to ensure that the NetBios and FQDN > were pointed to 6001-6002 and 6004. > 4. Lastly, and probably most importantly, when the login box popped up > when I launched Outlook, in the user field I placed "DOMAIN\USER". > > This was the trick for me. In #4 above, I was entering "SERVERNAME > \USER" and could not connect. I didn't even think about using "DOMAIN > \USER" until I saw it somewhere on the internet. > > Again, thanks for all of your kind assistance. I now have my sanity > back. > > Regards, > Dean One additional change made was to add a new key "RPC" and Dword "DefConnectOpts" under HKCU\sofrware\microsoft\office\12.0\outlook.
From: Ace Fekay [MVP-DS, MCT] on 25 Mar 2010 19:45 > On Mar 25, 2:56�pm, Dean K <d...(a)tmcpower.com> wrote: >> On Mar 24, 7:27�am, Ace Fekay [MVP-DS, MCT] >> >> >> >> <ace...(a)mvps.RemoveThisPart.org> wrote: >>>> On Mar 22, 10:03�pm, Ace Fekay [MVP-DS, MCT] >>>> 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 d...(a)tmcpower.com >>>> � �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 >>> Create a hostname record called "autodiscover" (without the quotes) >>> under tmcpower.com at your public DNS server. >>> I see down below you've already created it. Good. The problem may be >>> that the CAS server external Autodiscover record was not set in the CAS >>> configuration section. >> >>>> � �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 >>> Ignore the "tmepower.com" test. That is usually your website, such >>> ashttp://tmcpower.com, and can be ignored. No big deal. >>>> � �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/AutoDiscover/AutoDiscover.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 >>> Don't worry about this for Outlook connectivity. If the laptop has been >>> joined to the domain, and the domain is working and GPOs are applying, >>> the certificate would have been automatically deployed to the laptop. >>> Since it is a private cert, it will fail the external test, but for >>> domain machines, it should be fine. >> >>>> � �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. >>> Ok, when I tried to connect tohttps://tmcsbs.tmcpower.com/owatotest >>> your OWA, it failed to connect. This appears to be a port remap issue >>> either in your firewall or ISA. >> >>>> � �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 >> >>> I hope that helps. >> >>> -- >>> 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.comforregional support phone numbers. >> >> Hi Ace and All, >> >> Thank you to all of you for your support. I have finally resolved my >> issues with RPC over HTTP (Outlook Anywhere). Hopefully placing my >> resolution here will help others experiencing similar problems to get >> their implementations to work as well. >> >> Although I tried virtually everything on every website I could find >> regarding this issue, I think it all came down to a silly (stupid) >> mistake that I was making on my end. But here is the combination of >> things I did to make it work for me: >> >> 1. Installed the self-signed certificate in the Trusted Root >> certificate store on the laptop. Although I'm pretty sure it was >> stored there via GPO, I also manually installed the certificate there. >> 2. Enabled RPC over HTTP in Exchange. This was not enabled initially. >> 3. Modified the RPC registry key to ensure that the NetBios and FQDN >> were pointed to 6001-6002 and 6004. >> 4. Lastly, and probably most importantly, when the login box popped up >> when I launched Outlook, in the user field I placed "DOMAIN\USER". >> >> This was the trick for me. In #4 above, I was entering "SERVERNAME >> \USER" and could not connect. I didn't even think about using "DOMAIN >> \USER" until I saw it somewhere on the internet. >> >> Again, thanks for all of your kind assistance. I now have my sanity >> back. >> >> Regards, >> Dean > > One additional change made was to add a new key "RPC" and Dword > "DefConnectOpts" under HKCU\sofrware\microsoft\office\12.0\outlook. Interesting that you had to enable RPC/HTTPS in SBS and believe it's enabled by default. I didn't even think to ask because I assumed it was configured. I must have missed that in the thread somewhere? Yes, anytime you logon to a domain, you must use the domain, not the servername. I didn't realize there was an issue with prompting to logon, unless I missed that in the earlier posts, too? If you join a laptop to the SBS domain using the proper method (the Connect method), or manually joining it and manually moving the laptop computer object from Computers to SBS Computers, it should automatically get the certificate added. Curious, how did you join the laptop? Either way, I'm glad you figured it out. -- 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 check http://support.microsoft.com for regional support phone numbers.
From: SteveB on 25 Mar 2010 22:22 Dean you said you had looked at and followed the link on the RWW home page. It clearly states you must use domainname\username to login so I think you overlooked that very important part. Anyway congratulations on finally getting it working although I don't know why it was so hard in your case. "Dean K" <dean(a)tmcpower.com> wrote in message news:a7d0614c-d18a-4d81-8117-652b9cee6e35(a)z18g2000prh.googlegroups.com... On Mar 24, 7:27 am, Ace Fekay [MVP-DS, MCT] <ace...(a)mvps.RemoveThisPart.org> wrote: > > On Mar 22, 10:03 pm, Ace Fekay [MVP-DS, MCT] > > > 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 d...(a)tmcpower.com > > 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 > > Create a hostname record called "autodiscover" (without the quotes) > under tmcpower.com at your public DNS server. > > I see down below you've already created it. Good. The problem may be > that the CAS server external Autodiscover record was not set in the CAS > configuration section. > > > > > 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 > > Ignore the "tmepower.com" test. That is usually your website, such > ashttp://tmcpower.com, and can be ignored. No big deal. > > > > > > > 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/AutoDiscover/AutoDiscover.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 > > Don't worry about this for Outlook connectivity. If the laptop has been > joined to the domain, and the domain is working and GPOs are applying, > the certificate would have been automatically deployed to the laptop. > Since it is a private cert, it will fail the external test, but for > domain machines, it should be fine. > > > > > > > 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. > > Ok, when I tried to connect tohttps://tmcsbs.tmcpower.com/owato test > your OWA, it failed to connect. This appears to be a port remap issue > either in your firewall or ISA. > > > > > > > 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 > > I hope that helps. > > -- > 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.comfor regional support phone numbers. Hi Ace and All, Thank you to all of you for your support. I have finally resolved my issues with RPC over HTTP (Outlook Anywhere). Hopefully placing my resolution here will help others experiencing similar problems to get their implementations to work as well. Although I tried virtually everything on every website I could find regarding this issue, I think it all came down to a silly (stupid) mistake that I was making on my end. But here is the combination of things I did to make it work for me: 1. Installed the self-signed certificate in the Trusted Root certificate store on the laptop. Although I'm pretty sure it was stored there via GPO, I also manually installed the certificate there. 2. Enabled RPC over HTTP in Exchange. This was not enabled initially. 3. Modified the RPC registry key to ensure that the NetBios and FQDN were pointed to 6001-6002 and 6004. 4. Lastly, and probably most importantly, when the login box popped up when I launched Outlook, in the user field I placed "DOMAIN\USER". This was the trick for me. In #4 above, I was entering "SERVERNAME \USER" and could not connect. I didn't even think about using "DOMAIN \USER" until I saw it somewhere on the internet. Again, thanks for all of your kind assistance. I now have my sanity back. Regards, Dean
From: Dean K on 29 Mar 2010 14:04 HI Steve, Defnitely an oversight on my part - I don't blame anyone else but myself for not looking closely enough on the requirements for "domain/ user" on the RWW home page. I don't know if this was the silver bullet or if it was the combination of mods that did the trick but I wanted to advise others that may be facing similar problems of my resolution so that they might be able to resolve their issues more quickly than me. Thanks for all of your assistance. Regards, Dean On Mar 25, 7:22 pm, "SteveB" <newsgr...(a)public.lan> wrote: > Dean you said you had looked at and followed the link on the RWW home page. > It clearly states you must use domainname\username to login so I think you > overlooked that very important part. Anyway congratulations on finally > getting it working although I don't know why it was so hard in your case. > > "Dean K" <d...(a)tmcpower.com> wrote in message > > news:a7d0614c-d18a-4d81-8117-652b9cee6e35(a)z18g2000prh.googlegroups.com... > On Mar 24, 7:27 am, Ace Fekay [MVP-DS, MCT] > > > > > > > > <ace...(a)mvps.RemoveThisPart.org> wrote: > > > On Mar 22, 10:03 pm, Ace Fekay [MVP-DS, MCT] > > > > 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 d...(a)tmcpower.com > > > 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 > > > Create a hostname record called "autodiscover" (without the quotes) > > under tmcpower.com at your public DNS server. > > > I see down below you've already created it. Good. The problem may be > > that the CAS server external Autodiscover record was not set in the CAS > > configuration section. > > > > 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 > > > Ignore the "tmepower.com" test. That is usually your website, such > > ashttp://tmcpower.com, and can be ignored. No big deal. > > > > 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/AutoDiscover/AutoDiscover.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 > > > Don't worry about this for Outlook connectivity. If the laptop has been > > joined to the domain, and the domain is working and GPOs are applying, > > the certificate would have been automatically deployed to the laptop. > > Since it is a private cert, it will fail the external test, but for > > domain machines, it should be fine. > > > > 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. > > > Ok, when I tried to connect tohttps://tmcsbs.tmcpower.com/owatotest > > your OWA, it failed to connect. This appears to be a port remap issue > > either in your firewall or ISA. > > > > 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 > > > I hope that helps. > > > -- > > 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.comforregional support phone numbers. > > Hi Ace and All, > > Thank you to all of you for your support. I have finally resolved my > issues with RPC over HTTP (Outlook Anywhere). Hopefully placing my > resolution here will help others experiencing similar problems to get > their implementations to work as well. > > Although I tried virtually everything on every website I could find > regarding this issue, I think it all came down to a silly (stupid) > mistake that I was making on my end. But here is the combination of > things I did to make it work for me: > > 1. Installed the self-signed certificate in the Trusted Root > certificate store on the laptop. Although I'm pretty sure it was > stored there via GPO, I also manually installed the certificate there. > 2. Enabled RPC over HTTP in Exchange. This was not enabled initially. > 3. Modified the RPC registry key to ensure that the NetBios and FQDN > were pointed to 6001-6002 and 6004. > 4. Lastly, and probably most importantly, when the login box popped up > when I launched Outlook, in the user field I placed "DOMAIN\USER". > > This was the trick for me. In #4 above, I was entering "SERVERNAME > \USER" and could not connect. I didn't even think about using "DOMAIN > \USER" until I saw it somewhere on the internet. > > Again, thanks for all of your kind assistance. I now have my sanity > back. > > Regards, > Dean
|
Next
|
Last
Pages: 1 2 Prev: "SBS & EBS Users" group name change on LinkedIn Next: Time server error |