Re: XP Client Can't Log In To Server After Initial Setup
From: Trevor Home (_at_)
Date: 06/17/04
- Next message: root: "Re: Raid"
- Previous message: Brian: "Re: Where do you enter a WEP key on SBS 2003 DC??"
- In reply to: Bob N.: "Re: XP Client Can't Log In To Server After Initial Setup"
- Next in thread: Bob N.: "Re: XP Client Can't Log In To Server After Initial Setup"
- Reply: Bob N.: "Re: XP Client Can't Log In To Server After Initial Setup"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 16 Jun 2004 22:00:29 -0500
Bob,
Thanks for posting what you found out. I was stumped. I'll file this in
brain RAM. :)
-Trevor
"Bob N." <news@ranvest.com> wrote in message
news:%23nFwDW9UEHA.1952@TK2MSFTNGP12.phx.gbl...
> To All:
>
> Microsoft Tech Support has successfully helped me identify the source of
the
> connectivity issue, which is as follows.
>
> When I built the client machines, I gave a name to each machine such as
> Sys1, Sys2, etc. This was intended to be a temporary name for testing
> purposes only. When I set up the SBS 2003 server, I created computer
names
> for the final network such as Legal, Accounting, Reception, etc.
>
> Unbeknownst to me, when I attempted to set up the client computer on the
> network via http://server/connectcomputer, the server was "discovering"
the
> temporary system names and adding them to the list of network computers in
> Active Directory. When I selected Administrator and Username for the
system
> I was attempting to connect, I also selected the appropriate computer name
> that I had created in the To Do list such as Reception.
>
> Upon the first reboot of the client system, the computer name was
apparently
> changed to Reception and the Users were added to the system. On the
second
> reboot of the client system, the log in to the server with the domain
> administrator's credentials failed. The only log in that would work was a
> log in the local machine. However, if I then attempted to browse the
entire
> network from the local machine, I would be asked for credentials and I
could
> then log in to the server and browse the shared folders.
>
> The crux of the problem turned out to be the fact that although I had
> selected the appropriate computer name from the list I had created in the
To
> Do list, the server still thought that the machine was named Sys1. If I
> tried to connect to the server, the server would not acknowledge the
> credentials because the name of system didn't match what the server
expected
> to see. As a result, in order to use http://server/ConnectComputer to
> perform the necessary setup of the client systems, it appears as a best
> practice that the client system should be named with the same name that
> appears in the To Do list. This will prevent the issue I experienced from
> occurring. I was able to confirm this in a subsequent test with the
> Microsoft technician. It was also suggested to me that you could simply
name
> the client computer and not add any computers in the To Do list. At
setup,
> the server will add the name of computer you are joining to the domain and
> the only other thing to be done is the addition of the appropriate users.
>
> Thanks to all who responded to this issue. I hope that this will prevent
> others from encountering the same problem.
>
> Bob N.
>
> "Bob N." <news@ranvest.com> wrote in message
> news:et7pcToUEHA.484@TK2MSFTNGP10.phx.gbl...
> > To All:
> >
> > I have just set up a new SBS 2003 Premium server. I have been able to
get
> > my new XP Pro clients to connect to the server
> > (http://server/ConnectComputer). After the Administrator and the proper
> > User are selected, together with the proper Computer, the client system
> > reboots, connects to the server and initiates some activity that is
> > impossible to see due to the speed at which it executes.
> >
> > After the second reboot of the client system, if I try to log in to the
> > server using the Username and Password that were created during the
server
> > setup, I get a message that the client cannot connect to the domain or
the
> > user cannot be found. Before I continue setting up additional client
> > computers (and possibly creating more of the same problems) I would like
> to
> > know how I can resolve this problem on the two systems that are unable
to
> > log on to the server. Any assistance will be gratefully appreciated.
> >
> > Bob N.
> >
> >
>
>
- Next message: root: "Re: Raid"
- Previous message: Brian: "Re: Where do you enter a WEP key on SBS 2003 DC??"
- In reply to: Bob N.: "Re: XP Client Can't Log In To Server After Initial Setup"
- Next in thread: Bob N.: "Re: XP Client Can't Log In To Server After Initial Setup"
- Reply: Bob N.: "Re: XP Client Can't Log In To Server After Initial Setup"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
