SBS 2011 - OWA not working internal or external - errors Fix my network
Hello,
A few weeks back a client called that the SBS 2011 was booting extremely slow.
It took about 30 minutes for the sever to boot and ran slow and with errors, I was told they changed some NIC settings and I found out they disabled IPV6, after enabling it everything seemed to be worked fine.
But now the external mail isn't working anymore, I can't reach https//server/OWA or https://remote.hostname.com/OWA. When running "fix my network" I'm getting 2 errors that cannot be fixed by the wizard.
Error 1: Error while connecting to Exchange Management shell
Connecting to remote sever failed with the following error message: The WinRM-client ....
Error 2: A networking component is not configured properly. (Component ID 4) more info @kb 120178 which doesn't help me much.
I checked the bindings for the certificate with another SBS2011 and its show the same settings.
Another note: The person that disabled IPV6 also did ‘something’ to SharePoint (I noticed that all SharePoint services are stopped). Changing this did not resolve the problem.
They did this because they needed the same port that SharePoint was using, so I also checked if there was a service using port 80 or 443 just in case the software they installed also needed port 80 but it seems to be fine.
any thoughts?
A few weeks back a client called that the SBS 2011 was booting extremely slow.
It took about 30 minutes for the sever to boot and ran slow and with errors, I was told they changed some NIC settings and I found out they disabled IPV6, after enabling it everything seemed to be worked fine.
But now the external mail isn't working anymore, I can't reach https//server/OWA or https://remote.hostname.com/OWA. When running "fix my network" I'm getting 2 errors that cannot be fixed by the wizard.
Error 1: Error while connecting to Exchange Management shell
Connecting to remote sever failed with the following error message: The WinRM-client ....
Error 2: A networking component is not configured properly. (Component ID 4) more info @kb 120178 which doesn't help me much.
I checked the bindings for the certificate with another SBS2011 and its show the same settings.
Another note: The person that disabled IPV6 also did ‘something’ to SharePoint (I noticed that all SharePoint services are stopped). Changing this did not resolve the problem.
They did this because they needed the same port that SharePoint was using, so I also checked if there was a service using port 80 or 443 just in case the software they installed also needed port 80 but it seems to be fine.
any thoughts?
ASKER
Hi Simon,
It only flags that the Remote Desktop Gateway service should be started and to use NT AUTORITY\Network Service account as its login account.
But that service is not even listed in services.msc ?
It only flags that the Remote Desktop Gateway service should be started and to use NT AUTORITY\Network Service account as its login account.
But that service is not even listed in services.msc ?
Maybe check in IIS. Confirm the IIS services such as WWW Publishing Service is started. Make sure the Default Web Site is operational and running on the normal ports. Check Default Web Site bindings. Can you get to http://server/. SBS should return an IIS7 default page or possible something RWW / RDS related.
Run this and post the output:
I suppose the other thing it could be is IIS permissions, and that is easier fixed by resetting the virtual directory: http://technet.microsoft.com/en-us/library/ff629372(v=exchg.141).aspx
In addition, unchecking the ipv6 box on the NIC can corrupt the network stack itself.. so resetting that can help but I would be a bit weary about that.. it is your only domain controller (since you are running SBS 2011) and that could also have some negative side effects.
Test-ServiceHealth
I suppose the other thing it could be is IIS permissions, and that is easier fixed by resetting the virtual directory: http://technet.microsoft.com/en-us/library/ff629372(v=exchg.141).aspx
In addition, unchecking the ipv6 box on the NIC can corrupt the network stack itself.. so resetting that can help but I would be a bit weary about that.. it is your only domain controller (since you are running SBS 2011) and that could also have some negative side effects.
ASKER
Hi guys,
The WWW Publishing Service is running but I cannot connect to http://sbs-server/
Keeps saying: waiting for http://sbs-server, I expect it’s going to timeout any moment now.
The default website is giving a question mark but its running..
The default website bindings are the same as another sbs 2011 server that’s working fine (it also gives a question mark on the default website, so this is normal?)
@ adam, I can't run the Exchange Shell, it gives the same error:
[sbs-server.hostname.local
+ CategoryInfo : OpenError: (System.Manageme....Remote
Should I risk resetting the network stack?
The WWW Publishing Service is running but I cannot connect to http://sbs-server/
Keeps saying: waiting for http://sbs-server, I expect it’s going to timeout any moment now.
The default website is giving a question mark but its running..
The default website bindings are the same as another sbs 2011 server that’s working fine (it also gives a question mark on the default website, so this is normal?)
@ adam, I can't run the Exchange Shell, it gives the same error:
[sbs-server.hostname.local
+ CategoryInfo : OpenError: (System.Manageme....Remote
Should I risk resetting the network stack?
Can you connect to the Default Website if you just type http://localhost into a browser? Or https://localhost.
You mentioned they did something with SharePoint. Is SharePoint running in its own website? Maybe try shutting down the SharePoint site. Then shut down and start up the Default Website and then do an IISRESET from a command prompt.
Also, you mentioned they disabled IPv6. What happens if you re-enabling IPv6?
You mentioned they did something with SharePoint. Is SharePoint running in its own website? Maybe try shutting down the SharePoint site. Then shut down and start up the Default Website and then do an IISRESET from a command prompt.
Also, you mentioned they disabled IPv6. What happens if you re-enabling IPv6?
ASKER
Hello, sorry for the late response. http://localhost or https://localhost don't work, stopping SharePoint and preforming IISRESET didn't help however..
I found out that FILEMAKER SERVER 11 was installed on this server. I seems this is the reason for my errors, not the IPV6 problem. I tried the steps on these posts but I can't get it to run..
http://social.technet.microsoft.com/Forums/en-US/4fbd6944-5a96-46bb-aaa8-4aac96c4c4ce/filemaker-server-really-messed-things-up?forum=smallbusinessserver
and
https://www.experts-exchange.com/questions/27401709/IIS-Exchange-Broken-after-failed-Filemaker-Server-install.html
I found out that FILEMAKER SERVER 11 was installed on this server. I seems this is the reason for my errors, not the IPV6 problem. I tried the steps on these posts but I can't get it to run..
http://social.technet.microsoft.com/Forums/en-US/4fbd6944-5a96-46bb-aaa8-4aac96c4c4ce/filemaker-server-really-messed-things-up?forum=smallbusinessserver
and
https://www.experts-exchange.com/questions/27401709/IIS-Exchange-Broken-after-failed-Filemaker-Server-install.html
Sounds like FileMaker might be taking over ports 80 or 443. Can you change the default ports for FileMaker?
Maybe this can help?
http://help.filemaker.com/app/answers/detail/a_id/215/~/specifying-a-port-number-for-instant-web-publishing
Maybe this can help?
http://help.filemaker.com/app/answers/detail/a_id/215/~/specifying-a-port-number-for-instant-web-publishing
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I ended up checking the difference between a working sbs & the one I was repairing
EMS connects in via web services, so if OWA doesn't work then it is probably the same cause as OWA failing to work.
Simon.