Connecting Windows 7 to Windows Server 2003 SBS

[darboe]

Please
Most of my computers use windows xp and we are starting to upgrade them to Windows 7. We bought 3 new computers with Windows 7 professional on them.

When I setup through windows xp using the networkID wizard everything works fine but when I use the same information for windows 7 it does not work and gives me the following error:
an attemp to resolve the DNS name of a domain controller in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain.

Please help.
Darren

Here is the IPCONFIG info for both computers:
Windows Server 2003 SBS

Windows IP Configuration
Host Name . . . . . . . . . . . . : jerrys-plumbing
Primary Dns Suffix . . . . . . . : JerrysPlumbingSpecialties.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : JerrysPlumbingSpecialties.local

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 M Network Connection
Physical Address. . . . . . . . . : 00-0E-0C-4E-91-F1
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.179
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Disabled

Ethernet adapter Server Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 CT Network Connection
Physical Address. . . . . . . . . : 00-0E-0C-4E-91-F0
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.149
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1

Windows 7 Computer:

Windows IP Configuration
Host Name . . . . . . . . . . . . : install
Primary Dns Suffix . . . . . . . : jerrysplumbingspecialties.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : jerrysplumbingspecialties.local
digis.net
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : digis.net
Description . . . . . . . . . . . : Intel(R) 82567LM-3 Gigabit Network Connec
tion
Physical Address. . . . . . . . . : 18-A9-05-29-65-DF
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.121(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, December 05, 2013 9:39:58 AM
Lease Expires . . . . . . . . . . : Friday, December 06, 2013 10:27:29 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 66.182.72.3
66.182.71.3
192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.digis.net:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : digis.net
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6ab8:880:352a:3f57:fe86(Prefe
rred)
Link-local IPv6 Address . . . . . : fe80::880:352a:3f57:fe86%14(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

 

[chev65]

The DNS error may be a symptom of the actual problem.

Windows 7 typically has problems accessing shares on Server 03 unless you make the following adjustments to the lanman server and encryption settings in the Local Security Policy per the link.

Solved W2K3 Server can access W8 W8 computer cant see W2K server

 

[darboe]

This needs to be done on the server correct?

 

[chev65]

This needs to be done on the server correct?

It needs to be done on the Windows 7 client machines so they can connect to the Server.

 

[darboe]

Did not solve it....... Any other suggestions?

 

[chev65]

You might try pointing the DNS servers on the Windows 7 machine back to the Domain controller.

You cannot use the DNS service of your ISP if you are running a domain.

AD uses the local DNS to find domain resources. Point the workstation to the DC for DNS.

You should also modify the local DNS to forward to a public DNS (such as your ISP) so that it can resolve foreign URLs as well as local names. The client machine should use the local DNS server only. Do not add the ISP DNS address to the workstation, even as a secondary.

 

[darboe]

My server has two network cards. I have used both ip addresses as my dns servers with the combination of the google dns service 8.8.8.8. Still cannot connect to the server. I can get internet but nothing else.

 

[chev65]

Same problem with basically the fix I just mentioned but with an added twist maybe this will help.
Cannot add Windows 7 PC to domain. Get the following message. An - Microsoft Community

We finally got the computer to join the domain by doing the following: in the network adapter IP 4 properties, set the DNS ip address to that of the domain controller, NOT the DNS. Then went back to the computer properties to add the computer to the domain, it was added successfully. After rebooting the machine and logging into the domain account, go back to the IP 4 properties and reset the DNS to automatically get the ip address.

 

[darboe]

Still nothing. I have tried setting static ip address. I have tried everything.... I have no idea why it won't work...

 

[chev65]

Have you tried pointing the DNS to the gateway IP 192.168.1.1

From what I have read, if you changed the IP address of the domain controller at any point, the DNS forward and reverse lookup zones don’t update automatically (if you change the subnet). simply go into the DNS server and search for the old IP and change it to the new IP. For the reverse lookup zone you need to add a new zone and delete the old zone.