Re: ConnectComputer Page Cannot Be Found

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

You need to find out what port the apache server is using, relative to the IIS default website which is on port 80/443.

In a typical SBS/Trend implemenation, you might see:

Default Website 80/443
OfficeScan Website 8059/4343
SMEX Website 16372/16373

It's crazy to use Apache when you have IIS running though. I can't imagine what the issues were that led to this; Trend's products will pretty well always install and work if you just take the default > next approach.

Too much thinking (making advanced/optional selections) with an unfamiliar product is generally what causes problems. (that happens with SBS as well ;-))

--
-----------------------------------------------
Les Connor [SBS MVP]

"Keith" <Keith@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:F3EFA5E2-B258-44A7-9353-D9213AC96178@xxxxxxxxxxxxxxxx
Les,

Thanks for the response.

I think we have to use Apache with the Trend product. I spent literally two
days with their tech support people, and that was the solution that worked.
After all I went through to get that to work, I don't want to break it as
well.

Is there another way to connect clients to the SBS without using
ConnectComputer?

Thanks again,

Keith


"Les Connor [SBS MVP]" wrote:

Chances are there's a port conflict between the Apache server and the
default web site in IIS.

Uninstall Trend completely, including the apache server - it's not required.
The *other* option on installation of Trend is to install into IIS, which is
the correct choice. Don't install Trend into the default website, install it
into it's own - separate - website.

--
-----------------------------------------------
Les Connor [SBS MVP]

"Keith" <Keith@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8F3906E6-539B-4D09-82EA-8B6069F100C8@xxxxxxxxxxxxxxxx
> I have an SBS 2003 Premium installation that has been in operation for > 4
> years. Today, after setting up a new computer in Server Management, I > was
> unable to connect from the client. When I tried to go to
> http://servername/ConnectComputer from the client in IE, I get the
> following:
>
> HTTP 400 - Bad Request
>
> The page cannot be found.
>
> I also receive this same error from other clients when trying to browse > to
> the ConnectComputer page. This never happened before.
>
> I can successfully ping the server from this new client machine, so I > know
> I
> have connectivity.
>
> I found something online elsewhere suggesting that this involves the
> default
> website in IIS. The default website in IIS is Stopped, and, if I try > to
> start it, I receive the following message:
>
> The tracking (workstation) service is not running.
>
> When I Googled this message, I found the following suggestion:
>
> Go to the cmd line and type "net start httpfilter".
>
> Unfortunately, when I do this, I receive the following message:
>
> The service name is invalid.
>
> More help is available by typing NET HELPMSG 2185.
>
> The only thing different on the SBS server that I can think of is that > I
> installed Trend Micro's Worry-Free Business Security Standard, which
> required
> that Apache HTTP Server be installed. I'm wondering if that is what is
> causing the default website problem, which is in turn causing the
> ConnectComputer problem.
>
> Sorry for writing a novel...I just wanted to include as much info as
> possible. If anyone has any ideas, I would greatly appreciate hearing
> them.
>
> Thanks,
>
> Keith
>
>
>

.

Relevant Pages

  • Re: Permission Problems SBS2003 R1
    ... website on the SBS server? ... Default permissions and user rights for IIS 6.0 ... Step 3: Please check the permissions in IIS manager: ... Step 4: Re-running CEICW on SBS server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Apache vs IIS
    ... Windows Server not on my Linux Server so there for I would chose IIS. ... Not that Apache is bad but ASP.NET is far easier and faster to create good web forms in. ... PHP on a IIS server is rather easy to run once you install PHP on a PC but if you only use PHP why not use Apache for Windows. ...
    (alt.php)
  • Re: Apache vs IIS
    ... Windows Server not on my Linux Server so there for I would chose ... Not that Apache is bad but ASP.NET is far easier and faster to ... IIS is designed for ASP, ... Apache running on a Linux server. ...
    (alt.php)
  • Re: Apache vs IIS
    ... my Windows Server not on my Linux Server so there for I would ... IIS is designed for ASP, ... can run asp on Apache, ... in running php from IIS vs Apache. ...
    (alt.php)
  • Re: Apache vs IIS
    ... my Windows Server not on my Linux Server so there for I would chose IIS. ... Not that Apache is bad but ASP.NET is far easier and faster to create good web forms in. ... IIS is designed for ASP, ... PHP on a IIS server is rather easy to run once you install PHP on a PC but if you only use PHP why not use Apache for Windows. ...
    (alt.php)