Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Applying SP2 to 2003R2 drops Windows 7 clients using WSH

Answered Applying SP2 to 2003R2 drops Windows 7 clients using WSH

  • Thursday, July 26, 2012 6:47 PM
     
     
    Sign In to Vote
    0

    ONLY clients using Windows 7 receive error 80070035 when connecting to a file server running 2003 R2 with a newly installed SP2

    worked flawlessly prior to deployment of SP2.

    have tried 10 or 15 solutions at the client side, and now I'm convinced it's at the server side - especially after viewing this KB article

    http://support.microsoft.com/kb/898060

    any hotfixes or suggestions?

    Here - I'll summarize:

    not solved with:
    01 - enabling NetBIOS over TCP
    02 - disabling IPv6
    03 - disabling windows search and Remote Differential Compression
    04 - addng EnabledWiredConnections to registry
    05 - replacing server name with IP address in script
    06 - removing Hidden Devices in Device Manager/Network Adapters
    07 - replacing WSH with batch file
    08 - addning authentication to Credential Manager
    09 - Enabling Computer Browser in Services
    10 - removing Symantec Endpoint Protection completely
    11 - toggling Network Discovery

    this is solved (for a short time) by rebooting (not logging off) either the server or the workstation running Win7


    This is a static IP network, and I do NOT use GP for scripting.

    • Edited by colin sharpe Friday, July 27, 2012 10:00 PM clarification
    •  
     

All Replies

  • Sunday, July 29, 2012 3:12 PM
     
     
    Sign In to Vote
    0

    Can you post unedited ipconfig /all of problem server, workstation and local DNS server?

     

     

     

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

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

     
  • Sunday, July 29, 2012 6:34 PM
     
     
    Sign In to Vote
    0

    Problem Server:

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : wso-srv2
       Primary Dns Suffix  . . . . . . . : wso.local
       Node Type . . . . . . . . . . . . : Unknown
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : wso.local

    Ethernet adapter Intel Pro 1000 MT Gigabit Ethernet Adapter - Onboard:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
       Physical Address. . . . . . . . . : 00-0F-1F-F8-C8-C1
       DHCP Enabled. . . . . . . . . . . : No

       IP Address. . . . . . . . . . . . : 192.168.0.100
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.0.1
       DNS Servers . . . . . . . . . . . : 192.168.0.102

    Workstation:

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : WSO-00235
       Primary Dns Suffix  . . . . . . . : wso.local
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : wso.local

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) Family PCI-E
     Gigabit Ethernet NIC (NDIS 6.20)
       Physical Address. . . . . . . . . : 00-25-64-DB-1C-FA
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::85d5:44ab:5cb1:6b31%11(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.0.235(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.0.1
       DHCPv6 IAID . . . . . . . . . . . : 234890596
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-1C-5A-22-00-25-64-DB-1C-FA

       DNS Servers . . . . . . . . . . . : 192.168.0.102
                                           216.8.137.203
                                           216.8.137.204
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{C8F9F1EE-AC00-44D1-8BE9-C6C4BC06A282}:

       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

    Tunnel adapter Teredo Tunneling Pseudo-Interface:

       Media State . . . . . . . . . . . : Media disconnected
       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

    Local DNS Server:

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : WSO-MAIN
       Primary Dns Suffix  . . . . . . . : wso.local
       Node Type . . . . . . . . . . . . : Unknown
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : Yes
       DNS Suffix Search List. . . . . . : wso.local

    Ethernet adapter Local Area Connection 8:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
       Physical Address. . . . . . . . . : 00-18-8B-E6-AB-4E
       DHCP Enabled. . . . . . . . . . . : No
       IP Address. . . . . . . . . . . . : 192.168.0.102
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.0.1
       DNS Servers . . . . . . . . . . . : 192.168.0.102

     
  • Sunday, July 29, 2012 8:43 PM
     
     Proposed
    Sign In to Vote
    0

    You should remove public DNS addresses from workstation. Domain members should only have local DNS server address. Put public addresses in forward lookup zone of local DNS server. May want to do ipconfig /registerdns and or reboot after changes.

     

     

     

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

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

     
  • Tuesday, July 31, 2012 5:35 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi colin,

    Thanks for posting here.

    And what if access via the IP address of this windows 2003 file server from Windows 7 Client host ?

    Please first correcting the DNS address on client and see how is going .

    Thanks.

    Tiger Li

    Tiger Li

    TechNet Community Support

     
  • Tuesday, July 31, 2012 3:29 PM
     
     
    Sign In to Vote
    0
    RPC error (unavailable) after running ipconfig /registerdns
     
  • Wednesday, August 01, 2012 12:46 AM
     
     Proposed
    Sign In to Vote
    0

    Might be port blockage and or DNS misconfiguration. Possibly some help here.

    http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/8b62cd08-65c1-49e7-9919-881f6ff5a105

    http://social.technet.microsoft.com/wiki/contents/articles/4494.troubleshooting-the-rpc-server-is-unavailable.aspx

    http://technet.microsoft.com/en-us/library/dd772723(WS.10).aspx

    http://blogs.technet.com/b/abizerh/archive/2009/06/11/troubleshooting-rpc-server-is-unavailable-error-reported-in-failing-ad-replication-scenario.aspx

     

     

     

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

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

     
  • Wednesday, August 01, 2012 1:14 PM
     
     
    Sign In to Vote
    0

    I have a lot of reading to do.

    I'm not convinced, however, that this is not the result of a windows update flaw.

    This was a well connected system. No manual configuration changes had been made to cause this.

     
  • Thursday, August 02, 2012 12:32 AM
     
     
    Sign In to Vote
    0

          well connected system

    The fact that you had to have public DNS addresses in client is a little suspicious.

     

     

     

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

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

     
  • Saturday, August 11, 2012 7:13 PM
     
     Answered
    Sign In to Vote
    0

    Here's the solution:

    Wipe and re-install OS back to base 2003.

    and ... NEVER trust automatic updates.

    • Marked As Answer by colin sharpe Wednesday, August 15, 2012 4:59 PM
    •