Re: XP Client Can't Log In To Server After Initial Setup

Tech-Archive recommends: Fix windows errors by optimizing your registry

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

Date: Tue, 15 Jun 2004 11:06:47 -0500

On the workstation:

C:\Program Files\Microsoft Windows Small Business Server\Clients

the .log files. 

-- 
Les Connor [SBS MVP]
-------------------------------------
SBS Rocks !
"Bob N." <news@ranvest.com> wrote in message
news:OuQ9f6uUEHA.2520@TK2MSFTNGP10.phx.gbl...
> Hi Marina:
>
> On the client system I find two folders that seem to relate to the two
> attempts I have made to connect the client to the network. They are as
> follows:
>
>     _sbs_netsetup_|*.*
>     _sbs_netsetup_.RECP|*.*
>
> The second one refelcts the fact that I renamed the client computer to
RECP
> in order to try the network setup once again.  Both of these folders
contain
> the following two files:
>
>     NTUSER.DAT.LOG
>     NTUSER.DAT
>
> Neither of these files can be viewed with a text editor such as Notepad.
Is
> there another place where I might find the appropriate log file or does
this
> information suggest a reason for the problem I am having?
>
> Bob
>
> "Marina Roos [SBS-MVP]" <marina@roos.nodontwantspam.nl.com> wrote in
message
> news:%23oBAgnuUEHA.2908@TK2MSFTNGP10.phx.gbl...
> > On the client there should be a logfile as a result of the
connectcomputer
> > thing. Search for it and post the relevant parts.
> >
> > -- 
> > Regards,
> >
> > Marina
> > Microsoft SBS-MVP
> >
> > "Bob N." <news@ranvest.com> schreef in bericht
> > news:uYcGaiuUEHA.1656@TK2MSFTNGP09.phx.gbl...
> > > Hi Marina,
> > >
> > > I deleted the WINS adddress from the external NIC as you suggested.
The
> > > three options were all set correctly to point to 192.168.16.2.  At
this
> > > point I decided to reboot the server just to make sure that the WINS
> > change
> > > was properly implemented.  After the reboot I again tested the client
> and
> > I
> > > still cannot log on to the domain.
> > >
> > > I removed the client computer from the server's list of computers and
I
> > then
> > > changed the client computer to a different name and made it a member
of
> > > Workgroup.  I next added the original client computer name back to the
> > > server with the appropriate choices for applications, etc.  Finally, I
> > > repeated //ConnectComputer and  it worked well through the first
reboot
> of
> > > the client.  At the second reboot of the client, I still cannot log on
> to
> > > the domain and complete the client setup with applications, etc.  I
have
> > > tried logging on as Administrator with the domain administrator's
> > password,
> > > as Administrator with the local machine Administrator's password and
as
> > the
> > > User with the User's network password, all to no avail.
> > >
> > > Wither do we go from here?
> > >
> > > Best wishes,
> > >
> > > Bob N.
> > > "Marina Roos [SBS-MVP]" <marina@roos.nodontwantspam.nl.com> wrote in
> > message
> > > news:eOkR95rUEHA.644@tk2msftngp13.phx.gbl...
> > > > Hi Bob,
> > > >
> > > > Delete the WINS address from the external nic.
> > > > Make sure you have options 003, 006 and 044 in DHCP-server, Scope
> > options
> > > > pointing to your server-IP.
> > > > Your client is not getting all the settings now.
> > > >
> > > > -- 
> > > > Regards,
> > > >
> > > > Marina
> > > > Microsoft SBS-MVP
> > > >
> > > > "Bob N." <news@ranvest.com> schreef in bericht
> > > > news:%23mwkEEpUEHA.1604@TK2MSFTNGP12.phx.gbl...
> > > > > Hi Frank,
> > > > >
> > > > > Yes, it looks like we are crossing our posts.  Here are the IP
> > entries:
> > > > >
> > > > > Server Local Area Connection
> > > > > IP 192.168.16.2
> > > > > SubNet 255.255.255.0
> > > > > Default Gateway - empty
> > > > > DNS Server 192.168.16.2
> > > > >
> > > > > Network Connection
> > > > > IP 10.0.0.2
> > > > > Sub Net 255.255.255.0
> > > > > Default Gateway 10.0.0.1 (router address)
> > > > > DNS Server 192.168.16.2
> > > > > Primary WINS Server 192.168.16.2
> > > > > NETBIOS over TCPIP - disabled
> > > > >
> > > > > Client
> > > > > IP 192.168.16.100
> > > > > Sub Net 255.255.255.0
> > > > > Default Gateway - empty
> > > > > DNS Server 192.168.16.2
> > > > > "Frank McCallister" <anonymous@discussions.microsoft.com> wrote in
> > > message
> > > > > news:u41w03oUEHA.3692@TK2MSFTNGP09.phx.gbl...
> > > > > > Hi Bob
> > > > > >
> > > > > > I posted before you posted your second message. Please post the
> > > results
> > > > of
> > > > > > ipconfig /all for your server and one of the Workstations which
is
> > > > giving
> > > > > > difficulty.
> > > > > >
> > > > > > Frank
> > > > > > "Bob N." <news@ranvest.com> wrote in message
> > > > > > news:eBQ8eroUEHA.412@TK2MSFTNGP10.phx.gbl...
> > > > > > > Here is some additional information.  I logged onto one of the
> > > client
> > > > > > > systems as Administrator and then I browsed to My Computer,
> Entire
> > > > > > Network,
> > > > > > > Microsoft Windows Network, MyNetworkName.  I was then asked
for
> > user
> > > > > name
> > > > > > > and password credentials which, when entered, allowed me to
> browse
> > > to
> > > > > and
> > > > > > > see various folders on the Server.  I was able to replicate
this
> > > > > behavior
> > > > > > > when I logged on to the client using the correct user name and
> > > > password
> > > > > > for
> > > > > > > the User that was created when I ran ConnectComputer.
> > > > > > >
> > > > > > > Thus, it appears that something is preventing me from
connecting
> > > > > directly
> > > > > > to
> > > > > > > the server using the log on credentials that work when I
> > indirectly
> > > > > browse
> > > > > > > to the network.  I should add that I installed ISA 2000 as
part
> of
> > > the
> > > > > > > Premium installation and I directed the SBS client setup to
> > include
> > > > the
> > > > > > > Firewall Client.  I don't know if this is the source of the
> > problem,
> > > > but
> > > > > I
> > > > > > > thought it was worth noting.
> > > > > > >
> > > > > > > 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.
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: Client named on the network same as Server
    ... One user, one account. ... and always attempt to salvage log files. ... I also think that they had multiple machines that were using administrator ... I am certain SBS 2003 is strong enough not to allow a client with the ...
    (microsoft.public.windows.server.sbs)
  • Re: Help need desperately!
    ... I don't know if this will help, but reading through your log files and the ... when I ran the SMS Report Count SMS Client Versions, ... for the Client Push Installation ... IP subnet and Active Directory site ...
    (microsoft.public.sms.inventory)
  • Re: Windows 2004 deploy and SMSRestart
    ... Also please verify the settings for "Run with administrative rights". ... If you find the client still will not restart correctly, ... the log files on the client computer to check the issue further: ...
    (microsoft.public.sms.swdist)
  • Re: FreeNX on FC6 authentication problem
    ... As far as the log files, ... port 3441 ssh2. ... Now the client ...
    (Fedora)
  • Re: unable to install client after SMSLOGON point recovered
    ... Jeff Harbaugh ... This posting is provided "AS IS" with no warranties, ... Those icons would usually be blank in the case of a client de-install. ... > directory on the client PCs, there are missing log files such as ...
    (microsoft.public.sms.admin)