SBS 2008 - Cant connect client computers, seems like IIS is not working.

There is an issue with connecting a Win7 machine to a SBS 2008 using the http://connect path. Have you tried manually adding the pc to the domain? You can have a look at this link as well. http://blogs.technet.com/sbs/archive/2009/02/06/using-windows-7-beta-with-sbs-2008.aspx 
 Also, post the results of an ipconfig /all from both the SBS and the Win7 client.

Hi there;

I have been told quite firmly that manually connecting machines to a SBS is a very bad thing to do, so I have not tried it;

I have quite easily connected the prior 2 Windows 7 machines, there was no trouble there at all;

IPCONFIG of the server;

C:\Windows\system32>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : LUTZSERVER
   Primary Dns Suffix  . . . . . . . : lutz.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : lutz.local

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
   Physical Address. . . . . . . . . : 00-21-5E-47-D8-0E
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::a194:be5a:c97c:32da%10(Preferred)
   Link-local IPv6 Address . . . . . : fe80::a9fd:230d:bfbb:1fe7%10(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.2(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 251666782
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-CC-A5-9B-00-21-5E-47-D8-0E

   DNS Servers . . . . . . . . . . . : fe80::a9fd:230d:bfbb:1fe7%10
                                       192.168.0.2
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 8:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{A6F34805-23A8-479C-8F03-572993BFA
4FA}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

C:\Windows\system32>

The Workstation;


C:\Users\Owner>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Lutz_Win_7
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Broadcast
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : lutz.local

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : lutz.local
   Description . . . . . . . . . . . : Atheros AR8131 PCI-E Gigabit Ethernet Con
troller (NDIS 6.20)
   Physical Address. . . . . . . . . : E0-CB-4E-2C-4A-AF
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.0.11(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Tuesday, 16 February 2010 11:08:02 AM
   Lease Expires . . . . . . . . . . : Wednesday, 24 February 2010 11:08:01 AM
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.2
   DNS Servers . . . . . . . . . . . : 192.168.0.2
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.lutz.local:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : lutz.local
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

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.

Hi,

Restart the IIS Admin Service.

Also check the event log for any errors.

------------
Shree

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)

I found the following comments in another question that refer to the two event log errors, made by TechSoEasy;

The thing is that Event ID 2436 is caused by a DNS issue:
(http://www.sharepointblogs.com/mcotw/archive/2007/01/20/wssv3-search-small-business-server-amp-dns.aspx)

and Event ID 2424 is actually caused by configuring search to run under the Network Service Account (http://support.microsoft.com/kb/927012)

And there is a hotfix that supposedly corrects that:  http://support.microsoft.com/kb/931008

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.

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 ?

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

Verify that the new WIndows 7 machine has the SBS server's IP set for its DNS and make sure there is no other DNS set on the workstation.

the proper URL should be https://servername/connectcomputer

to markdmac:
This is SBS 08...the correct URL for SBS 08 is http://connect
 

Mea culpa, I missed we were not talking SBS 2003.  The part about DNS still applies.  :-)

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.

Looks like the only error in the Best Practices Analyser that I won't be able to fix is this one;

The CNAME resource record for the Sites alias should point to the fully qualified domain name of the computer that is running Windows SBS 2008.

Which from this query;

https://www.experts-exchange.com/questions/24737476/CNAME-resource-reocrds-for-Site-is-incorrect.html

Appears to be a bogus problem, but perhaps in my case it's not?

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.

Glad to hear things are beginning to fall back into line

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!