Join a computer to sbs2008

[ahanderson]

I am setting up an SBS2008 domain for a client location and have worked out most of the bugs. I can manually join a computer to the domain, but not log in with verified credential.

The real problem is that when I use http://connect all I am shown is "page cannot be displayed". This is my first experience with w2008. Can anyone shed any light on possible causes/solutions?

First thing is first . . . can you successfully ping connect from the
client you are trying to join?

If the connect wizard is not working you have some very fundamental issues going on.

How many nics in the server?

[ahanderson]

There are 2 questions I will answer here:
--------------------
First thing is first . . . can you successfully ping connect from the
client you are trying to join?
--------------------

The answer is yes. I can ping. I can even join manually, and I figured out the log in problem, that was my own issue.
--------------------

If the connect wizard is not working you have some very fundamental issues going on.

How many nics in the server?

--------------------

I have 2 nics, with one disabled. ]

And what is that single nic connected to? One presumes a router, or a switch and the router is connected to that switch as well?

Which is providing DHCP, the SBS server or the router?

Please post the unedited results of running ipconfig /all on both the server and a workstation and post them here
Please identify which is which

Check the IIS permissions on the connect website

[ahanderson]

The single NIC is connected to a router which is creating a subnet. The upstream network is a private network using a 192.168.x.x addressing scheme and the subnet is using 10.0.0.x addressing scheme. The SBS server is the DNS and DHCP server. I did manage to manually join the computer I was initially using in my test subnet to the new DC.

As you have requested:

Client computer:

Windows IP Configuration
Host Name . . . . . . . . . . . . : xxxxxx
Primary Dns Suffix . . . . . . . : xxxxx.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : xxxxx.local

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :

Intel(R) PRO/100 VE Network Connection
Physical Address. . . . . . . . . : 00-07-E9-3E-38-B6
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.0.0.100
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . : 10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.10
DNS Servers . . . . . . . . . . . : 10.0.0.10
Primary WINS Server . . . . . . . : 10.0.0.10
Lease Obtained. . . . . . . . . . : Tuesday, March 03, 2009 11:16:24 AM
Lease Expires . . . . . . . . . . : Wednesday, March 11, 2009 11:16:24 AM


server computer:


Windows IP Configuration

Host Name . . . . . . . . . . . . : xxxxxx
Primary Dns Suffix . . . . . . . : xxxxx.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : xxxxx.local

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 EB Network Connection with I/O Acceleration #2
Physical Address. . . . . . . . . : 00-15-17-61-0C-35
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 EB Network Connection with I/O Acceleration
Physical Address. . . . . . . . . : 00-15-17-61-0C-34
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.0.0.10(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 10.0.0.10
Primary WINS Server . . . . . . . : 10.0.0.10
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 8:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{9527B260-5063-4D92-A2FB-8C205D84A5B1}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{3624B268-85BD-412E-A048-EDB59F6F77E2}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


Sorry I couldn't get the answer yesterday. Since there is a subnet for the new domain, I am unable to remote to it.



--------------------------------------

And what is that single nic connected to? One presumes a router, or a switch and the router is connected to that switch as well?

Which is providing DHCP, the SBS server or the router?

Please post the unedited results of running ipconfig /all on both the server and a workstation and post them here
Please identify which is which

--------------------------------------

Well, I'll be. That would definately cause some issues. I never even noticed that. Sometimes it takes a second pair of eyes. I'll let you know how that goes. I have also discovered I now need to learn IPv6. I've never had a need to before now, but the wizard "Connect to the internet" won't work since that part of the DHCP server isn't set up yet.

I did not do the initial installation of the server, and as of yet, have not disabled it. I was just doing some research on the best way. I will be doing that tomorrow at the site.

I did some more checking on the client and server with the ip addressing and subnetting. I'm not sure how it came about being posted as 255.0.0.0 on the client. I did a couple release and renews and it was 255.255.255.0. Kind of odd. I fixed it all anyways to the correct subnet and rebuilt the scope at 255.0.0.0. Both server and clients now show that.

However, I am still 100% unable to join computers via http://connect

Tried that. Reinstalled DNS 2 times and just finishing web services reinstall.

Sorry if you mis-understood the question
DO NOT disable IPv6

And you should not have to do anything within DHCP server to configure it.

[the blur]

just use connect without the http

take OUT the HTTP: and just type in connect.

[eiger3970]

My http://connect also doesn't work.

1.
a.
Windows 7 Ultimate 2009
Network connecting PC desktop to xxxxxxxxxxxxSBS.
Computer name: Desktop
Full computer name: Desktop.xxxxxxxxxxxx.local
Computer description: Desktop
Domain: xxxxxxxxxxxx.local

Username: xxxxxxxxxxxx\xxx
Password: J...
Error: Logon failure: unknown user name or bad password.
OR
Username: xxxxxxxxxxxx\desktop
Password: J...
Error: Logon failure: unknown user name or bad password.

b.
http://connect installs Launcher.exe. Error: An error

occurred during the download of Connect Computer. Please

go to http://connect and try again.

c.
USB stick with http://connect launcher.exe file gives

error in a Google chrome page: This computer does not

meet the maximum operating system requirements for

running client setup.

d.
Ping 192.168.1.101 0% loss.
Network shows SBS and other client pc.
Network access SBS files.
Network won't access client pc 2. Error: \\xxxx is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. There are currently no logon servers available to service the logon request.

2.
a.
Windows XP Professional Version 2002 Service Pack 3
Network connecting laptop Andy to xxxxxxxxxxxxSBS.
Full computer name: xxxx.xxxxxxxxxxxx.local
Computer description: xxxx
Domain: xxxxxxxxxxxx.local

Username: xxx
Password: J...
Error 800: Unable to establish VPN connection. The VPN

server may be unreachable, or security parameters may

not be configured properly for this connection.
Redialling = 60
OR
Username: xxxx
Password: J...
Error 800: Unable to establish VPN connection. The VPN

server may be unreachable, or security parameters may

not be configured properly for this connection.
Redialling = 60

b.
http://connect gives error: Oops! Google Chrome could

not find connect.
via IE, http://connect prompts the dialup dialler.

c.
USB stick with http://connect launcher.exe file gives

error: An error occurred while downloading the Connect

Comuter application. Please run this application again.

d.
Ping 192.168.1.102 0% loss.

3.
SBS 2008.
Clicked Network,
Connectivity,
Virtual Private Network (VPN connection),
Configure a virtual private network (on right).

a.
Clicked Users and Groups,
double clicked user xxxxxxxx.
changes username from xxxxxxxx to xxx.
Desktop now connects to xxxxxxxxxxxxSBS.
Laptop has same error failing to xxxxxxxxxxxxSBS.

[addie]

For that at first you have to login and then when you on the network you have to ensure that you update the dns suffix. This you have to do when the new system joins the domain. To update the dns suffix you can browse via your web browser and type http://connect. Hit enter and you get the screen of Windows SBS 2008. Follow the screen instruction and configure the new system.

[bdridder]

As far as this error is concerned "An error occurred during the download of Connect Computer. Please go to http://connect and try again."

I think your DNS settings are wrong, that is : your server has to 'know' about your client.

In my experience, if you either entered your DNS servers manually in your client to something else than the SBS server, or your DHCP server (SBS) does not update the DNS server on the SBS itself, it won't work.

[MPhillips]

When I first setup our SBS2008 Box I had the same problem. I ran the Fix my network wizard in the Network -> Connectivity section of the SBS Console.

This may be way off the mark, but its worth a try.

Mat

[eiger3970]

Well...finally after weeks of pain connected client PCs to Windows 2008.
Totally different way from using the SBS 2008 wizard thingy.
I just change the computer name from a workgroup to a domain et voila.

Now stuck on setting up exchange as the SBS 2008 way doesn't work.

Have tried a different method which worked on 1 PC, but not on 2 other client PCs.

Why won't it be easy...how could a small business owner use setup this up?

[Solomon]

Originally Posted by eiger3970

Well...finally after weeks of pain connected client PCs to Windows 2008.
Totally different way from using the SBS 2008 wizard thingy.
I just change the computer name from a workgroup to a domain et voila.

Now stuck on setting up exchange as the SBS 2008 way doesn't work.

Have tried a different method which worked on 1 PC, but not on 2 other client PCs.

Why won't it be easy...how could a small business owner use setup this up?

I think that you just need to follow the SBS wizard that does everything that you need for you. You just have to follow the prompts and setup the DNS as it asks. Otherwise you can do it the manual way if you wish, that will also work. I have done both. Did you generate the request using the wizard or Powershell? You need to complete the request using whichever method you used to generate the request. Read up more here - SBS Server 2008 exchange setup