403 Forbidden On Remote Web Workplace on SBS 2011

Hello Experts,

we recently had a server die and had to restore it from a backup, its running sbs 2011.  After this restore though i have noticed that no one can login to the remote web workplace anymore.  when you do login whether its from the domain admin account or a regular user, you get a 403 forbidden message.  The login page also does not show up properly, normally the RWW will show the company name, a little blue gradient behind the login, and the windows sbs logo to the left of the username and password boxes but in this case i only see the login boxes, checkmark to rememerb me, divider line, and blue login arrow.  

Things I have tried so far -
verified permissions in the sbs console, went to the shared folders and websites and ensured the  users are on there
checked permissions in iis, currently it has the exact same permissions as another work sbs 2011 install
check the application pool associated with it and it is set to version 4 on .net framework

things i have noticed -
first i noticed that when i try to login on the server I get "HTTP Eroor 403.14 - forbidden the web server is configured to not list the contents of this directory"  when i go into the remote virtual directory in iis and then enable directory browsing it will log you in but the login screen still doesn't display correctly and it doesn't allow any useful fucntions, it just shows the contents of the remoteaccess directory

I have also noticed that when compared against the source of a working RWW login page the login page of the problem on is missing some code, I'll place an example snippet below

Problem Server
 <div id="MainArea" class="main">
        <div id="LanguageSelectPanel" class="language-container">
            <span class="language-selector">

Open in new window


Working Server
 <div id="MainArea" class="main" style="background-image:url(&#39;/Remote/Customization/Product/logon.bg.png&#39;);">
        <div id="LanguageSelectPanel" class="language-container">
            <span class="language-selector">

Open in new window


when i checked that file the path that is missing from the problem servers code is the blue gradient i mentioned earlier that is missing from behind the username and password boxes, something that i'm sure is related to the issue of not being able to login.  the file is there on the problem server.

Now to me easiest solution to this would be to recover the whole RWW site from a backup prior to the failures, I have one prior to all the RAID issues and server crashes that we had experienced that caused the server to crash from a few months back, since nothing really changes from the time of install except for any customization, then i figure that is my best bet, but I'm not sure how to restore it.  

Any help is greatly appreciated, thank you.
ctagleAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AndyKeenCommented:
Hi Ctagle

We have seen this issue lots of times with SBS2011.

Have you considered that it may be the client that is struggling and not SBS itself.

While I am not saying for one minute it is the client - you may well have a server issue, our clients often call us when windows has performed an update and it somehow screws up IE and hence remote connection.

We have a 'How To' PDF documents (Corny name I know - but hey...) on how to repair / set IE on a client PC when RWW doesn't work.

I have attached it - please have a look, its not long or difficult and see how you go.

In addition, what you can try first is on the SBS server itself launch an elevated command prompt and type - iisreset - Return - let it finish and try RWW again from a client.

There are other options we can look at so let us know how you get on.

Regards
Andy
ctagleAuthor Commented:
i have tried it from three or four differetn computers and browsers, client has tried it on three, tried compatibility view in IE as well, i have also run iisreset several times during my troubleshooting.  my apologies, I didn't specify that in the original question.
AndyKeenCommented:
Ok - have you checked out and followed the document as there are a couple of other things in there to check.

Also - in the SBS Console - Network - Connectivity - have you run the FIX MY NETWORK wizard?
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

AndyKeenCommented:
Also to check are the relative correct ports are open. I know this is a re-build so I can only assume they were open before.

Note these ports are different to that of SBS2003 if this a rebuild of a new OS install.
ctagleAuthor Commented:
not sure which documents you are referring to, but i'm pretty sure its not a browser issue in this case.

sbs console crashes when trying to go to the network section, will have to repair but have to take a dvd out there

ports are open
AndyKeenCommented:
The document I attached on my first post - I have attached it again.

I am just looking for the command to run the 'Fix my Network' wizard manually.

In the meantime checkout this location for errors - c:\program files\windows small business server\logs
C--temp-How-to-Fix-Remote-Web-Workpl.pdf
ctagleAuthor Commented:
seeing a ton of these:

[6524] 151104.091131.4953: Exception:
---------------------------------------
An exception of type 'Type: System.Data.SqlClient.SqlException, System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' has occurred.
Timestamp: 11/04/2015 09:11:31
Message: Cannot open database "SBSMonitoring" requested by the login. The login failed.
Login failed for user 'CORRALBOOTS\username'.
Stack:    at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
         at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
         at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
         at System.Data.SqlClient.SqlConnection.Open()
         at Microsoft.WindowsServerSolutions.SystemHealth.Monitoring.MonitoringSQLDataStore.GetSecurityProducts(String computerName, String productNamespace, String className)


i'll have to dig through them all to find others.  there are a bunch of text files
AndyKeenCommented:
I think you need to try and run 'Fix My Network on the NETWORK - FIX MY NETWORK  wizard.

There is another SBS console available - there is the standard one
START - ADMINISTRATIVE TOOLS - Windows SBS Console

there is also another one - Windows SBS Console (Advanced Mode)

Do both of these fail - can you quickly flick to them and click the Wizard before they crash.
AndyKeenCommented:
The location of the SBS 2011 fix network connection wizard is here:
C:\Program Files\Windows Small Business Server\Bin

the program you are looking for is: FNCW.exe

You can run this independently of the SBS Console
Hope it helps
Andy
ctagleAuthor Commented:
yea i actually managed to find it and i just finished running it, it didn't change anything though.
AndyKeenCommented:
can you get RWW to work on the server itself:

https://<server ip>/remote
https://<server ip>/Remote/logon?ReturnUrl=%2fremote

Can you get company web to come up - http://companyweb/SitePages/Home.aspx
ctagleAuthor Commented:
RWW doesn't work on the server itself, company web tells me "Can't connect to the configration database" when i browse to it on the server
AndyKeenCommented:
SBS and RWW are temperamental beasts.

In my experience, depending on the amount of time you have you can either spend more time/hours trying to resolve the issue and still get nowhere, or you can restore from your backup and have it sorted in 1/2 hour.

For me in this situation - it would be the restore.

I know it's not the answer you want but in the absence of anything / anyone else, that would be my best advice and advise I would take myself.

Andy

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ctagleAuthor Commented:
Sorry it took so long to select an answer, I thought I had already, I'm going to have to do a full restore.  I ended up just mapping his local drive via the rdp client to the terminal server in the mean time, thank you very much for your help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SBS

From novice to tech pro — start learning today.