<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://msmvps.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"><channel><title>Thank you Mr. Neale</title><link>http://msmvps.com/blogs/bradley/archive/2005/01/13/31827.aspx</link><description>Drat. Come home, need to check on something at the office and RWW isn't working. Rats. Okay I've got a back door so lets check out the issues..... Port 443 is responding - ran a Portqry [the GUI one for me ] and 443 and 4125 are good. Web site Certificate</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>On Documentation</title><link>http://msmvps.com/blogs/bradley/archive/2005/01/13/31827.aspx#79410</link><pubDate>Mon, 19 Dec 2005 13:24:21 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:79410</guid><dc:creator>On Q</dc:creator><description>While getting caught up on some billing and administrative whatnot this weekend, I ran across a few items that I wanted to review when they came up, but just didn't have the time. Fortunately, I had saved them for later...&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=79410" width="1" height="1"&gt;</description></item><item><title>re: Thank you Mr. Neale</title><link>http://msmvps.com/blogs/bradley/archive/2005/01/13/31827.aspx#78899</link><pubDate>Sun, 11 Dec 2005 07:49:19 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:78899</guid><dc:creator>JohnB</dc:creator><description>The problem is in the IIS Metabase - installing the frontpage extensions does something to the IIS metabase security settings, toggling the &amp;quot;IP address and Domain name restrictions&amp;quot; setting changes the metabase enough to allow the ICW firewall section to run successfully, which once it is run, corrects the Security settings even the change you have made on the &amp;quot;IP address and Domain name restrictions&amp;quot;&lt;br&gt;&lt;br&gt;Mr. Neale should know he wrote the book on it! ;-)&lt;br&gt;&lt;br&gt;&lt;a rel="nofollow" target="_new" href="http://www.amazon.com/gp/product/0672328054/ref=br_lf_b_/103-8323960-6432645?n=5&amp;amp;s=books&amp;amp;v=glance"&gt;http://www.amazon.com/gp/product/0672328054/ref=br_lf_b_/103-8323960-6432645?n=5&amp;amp;s=books&amp;amp;v=glance&lt;/a&gt;&lt;br&gt;&lt;br&gt;JohnB&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=78899" width="1" height="1"&gt;</description></item><item><title>re: Thank you Mr. Neale</title><link>http://msmvps.com/blogs/bradley/archive/2005/01/13/31827.aspx#39016</link><pubDate>Sat, 19 Mar 2005 14:38:00 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:39016</guid><dc:creator>bradley</dc:creator><description>I had the same problem and came across this by a search for &amp;quot;Error 0x80005006 returned from call to Fixing the inheritance for root dir&amp;quot;.  The sbs2003 server had been running fine for a year, I went to run the wizard a week ago to open up OWA and came across the same issue of the firewall portion failing.  I am not sure what would have changed???  Maybe a security patch???  Should I rerun the IP address and domain name restrictions to all granted access or leave it where it is now at with the local subnet only included?&lt;br&gt;&lt;br&gt;Tony&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=39016" width="1" height="1"&gt;</description></item><item><title>re: Thank you Mr. Neale</title><link>http://msmvps.com/blogs/bradley/archive/2005/01/13/31827.aspx#33396</link><pubDate>Thu, 20 Jan 2005 23:53:00 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:33396</guid><dc:creator>bradley</dc:creator><description>to me what is amazing about this type of issue...&lt;br&gt;&lt;br&gt;1.  the first thing that anyone does, is hit Google.  It is almost impossible to find something on Microsoft's web site to resolve an issue.  I would venture 80% of the error messages I run into, I google and find a message that points to a KB on MS site.  If I would go to MS site and do a search for the same error message I would Never find it.&lt;br&gt;&lt;br&gt;2.  SBS2k3 is a superior product compared to SBS 4.5 or SBS2k, However to me it seems much more fragile in the area of Breaking something that is working.  Ever patch I install now, is with crossed fingers, hoping it doesn't break something I can not resolve without a painstaking 4 hour search on Google.   My own box, which was running fine for 8 months, refused to allow me to login.  Would just sit there at a grey screen.  Tried a couple of ideas from google.  They appeared to work for a couple of days, then back to the same. Many hours of searching without a clear answer to the problem. No changes to the box, nothing in the event logs, nada.... now it appears to be working ok.   I am just waiting for one of my customers to call me, &amp;quot;oh I can't log into my server today&amp;quot;&lt;br&gt;&lt;br&gt;3.  Everyone screams load the patches, patch the box... and how many times to we have to load this on production equipment, begging and pleading to the Boot up Gods that the machine will reboot ok or better yet.. that the machine will not need to be rebooted.    &lt;br&gt;&lt;br&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=33396" width="1" height="1"&gt;</description></item><item><title>re: Thank you Mr. Neale</title><link>http://msmvps.com/blogs/bradley/archive/2005/01/13/31827.aspx#32048</link><pubDate>Thu, 13 Jan 2005 23:56:00 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:32048</guid><dc:creator>bradley</dc:creator><description>Rerunning the wizard reset the permissions as to what was needed.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=32048" width="1" height="1"&gt;</description></item><item><title>re: Thank you Mr. Neale</title><link>http://msmvps.com/blogs/bradley/archive/2005/01/13/31827.aspx#32047</link><pubDate>Thu, 13 Jan 2005 23:49:00 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:32047</guid><dc:creator>bradley</dc:creator><description>1. Congrats on finding the solution to your problem... and showing how a resourceful search can turn up the answer. Since MS employees have become so much active on the Internet, it's revolutionized how anyone who supports or builds applications using Microsoft technologies can do their work.&lt;br&gt;&lt;br&gt;2. The solution worries me. There is a similar solution for ISA logging (authentication fails, the recommendation for that situation is to enter a blank password even if the account requires a password) and the solution worked for a few weeks, then failed and I found that changing back to the original setting worked again. I wonder if the same thing will happen here because the fix is illogical.&lt;br&gt;&lt;br&gt;3. MS has got to do something about how fragile Frontpage Extensions might still be, at least there is a big improvement in Win2K3 supporting WSS compared to STS on Win2K. It's why although I have always thought that these technologies are nice ideas, if they break they're more trouble than they're worth. Besides, today if you are running WSS there is less reason (I didn't say no reason!) to be using FrontPage to support your website.&lt;br&gt;&lt;br&gt;Tony&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=32047" width="1" height="1"&gt;</description></item></channel></rss>