Re: ConnectComputer, Reboot, can't connect to domain.

From: Tristan (Tristan_at_nospam.com)
Date: 02/09/04 

Date: Mon, 9 Feb 2004 17:45:19 +1300

I didn't use the same domain name. It used to be PCI and it got changed to
PUBC.Local.

3 machines worked perfectly, the others just all failed after reboot. Only
thing different between the 3 that worked was that they had a different
Ethernet card in them.

"Tony Su" <anonymous@discussions.microsoft.com> wrote in message
news:c84b01c3edb5$4a1ace00$a501280a@phx.gbl...
> Next time, take the advice of experience SysAdmins and
> don't re-use the same Domain or machine names.
>
> If believe the client/Users won't feel comfortable with
> new names, you can modify names imperceptibly by doing
> things like adding a period to the names.
>
> Tony Su
>
>
>
>
>
> >-----Original Message-----
> >Hi,
> >
> >I can't figure this out, setup 20 users on the server
> using the 'user'
> >template.
> >
> >On the workstation, logged in as Local administator.
> Loaded up IE, typed in
> >servername\connectcomputer, wizard loaded fine, entered
> in username and
> >password. Message pops up saying that I've joined the
> domain and then it
> >reboots. Change the login to the name of the user I've
> just added and click
> >ok and it says either one of the following errors:
> >
> >The system cannot log you on now because the domain pubc
> is not available.
> >
> >and I different machines I would sometimes get:
> >
> >The trust relationship between the primary domain failed.
> >
> >I've managed to get connected manually by logging in
> locally as the
> >Administrator and using the Network ID Wizard, and re-
> entering the
> >information for the user. It comes up saying something
> about the user was
> >already found on the domain, would I like to use it. And
> then I reboot
> >again and everything is fine.
> >
> >These workstations are running XP Pro, they used to be
> connected up to a
> >previous domain.
> >
> >Any ideas?
> >
> >
> >.
> >

Relevant Pages

  • Re: Connecting a remote workstation to a domain
    ... I have also selected not to dial an initial connection before ... I assume the CEO does not have a workstation available at the main office, ... remark that you will have to reboot the workstation. ... After the login script has finished and if you have Premium, ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting a remote workstation to a domain
    ... Even setting up a low end workstation in the ... I have also selected not to dial an initial connection before ... remark that you will have to reboot the workstation. ... After the login script has finished and if you have Premium, ...
    (microsoft.public.windows.server.sbs)
  • Connecting a remote workstation to a domain
    ... Login as administrator on the workstation and create a VPN-connection ... remark that you will have to reboot the workstation. ...
    (microsoft.public.windowsxp.security_admin)
  • Connecting a remote workstation to a domain
    ... Login as administrator on the workstation and create a VPN-connection ... remark that you will have to reboot the workstation. ...
    (microsoft.public.windows.server.sbs)
  • Cant login the morning after.
    ... I tried to log on after a reboot and got 2 ... logon after multiple reboots without getting a error ... server re-syncronize. ... >Each workstation has netbios turned off, ...
    (microsoft.public.windowsxp.security_admin)