• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Joining a new SBS 2008 domain

mxnerd

mxnerd

Diamond Member
I'm new to SBS 2008 and just installed a SBS server 2008.

The installation basically went smoothly. When I try to join a Windows 7 PC to the domain, I just can't connect to the server using "http://connect", even after applying SBS 2008 Rollup 3 update.

the server name is "srv", and when I looked at the DNS records, there is a "connect" CNAME points to "srv.mydomain.local"

I can ping "srv", but not "connect". when using nslookup tool, "connect" also can't be resolved.

What's wrong and how can I fix it?

And if I don't use the http://connect to join the domain, can I use the old way - join domain through computer property?

Is there really any difference between the two methods?
 
Last edited:
rebooted the PC and it did not help.

And I did check the PC's IP & DNS configuration. DNS did points to SBS server.

By the way, I'm thinking about disabling IP6 support for the whole network. Is it a good idea? I really don't see the usage of IPv6 in my environment.

Here is SBS 2008 server DNS configuration

23vyekl.jpg
 
Last edited:
I have a vague recollection that disabling IPV6 is a bad idea with SBS 2008.

Yup.

http://blogs.technet.com/b/sbs/arch...r-disabling-ipv6-on-your-nic-on-sbs-2008.aspx

"If you uncheck the IPv6 protocol from your network interface card on your Windows SBS 2008 server you may see the following issues after a reboot:

•Microsoft Exchange services fail to start
•Server hangs at "Applying Computer Settings..." (can eventually logon after 30 - 60 minutes)
•Network icons show as offline
•Some or all of the following events "

Seriously, I strongly suggest you don't try to "improve" the SBS installation until you've got it fully working and have image backups available. SBS is pretty complex internally and there can be unintended results when you leave the standard setup. I can't count how many SBS installations I've seen messed up by folks trying to improve it. It works very well "as-is".

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

I suggest you solve the problem with the http://connect site. Something is wrong and trying to work around it with a manual Domain join is likely ignoring a problem that ought to be fixed.

I have a really bad feeling about naming a host "SRV", since that has a special meaning in DNS. It's probably not a problem...but offhand it scares me.
 
Last edited:
ipv6 can be disabled on your client pc, remember you have totally separate configs for ipv4 and ipv6 (ie dhcp on ipv6, static on ipv4).


disable ipv6 on the client pc (not the sbs) and try again.

gotta be a config problem dns wise

you could hotwire your hosts file to point to the ipv4 address of the sbs server
 
Thanks.

I leave IPv6 on server alone and disable IPv6 on client & reboot.

IP config for client
6pakb8.png


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

IPconfig & nslookup output, why even srv can't be resolved?

C:\Users\Administrator>ipconfig

Windows IP Configuration


Ethernet adapter OnBoard 1GB LAN:

Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 192.168.1.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e74:38:19f6:3f57:feeb
Link-local IPv6 Address . . . . . : fe80::38:19f6:3f57:feeb%12
Default Gateway . . . . . . . . . : ::

Tunnel adapter isatap.{E1600DBC-D43A-4A6B-9B1A-F322D301071F}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

C:\Users\Administrator>nslookup
Default Server: srv.mnet.local
Address: 192.168.1.8

> srv
Server: srv.mnet.local
Address: 192.168.1.8

*** srv.mnet.local can't find srv: Server failed
> connect
Server: srv.mnet.local
Address: 192.168.1.8

*** srv.mnet.local can't find connect: Server failed
> sites
Server: srv.mnet.local
Address: 192.168.1.8

*** srv.mnet.local can't find sites: Server failed
> google.com
Server: srv.mnet.local
Address: 192.168.1.8

Non-authoritative answer:
Name: google.com
Addresses: 66.102.7.104
66.102.7.99

---------------------------------------------------------
Ping result

C:\Users\Administrator>ping srv

Pinging SRV [192.168.1.8] with 32 bytes of data:
Reply from 192.168.1.8: bytes=32 time<1ms TTL=128
Reply from 192.168.1.8: bytes=32 time<1ms TTL=128
Reply from 192.168.1.8: bytes=32 time<1ms TTL=128
Reply from 192.168.1.8: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\Administrator>ping sites
Ping request could not find host sites. Please check the name and try again.

C:\Users\Administrator>ping connect
Ping request could not find host connect. Please check the name and try again.
 
Last edited:
OK, I disable the DHCP server on router and configure & enable the DHCP server on SBS 2008, refresh client's IP and it did not help.
 
I suggest removing that second DNS setting (4.2.2.1) on clients. It'll only confuse things if your primary DNS Server (192.1681.8) isn't working. Users will be able to browse the Internet, but nothing else will be working.
 
Because you've statically configured the client, it hasn't picked up its DNS suffix, which means that when looking for "srv" or "connect", it's actually looking for NetBIOS names, rather than DNS names, because it won't be able to find them. Allow the SBS server to give DHCP to your machine so that it gets the proper DNS suffix (or manually input the DNS suffix (under IPv4 Properties -> Advanced -> DNS tab).

Without that, the client is looking for a TLD of "connect" or "srv". Adding the proper suffix will properly have it look for "connect.domain.local". I suspect that the reason http://connect.domain.local (if you even tried it) doesn't work is because the IIS server is looking for a specific host name within the HTTP headers.
 
Thanks drebo!

You are right, after I added suffix in client's IP configuration manually, I was able to connect to http://connect finally!

But how do I configure in SBS 2008's DHCP server's option so it will hand out the suffix to client automatically?

I currently only set option 003 - router and option 006 - DNS Servers.
 
mxnerd said:
But how do I configure in SBS 2008's DHCP server's option so it will hand out the suffix to client automatically?
Click to expand...
Good catch, Drebo.

The SBS Installation Wizards should have automatically set the DNS Suffix in the DHCP Scope. I don't have any SBS 2008 servers running right now, but in SBS 2003, it's in one of the six Scope Options that are automatically set by SBS. It's probably set when running the "Connect to the Internet" Wizard. But if the SBS DHCP Server was disabled, then it probably didn't get set.

SBS 2003 automatically set DHCP Scope Options:

003 Router 192.168.1.1
006 DNS Servers 192.168.1.8
015 DNS Domain Name MNET.LOCAL
044 WINS/NBNS Servers 192.168.1.8 (I don't know if SBS 2008 has a WINS server)
046 WINS/NBT Node Type 0x8 (I don't know if SBS 2008 has a WiNS server)

Edit: It looks like you may have to manually add Scope Option 015 to your DHCP Scope Options to allow XP computers to find your DNS server. As noted, I don't have a running SBS 2008 server at the moment, so I can't look.
 
Last edited:
RebateMonger said:
Is it only Win7 clients that can't join the Domain using the Connect Wizard?
Click to expand...

No. XP clients also can't connect.

But after adding DNS suffix manually, then all clients can connect to http://connect.

I searhed the net and it seems Microsoft IPv4 DHCP does not support suffix, only IPv6, it seems then all XP clients must set DNS suffix manully.

I think Vista & Win 7 clients can get by this via enabling IPv6 and enable SBS 2008's IPv6 DHCP & configure it's suffix option.

Will see.
 
Thanks RebateMonger!

Just after adding option 015 and all clients work now. No deed for IPv6.

I'll try to not touching default config for SBS 2008

I just checked my SBS 2003 configuration and it does have all 5 options set. I was unable to connect to it to check its configuration last night probably due to internet problem.

Thanks again for all helpers!
 
Last edited:
mxnerd said:
Just after adding option 015 and all clients work now. No deed for IPv6.
Click to expand...
One caution: If you ever try to manually set the DNS Suffixes in Vista, be careful. I spent a couple of hours trying to manually set the DNS Suffix for a VPN connection in Vista Business and found that it WON'T SAVE THE SETTINGS.

XP worked fine, but Vista didn't. This seems to be a known bug. It may work for you, but it didn't work for me.
 
RebateMonger said:
One caution: If you ever try to manually set the DNS Suffixes in Vista, be careful. I spent a couple of hours trying to manually set the DNS Suffix for a VPN connection in Vista Business and found that it WON'T SAVE THE SETTINGS.

XP worked fine, but Vista didn't. This seems to be a known bug. It may work for you, but it didn't work for me.
Click to expand...

Thanks for the tip.

Best regards,
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top