none
Unable to connect Windows 7 client to Server 2003

    Question

  • I have a Windows 7 Pro SP1 tablet trying to join the domain of a Windows 2003 SP2 server. I have no issues with my 2K or XP systems (about 10 total), and oddly, I have a Windows 7 desktop that had no serious issues in joining either--but I have spent much time with this unit and don't know what I am missing.

    The error is: "An attempt 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."

    I have performed a clean boot; Unselected TCP/IPv6; and set the DNS server Address manually, all per suggestions in various forums.

    We need to get this up ASAP; thank you so much in advance...

    ---------
    This is the Tablets IPCONFIG/ALL info:

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Inspect
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Bluetooth Network Connection:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
       Physical Address. . . . . . . . . : 7C-E9-D3-24-31-98
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Wireless LAN adapter Wireless Network Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Dell Wireless 1535C Half MiniCard
       Physical Address. . . . . . . . . : 7C-E9-D3-24-31-97
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.1.100(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 192.168.1.1
                                           192.168.1.3
       NetBIOS over Tcpip. . . . . . . . : Enabled

    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:4137:9e76:209a:1ccb:3f57:fe9b(Pref
    erred)
       Link-local IPv6 Address . . . . . : fe80::209a:1ccb:3f57:fe9b%15(Preferred)
       Default Gateway . . . . . . . . . : ::
       NetBIOS over Tcpip. . . . . . . . : Disabled

    Tunnel adapter isatap.{99374A1D-28DE-4831-A9C5-4BD0CAD96419}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    ----------
    This is the server's:

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : mvmws2
       Primary Dns Suffix  . . . . . . . : mvmw.local
       Node Type . . . . . . . . . . . . : Broadcast
       IP Routing Enabled. . . . . . . . : Yes
       WINS Proxy Enabled. . . . . . . . : Yes
       DNS Suffix Search List. . . . . . : mvmw.local

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) 82544GC Based Network Connection

       Physical Address. . . . . . . . . : 00-C0-9F-27-98-8E
       DHCP Enabled. . . . . . . . . . . : No
       IP Address. . . . . . . . . . . . : 192.168.1.3
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 192.168.1.3

    --------

    In addition, the wireless router's info:

    Static IP Address: 71.86.25.66
    IP Subnet Mask: 255.255.255.252
    Gateway IP Address: 71.86.25.65
    Primary DNS: 192.168.1.3
    Secondary DNS: 24.217.0.5


    • Edited by KSVIL Thursday, August 23, 2012 4:44 AM
    Thursday, August 23, 2012 4:20 AM

Answers

  • windows server 2003 need one compatibility update for vista and windows 7 usually if you have windows server 2003 SP 2 then its already installed on it...

    update is :

    KB926505

    1st thing check it out this update is already installed on server or not..

    in my case this update was already installed on server but still was getting the error message of administrative rights so i follow bellow additional steps on windows 7 and relogin as administrator and after that the regual small business network configuration wizard that we usually use to add windows xp to add to domain runs perfectly fine this is the steps that i follow on windows 7

    1. Run 'secpol.msc' from the Start menu.
    2. Go to Local Policies -> Security Options
    3. Double Click on 'Accounts: Administrator account status'
    4. Click 'enabled'
    5. Click OK

    Thanks, Swapnil Prajapati

    Thursday, August 23, 2012 5:58 AM
  • Hello,

    in a domain NEVER use the Default gateway as DNS server, ONLY the domain DNS server, in your case 192.168.1.3 has to be used on ALL domain machines.

    So on the client machine REMOVE the 192.168.1.1 as DNS server on the NIC and work ONLY with 192.168.1.3, after the change run ipconfig /flushdns and restart the workstation.

    Also on a DC NEVER enable RRAS or the WINS proxy, IP Routing Enabled. . . . . . . . : Yes and   WINS Proxy Enabled. . . . . . . . : Yes, so disable that ones also and run ipconfig /flushdns and ipconfig /registerdns and restart the netlogon service on the DC.

    To have internet access on domain machines, the FORWARDERS in the DNS server properties in the DNS management console must be configured with the ISPs DNS server.


    Best regards

    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://msmvps.com/blogs/mweber/

    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.


    Thursday, August 23, 2012 7:31 AM

All replies

  • Hi,

    Can you change your Preferred DNS servers as below and try ?

    DNS Servers . . . . . . . . . . . : 192.168.1.3
                                           192.168.1.1


    Thanks, Swapnil Prajapati

    Thursday, August 23, 2012 4:38 AM
  • Thank you for the quick reply! Sadly, I tried that just moments before your post; the same error comes up. Any other suggestions?
    Thursday, August 23, 2012 4:50 AM
  • From windows 7, click start, type local and open the Local Security Policy
    Manager.

    Select Local Policies -> Security Options, in the right find Network
    Secuity: LAN Manager Authentication Leven, and set to Send LM & NTLM - use
    NTLMv2 session security if negotiated.

    Thanks, Swapnil Prajapati

    Thursday, August 23, 2012 4:57 AM
  • From windows 7, click start, type local and open the Local Security Policy
    Manager.

    Select Local Policies -> Security Options, in the right find Network
    Secuity: LAN Manager Authentication Leven, and set to Send LM & NTLM - use
    NTLMv2 session security if negotiated.

    Thanks, Swapnil Prajapati

    You can also use netdom to take system in domain

    netdom join %computername% /domain:DOMAIN.COM /userd:DOMAIN\administrator /passwordd:P@ssw0rd


    Thanks, Swapnil Prajapati

    Thursday, August 23, 2012 4:59 AM
  • Tried suggestion, same error occurred; rebooted (just in case) and tried again, no change in results.

    Currently working on next suggestion of netdom... Thanks...

    Thursday, August 23, 2012 5:21 AM
  • I tried netdom, but didn't get anywhere: netdom join Inspect /d:mvmw.local /ud:Administrator /pd:*

    Did I get the syntax right?

    Thanks!

    Thursday, August 23, 2012 5:40 AM
  • windows server 2003 need one compatibility update for vista and windows 7 usually if you have windows server 2003 SP 2 then its already installed on it...

    update is :

    KB926505

    1st thing check it out this update is already installed on server or not..

    in my case this update was already installed on server but still was getting the error message of administrative rights so i follow bellow additional steps on windows 7 and relogin as administrator and after that the regual small business network configuration wizard that we usually use to add windows xp to add to domain runs perfectly fine this is the steps that i follow on windows 7

    1. Run 'secpol.msc' from the Start menu.
    2. Go to Local Policies -> Security Options
    3. Double Click on 'Accounts: Administrator account status'
    4. Click 'enabled'
    5. Click OK

    Thanks, Swapnil Prajapati

    Thursday, August 23, 2012 5:58 AM
  • Hello,

    in a domain NEVER use the Default gateway as DNS server, ONLY the domain DNS server, in your case 192.168.1.3 has to be used on ALL domain machines.

    So on the client machine REMOVE the 192.168.1.1 as DNS server on the NIC and work ONLY with 192.168.1.3, after the change run ipconfig /flushdns and restart the workstation.

    Also on a DC NEVER enable RRAS or the WINS proxy, IP Routing Enabled. . . . . . . . : Yes and   WINS Proxy Enabled. . . . . . . . : Yes, so disable that ones also and run ipconfig /flushdns and ipconfig /registerdns and restart the netlogon service on the DC.

    To have internet access on domain machines, the FORWARDERS in the DNS server properties in the DNS management console must be configured with the ISPs DNS server.


    Best regards

    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://msmvps.com/blogs/mweber/

    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.


    Thursday, August 23, 2012 7:31 AM