SBS 2008 - Cant connect client computers, seems like IIS is not working.
Hello Experts;
Today I tried connecting a brand new Windows 7 Pro workstation to a SBS 2008 setup that is barely a month old; The Server has already had two Win 7 Pro machines connected to it, so it has all the necessary updates to make that work properly.
I have checked for all the obvious problems with connecting workstations, all is exactly as it should be as far as I can tell.
Trying to browse to http;//connect does not work, the page is never displayed. Running the IE connection diagnostic says that the server is there but is not accepting connection requests.
I also cannot browse to the server in any other web based capacity either, which makes me think something has gone arwy with IIS or similar, causing none of the web functionality to work.
Hoping an expert can point me in the direction of a solution!
With regards the link you posted, I knew about that, and as that page now states, Rollup 3 solves the problem, and I have made sure the server has Rollup 3 installed.
Also, I have noted that I don't seem to be able to hit ANY web resources on the SBS 2008, so I suspect that is the root cause of all the problems.
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck
Shreedhar Ette
Hi,
Restart the IIS Admin Service.
Also check the event log for any errors.
------------
Shree
OzoneFriendly
ASKER
We not only tried that, but rebooted the whole server, and still no go.
There are pairs of these errors over and over;
The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.
Context: Application 'Search', Catalog 'index file on the search server Search'
The start address <sts3s://remote.clientdomain.com:987/contentdbid={82200f11-4237-4eac-a0f8-268af13c0b74}> cannot be crawled.
Context: Application 'Search index file on the search server', Catalog 'Search'
Details:
The crawler could not communicate with the server. Check that the server is available and that the firewall access is configured correctly. (0x80041200)
OzoneFriendly
ASKER
I found the following comments in another question that refer to the two event log errors, made by TechSoEasy;
Problem is, This is a clean SBS 2008 install, I can't see how the problem occurred, as nothing was done to the server at all between when it last worked and now.
Unlimited question asking, solutions, articles and more.
OzoneFriendly
ASKER
I think maybe I have found the problem;
Looks likely that someone installed some Eaton Power Software for a new UPS, and it's management interface is setup on LOCALHOST;
Could it be that this has interferred with the website stuff running on SBS ?
OzoneFriendly
ASKER
Okay, so I went poking around in the SBS 2008 console and found the websites tab, and all the websites were listed as OFFLINE, and lo and behold, I can just click to turn them back on;
So now the remote web workplace is working, as is Companyweb;
But, trying to use the connect url still doesn't work, but now it returns a 404
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
Your help has saved me hundreds of hours of internet surfing.
fblack61
Cris Hanna
to markdmac:
This is SBS 08...the correct URL for SBS 08 is http://connect
markdmac
Mea culpa, I missed we were not talking SBS 2003. The part about DNS still applies. :-)
OzoneFriendly
ASKER
The DNS stuff is all good, that's SBS basics I do understand; The Best Practices analyser has listed a bunch of problems, I'm working through the ones I can figure out to see what difference they make.
As far I as I know, all updates are applied, however it now appears the update service is broken (says I changed the WSUS configuration, which I don't recall doing), so I can't be 100% just now, will need to look into it.
Appears to be a bogus problem, but perhaps in my case it's not?
OzoneFriendly
ASKER
WOO HOO! Now I can use the HTTP://CONNECT URL to hook up the new workstation. Sadly, I have no idea what fixed it, but as I was working through the Best Practices Analyser, I'm giving the points to that comment, as it seems to have done the trick.
Cris Hanna
Glad to hear things are beginning to fall back into line
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
OzoneFriendly
ASKER
Thank's for the help; I don't actually know what fixed it, but it came good after working through the SBSBPA, so that's a win!
Also, post the results of an ipconfig /all from both the SBS and the Win7 client.