SBS2008 - will not join PC to domain using http://connect
Ok background info, I setup the sbs2008 server using the wizards etc. Gave it a 192.168.10.x range.
I have now placed the server in my office. I have 2 sonicwalls which connect my 2 offices up and they manage the DHCP. So I have disabled the dhcp on the server and given it a static address of 192.168.1.100 which is the same range as the sonicwall dhcp.
Can access the sbs2008 server shares etc from clients PC.
I am however unable to join PCs to the domain. I go to http://connect in the webbrowser of a win7 professional PC and it doesnt connect - so I run the client wizard which I extracted from sbs console and I get the message "not meet maximum operating system requirements"
I have installed rollup 4 on my sbs2008 as this was mentioned in other threads. I also tried a Win XP PRO PC, with no luck. Although when I had this in the office on the 192.168.10.x range I was able to join PCs to the domain using the http://connect.
Any thoughts?
I have now placed the server in my office. I have 2 sonicwalls which connect my 2 offices up and they manage the DHCP. So I have disabled the dhcp on the server and given it a static address of 192.168.1.100 which is the same range as the sonicwall dhcp.
Can access the sbs2008 server shares etc from clients PC.
I am however unable to join PCs to the domain. I go to http://connect in the webbrowser of a win7 professional PC and it doesnt connect - so I run the client wizard which I extracted from sbs console and I get the message "not meet maximum operating system requirements"
I have installed rollup 4 on my sbs2008 as this was mentioned in other threads. I also tried a Win XP PRO PC, with no luck. Although when I had this in the office on the 192.168.10.x range I was able to join PCs to the domain using the http://connect.
Any thoughts?
Alan Hardisty
Turn off the Windows Firewall on the server - I just turned it off on my SBS 03 to SBS 08 migration and everything is running smoothly now. Previously I couldn't pick up and IP address via the LAN NIC but could via the WiFi NIC!
where are you getting dns from on the client machines?
ASKER
@ Hi alanhardisty - the firewall is turned off
@jorlando66 - clients are all set to automatic, as they get their IP addresses from the dhcp on the sonicwall, is it likely the dns on the sonicwall is acting as the dns, rather than the SBS2008 Server?
@jorlando66 - clients are all set to automatic, as they get their IP addresses from the dhcp on the sonicwall, is it likely the dns on the sonicwall is acting as the dns, rather than the SBS2008 Server?
Ah well - sounds like jorland066 has it with DNS from the router not server.
I always use DHCP on the server and not the router. More controllable that way : )
I always use DHCP on the server and not the router. More controllable that way : )
Hi Alan. Good to see you.
@unrealone1: It is likely your clients are not seeing the AD. I would set up the dhcp scopes and let windows be your dhcp provider and the firewall handling the firewalling.
You can set up the dhcp on the firewall to hand out your AD dns server addresses but make sure your forwarders are set up properly on the servers.
@unrealone1: It is likely your clients are not seeing the AD. I would set up the dhcp scopes and let windows be your dhcp provider and the firewall handling the firewalling.
You can set up the dhcp on the firewall to hand out your AD dns server addresses but make sure your forwarders are set up properly on the servers.
ASKER
Ok will look into disabling the dhcp on the Sonicwall and putting it back on to the server.
Will post back tomorrow, thanks for your quick response.
Will post back tomorrow, thanks for your quick response.
Good Luck
There is a blog article on using the router for DHCP but you are supposed to use the SBS as the DHCP server. Doing so not only hands out the IP and gateway but also the necessary SBS as the *ONLY* DNS server, domain suffix, WINS (SBS 2003) and node type.
In order to use http://connect :
-The client can point only to the SBS for DNS
-there can only be one NIC (wired, wireless, or virtual) enabled on the client. You can enable others after
-if WIN7 rollup 3 must be installed on the server
In order to use http://connect :
-The client can point only to the SBS for DNS
-there can only be one NIC (wired, wireless, or virtual) enabled on the client. You can enable others after
-if WIN7 rollup 3 must be installed on the server
ASKER
@Robwill
- I have installed rollup4 on my sbs2008 server, I dont need rollup3 do I as well? (4 is latest, correct?)
Another thought:
I forgot to mention, that I did add my servers IP address as a preferred dns server on the NIC of the client PC, but from what I can remember that client PC still wouldnt see http://connect.
- I have installed rollup4 on my sbs2008 server, I dont need rollup3 do I as well? (4 is latest, correct?)
Another thought:
I forgot to mention, that I did add my servers IP address as a preferred dns server on the NIC of the client PC, but from what I can remember that client PC still wouldnt see http://connect.
Rollup 4 is fine.
>>" did add my servers IP address as a preferred dns server "
Preferred or only? If you have another DNS server listed that is not a Domain Controller in your domain, such as an ISP or router, even as an alternate, it will fail.
Also as mentioned make sure only one NIC enabled.
Once set correctly try from a command line
nslookup servername
nslookup domainname (include suffix such as internal-domain.local)
nslookup connect
all should return the IP of the SBS.
>>" did add my servers IP address as a preferred dns server "
Preferred or only? If you have another DNS server listed that is not a Domain Controller in your domain, such as an ISP or router, even as an alternate, it will fail.
Also as mentioned make sure only one NIC enabled.
Once set correctly try from a command line
nslookup servername
nslookup domainname (include suffix such as internal-domain.local)
nslookup connect
all should return the IP of the SBS.
ASKER
Hi Rob, I only have my SBS2008 server dns, so I put the Ip address of this server, no other network cards on my client PC - just the one.
Will try your suggestions, thanks
Will try your suggestions, thanks
I was just re-reading the original question.
You changed the server from the 192.168.10.0/24 subnet to the 192.168.1.100 subnet. Did you re-run the connect to the Internet wizard? If not you should.
SBS should definitely be handling DHCP not the Sonicwall. The SBS will hand out scope options the Sonicwall will not.
Is the client PC on the same LAN as the SBS or the remote site, connected by VPN. If the SBS is not the DHCP server, or if the client PC is located at the remote site you should also add the domain suffix to the Advanced TCP/IP properties of the client NIC as per:
http://www.lan-2-wan.com/Added%20Images/Blog/DNS.jpg
You changed the server from the 192.168.10.0/24 subnet to the 192.168.1.100 subnet. Did you re-run the connect to the Internet wizard? If not you should.
SBS should definitely be handling DHCP not the Sonicwall. The SBS will hand out scope options the Sonicwall will not.
Is the client PC on the same LAN as the SBS or the remote site, connected by VPN. If the SBS is not the DHCP server, or if the client PC is located at the remote site you should also add the domain suffix to the Advanced TCP/IP properties of the client NIC as per:
http://www.lan-2-wan.com/Added%20Images/Blog/DNS.jpg
ASKER
Yeah I reran the internet wizard but it failed to complete, because it complained that the dhcp already existed etc. Will disable the sonicwall and rerun the wizard.
The client PCs I am trying this on, are on the same site as the SBS server.
The client PCs I am trying this on, are on the same site as the SBS server.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks to Jorlando and Rob.