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

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.

Frank
Mon Jun 14 22:35:26 CDT 2004

Hi Bob

On the second reboot you should logon as Administrator to finish the Client
Install. This will Install all Client Apps setup for deployment. If you have
already installed ISA be sure the Firewall Client was pushed to WS if you
set it up in Client Apps to be installed. If not manually install it while
logged in as Administrator by running Setup from \\servername\Program
Files\Microsoft ISA Server\Clients folder. This should resolve your issue.
For the remaining clients you can setup deployment ahead of time by
following Instructions in the document in the root of CD5 Premium
Technologies CD.

Frank McCallister
COMPUMAC
"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.
>
>

Bob
Mon Jun 14 22:43:05 CDT 2004

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.
>
>

Frank
Mon Jun 14 23:05:10 CDT 2004

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.
> >
> >
>
>

Bob
Mon Jun 14 23:16:49 CDT 2004

Hi Frank,

Thanks for your reply. I checked the client and the Firewall Client did not
get installed, even though it is included in the Client Applications that
are to be deployed when the client is set up through the server. I manually
installed it by going to \\server\mspclnt\setup.exe as noted in the document
on the Premium edition CD. By the way, I did use that document to guide me
through the ISA installation.

After I logged off and back on the client locally, I could see that the
Firewall Client has now been installed. However, I still cannot log on to
the server through the domain, regardless if I try Administrator or
Username. This really has me baffled. Any ideas as to what I should try
next?

Bob N.
"Frank McCallister" <anonymous@discussions.microsoft.com> wrote in message
news:eplcNnoUEHA.2972@TK2MSFTNGP12.phx.gbl...
> Hi Bob
>
> On the second reboot you should logon as Administrator to finish the
Client
> Install. This will Install all Client Apps setup for deployment. If you
have
> already installed ISA be sure the Firewall Client was pushed to WS if you
> set it up in Client Apps to be installed. If not manually install it while
> logged in as Administrator by running Setup from \\servername\Program
> Files\Microsoft ISA Server\Clients folder. This should resolve your issue.
> For the remaining clients you can setup deployment ahead of time by
> following Instructions in the document in the root of CD5 Premium
> Technologies CD.
>
> Frank McCallister
> COMPUMAC
> "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.
> >
> >
>
>

Bob
Mon Jun 14 23:27:06 CDT 2004

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.
> > >
> > >
> >
> >
>
>

Marina
Tue Jun 15 04:50:53 CDT 2004

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.
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Bob
Tue Jun 15 09:54:04 CDT 2004

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.
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Marina
Tue Jun 15 10:01:30 CDT 2004

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.
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Bob
Tue Jun 15 10:37:12 CDT 2004

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.
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Les
Tue Jun 15 11:06:47 CDT 2004

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.
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Bob
Tue Jun 15 11:19:30 CDT 2004

Hi Les,

Thank you for the log file location. I located two log files as follows:

sbmig.log:

6/14/2004 7:13 PM
-- Starting sbsmig.exe --
AddUsersToLocalAdmin() -- calling NetLocalGroupAddMembers( Administrators,
TCNET.local\Administrator )
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() -- calling NetLocalGroupAddMembers( Administrators,
TCNET.local\Stephanie )
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddDomainUserToRemoteDesktopGroup() -- we're not a server, not adding domain
users group to remote desktop group
calling SetComputerNameEx( Reception )
ChangeComputerName() -- decrypt(1) OK
ChangeComputerName() -- decrypt(2) OK
RemoveAccount() -- ADsOpenObject() failed [-2147467259]
ChangeComputerName() -- RemoveAccount() failed, dwErr = [-2147467259]
ChangeComputerName() -- NetRenameMachineInDomain() failed, dwErr = [1355]
ChangeIPAddress() -- we're not a server, not changing the IP config
DeleteSBSFile() -- DeleteFile( C:\Program Files\Microsoft Windows Small
Business Server\Clients\sbsmig.exe ) failed -- GLE = [5]
running logoff command [C:\Program Files\Microsoft Windows Small Business
Server\Clients\sbsmig.exe] [C:\Program Files\Microsoft Windows Small
Business Server\Clients\sbsmig.exe /l]
-- Exiting sbsmig.exe --

6/14/2004 7:13 PM
-- Starting sbsmig.exe --
running with the /l switch
WinMain() - calling DwWaitForShell()
WinMain() - calling ExitWindowsEx()
WinMain() - ExitWindowsEx() returned [1] - GLE() - [183]
-- Exiting sbsmig.exe --

6/15/2004 6:47 AM
-- Starting sbsmig.exe --
AddUsersToLocalAdmin() -- calling NetLocalGroupAddMembers( Administrators,
TCNET.local\Administrator )
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() -- calling NetLocalGroupAddMembers( Administrators,
TCNET.local\Stephanie )
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddUsersToLocalAdmin() - NetLocalGroupAddMembers() failed -- nas == [1789]
AddDomainUserToRemoteDesktopGroup() -- we're not a server, not adding domain
users group to remote desktop group
calling SetComputerNameEx( Reception )
ChangeComputerName() -- decrypt(1) OK
ChangeComputerName() -- decrypt(2) OK
RemoveAccount() -- ADsOpenObject() failed [-2147467259]
ChangeComputerName() -- RemoveAccount() failed, dwErr = [-2147467259]
ChangeComputerName() -- NetRenameMachineInDomain() failed, dwErr = [1355]
ChangeIPAddress() -- we're not a server, not changing the IP config
DeleteSBSFile() -- DeleteFile( C:\Program Files\Microsoft Windows Small
Business Server\Clients\sbsmig.exe ) failed -- GLE = [5]
running logoff command [C:\Program Files\Microsoft Windows Small Business
Server\Clients\sbsmig.exe] [C:\Program Files\Microsoft Windows Small
Business Server\Clients\sbsmig.exe /l]
-- Exiting sbsmig.exe --

6/15/2004 6:47 AM
-- Starting sbsmig.exe --
running with the /l switch
WinMain() - calling DwWaitForShell()
WinMain() - calling ExitWindowsEx()
WinMain() - ExitWindowsEx() returned [1] - GLE() - [183]
-- Exiting sbsmig.exe --

SBSNetSetup.log:

6/14/2004 6:45 PM
-- Starting SBS Net Setup --
found [16] keys
CProfileList::CProfileList() - added [1003, C:\Documents and
Settings\Stephanie Bellone] to the profile dir map
CProfileList::CProfileList() - added [Stephanie Bellone, C:\Documents and
Settings\Stephanie Bellone] to the profile dir map
CAuthPage::OnNotify() - PSN_WIZNEXT - User Name: Stephanie
CAuthPage::GetUsersAndComputers() - ADsOpenObject(
LDAP://SERVER.TCNET.local/DC=TCNET,DC=local, Stephanie, [PW] )
CAuthPage::OnNotify() - PSN_WIZNEXT - GetUsersAndComputers() failed, hr =
[-2147016646]
CAuthPage::OnNotify() - PSN_WIZNEXT - User Name: Administrator
CAuthPage::GetUsersAndComputers() - ADsOpenObject(
LDAP://SERVER.TCNET.local/DC=TCNET,DC=local, Administrator, [PW] )
CAuthPage::OnNotify() - PSN_WIZNEXT - GetUsersAndComputers() failed, hr =
[-2147016646]
-- user canceled, exiting setup.exe

6/14/2004 6:53 PM
-- Starting SBS Net Setup --
found [16] keys
CProfileList::CProfileList() - added [1003, C:\Documents and
Settings\Stephanie Bellone] to the profile dir map
CProfileList::CProfileList() - added [Stephanie Bellone, C:\Documents and
Settings\Stephanie Bellone] to the profile dir map
CAuthPage::OnNotify() - PSN_WIZNEXT - User Name: administrator
CAuthPage::GetUsersAndComputers() - ADsOpenObject(
LDAP://SERVER.TCNET.local/DC=TCNET,DC=local, administrator, [PW] )
CAuthPage::OnNotify() - PSN_WIZNEXT - GetUsersAndComputers() failed, hr =
[-2147016646]
-- user canceled, exiting setup.exe

6/14/2004 7:10 PM
-- Starting SBS Net Setup --
found [16] keys
CProfileList::CProfileList() - added [1003, C:\Documents and
Settings\Stephanie Bellone] to the profile dir map
CProfileList::CProfileList() - added [Stephanie Bellone, C:\Documents and
Settings\Stephanie Bellone] to the profile dir map
CAuthPage::OnNotify() - PSN_WIZNEXT - User Name: Administrator
CAuthPage::GetUsersAndComputers() - ADsOpenObject(
LDAP://SERVER.TCNET.local/DC=TCNET,DC=local, Administrator, [PW] )
CAuthPage::GetUsersAndComputers() - ADsOpenObject(
LDAP://SERVER.TCNET.local/DC=TCNET,DC=local, Administrator, [PW] )
OpenXMLFile() - DOMDocument::load( C:\Program Files\Microsoft Windows Small
Business Server\Clients\usermap.txt ) failed - [1]
CWizard::PrepAutoLogon()
CWizard::PrepAutoLogon() - runonce key set
CWizard::PrepAutoLogon() - setting DefaultDomainName_PostMigrate to [TCNET],
[0]
FinishNetworkingSetup()
CWizard::FinishNetworkingSetup() - outputting XML file
FinishNetworkingSetup() -- calling NetJoinDomain( NULL, TCNET.local,
ou=sbscomputers,ou=computers,ou=mybusiness,dc=tcnet,dc=local,
TCNET.local\Administrator, [pw], 359 )
FinishNetworkingSetup() - succeeded
CWizard::DeleteCSAllUsers() -- deleting
'HKEY_USERS\.DEFAULT\software\microsoft\smallbusinessserver\clientsetup'
CWizard::DeleteCSAllUsers() -- deleting
'HKEY_USERS\S-1-5-19\software\microsoft\smallbusinessserver\clientsetup'
CWizard::DeleteCSAllUsers() -- deleting
'HKEY_USERS\S-1-5-19_Classes\software\microsoft\smallbusinessserver\clientse
tup'
CWizard::DeleteCSAllUsers() -- deleting
'HKEY_USERS\S-1-5-20\software\microsoft\smallbusinessserver\clientsetup'
CWizard::DeleteCSAllUsers() -- deleting
'HKEY_USERS\S-1-5-20_Classes\software\microsoft\smallbusinessserver\clientse
tup'
CWizard::DeleteCSAllUsers() -- deleting
'HKEY_USERS\S-1-5-21-3221298443-292744275-950438618-1003\software\microsoft\
smallbusinessserver\clientsetup'
CWizard::DeleteCSAllUsers() -- deleting
'HKEY_USERS\S-1-5-21-3221298443-292744275-950438618-1003_Classes\software\mi
crosoft\smallbusinessserver\clientsetup'
CWizard::DeleteCSAllUsers() -- deleting
'HKEY_USERS\S-1-5-18\software\microsoft\smallbusinessserver\clientsetup'
Reboot() -- about to reboot

6/14/2004 9:59 PM
-- Starting SBS Net Setup --
CheckPreInstall() -- already in the domain -- exiting

6/14/2004 10:05 PM
-- Starting SBS Net Setup --
CheckPreInstall() -- DsRoleGetPrimaryDomainInformation for sbs domain failed
5
found [16] keys
CProfileList::CProfileList() - added [1003, C:\Documents and
Settings\Stephanie Bellone] to the profile dir map
CProfileList::CProfileList() - added [1006, C:\Documents and
Settings\__sbs_netsetup__] to the profile dir map
CProfileList::CProfileList() - added [500, C:\Documents and
Settings\Administrator] to the profile dir map
CProfileList::CProfileList() - added [Administrator, C:\Documents and
Settings\Administrator] to the profile dir map
CProfileList::CProfileList() - added [Stephanie, C:\Documents and
Settings\Stephanie Bellone] to the profile dir map
CAuthPage::OnNotify() - PSN_WIZNEXT - User Name: Administrator
CAuthPage::GetUsersAndComputers() - ADsOpenObject(
LDAP://SERVER.TCNET.local/DC=TCNET,DC=local, Administrator, [PW] )
CAuthPage::GetUsersAndComputers() - ADsOpenObject(
LDAP://SERVER.TCNET.local/DC=TCNET,DC=local, Administrator, [PW] )
CAuthPage::OnNotify() - PSN_SETACTIVE - our computer name IS in the AD
OpenXMLFile() - DOMDocument::load( C:\Program Files\Microsoft Windows Small
Business Server\Clients\usermap.txt ) failed - [1]
-- user canceled, exiting setup.exe

6/15/2004 6:39 AM
-- Starting SBS Net Setup --
found [16] keys
CProfileList::CProfileList() - added [1003, C:\Documents and
Settings\Stephanie Bellone] to the profile dir map
CProfileList::CProfileList() - added [1006, C:\Documents and
Settings\__sbs_netsetup__] to the profile dir map
CProfileList::CProfileList() - added [500, C:\Documents and
Settings\Administrator] to the profile dir map
CProfileList::CProfileList() - added [Administrator, C:\Documents and
Settings\Administrator] to the profile dir map
CProfileList::CProfileList() - added [Stephanie, C:\Documents and
Settings\Stephanie Bellone] to the profile dir map
CAuthPage::OnNotify() - PSN_WIZNEXT - User Name: administrator
CAuthPage::GetUsersAndComputers() - ADsOpenObject(
LDAP://SERVER.TCNET.local/DC=TCNET,DC=local, administrator, [PW] )
CAuthPage::GetUsersAndComputers() - ADsOpenObject(
LDAP://SERVER.TCNET.local/DC=TCNET,DC=local, administrator, [PW] )
OpenXMLFile() - DOMDocument::load( C:\Program Files\Microsoft Windows Small
Business Server\Clients\usermap.txt ) failed - [1]
-- user canceled, exiting setup.exe

6/15/2004 6:45 AM
-- Starting SBS Net Setup --
found [16] keys
CProfileList::CProfileList() - added [1003, C:\Documents and
Settings\Stephanie Bellone] to the profile dir map
CProfileList::CProfileList() - added [1006, C:\Documents and
Settings\__sbs_netsetup__] to the profile dir map
CProfileList::CProfileList() - added [500, C:\Documents and
Settings\Administrator] to the profile dir map
CProfileList::CProfileList() - added [Administrator, C:\Documents and
Settings\Administrator] to the profile dir map
CProfileList::CProfileList() - added [Stephanie, C:\Documents and
Settings\Stephanie Bellone] to the profile dir map
CAuthPage::OnNotify() - PSN_WIZNEXT - User Name: administrator
CAuthPage::GetUsersAndComputers() - ADsOpenObject(
LDAP://SERVER.TCNET.local/DC=TCNET,DC=local, administrator, [PW] )
CAuthPage::GetUsersAndComputers() - ADsOpenObject(
LDAP://SERVER.TCNET.local/DC=TCNET,DC=local, administrator, [PW] )
OpenXMLFile() - DOMDocument::load( C:\Program Files\Microsoft Windows Small
Business Server\Clients\usermap.txt ) failed - [1]
CWizard::PrepAutoLogon()
CWizard::PrepAutoLogon() - runonce key set
CWizard::PrepAutoLogon() - setting DefaultDomainName_PostMigrate to [TCNET],
[0]
FinishNetworkingSetup()
CWizard::FinishNetworkingSetup() - outputting XML file
FinishNetworkingSetup() -- calling NetJoinDomain( NULL, TCNET.local,
ou=sbscomputers,ou=computers,ou=mybusiness,dc=tcnet,dc=local,
TCNET.local\administrator, [pw], 359 )
FinishNetworkingSetup() - succeeded
CWizard::DeleteCSAllUsers() -- deleting
'HKEY_USERS\.DEFAULT\software\microsoft\smallbusinessserver\clientsetup'
CWizard::DeleteCSAllUsers() -- deleting
'HKEY_USERS\S-1-5-19\software\microsoft\smallbusinessserver\clientsetup'
CWizard::DeleteCSAllUsers() -- deleting
'HKEY_USERS\S-1-5-19_Classes\software\microsoft\smallbusinessserver\clientse
tup'
CWizard::DeleteCSAllUsers() -- deleting
'HKEY_USERS\S-1-5-20\software\microsoft\smallbusinessserver\clientsetup'
CWizard::DeleteCSAllUsers() -- deleting
'HKEY_USERS\S-1-5-20_Classes\software\microsoft\smallbusinessserver\clientse
tup'
CWizard::DeleteCSAllUsers() -- deleting
'HKEY_USERS\S-1-5-21-3221298443-292744275-950438618-500\software\microsoft\s
mallbusinessserver\clientsetup'
CWizard::DeleteCSAllUsers() -- deleting
'HKEY_USERS\S-1-5-21-3221298443-292744275-950438618-500_Classes\software\mic
rosoft\smallbusinessserver\clientsetup'
CWizard::DeleteCSAllUsers() -- deleting
'HKEY_USERS\S-1-5-18\software\microsoft\smallbusinessserver\clientsetup'
Reboot() -- about to reboot

From the contents of these log files I can see I have some issues, but I
really don't know where to go from here. Les and Marina, your interest and
your assistance is greatly appreciated. I will be away from my office
during the course of the day but I will check back in when I return this
evening.

Bob N.


"Les Connor [SBS MVP]" <les.connor@DEL.cfive.ca> wrote in message
news:OgVVELvUEHA.3664@TK2MSFTNGP12.phx.gbl...
> 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.
> > > > > > > >
> > > > > > &g