Re: Problems with 'connectcomputer'

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

Date: Fri, 20 Feb 2004 14:36:32 -0600

Hi Rick,

The procedure for joining xp is basically this:

Run ipconfig/release at a dos prompt.
Unjoin from any existing domain, and join workgroup.
Reboot.
Run http://servername/connectcomputer
Select the user and computername from the wizard.
Follow the prompts
After a restart or two, you are all done.

For complete information, use SBS help (on the server), it is complete,
including joining older OS's. 

--
Les Connor [SBS MVP]
-------------------------------------
SBS Rocks !
"Rick R." <rrollins@rtsnospamtechnicalservices.com> wrote in message
news:O38NIr69DHA.2532@TK2MSFTNGP09.phx.gbl...
> Matt,
>
> I must not have the right procedures.  What I have been doing to get these
> XP machines up and running:
>
> 1-Create a user on the server using the wizard. This also creates a
computer
> for that user.
> 2-On the client machine, go into the users area and add the network
password
> to the users account.
>    For the XP machines, this automatically connects any shared folders and
> shared printers.
> 3-Setup the users Outlook Express to point to the IP of the new server.
>     Now the client has email from the exchange portion of the new server.
> 4-Eventually, try the 'https://servername/connectcomputer'  for the
purpose
> of configuring this pc
>     to allow a remote session. The intent is to allow the user to connect
to
> their desktop from home.
>     Of course, the user at home would bring up the
> 'https://servername/remote' to actually login from home.
>
> Step4 is a big problem on both machines I've tried so far.  The first
> machine starts a configuration wizard. But it winds up taking hours for
the
> status bar to get to 100% and then it just sits there. Never telling me
it's
> done, or I have to reboot.  In a previous post, they told me to do a
windows
> update manually first and then try again. (haven't yet).  But the other
> machine, which has XP SP1 give me this 'You have open connections to the
> server' error and doesn't let me go through the 'connectcomputer' wizard.
>
> So am I doing this right?  Is there a manual way to configure these XP pro
> machines for a remote session?
>
> Thanks
>
>
> "Matthew Huynh [MSFT]" <mhuynh@online.microsoft.com> wrote in message
> news:#SBAzA69DHA.1128@tk2msftngp13.phx.gbl...
> > Hi Rick,
> >
> > The remote web workplace is accessed through https://servername/remote
> from
> > your internal client computer.  The site you are connecting to is for
the
> > purpose of joining the computer to the SBS domain.  It sounds like you
are
> > already joined to the domain.
> >
> > --
> > -Matt
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> > "Rick R." <rrollins(nospam)@rtstechnicalservices.com> wrote in message
> > news:edRRxky9DHA.1312@TK2MSFTNGP09.phx.gbl...
> > > I have SBS2003 and I'm trying to get this remote workplace going. So
on
> my
> > > XP machines (which are connecting to the server for email,
> > printers,etc...)
> > > I bring up the ConnectComputer webpage
> > (http://servername/connectcomputer).
> > > It brings up the link to 'connect to the network now'.  That link
> responds
> > > with an error something like 'There are open connections to the sbs
> > server.
> > > Close all windows and connections and try again'.
> > >
> > > Well I do not have any other programs running, except the internet
> > explorer
> > > window itself.  So what is making the connection?  I guess it auto
finds
> > the
> > > printers that are setup on the server. But nothing I can tell is
> running.
> > >
> > > Any ideas?
> > >
> > > Do I need to run this machine in a special startup mode or something?
> > >
> > > Thanks
> > >
> > > Rick
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: Joining Domain Across Subnets
    ... concerning the joining of the machines see: ... The new server isn't going to be a DNS server so do I need zone transfers ... Host records that map the name of the domain controller to its IP ...
    (microsoft.public.windows.server.active_directory)
  • maximum number of sessions
    ... We have 6 pcs connecting to a 7 pc we call our server. ... to peer all the machines including the server are running windows xp pro. ... session command we can see ... the ten connections, but it is showing multiple connections for the same ...
    (microsoft.public.windowsxp.network_web)
  • connection limit reached
    ... We have 6 pcs connecting to a 7 pc we call our server. ... to peer all the machines including the server are running windows xp pro. ... session command we can see ... the ten connections, but it is showing multiple connections for the same ...
    (microsoft.public.windowsxp.general)
  • Re: Host Public Website on SBS 2008 Network
    ... you mention a dual WAN router. ... If I configured the server to run in the DMZ of the netgear router ... All it does is to nominate a computer within the LAN to which all incoming connections are forwarded which aren't explicitly sent elsewhere. ... The idea is that if the machines in it get hacked, they cannot then be used as platforms to attack machines in the main LAN. ...
    (microsoft.public.windows.server.sbs)
  • Re: users limitation in Win XP Home
    ... >>I have a running five machines and one ... >>of them acts as a server for a particular program. ... routers do not normally create connections to PCs. ... my home LAN currently has 5 connections from 5 PCs ...
    (microsoft.public.windowsxp.network_web)