The SBS 2003 Network Configuration Wizard InOp

I am starting a new posting, hoping that myself along with ALL the others
here in thes tech newsgroup can get this problem resolved with the SBS 2003
Network Configuration Wizard setup.

Here is the environment, I have 27 workstations that I am migrating to SBS
2003. ALL the workstations were a member of a WORKGROUP, they were NEVER a
member of a Domain. They are all running Windows XP Professional and they ALL
point to the SBS 2003 for DHCP and DNS. I successfully connected 25 of the 27
workstations with no problem. I have two workstations that when you ran the
Network Configuration Wizard, when you clicked on "Connect to the Network"
you would receive the following error message "The Small Business Server
Networking Wizard was not installed. You may not be a member of the local
Administrators security group on this computer or your Local Intranet
security settings may be set to High. Click Connect to the network now to try
again and click Yes when prompted. If the wizard fails to install, contact
the person responsible for your network."

I have reset IE's security to the LOWEST settings, this did not help. I have
setup static IP settings, this did not work. I have reset the IP in XP, this
did not work.

I am posting the SBSClientsApps.Log here to see if this problem can be
resolved not only for me, but for everyone in this newsgroup who is
frustrated that there seems to be NO ANSWER EXCEPT TOTALLY WIPING OUT THE
ENTIRE HARD DRIVE AND REINSTALLING XP. I did this on one of the machines that
woudl not connect and NOW, it is connected to the SBS 2003 with NO PROBLEMS.

Here is the log information ;
-- Starting AppLnch.exe --
DoAlwaysRun() -- '/s' not found on the command line
-- DoAlwaysRun() failed, exiting --

NOW, can someone PLEASE come up with a solution for the problem?

I am also begging that you DO NOT go down the road of IP settings not
pointing to the SBS 2003 DNS or that the machine was probably a member of
another domain. Once again, ALL THE MACHINES are pointing directly to the SBS
2003 on this LAN. ALL of the machines were NEVER a member of a domain, only a
workgroup.

The one machine that is left, has all sorts of custom applications and data,
to wipe it out and start over would be a DISASTER.

PLEASE....HELP!!
--
PCNS Support Team

Sorry, I don't have a solution to the specific problem you're having
with running the Connect to wizard. However, I believe that as long as
you created the computer accounts using the wizard on the server, if
you end up having to joing the computers manually, it's no big deal.
I've had to do this before because sometimes those darned computers
just won't cooperate. But if you believe that you must use the connect
to wizard, then hopefully someone else will have some suggestions for
you.


On Jan 30, 2:51 pm, PCNS <P...@discussions.microsoft.com> wrote:
> I am starting a new posting, hoping that myself along with ALL the others
> here in thes tech newsgroup can get this problem resolved with the SBS 2003
> Network Configuration Wizard setup.
>
> Here is the environment, I have 27 workstations that I am migrating to SBS
> 2003. ALL the workstations were a member of a WORKGROUP, they were NEVER a
> member of a Domain. They are all running Windows XP Professional and they ALL
> point to the SBS 2003 for DHCP and DNS. I successfully connected 25 of the 27
> workstations with no problem. I have two workstations that when you ran the
> Network Configuration Wizard, when you clicked on "Connect to the Network"
> you would receive the following error message "The Small Business Server
> Networking Wizard was not installed. You may not be a member of the local
> Administrators security group on this computer or your Local Intranet
> security settings may be set to High. Click Connect to the network now to try
> again and click Yes when prompted. If the wizard fails to install, contact
> the person responsible for your network."
>
> I have reset IE's security to the LOWEST settings, this did not help. I have
> setup static IP settings, this did not work. I have reset the IP in XP, this
> did not work.
>
> I am posting the SBSClientsApps.Log here to see if this problem can be
> resolved not only for me, but for everyone in this newsgroup who is
> frustrated that there seems to be NO ANSWER EXCEPT TOTALLY WIPING OUT THE
> ENTIRE HARD DRIVE AND REINSTALLING XP. I did this on one of the machines that
> woudl not connect and NOW, it is connected to the SBS 2003 with NO PROBLEMS.
>
> Here is the log information ;
> -- Starting AppLnch.exe --
> DoAlwaysRun() -- '/s' not found on the command line
> -- DoAlwaysRun() failed, exiting --
>
> NOW, can someone PLEASE come up with a solution for the problem?
>
> I am also begging that you DO NOT go down the road of IP settings not
> pointing to the SBS 2003 DNS or that the machine was probably a member of
> another domain. Once again, ALL THE MACHINES are pointing directly to the SBS
> 2003 on this LAN. ALL of the machines were NEVER a member of a domain, only a
> workgroup.
>
> The one machine that is left, has all sorts of custom applications and data,
> to wipe it out and start over would be a DISASTER.
>
> PLEASE....HELP!!
> --
> PCNS Support Team

Thank you clarv02 for your replay.

Yes, I did use the computer wizard on the SBS 2003 to create the comptuer
account first. I also rest the computer account, along with removing it and
recreating it. This action did not fix either of the two computers that would
not connect using the Network Connection Wizard.

I read that you can manually connect the computer to the SBS 2003 domain by
going to the System Properties, selecting Computer Name and then click on the
Change button and join the domain that way. But I also read that this does
not install the applications to the workstation nor does Microsoft support
this way of joining the computer to the SBS domain, since all the "hooks" are
not installed correctly. That is why I am trying to find the answer to this
problem. I want to remove all avenues of failure for my customer. I want to
make sure that SBS 2003 has everything it needs.
--
PCNS Support Team


"clarv02" wrote:

> Sorry, I don't have a solution to the specific problem you're having
> with running the Connect to wizard. However, I believe that as long as
> you created the computer accounts using the wizard on the server, if
> you end up having to joing the computers manually, it's no big deal.
> I've had to do this before because sometimes those darned computers
> just won't cooperate. But if you believe that you must use the connect
> to wizard, then hopefully someone else will have some suggestions for
> you.
>
>
> On Jan 30, 2:51 pm, PCNS <P...@discussions.microsoft.com> wrote:
> > I am starting a new posting, hoping that myself along with ALL the others
> > here in thes tech newsgroup can get this problem resolved with the SBS 2003
> > Network Configuration Wizard setup.
> >
> > Here is the environment, I have 27 workstations that I am migrating to SBS
> > 2003. ALL the workstations were a member of a WORKGROUP, they were NEVER a
> > member of a Domain. They are all running Windows XP Professional and they ALL
> > point to the SBS 2003 for DHCP and DNS. I successfully connected 25 of the 27
> > workstations with no problem. I have two workstations that when you ran the
> > Network Configuration Wizard, when you clicked on "Connect to the Network"
> > you would receive the following error message "The Small Business Server
> > Networking Wizard was not installed. You may not be a member of the local
> > Administrators security group on this computer or your Local Intranet
> > security settings may be set to High. Click Connect to the network now to try
> > again and click Yes when prompted. If the wizard fails to install, contact
> > the person responsible for your network."
> >
> > I have reset IE's security to the LOWEST settings, this did not help. I have
> > setup static IP settings, this did not work. I have reset the IP in XP, this
> > did not work.
> >
> > I am posting the SBSClientsApps.Log here to see if this problem can be
> > resolved not only for me, but for everyone in this newsgroup who is
> > frustrated that there seems to be NO ANSWER EXCEPT TOTALLY WIPING OUT THE
> > ENTIRE HARD DRIVE AND REINSTALLING XP. I did this on one of the machines that
> > woudl not connect and NOW, it is connected to the SBS 2003 with NO PROBLEMS.
> >
> > Here is the log information ;
> > -- Starting AppLnch.exe --
> > DoAlwaysRun() -- '/s' not found on the command line
> > -- DoAlwaysRun() failed, exiting --
> >
> > NOW, can someone PLEASE come up with a solution for the problem?
> >
> > I am also begging that you DO NOT go down the road of IP settings not
> > pointing to the SBS 2003 DNS or that the machine was probably a member of
> > another domain. Once again, ALL THE MACHINES are pointing directly to the SBS
> > 2003 on this LAN. ALL of the machines were NEVER a member of a domain, only a
> > workgroup.
> >
> > The one machine that is left, has all sorts of custom applications and data,
> > to wipe it out and start over would be a DISASTER.
> >
> > PLEASE....HELP!!
> > --
> > PCNS Support Team
>
>
>

For kicks, just make sure you dont have any mapped drives or VPN/
Incomming Connections. Basically any connection to any other PC. Make
sure you have a dynamic address and you aren't assigning a DNS.

I have had issues before similiar. Most of the time the one of the
above solves the problem.

Good luck.

Thank you "milhouse 241".

There were no mapped drives, all of the previous mapped drives were removed.
There is no VPN, all the machines are on the same LAN and all the machines
are setup for dynamic IP addressing from the SBS 2003 server.
--
PCNS Support Team


"milhouse241" wrote:

> For kicks, just make sure you dont have any mapped drives or VPN/
> Incomming Connections. Basically any connection to any other PC. Make
> sure you have a dynamic address and you aren't assigning a DNS.
>
> I have had issues before similiar. Most of the time the one of the
> above solves the problem.
>
> Good luck.
>
>

Did you get this resolved without having to wipe the computers?


On Jan 30, 6:16 pm, PCNS <P...@discussions.microsoft.com> wrote:
> Thank you "milhouse 241".
>
> There were no mapped drives, all of the previous mapped drives were removed.
> There is no VPN, all the machines are on the same LAN and all the machines
> are setup for dynamic IP addressing from the SBS 2003 server.
> --
> PCNS Support Team
>
>
>
> "milhouse241" wrote:
> > For kicks, just make sure you dont have any mapped drives or VPN/
> > Incomming Connections. Basically any connection to any other PC. Make
> > sure you have a dynamic address and you aren't assigning a DNS.
>
> > I have had issues before similiar. Most of the time the one of the
> > above solves the problem.
>
> > Good luck.- Hide quoted text -
>
> - Show quoted text -

clarv02 - Want to thank you for checking back on this issue. No, so far I can
not get any answers or support on resolving this issue. I did wipe the one
machine out and re-imaged it and it worked. The other machine, which is a 4
month old Dell, I have not wiped it out as of yet. I am having to try and
schedule this around the end-user since she uses it very much for her work
and can not be down for several hours, this will cost her a lot of money.

I have gone back out onto the Internet and did some more research and all I
get is the same garbage ; check your TCP/IP, check your IE settings, make
sure you are logged on as Administrator, you are not pointing to the SBS DNS.
I am putting off wiping out the Dell as long as possible because what if I do
and the Dell image has the same problem? Then what do I do, switch to SUS 10?
I am just extremely disappointed in Microsoft that they can not resolve this
issue at all.

Again clarv02, thank you so very much in checking back to see if I have
resolved this.


--
PCNS Support Team


"clarv02" wrote:

> Did you get this resolved without having to wipe the computers?
>
>
> On Jan 30, 6:16 pm, PCNS <P...@discussions.microsoft.com> wrote:
> > Thank you "milhouse 241".
> >
> > There were no mapped drives, all of the previous mapped drives were removed.
> > There is no VPN, all the machines are on the same LAN and all the machines
> > are setup for dynamic IP addressing from the SBS 2003 server.
> > --
> > PCNS Support Team
> >
> >
> >
> > "milhouse241" wrote:
> > > For kicks, just make sure you dont have any mapped drives or VPN/
> > > Incomming Connections. Basically any connection to any other PC. Make
> > > sure you have a dynamic address and you aren't assigning a DNS.
> >
> > > I have had issues before similiar. Most of the time the one of the
> > > above solves the problem.
> >
> > > Good luck.- Hide quoted text -
> >
> > - Show quoted text -
>
>
>

You're welcome (for the follow up). I do understand that you want the
ideal situation of being able to join the domain using the wizard to
get all the hooks. Given the situation you've described with this last
Dell, and the possibility of still having the same problem after doing
a reimage, I would definitely go the route of manually adding it to
the domain. I've had to do this a few times and have not experienced
any problems. In a non-SBS environment, that's the normal way of
adding computers to a domain. I see it's been a couple of weeks now
since your last post, so you have likely already moved on, but in case
not, you may want to reconsider manually adding to the domain.



On Feb 7, 2:43 pm, PCNS <P...@discussions.microsoft.com> wrote:
> clarv02 - Want to thank you for checking back on this issue. No, so far I can
> not get any answers or support on resolving this issue. I did wipe the one
> machine out and re-imaged it and it worked. The other machine, which is a 4
> month old Dell, I have not wiped it out as of yet. I am having to try and
> schedule this around the end-user since she uses it very much for her work
> and can not be down for several hours, this will cost her a lot of money.
>
> I have gone back out onto the Internet and did some more research and all I
> get is the same garbage ; check your TCP/IP, check your IE settings, make
> sure you are logged on as Administrator, you are not pointing to the SBS DNS.
> I am putting off wiping out the Dell as long as possible because what if I do
> and the Dell image has the same problem? Then what do I do, switch to SUS 10?
> I am just extremely disappointed in Microsoft that they can not resolve this
> issue at all.
>
> Again clarv02, thank you so very much in checking back to see if I have
> resolved this.
>
> --
> PCNS Support Team
>
>
>
> "clarv02" wrote:
> > Did you get this resolved without having to wipe the computers?
>
> > On Jan 30, 6:16 pm, PCNS <P...@discussions.microsoft.com> wrote:
> > > Thank you "milhouse 241".
>
> > > There were no mapped drives, all of the previous mapped drives were removed.
> > > There is no VPN, all the machines are on the same LAN and all the machines
> > > are setup for dynamic IP addressing from the SBS 2003 server.
> > > --
> > > PCNS Support Team
>
> > > "milhouse241" wrote:
> > > > For kicks, just make sure you dont have any mapped drives or VPN/
> > > > Incomming Connections. Basically any connection to any other PC. Make
> > > > sure you have a dynamic address and you aren't assigning a DNS.
>
> > > > I have had issues before similiar. Most of the time the one of the
> > > > above solves the problem.
>
> > > > Good luck.- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

clarv02 -

Thank you for checking back. No, I have not resolved the problem. I have
checked into the manual adding to AD, but, as I have read, this is NOT
SUPPORTED by MICROSOFT. I don't want to leave my client with an unsupported
solution. Again, Microsoft needs to address this problem and if the solution
is a nonsupported answer, then there is something terribly wrong. I had Bob
Genestet suggest running the "sfc /scannow" which I did twice, and still
have the same problem. The whole point of the Wizard, is that everything, all
the hooks are automatically installed, all programs are installed. What does
Microsoft insist you use in SBS 2003, the Wizards.

Thanks again for checking back with me, I really appreciate.

Does ANYONE have the ANSWER??????
--
PCNS Support Team


"clarv02" wrote:

> You're welcome (for the follow up). I do understand that you want the
> ideal situation of being able to join the domain using the wizard to
> get all the hooks. Given the situation you've described with this last
> Dell, and the possibility of still having the same problem after doing
> a reimage, I would definitely go the route of manually adding it to
> the domain. I've had to do this a few times and have not experienced
> any problems. In a non-SBS environment, that's the normal way of
> adding computers to a domain. I see it's been a couple of weeks now
> since your last post, so you have likely already moved on, but in case
> not, you may want to reconsider manually adding to the domain.
>
>
>
> On Feb 7, 2:43 pm, PCNS <P...@discussions.microsoft.com> wrote:
> > clarv02 - Want to thank you for checking back on this issue. No, so far I can
> > not get any answers or support on resolving this issue. I did wipe the one
> > machine out and re-imaged it and it worked. The other machine, which is a 4
> > month old Dell, I have not wiped it out as of yet. I am having to try and
> > schedule this around the end-user since she uses it very much for her work
> > and can not be down for several hours, this will cost her a lot of money.
> >
> > I have gone back out onto the Internet and did some more research and all I
> > get is the same garbage ; check your TCP/IP, check your IE settings, make
> > sure you are logged on as Administrator, you are not pointing to the SBS DNS.
> > I am putting off wiping out the Dell as long as possible because what if I do
> > and the Dell image has the same problem? Then what do I do, switch to SUS 10?
> > I am just extremely disappointed in Microsoft that they can not resolve this
> > issue at all.
> >
> > Again clarv02, thank you so very much in checking back to see if I have
> > resolved this.
> >
> > --
> > PCNS Support Team
> >
> >
> >
> > "clarv02" wrote:
> > > Did you get this resolved without having to wipe the computers?
> >
> > > On Jan 30, 6:16 pm, PCNS <P...@discussions.microsoft.com> wrote:
> > > > Thank you "milhouse 241".
> >
> > > > There were no mapped drives, all of the previous mapped drives were removed.
> > > > There is no VPN, all the machines are on the same LAN and all the machines
> > > > are setup for dynamic IP addressing from the SBS 2003 server.
> > > > --
> > > > PCNS Support Team
> >
> > > > "milhouse241" wrote:
> > > > > For kicks, just make sure you dont have any mapped drives or VPN/
> > > > > Incomming Connections. Basically any connection to any other PC. Make
> > > > > sure you have a dynamic address and you aren't assigning a DNS.
> >
> > > > > I have had issues before similiar. Most of the time the one of the
> > > > > above solves the problem.
> >
> > > > > Good luck.- Hide quoted text -
> >
> > > > - Show quoted text -- Hide quoted text -
> >
> > - Show quoted text -
>
>
>

Please suply the output of 'ipconfig /all' from both the SBS and affected
workstation.

"PCNS" <PCNS@discussions.microsoft.com> wrote in message
news:8EAF6575-C4D6-4819-905B-5E65065DD328@microsoft.com...
> clarv02 -
>
> Thank you for checking back. No, I have not resolved the problem. I have
> checked into the manual adding to AD, but, as I have read, this is NOT
> SUPPORTED by MICROSOFT. I don't want to leave my client with an
> unsupported
> solution. Again, Microsoft needs to address this problem and if the
> solution
> is a nonsupported answer, then there is something terribly wrong. I had
> Bob
> Genestet suggest running the "sfc /scannow" which I did twice, and still
> have the same problem. The whole point of the Wizard, is that everything,
> all
> the hooks are automatically installed, all programs are installed. What
> does
> Microsoft insist you use in SBS 2003, the Wizards.
>
> Thanks again for checking back with me, I really appreciate.
>
> Does ANYONE have the ANSWER??????
> --
> PCNS Support Team
>
>
> "clarv02" wrote:
>
>> You're welcome (for the follow up). I do understand that you want the
>> ideal situation of being able to join the domain using the wizard to
>> get all the hooks. Given the situation you've described with this last
>> Dell, and the possibility of still having the same problem after doing
>> a reimage, I would definitely go the route of manually adding it to
>> the domain. I've had to do this a few times and have not experienced
>> any problems. In a non-SBS environment, that's the normal way of
>> adding computers to a domain. I see it's been a couple of weeks now
>> since your last post, so you have likely already moved on, but in case
>> not, you may want to reconsider manually adding to the domain.
>>
>>
>>
>> On Feb 7, 2:43 pm, PCNS <P...@discussions.microsoft.com> wrote:
>> > clarv02 - Want to thank you for checking back on this issue. No, so far
>> > I can
>> > not get any answers or support on resolving this issue. I did wipe the
>> > one
>> > machine out and re-imaged it and it worked. The other machine, which is
>> > a 4
>> > month old Dell, I have not wiped it out as of yet. I am having to try
>> > and
>> > schedule this around the end-user since she uses it very much for her
>> > work
>> > and can not be down for several hours, this will cost her a lot of
>> > money.
>> >
>> > I have gone back out onto the Internet and did some more research and
>> > all I
>> > get is the same garbage ; check your TCP/IP, check your IE settings,
>> > make
>> > sure you are logged on as Administrator, you are not pointing to the
>> > SBS DNS.
>> > I am putting off wiping out the Dell as long as possible because what
>> > if I do
>> > and the Dell image has the same problem? Then what do I do, switch to
>> > SUS 10?
>> > I am just extremely disappointed in Microsoft that they can not resolve
>> > this
>> > issue at all.
>> >
>> > Again clarv02, thank you so very much in checking back to see if I have
>> > resolved this.
>> >
>> > --
>> > PCNS Support Team
>> >
>> >
>> >
>> > "clarv02" wrote:
>> > > Did you get this resolved without having to wipe the computers?
>> >
>> > > On Jan 30, 6:16 pm, PCNS <P...@discussions.microsoft.com> wrote:
>> > > > Thank you "milhouse 241".
>> >
>> > > > There were no mapped drives, all of the previous mapped drives were
>> > > > removed.
>> > > > There is no VPN, all the machines are on the same LAN and all the
>> > > > machines
>> > > > are setup for dynamic IP addressing from the SBS 2003 server.
>> > > > --
>> > > > PCNS Support Team
>> >
>> > > > "milhouse241" wrote:
>> > > > > For kicks, just make sure you dont have any mapped drives or VPN/
>> > > > > Incomming Connections. Basically any connection to any other PC.
>> > > > > Make
>> > > > > sure you have a dynamic address and you aren't assigning a DNS.
>> >
>> > > > > I have had issues before similiar. Most of the time the one of
>> > > > > the
>> > > > > above solves the problem.
>> >
>> > > > > Good luck.- Hide quoted text -
>> >
>> > > > - Show quoted text -- Hide quoted text -
>> >
>> > - Show quoted text -
>>
>>
>>

SuperGumby -

Wanted to thank you for your reply. Here is the IPCONFIG /ALL that I ran on
the computer that was having the problem. This was done a few weeks ago, so
the lease time will be wrong now, but other than that, all else is the same.
Also, I did try static IP address on this machine and stil it did not work.

Here is my internal IP settings on one of the machines ;

Windows IP Configuration


Host Name . . . . . . . . . . . . : 300-WPA

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : wpa.local



Ethernet adapter Local Area Connection:


Connection-specific DNS Suffix . : wpa.local

Description . . . . . . . . . . . : Intel(R) PRO/1000 CT
NetworkConnection

Physical Address. . . . . . . . . : 00-11-11-9F-0E-F5

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.118

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.89
DNS Servers . . . . . . . . . . . : 192.168.0.89
Primary WINS Server . . . . . . . : 192.168.0.89

Lease Obtained. . . . . . . . . . : Sunday, January 28, 20074:38:19PM

Lease Expires . . . . . . . . . . : Monday, February 05, 2007 4:38:19 PM

--
PCNS Support Team


"SuperGumby [SBS MVP]" wrote:

> Please suply the output of 'ipconfig /all' from both the SBS and affected
> workstation.
>
> "PCNS" <PCNS@discussions.microsoft.com> wrote in message
> news:8EAF6575-C4D6-4819-905B-5E65065DD328@microsoft.com...
> > clarv02 -
> >
> > Thank you for checking back. No, I have not resolved the problem. I have
> > checked into the manual adding to AD, but, as I have read, this is NOT
> > SUPPORTED by MICROSOFT. I don't want to leave my client with an
> > unsupported
> > solution. Again, Microsoft needs to address this problem and if the
> > solution
> > is a nonsupported answer, then there is something terribly wrong. I had
> > Bob
> > Genestet suggest running the "sfc /scannow" which I did twice, and still
> > have the same problem. The whole point of the Wizard, is that everything,
> > all
> > the hooks are automatically installed, all programs are installed. What
> > does
> > Microsoft insist you use in SBS 2003, the Wizards.
> >
> > Thanks again for checking back with me, I really appreciate.
> >
> > Does ANYONE have the ANSWER??????
> > --
> > PCNS Support Team
> >
> >
> > "clarv02" wrote:
> >
> >> You're welcome (for the follow up). I do understand that you want the
> >> ideal situation of being able to join the domain using the wizard to
> >> get all the hooks. Given the situation you've described with this last
> >> Dell, and the possibility of still having the same problem after doing
> >> a reimage, I would definitely go the route of manually adding it to
> >> the domain. I've had to do this a few times and have not experienced
> >> any problems. In a non-SBS environment, that's the normal way of
> >> adding computers to a domain. I see it's been a couple of weeks now
> >> since your last post, so you have likely already moved on, but in case
> >> not, you may want to reconsider manually adding to the domain.
> >>
> >>
> >>
> >> On Feb 7, 2:43 pm, PCNS <P...@discussions.microsoft.com> wrote:
> >> > clarv02 - Want to thank you for checking back on this issue. No, so far
> >> > I can
> >> > not get any answers or support on resolving this issue. I did wipe the
> >> > one
> >> > machine out and re-imaged it and it worked. The other machine, which is
> >> > a 4
> >> > month old Dell, I have not wiped it out as of yet. I am having to try
> >> > and
> >> > schedule this around the end-user since she uses it very much for her
> >> > work
> >> > and can not be down for several hours, this will cost her a lot of
> >> > money.
> >> >
> >> > I have gone back out onto the Internet and did some more research and
> >> > all I
> >> > get is the same garbage ; check your TCP/IP, check your IE settings,
> >> > make
> >> > sure you are logged on as Administrator, you are not pointing to the
> >> > SBS DNS.
> >> > I am putting off wiping out the Dell as long as possible because what
> >> > if I do
> >> > and the Dell image has the same problem? Then what do I do, switch to
> >> > SUS 10?
> >> > I am just extremely disappointed in Microsoft that they can not resolve
> >> > this
> >> > issue at all.
> >> >
> >> > Again clarv02, thank you so very much in checking back to see if I have
> >> > resolved this.
> >> >
> >> > --
> >> > PCNS Support Team
> >> >
> >> >
> >> >
> >> > "clarv02" wrote:
> >> > > Did you get this resolved without having to wipe the computers?
> >> >
> >> > > On Jan 30, 6:16 pm, PCNS <P...@discussions.microsoft.com> wrote:
> >> > > > Thank you "milhouse 241".
> >> >
> >> > > > There were no mapped drives, all of the previous mapped drives were
> >> > > > removed.
> >> > > > There is no VPN, all the machines are on the same LAN and all the
> >> > > > machines
> >> > > > are setup for dynamic IP addressing from the SBS 2003 server.
> >> > > > --
> >> > > > PCNS Support Team
> >> >
> >> > > > "milhouse241" wrote:
> >> > > > > For kicks, just make sure you dont have any mapped drives or VPN/
> >> > > > > Incomming Connections. Basically any connection to any other PC.
> >> > > > > Make
> >> > > > > sure you have a dynamic address and you aren't assigning a DNS.
> >> >
> >> > > > > I have had issues before similiar. Most of the time the one of
> >> > > > > the
> >> > > > > above solves the problem.
> >> >
> >> > > > > Good luck.- Hide quoted text -
> >> >
> >> > > > - Show quoted text -- Hide quoted text -
> >> >
> >> > - Show quoted text -
> >>
> >>
> >>
>
>
>

if that is the complete unedited output and the server is on .89 I see no
reason for your problem.

I will however repeat.
>> Please suply the output of 'ipconfig /all' from both the SBS and affected
>> workstation.


"PCNS" <PCNS@discussions.microsoft.com> wrote in message
news:6168999C-AAE9-4C9D-8343-05964F831F52@microsoft.com...
> SuperGumby -
>
> Wanted to thank you for your reply. Here is the IPCONFIG /ALL that I ran
> on
> the computer that was having the problem. This was done a few weeks ago,
> so
> the lease time will be wrong now, but other than that, all else is the
> same.
> Also, I did try static IP address on this machine and stil it did not
> work.
>
> Here is my internal IP settings on one of the machines ;
>
> Windows IP Configuration
>
>
> Host Name . . . . . . . . . . . . : 300-WPA
>
> Primary Dns Suffix . . . . . . . :
>
> Node Type . . . . . . . . . . . . : Hybrid
>
> IP Routing Enabled. . . . . . . . : No
>
> WINS Proxy Enabled. . . . . . . . : No
>
> DNS Suffix Search List. . . . . . : wpa.local
>
>
>
> Ethernet adapter Local Area Connection:
>
>
> Connection-specific DNS Suffix . : wpa.local
>
> Description . . . . . . . . . . . : Intel(R) PRO/1000 CT
> NetworkConnection
>
> Physical Address. . . . . . . . . : 00-11-11-9F-0E-F5
>
> Dhcp Enabled. . . . . . . . . . . : Yes
>
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.168.0.118
>
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>
> Default Gateway . . . . . . . . . : 192.168.0.1
>
> DHCP Server . . . . . . . . . . . : 192.168.0.89
> DNS Servers . . . . . . . . . . . : 192.168.0.89
> Primary WINS Server . . . . . . . : 192.168.0.89
>
> Lease Obtained. . . . . . . . . . : Sunday, January 28, 20074:38:19PM
>
> Lease Expires . . . . . . . . . . : Monday, February 05, 2007 4:38:19 PM
>
> --
> PCNS Support Team
>
>
> "SuperGumby [SBS MVP]" wrote:
>
>> Please suply the output of 'ipconfig /all' from both the SBS and affected
>> workstation.
>>
>> "PCNS" <PCNS@discussions.microsoft.com> wrote in message
>> news:8EAF6575-C4D6-4819-905B-5E65065DD328@microsoft.com...
>> > clarv02 -
>> >
>> > Thank you for checking back. No, I have not resolved the problem. I
>> > have
>> > checked into the manual adding to AD, but, as I have read, this is NOT
>> > SUPPORTED by MICROSOFT. I don't want to leave my client with an
>> > unsupported
>> > solution. Again, Microsoft needs to address this problem and if the
>> > solution
>> > is a nonsupported answer, then there is something terribly wrong. I had
>> > Bob
>> > Genestet suggest running the "sfc /scannow" which I did twice, and
>> > still
>> > have the same problem. The whole point of the Wizard, is that
>> > everything,
>> > all
>> > the hooks are automatically installed, all programs are installed. What
>> > does
>> > Microsoft insist you use in SBS 2003, the Wizards.
>> >
>> > Thanks again for checking back with me, I really appreciate.
>> >
>> > Does ANYONE have the ANSWER??????
>> > --
>> > PCNS Support Team
>> >
>> >
>> > "clarv02" wrote:
>> >
>> >> You're welcome (for the follow up). I do understand that you want the
>> >> ideal situation of being able to join the domain using the wizard to
>> >> get all the hooks. Given the situation you've described with this last
>> >> Dell, and the possibility of still having the same problem after doing
>> >> a reimage, I would definitely go the route of manually adding it to
>> >> the domain. I've had to do this a few times and have not experienced
>> >> any problems. In a non-SBS environment, that's the normal way of
>> >> adding computers to a domain. I see it's been a couple of weeks now
>> >> since your last post, so you have likely already moved on, but in case
>> >> not, you may want to reconsider manually adding to the domain.
>> >>
>> >>
>> >>
>> >> On Feb 7, 2:43 pm, PCNS <P...@discussions.microsoft.com> wrote:
>> >> > clarv02 - Want to thank you for checking back on this issue. No, so
>> >> > far
>> >> > I can
>> >> > not get any answers or support on resolving this issue. I did wipe
>> >> > the
>> >> > one
>> >> > machine out and re-imaged it and it worked. The other machine, which
>> >> > is
>> >> > a 4
>> >> > month old Dell, I have not wiped it out as of yet. I am having to
>> >> > try
>> >> > and
>> >> > schedule this around the end-user since she uses it very much for
>> >> > her
>> >> > work
>> >> > and can not be down for several hours, this will cost her a lot of
>> >> > money.
>> >> >
>> >> > I have gone back out onto the Internet and did some more research
>> >> > and
>> >> > all I
>> >> > get is the same garbage ; check your TCP/IP, check your IE settings,
>> >> > make
>> >> > sure you are logged on as Administrator, you are not pointing to the
>> >> > SBS DNS.
>> >> > I am putting off wiping out the Dell as long as possible because
>> >> > what
>> >> > if I do
>> >> > and the Dell image has the same problem? Then what do I do, switch
>> >> > to
>> >> > SUS 10?
>> >> > I am just extremely disappointed in Microsoft that they can not
>> >> > resolve
>> >> > this
>> >> > issue at all.
>> >> >
>> >> > Again clarv02, thank you so very much in checking back to see if I
>> >> > have
>> >> > resolved this.
>> >> >
>> >> > --
>> >> > PCNS Support Team
>> >> >
>> >> >
>> >> >
>> >> > "clarv02" wrote:
>> >> > > Did you get this resolved without having to wipe the computers?
>> >> >
>> >> > > On Jan 30, 6:16 pm, PCNS <P...@discussions.microsoft.com> wrote:
>> >> > > > Thank you "milhouse 241".
>> >> >
>> >> > > > There were no mapped drives, all of the previous mapped drives
>> >> > > > were
>> >> > > > removed.
>> >> > > > There is no VPN, all the machines are on the same LAN and all
>> >> > > > the
>> >> > > > machines
>> >> > > > are setup for dynamic IP addressing from the SBS 2003 server.
>> >> > > > --
>> >> > > > PCNS Support Team
>> >> >
>> >> > > > "milhouse241" wrote:
>> >> > > > > For kicks, just make sure you dont have any mapped drives or
>> >> > > > > VPN/
>> >> > > > > Incomming Connections. Basically any connection to any other
>> >> > > > > PC.
>> >> > > > > Make
>> >> > > > > sure you have a dynamic address and you aren't assigning a
>> >> > > > > DNS.
>> >> >
>> >> > > > > I have had issues before similiar. Most of the time the one of
>> >> > > > > the
>> >> > > > > above solves the problem.
>> >> >
>> >> > > > > Good luck.- Hide quoted text -
>> >> >
>> >> > > > - Show quoted text -- Hide quoted text -
>> >> >
>> >> > - Show quoted text -
>> >>
>> >>
>> >>
>>
>>
>>

You can manually join the domain any time you want. Who says it is not
supported? It is more convenient to add with the wizard but sometimes
the wizard does not work. Make sure your NLA service is set to
automatic and reboot. NLA set to manual is know to cause issues.
Almost guaranteed to cause issues with Dells. Been there recently and
suffered greatly until Dave N. reminded me of the NLA service.

I do not see the ipconfig/all from the server? I guess I have tired
eyes and I need to go to bed.

On Fri, 2 Mar 2007 19:08:56 -0800, PCNS
<PCNS@discussions.microsoft.com> wrote:

>SuperGumby -
>
>Wanted to thank you for your reply. Here is the IPCONFIG /ALL that I ran on
>the computer that was having the problem. This was done a few weeks ago, so
>the lease time will be wrong now, but other than that, all else is the same.
>Also, I did try static IP address on this machine and stil it did not work.
>
>Here is my internal IP settings on one of the machines ;
>
>Windows IP Configuration
>
>
>Host Name . . . . . . . . . . . . : 300-WPA
>
>Primary Dns Suffix . . . . . . . :
>
>Node Type . . . . . . . . . . . . : Hybrid
>
>IP Routing Enabled. . . . . . . . : No
>
>WINS Proxy Enabled. . . . . . . . : No
>
>DNS Suffix Search List. . . . . . : wpa.local
>
>
>
>Ethernet adapter Local Area Connection:
>
>
>Connection-specific DNS Suffix . : wpa.local
>
>Description . . . . . . . . . . . : Intel(R) PRO/1000 CT
>NetworkConnection
>
>Physical Address. . . . . . . . . : 00-11-11-9F-0E-F5
>
>Dhcp Enabled. . . . . . . . . . . : Yes
>
>Autoconfiguration Enabled . . . . : Yes
>IP Address. . . . . . . . . . . . : 192.168.0.118
>
>Subnet Mask . . . . . . . . . . . : 255.255.255.0
>
>Default Gateway . . . . . . . . . : 192.168.0.1
>
>DHCP Server . . . . . . . . . . . : 192.168.0.89
>DNS Servers . . . . . . . . . . . : 192.168.0.89
>Primary WINS Server . . . . . . . : 192.168.0.89
>
>Lease Obtained. . . . . . . . . . : Sunday, January 28, 20074:38:19PM
>
>Lease Expires . . . . . . . . . . : Monday, February 05, 2007 4:38:19 PM

Jim Behning -

Thank you for the response. Microsoft has stated several times in this
forum, along with several webinars that I have attended, along with several
workshops that I have attended, that manually joining a SBS 2003 domain is
not supported. They, Microsoft, have explicitly stated, at these webinars and
workshops that you must use the wizards to guarantee that all the hooks are
installed. I have had two Microsoft support people at two different workshops
tell me that if I did not use the wizards, and then called Microsoft for
support, that they would insist that I go back and re-do the entire
installation using the wizard(s) because bypassing the wizard(s) is not
supported. I can not risk an installation for a customer that is not
supported by Microsoft, just in case something happens.

What everyone here, in this forum, keeps missing is an ANSWER TO THE PROBLEM!

Instead of work-arounds, or, short-cuts, how about an ANSWER!

1 - Microsoft, what is the answer to the SBS 2003 Network Connection Wizard,
failing?

2 - Microsoft, to fix the SBS 2003 Network Connection Wizard failure, does
that require me to wipe the machine out and re-install the XP to get the
Network Connection Wizard to work correclty (like I had to on the one
computer)?

3 - Microsoft, is the MANUAL way of joining a computer to the SBS 2003
domain supported or not?...and if so, POST IT.

What I (and others here with the same problem) need is a supported answer to
this problem.

Thanks for your input.
--
PCNS Support Team


"Jim Behning SBS MVP" wrote:

> You can manually join the domain any time you want. Who says it is not
> supported? It is more convenient to add with the wizard but sometimes
> the wizard does not work. Make sure your NLA service is set to
> automatic and reboot. NLA set to manual is know to cause issues.
> Almost guaranteed to cause issues with Dells. Been there recently and
> suffered greatly until Dave N. reminded me of the NLA service.
>
> I do not see the ipconfig/all from the server? I guess I have tired
> eyes and I need to go to bed.
>
> On Fri, 2 Mar 2007 19:08:56 -0800, PCNS
> <PCNS@discussions.microsoft.com> wrote:
>
> >SuperGumby -
> >
> >Wanted to thank you for your reply. Here is the IPCONFIG /ALL that I ran on
> >the computer that was having the problem. This was done a few weeks ago, so
> >the lease time will be wrong now, but other than that, all else is the same.
> >Also, I did try static IP address on this machine and stil it did not work.
> >
> >Here is my internal IP settings on one of the machines ;
> >
> >Windows IP Configuration
> >
> >
> >Host Name . . . . . . . . . . . . : 300-WPA
> >
> >Primary Dns Suffix . . . . . . . :
> >
> >Node Type . . . . . . . . . . . . : Hybrid
> >
> >IP Routing Enabled. . . . . . . . : No
> >
> >WINS Proxy Enabled. . . . . . . . : No
> >
> >DNS Suffix Search List. . . . . . : wpa.local
> >
> >
> >
> >Ethernet adapter Local Area Connection:
> >
> >
> >Connection-specific DNS Suffix . : wpa.local
> >
> >Description . . . . . . . . . . . : Intel(R) PRO/1000 CT
> >NetworkConnection
> >
> >Physical Address. . . . . . . . . : 00-11-11-9F-0E-F5
> >
> >Dhcp Enabled. . . . . . . . . . . : Yes
> >
> >Autoconfiguration Enabled . . . . : Yes
> >IP Address. . . . . . . . . . . . : 192.168.0.118
> >
> >Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >
> >Default Gateway . . . . . . . . . : 192.168.0.1
> >
> >DHCP Server . . . . . . . . . . . : 192.168.0.89
> >DNS Servers . . . . . . . . . . . : 192.168.0.89
> >Primary WINS Server . . . . . . . : 192.168.0.89
> >
> >Lease Obtained. . . . . . . . . . : Sunday, January 28, 20074:38:19PM
> >
> >Lease Expires . . . . . . . . . . : Monday, February 05, 2007 4:38:19 PM
>

I don't know that you are but... You're not confusing wizards perchance?

The SBS itself must be installed using the full wizard process.

MS however support introduction of SBS into an existing AD. ie. a situation
where the workstations _could not_ have been connected using SBS' process.

I would however like to get to the bottom of your problem. You suggest that
many machines were installed using /connectcomputer and only two proved
problematic. Simly, I'm interested. Answer my question and I'll ask another,
or possibly comment.

"PCNS" <PCNS@discussions.microsoft.com> wrote in message
news:9C315FC5-B3BB-4A0D-A5A6-04DCD01583CB@microsoft.com...
> Jim Behning -
>
> Thank you for the response. Microsoft has stated several times in this
> forum, along with several webinars that I have attended, along with
> several
> workshops that I have attended, that manually joining a SBS 2003 domain is
> not supported. They, Microsoft, have explicitly stated, at these webinars
> and
> workshops that you must use the wizards to guarantee that all the hooks
> are
> installed. I have had two Microsoft support people at two different
> workshops
> tell me that if I did not use the wizards, and then called Microsoft for
> support, that they would insist that I go back and re-do the entire
> installation using the wizard(s) because bypassing the wizard(s) is not
> supported. I can not risk an installation for a customer that is not
> supported by Microsoft, just in case something happens.
>
> What everyone here, in this forum, keeps missing is an ANSWER TO THE
> PROBLEM!
>
> Instead of work-arounds, or, short-cuts, how about an ANSWER!
>
> 1 - Microsoft, what is the answer to the SBS 2003 Network Connection
> Wizard,
> failing?
>
> 2 - Microsoft, to fix the SBS 2003 Network Connection Wizard failure, does
> that require me to wipe the machine out and re-install the XP to get the
> Network Connection Wizard to work correclty (like I had to on the one
> computer)?
>
> 3 - Microsoft, is the MANUAL way of joining a computer to the SBS 2003
> domain supported or not?...and if so, POST IT.
>
> What I (and others here with the same problem) need is a supported answer
> to
> this problem.
>
> Thanks for your input.
> --
> PCNS Support Team
>
>
> "Jim Behning SBS MVP" wrote:
>
>> You can manually join the domain any time you want. Who says it is not
>> supported? It is more convenient to add with the wizard but sometimes
>> the wizard does not work. Make sure your NLA service is set to
>> automatic and reboot. NLA set to manual is know to cause issues.
>> Almost guaranteed to cause issues with Dells. Been there recently and
>> suffered greatly until Dave N. reminded me of the NLA service.
>>
>> I do not see the ipconfig/all from the server? I guess I have tired
>> eyes and I need to go to bed.
>>
>> On Fri, 2 Mar 2007 19:08:56 -0800, PCNS
>> <PCNS@discussions.microsoft.com> wrote:
>>
>> >SuperGumby -
>> >
>> >Wanted to thank you for your reply. Here is the IPCONFIG /ALL that I ran
>> >on
>> >the computer that was having the problem. This was done a few weeks ago,
>> >so
>> >the lease time will be wrong now, but other than that, all else is the
>> >same.
>> >Also, I did try static IP address on this machine and stil it did not
>> >work.
>> >
>> >Here is my internal IP settings on one of the machines ;
>> >
>> >Windows IP Configuration
>> >
>> >
>> >Host Name . . . . . . . . . . . . : 300-WPA
>> >
>> >Primary Dns Suffix . . . . . . . :
>> >
>> >Node Type . . . . . . . . . . . . : Hybrid
>> >
>> >IP Routing Enabled. . . . . . . . : No
>> >
>> >WINS Proxy Enabled. . . . . . . . : No
>> >
>> >DNS Suffix Search List. . . . . . : wpa.local
>> >
>> >
>> >
>> >Ethernet adapter Local Area Connection:
>> >
>> >
>> >Connection-specific DNS Suffix . : wpa.local
>> >
>> >Description . . . . . . . . . . . : Intel(R) PRO/1000 CT
>> >NetworkConnection
>> >
>> >Physical Address. . . . . . . . . : 00-11-11-9F-0E-F5
>> >
>> >Dhcp Enabled. . . . . . . . . . . : Yes
>> >
>> >Autoconfiguration Enabled . . . . : Yes
>> >IP Address. . . . . . . . . . . . : 192.168.0.118
>> >
>> >Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> >
>> >Default Gateway . . . . . . . . . : 192.168.0.1
>> >
>> >DHCP Server . . . . . . . . . . . : 192.168.0.89
>> >DNS Servers . . . . . . . . . . . : 192.168.0.89
>> >Primary WINS Server . . . . . . . : 192.168.0.89
>> >
>> >Lease Obtained. . . . . . . . . . : Sunday, January 28, 20074:38:19PM
>> >
>> >Lease Expires . . . . . . . . . . : Monday, February 05, 2007 4:38:19 PM
>>