Re: connect computer setup fails

From: Les Connor [SBS MVP] (les.connor_at_DEL.cfive.ca)
Date: 07/10/04 

Date: Sat, 10 Jul 2004 08:38:59 -0500

Steve,

You aren't getting the 'connect to the network now' link, then? Or you are
and it fails when you click that link ?

The administrator account you use to login - this is an account with
administrative rights on the *local* computer, right?

Try entering the the urls into the address bar, starting with
http://servername/connectcomputer/start.htm. Inspect the workstation drive
and see if any of the folders/files listed are written to the disk. 

-- 
Les Connor [SBS MVP]
-------------------------------------
SBS Rocks !
"steve" <spearson@socal.rr.com> wrote in message
news:uKB9WzjZEHA.716@TK2MSFTNGP11.phx.gbl...
> Hi Les,
>
> It fails on the first step (a) and returns
> http://willswing01/ConnectComputer/error.htm.
>
>  error: automation server can't creat object
>  code: 0
>  url: http://willswing01/connectcomputer/start.htm
>
> willswing01 is the SBS server. The local user is the default
'administrator'
> account. I haven't installed anything except the network card driver. I
can
> log on to the server remotely from the problem computer to get email
> http://willswing01/exchange or to the remote workplace. The fresh install
IP
> info is the same as I originally posted except the workstation name is
> 'temp' on 'workgroup'. I set every option in browser security to 'allow'.
I
> even tried a different network card. I never had any problems with the
other
> client installs but they were all before I installed ISA.
>
> Steve
>
> "Les Connor [SBS MVP]" <les.connor@DEL.cfive.ca> wrote in message
> news:%23uqx%23LgZEHA.2944@TK2MSFTNGP11.phx.gbl...
> > Steve,
> >
> > Can you identify where in the process your error shows up:
> >
> > a) Client Setup Main Page http://ServerName/ConnectComputer/Default.htm
> >
> > This is the default page, and should give you a "connect to the network
> now"
> > link.
> >
> > b) http://ServerName/ConnectComputer/precheck.htm
> >
> > After clicking the link, you go to the above page. This page checks that
> the
> > computer OS is w2k or above. If it passes,
> >
> > c) http://ServerName/ConnectComputer/start.htm
> >
> > This page should ask you to download an active-x control (nshelp.dll)
and
> it
> > should be copied to the workstation %windir%\Downloaded Program Files
> > folder. At the same time, At the same time, setup will create a folder
> > %sbsprogramdir%\Clients at the client computer, and copy NetSetup.chm,
> > sbsart.chm, sbsshared.chm, server.txt, and usermap.txt from the server
> > (http://ServerName/ConnectComputer) to the folder. There should also be
a
> > file called SBSNetSetup.log created in the folder to log the setup
> process.
> > If this log file exists, please post the contents of it.
> >
> > The Acive-X control then performs some checks, and if the computer is a)
> > already a domain member, b) a domain controller or SBS server, c) not
able
> > to resolve the SBS server and/or domain name (as listed in server.txt),
or
> > d) more than one active non-vpn connection - various error messages are
> > generated.
> >
> > If you get by the above, then you are asked for a username and password
> for
> > an account that has permissions on the domain to join the computer.
> >
> > After successful authentication, you can assign users to the computer
and
> > migrate local profiles.
> >
> > Next, you select a computer name from the list.
> >
> > Once you click finish, we are into another process.
> >
> > So, if you can identify the point of failure in the above, and post the
> log
> > file if it exists, then we may be able to troubleshoot. Detailed
> information
> > such as the account name (local administrator) on the workstation, etc.
> > would also help.
> >
> > -- 
> > Les Connor [SBS MVP]
> > -------------------------------------
> > SBS Rocks !
> >
> >
> >
> > "steve" <spearson@socal.rr.com> wrote in message
> > news:OGqAktfZEHA.808@tk2msftngp13.phx.gbl...
> > > Sorry for the extra thread, I've been borrowing other computers to
> search
> > > for a solution. In any case, I used your recommended procedure before
> the
> > > initial post and I've since reformatted and reinstalled a fresh copy
of
> > > XPpro with the same results. The return error from the browser is :
> > >  >  error: automation server can't creat object
> > >  >  code: 0
> > >  >  url: http://servername/connectcomputer/start.htm
> > > The browser security settings are at the default level that worked for
> > every
> > > other install--maybe they need to be lower with ISA installed? I'll
add
> > the
> > > server to trusted sites and report the results.
> > >
> > > Thanks for your suggestions.
> > > Steve
> > >
> > >
> > >
> > > "Marina Roos [SBS-MVP]" <marina@roos.nodontwantspam.nl.com> wrote in
> > message
> > > news:u4p2v9dZEHA.2388@TK2MSFTNGP11.phx.gbl...
> > > > Hi Steven,
> > > >
> > > > Delete the computeraccount on the SBS.
> > > > Put the workstation in a workgroup, reboot.
> > > > Create the computeraccount on the SBS and use
> servername/connectcomputer
> > > on
> > > > the workstatioin to join it to the domain.
> > > > If ISA is installed on your server, make sure the Firewall client
gets
> > > > installed on the workstation and check that the LAN-settings in IE
are
> > > > pointing to your servername and port 8080.
> > > >
> > > > -- 
> > > > Regards,
> > > >
> > > > Marina
> > > > Microsoft SBS-MVP
> > > >
> > > > "Steven Pearson" <steve@willswing.com> schreef in bericht
> > > > news:6b738552.0407090746.21a8222a@posting.google.com...
> > > > > I have an small SBS 2003 Premium installation with 10 clients and
15
> > > > > licenses. The SBS server provides DHCP. I installed all of the
> clients
> > > > > before ISA server using the connectcomputer wizard without
incident.
> > > > > Last week after my hard drive crashed, I installed XP on a new
drive
> > > > > and used the SBS server manager to add a new computer to the
domain.
> > > > > When I tried the connect computer wizard from the new XP install
(as
> a
> > > > > local administrator with the client as a unique name in workgroup
> > > > > mode), it returns the error page
> > > > > http://willswing01/ConnectComputer/error.htm. Adding the client to
> the
> > > > > domain with yet a different name through the 'control panel,
> computer
> > > > > name, change' allowed me to add applications, service packs and
the
> > > > > ISA client but I wasn't able to connect to the Internet.
> > > > > Interestingly, if I logged on locally as the domain administrator,
I
> > > > > could browse the Internet even though my other login was also a
> domain
> > > > > administrator. I noticed that computer name in the server
> > > > > administration screen that was associated with the crashed hard
> drive
> > > > > had a red x through the name--I thought maybe the server was
somehow
> > > > > locking my computer with the mac ID so I deleted the old computer
> > > > > name. I uninstalled the ISA client and set the client back to
> > > > > workgroup mode but the connectcomputer wizard still won't start.
> > > > >
> > > > > Microsoft Windows XP [Version 5.1.2600]
> > > > > (C) Copyright 1985-2001 Microsoft Corp.
> > > > > C:\Documents and Settings\Administrator>ipconfig /all
> > > > > Windows IP Configuration
> > > > >         Host Name . . . . . . . . . . . . : CNAME
> > > > >         Primary Dns Suffix  . . . . . . . :
> > > > >         Node Type . . . . . . . . . . . . : Hybrid
> > > > >         IP Routing Enabled. . . . . . . . : No
> > > > >         WINS Proxy Enabled. . . . . . . . : No
> > > > > Ethernet adapter Local Area Connection:
> > > > >         Connection-specific DNS Suffix  . : WillsWing.local
> > > > >         Description . . . . . . . . . . . : Intel(R) PRO/1000 MT
> > > > > Network Connection
> > > > >         Physical Address. . . . . . . . . : 00-07-E9-4E-42-C9
> > > > >         Dhcp Enabled. . . . . . . . . . . : Yes
> > > > >         Autoconfiguration Enabled . . . . : Yes
> > > > >         IP Address. . . . . . . . . . . . : 192.168.16.21
> > > > >         Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > > > >         Default Gateway . . . . . . . . . : 192.168.16.2
> > > > >         DHCP Server . . . . . . . . . . . : 192.168.16.2
> > > > >         DNS Servers . . . . . . . . . . . : 192.168.16.2
> > > > >         Primary WINS Server . . . . . . . : 192.168.16.2
> > > > >         Lease Obtained. . . . . . . . . . : Thursday, July 08,
2004
> > > > > 6:13:31 PM
> > > > >         Lease Expires . . . . . . . . . . : Friday, July 16, 2004
> > > > > 6:13:31 PM
> > > > >
> > > > > I've browsed at least 50 client setup failure threads in this
> > > > > newsgroup and can't find a solution.
> > > > > Steve Pearson
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: FIRED IT ADMIN HAS LOCKED US OUT OF SBS
    ... you have risen to an Administrator this would be a given. ... server and run all LOB apps on these. ... If there are no encrypted files, just reset the DSRM account ...
    (microsoft.public.windows.server.sbs)
  • Re: FIRED IT ADMIN HAS LOCKED US OUT OF SBS
    ... Teneo> Interesting post and Im now gonna be a party pooper... ... connections) before cutting power to the server and to the Internet ... If there are no encrypted files, just reset the DSRM account ... and try old domain Administrator account's passwords. ...
    (microsoft.public.windows.server.sbs)
  • RE: Getting alot of these emails
    ... Thank you for posting in the SBS newsgroup. ... this issue can occur if your SBS 2003 server is ... Disable the Guest account in your SBS 2003 server and enable Stronger ... Microsoft is providing this information as a convenience to you. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote desktop: cannot copy files why still not working
    ... I created a new user on the XP box, set as an administrator ... this new user account is local to the XP system, ... In my environment, when I do an RDP connection to a server, I first log ... member of the local administrators group on the server. ...
    (microsoft.public.windows.server.security)
  • Re: Remote desktop: cannot copy files why still not working
    ... this new user account is local to the XP system, and a member of the local administrator's group on that workstation. ... In my environment, when I do an RDP connection to a server, I first log on to the xp workstation using my regular, non-privileged domain account, run mstsc, and then logon to the server using a domain account that is a member of the local administrators group on the server. ... In addition, I frequently use runas to run privileged applications on the workstation using my "administrator" account, and have found that files cannot be copied between those applications and anything running under the credentials of my regular account - even though my administrator account actually does have full access to everything on the workstation - just not through my regular account's view of that workstation. ...
    (microsoft.public.windows.server.security)