Cannot access Remote, OWA and Active Sync
I was able to access Remote, OWA and Active Sync on my systems. We were troubleshooting issues with Windows updates and can no longer access these modules.
Server: SBS2008SBS
Exchange: 2007
Router NSA220
Intel Modular servers
On the router I have a service setup with the ports that I want opened. I have a separate service for mail. I had https in the Mail group but changed it into the other services. When I run MxToolbox Ports 443 and http are closed. All of the other ports are working?
When I run the Exchange connectivity test I get the following:
Host name freedomsys.com doesn't match any name found on the server certificate CN=secure.concentric.com, OU=Concentric Cloud Solutions, O=XO Communications LLC, L=Plano, S=Texas, C=US.
Attempting to test potential Autodiscover URL https://autodiscover.freedomsys.com/AutoDiscover/AutoDiscover.xml
Testing of this potential Autodiscover URL failed.
Test Steps
Attempting to resolve the host name autodiscover.freedomsys.co
The host name couldn't be resolved.
Tell me more about this issue and how to resolve it
Additional Details
Host autodiscover.freedomsys.co
Attempting to resolve the host name autodiscover.freedomsys.co
The host name couldn't be resolved.
Tell me more about this issue and how to resolve it
Additional Details
Attempting to contact the Autodiscover service using the DNS SRV redirect method.
The Microsoft Connectivity Analyzer failed to contact the Autodiscover service using the DNS SRV redirect method.
Test Steps
Attempting to locate SRV record _autodiscover._tcp.freedom
The Autodiscover SRV record wasn't found in DNS.
Tell me more about this issue and how to resolve it
Can someone point me to these certificates?
Server: SBS2008SBS
Exchange: 2007
Router NSA220
Intel Modular servers
On the router I have a service setup with the ports that I want opened. I have a separate service for mail. I had https in the Mail group but changed it into the other services. When I run MxToolbox Ports 443 and http are closed. All of the other ports are working?
When I run the Exchange connectivity test I get the following:
Host name freedomsys.com doesn't match any name found on the server certificate CN=secure.concentric.com, OU=Concentric Cloud Solutions, O=XO Communications LLC, L=Plano, S=Texas, C=US.
Attempting to test potential Autodiscover URL https://autodiscover.freedomsys.com/AutoDiscover/AutoDiscover.xml
Testing of this potential Autodiscover URL failed.
Test Steps
Attempting to resolve the host name autodiscover.freedomsys.co
The host name couldn't be resolved.
Tell me more about this issue and how to resolve it
Additional Details
Host autodiscover.freedomsys.co
Attempting to resolve the host name autodiscover.freedomsys.co
The host name couldn't be resolved.
Tell me more about this issue and how to resolve it
Additional Details
Attempting to contact the Autodiscover service using the DNS SRV redirect method.
The Microsoft Connectivity Analyzer failed to contact the Autodiscover service using the DNS SRV redirect method.
Test Steps
Attempting to locate SRV record _autodiscover._tcp.freedom
The Autodiscover SRV record wasn't found in DNS.
Tell me more about this issue and how to resolve it
Can someone point me to these certificates?
How are you trying access OWA, internally or externally?
What is the URL you are using for OWA access?
What does this means
"I had https in the Mail group but changed it into the other services" elobrate on this?
What is the URL you are using for OWA access?
What does this means
"I had https in the Mail group but changed it into the other services" elobrate on this?
You need to ensure port 443 is open on your NSA220. Remote, OWA and ActiveSync will not work unless this port is open.
The Public Server Wizard on your NSA220 should help you open port 443 correctly.
The Public Server Wizard on your NSA220 should help you open port 443 correctly.
ASKER
I will start up the list:
1. Port 443 is opened on the NSA
2. I have service groups setup for each server on the NSA rather than create rules for many ports.
3. The RWA does not work inside or outside only on the server as localhost
I have been working backwards from the ISP back. I am now back to the server.
Thank you for your help.
1. Port 443 is opened on the NSA
2. I have service groups setup for each server on the NSA rather than create rules for many ports.
3. The RWA does not work inside or outside only on the server as localhost
I have been working backwards from the ISP back. I am now back to the server.
Thank you for your help.
ASKER
It appears that something is blocking the ports. I have ran wireshark and have not found anything.
I know there is a command to run to see blocked ports and what is using it but I cannot find the command.
I know there is a command to run to see blocked ports and what is using it but I cannot find the command.
Netstat is your friend.
As is the SBS BPA and the Fix My Network Wizard. After a good backup, of course.
ASKER
This whole issue started with trying to do a software upgrade for the backup that was not failing. Big issue - no backup:
Course of events
1. The software company tried to help with the install and found windows updates would not run.
2. Called Microsoft stated complex issue
3. ISP DNS server outage
4. Lost all Active Sync and OWA
Course of events
1. The software company tried to help with the install and found windows updates would not run.
2. Called Microsoft stated complex issue
3. ISP DNS server outage
4. Lost all Active Sync and OWA
ASKER
Ran netstat -abn
Stated Windows Sockets initialization failed: t
TCP 127.0.0.1:443 0.0.0.0
Stated Windows Sockets initialization failed: t
TCP 127.0.0.1:443 0.0.0.0
ASKER
Windows Sockets initialization failed: 5
UDP 0.0.0.0:50443
UDP 0.0.0.0:51443
UDP 0.0.0.0:52443
UDP 0.0.0.0:50443
UDP 0.0.0.0:51443
UDP 0.0.0.0:52443
Yeah, that info would've been good to know earlier. You've got some much bigger core networking issues going on. Much more than just an IIS or certificate issue. I doubt you can get this fixed via forums or EE. I know I'd personally need to run a half dozen tools and collate the resulting output to even know what is broke. And that is before formulating how to fix it. I think you'll need to call in some paid support, from MS or a 3rd party.
Run from cmd as administrator:
netsh winsock reset catalog
netsh int ip reset reset.log hitASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
All of the tips were great. I appreciate the help.
Start with troubleshooting *basic* connectivity. Does the RWA site work from the local LAN? If so then you likely have a router/firewall issue. If not then you likely have an IIS issue unrelated to certificates.
Posting more detailed errors and troubleshooting steps may be helpful as well. For now, don't even worry about TestExchangeConnectivity. That only helps troubleshoot configuration issues after you know IIS and your router are working as expected. And we aren't there yet.