Re: The SBS 2003 Network Configuration Wizard InOp

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@xxxxxxxxxxxxxxxxxxxxxxxxx> 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

.

Relevant Pages