Announcement

Collapse
No announcement yet.

win 8 clients cannot map drive to dc unless mapping by ip

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • win 8 clients cannot map drive to dc unless mapping by ip

    we have a single vmware host, and 3 production VMs on it
    the host, less than 6 months old, had some issues. IBM replaced the motherboard a week ago. i have had one problem outstanding since then.
    When firing it back up, vcenter asked if we moved or copied the vms. I said moved, maybe i should have said copied. but i said moved.

    So the vms all fire up fine. a 2012 r2 vm running sql and some shared files works great. a 2003 vm that was a p2v conversion with terminal services and shared files works great.
    and a server 2008 r2 domain controller. shared printers, shared files...that seems to work, but is having issues.

    Windows 7 clients connect fine to the DC, they get mapped drives and printers without issue.

    windows 8 clients do not connect by name *SOMETIMES*. sometimes they get the mapped drives [still handled by a logon bat file] and printers, sometimes they dont.

    The windows 8 pcs can always ping the DC by name, every time, without fail. i did an ipconfig /flushdns on them and they still ping fine. i tried netsh int ip reset on them, reboot, drives are there! startup a pc the next day...no drives! crap!

    a net use or net view gets me a "system error 53 has occurred. the network path was not found" and that is consistent to all the devices with the issue.

    its driving me nuts.

    its not dns, browsing the network shows the server by name, i just cant map a drive to it. i can ping it, i can rdp to it, but i cant map a drive or connect to a printer. ive rebooted the vm for the hell of it--no luck.

    i have seen weird things, but this is beyond them all right now. any suggestions? it may be client or vmware related for all i know.

  • #2
    Can you post and IPCONFIG/ALL from
    a) the DC
    b) a WIn7 (working) client
    c) a WIn8 (not working) client

    Also, when you ping, are you resolving IPv6 or IPv4 addresses?
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      What does the relevant event viewer log say? Clean up the event logs, boot a client, and manually go through the logs to see what relevant errors you're getting.
      Cheers,

      Daniel Petri
      Microsoft Most Valuable Professional - Active Directory Directory Services
      MCSA/E, MCTS, MCITP, MCT

      Comment


      • #4
        Originally posted by Ossian View Post
        Can you post and IPCONFIG/ALL from
        a) the DC
        b) a WIn7 (working) client
        c) a WIn8 (not working) client

        Also, when you ping, are you resolving IPv6 or IPv4 addresses?

        in my research i discovered some people had an issue with this and ipv6, it is disable on the server, and on a couple of the win 8 clients i have been testing.
        i also tried another profile last night on the off-chance it was profile related, but it is not. here is the ipconfigs as requested

        ** from DC **
        PS C:\Users\administrator.company> ipconfig /all

        Windows IP Configuration

        Host Name . . . . . . . . . . . . : sitedc
        Primary Dns Suffix . . . . . . . : company.com
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : company.com

        Ethernet adapter Local Area Connection 4:

        Connection-specific DNS Suffix . :
        Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
        Physical Address. . . . . . . . . : 00-50-56-9B-8B-48
        DHCP Enabled. . . . . . . . . . . : No
        Autoconfiguration Enabled . . . . : company
        Link-local IPv6 Address . . . . . : fe80::ad42:b61d:e79:aeaa%18(Preferred)
        IPv4 Address. . . . . . . . . . . : 192.168.190.2(Preferred)
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.190.1
        DHCPv6 IAID . . . . . . . . . . . : 352324649
        DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-38-2A-D9-6C-AE-8B-66-6A-54
        DNS Servers . . . . . . . . . . . : 192.168.190.2
        192.168.140.2
        NetBIOS over Tcpip. . . . . . . . : Enabled

        * NOTE: IPv6 disabled so isatap, reusable isatap and teredo tunnel are all null


        ** from win 8 client, not working usually **

        Windows IP Configuration

        Host Name . . . . . . . . . . . . : ALC-USER
        Primary Dns Suffix . . . . . . . : company.com
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : company.com

        Ethernet adapter Ethernet:

        Connection-specific DNS Suffix . : company.com
        Description . . . . . . . . . . . : Intel(R) Ethernet Connection I217-LM
        Physical Address. . . . . . . . . : 40-A8-F0-65-DC-8D
        DHCP Enabled. . . . . . . . . . . : company
        Autoconfiguration Enabled . . . . : company
        IPv4 Address. . . . . . . . . . . : 192.168.190.112(Preferred)
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Lease Obtained. . . . . . . . . . : Tuesday, September 29, 2015 5:13:12 PM
        Lease Expires . . . . . . . . . . : Friday, October 2, 2015 7:02:18 AM
        Default Gateway . . . . . . . . . : 192.168.190.1
        DHCP Server . . . . . . . . . . . : 192.168.190.2
        DNS Servers . . . . . . . . . . . : 192.168.190.2
        150.150.100.70
        Primary WINS Server . . . . . . . : 192.168.190.2
        Secondary WINS Server . . . . . . : 150.150.100.70
        NetBIOS over Tcpip. . . . . . . . : Enabled

        Tunnel adapter isatap.company.com:

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


        ** from win 7 client, working **

        Windows IP Configuration

        Host Name . . . . . . . . . . . . : KMD-USER
        Primary Dns Suffix . . . . . . . : company.com
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : company.com

        Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix . : company.com
        Description . . . . . . . . . . . : Intel(R) Ethernet Connection I217-LM
        Physical Address. . . . . . . . . : A0-D3-C1-22-EF-56
        DHCP Enabled. . . . . . . . . . . : company
        Autoconfiguration Enabled . . . . : company
        Link-local IPv6 Address . . . . . : fe80::5049:e48e:f1bc:e7a1%12(Preferred)
        IPv4 Address. . . . . . . . . . . : 192.168.190.127(Preferred)
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Lease Obtained. . . . . . . . . . : Wednesday, September 30, 2015 8:02:54 AM
        Lease Expires . . . . . . . . . . : Friday, October 02, 2015 8:02:54 AM
        Default Gateway . . . . . . . . . : 192.168.190.1
        DHCP Server . . . . . . . . . . . : 192.168.190.2
        DHCPv6 IAID . . . . . . . . . . . : 262198209
        DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-4C-3B-AC-A0-D3-C1-22-EF-56
        DNS Servers . . . . . . . . . . . : 192.168.190.2
        150.150.100.70
        Primary WINS Server . . . . . . . : 150.150.100.70
        Secondary WINS Server . . . . . . : 192.168.190.2
        NetBIOS over Tcpip. . . . . . . . : Enabled

        Tunnel adapter isatap.company.com:

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

        Tunnel adapter Local Area Connection* 11:

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

        Comment


        • #5
          What is the server 150.150.100.70?

          Comment


          • #6
            WINS won't be needed normally (and your WINS server should be inside your network anyway). Also, while disabling IPv6 was recommended under some circumstances for Server 2008, AFAIK from 2008R2 onwards the recommendation is always NOT to disable it
            Tom Jones
            MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
            PhD, MSc, FIAP, MIITT
            IT Trainer / Consultant
            Ossian Ltd
            Scotland

            ** Remember to give credit where credit is due and leave reputation points where appropriate **

            Comment


            • #7
              Originally posted by danielp View Post
              What does the relevant event viewer log say? Clean up the event logs, boot a client, and manually go through the logs to see what relevant errors you're getting.

              not really seeing server side errors that may be relevant since 9/23

              i do not see a windows 7 SMBClient log like i do in windows 8. the windows 7 clients works consistently, however.

              digging deeper into broken windows 8 clients i am seeing this:
              The network connection failed.

              Error: The transport connection attempt was refused by the remote system.
              Server name: sitedc.company.com
              Server address: 192.168.190.2:445
              Connection type: Wsk
              smbclient event id 30803


              ​trying to see if i can find out what can cause that. but a reboot on those systems gets the drives to map every time as far as we can tell, which means were not even changing something on the broken [ish] clients to get them to work again.

              Comment


              • #8
                What is the server 150.150.100.70?
                another DC at another site. ridiculously, years and years ago, someone made one of the site subnets 150.150.x.x /16. i have been trying to get my boss to let us change it since i got here two years ago, that might finally happen in Q1 2016.

                Comment


                • #9
                  I would remove the 150 address from the DHCP scope and try that.

                  Can the client access the server using its FQDN? I.E. server1.domainname.com

                  Can it access the server using its NetBIOS name? server1

                  Comment


                  • #10
                    Originally posted by wullieb1 View Post
                    I would remove the 150 address from the DHCP scope and try that.

                    Can the client access the server using its FQDN? I.E. server1.domainname.com

                    Can it access the server using its NetBIOS name? server1

                    they are all working at the moment, ill test FQDN next time one breaks. accessing just via \\sitedc doesnt work, and a net view \\sitedc gives the same error 53 as the net use command/drive mapping.

                    ive changed the DHCP DNS option to remove 150 and add another 192.168 address at another site.

                    thanks for all the suggestions
                    -dave

                    Comment


                    • #11
                      after a week, i get informed just now that the drives work after a reboot...and then randomly disconnect during the day.

                      which means i have an update:

                      1 - changing the dns 2nd host in dhcp didnt change anything.

                      2 - this broken client can do a net view \\sitedc.company.com but NOT just net view \\sitedc that we usually use. what would cause this? the DNS suffix is there in the ipconfig so im not sure what else to look for.
                      --- i am not changing his mapped drives yet to try and use the fqdn, its the plant manager, he is not for testing.
                      --- there is a user pc that this keeps happening to, i will test it more thoroughly when she leaves today

                      3 - each of our 5 sites has a domain controller that does dhcp,file and print shares at its site. its the first dns responder in each dhcp scope. i am testing loging into a windows 8 client at my site, the 150.150.x.x site, as a user from the 192.168.190.x site [to get their login script], to see if i have mapped drive issues.
                      --i set two test windows 8 clients here to use 192.168.190.2 for their first dns server and 150.150.100.70 as the second
                      --so far, i do not have any issues. i have restarted each client about 5 times. no problems. i thus remain flummoxed.
                      Last edited by davensc; 30th September 2015, 19:28.

                      Comment


                      • #12
                        IIRC if WINS is available, it will be used for NetBIOS (short) name resolution over DNS, so it would appear the issue is the WINS server
                        (May well be wrong - I have not used WINS for many years now)
                        Tom Jones
                        MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
                        PhD, MSc, FIAP, MIITT
                        IT Trainer / Consultant
                        Ossian Ltd
                        Scotland

                        ** Remember to give credit where credit is due and leave reputation points where appropriate **

                        Comment


                        • #13
                          Originally posted by Ossian View Post
                          IIRC if WINS is available, it will be used for NetBIOS (short) name resolution over DNS, so it would appear the issue is the WINS server
                          (May well be wrong - I have not used WINS for many years now)
                          so ill set a test pc at my site [the 150.150.x.x /16 subnet] to use a static ip/dns and try to reboot/net use/net view/browse to just SITEDC but not SITEDC.COMPANY.COM and see how it goes without designating it a WINS server to use.

                          here is the ipconfig /all
                          -- after setting a static i did ipconfig /flushdns and restarted the pc immediately

                          Windows IP Configuration

                          Host Name . . . . . . . . . . . . : 150-SPARE8
                          Primary Dns Suffix . . . . . . . : company.com
                          Node Type . . . . . . . . . . . . : Hybrid
                          IP Routing Enabled. . . . . . . . : No
                          WINS Proxy Enabled. . . . . . . . : No
                          DNS Suffix Search List. . . . . . : company.com

                          Ethernet adapter Ethernet:

                          Connection-specific DNS Suffix . :
                          Description . . . . . . . . . . . : Intel(R) Ethernet Connection I217-LM
                          Physical Address. . . . . . . . . : F0-92-1C-F3-7B-88
                          DHCP Enabled. . . . . . . . . . . : No
                          Autoconfiguration Enabled . . . . : Yes
                          Link-local IPv6 Address . . . . . : fe80::2c3f:5f97:7cb3:af40%3(Preferred)
                          IPv4 Address. . . . . . . . . . . : 150.150.200.231(Preferred)
                          Subnet Mask . . . . . . . . . . . : 255.255.0.0
                          Default Gateway . . . . . . . . . : 150.150.90.1
                          DHCPv6 IAID . . . . . . . . . . . : 66097692
                          DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-7B-8D-0F-F0-92-1C-F3-7B-88
                          DNS Servers . . . . . . . . . . . : 192.168.190.2
                          NetBIOS over Tcpip. . . . . . . . : Enabled

                          Tunnel adapter 6TO4 Adapter:

                          Connection-specific DNS Suffix . :
                          Description . . . . . . . . . . . : Microsoft 6to4 Adapter
                          Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
                          DHCP Enabled. . . . . . . . . . . : No
                          Autoconfiguration Enabled . . . . : Yes
                          IPv6 Address. . . . . . . . . . . : 2002:9696:c8e7::9696:c8e7(Preferred)
                          Default Gateway . . . . . . . . . :
                          DHCPv6 IAID . . . . . . . . . . . : 134217728
                          DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-7B-8D-0F-F0-92-1C-F3-7B-88
                          DNS Servers . . . . . . . . . . . : 192.168.190.2
                          NetBIOS over Tcpip. . . . . . . . : Disabled

                          Tunnel adapter isatap.{03BB4FDA-0056-4B86-ACB5-EE192D470E51}:

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


                          after reboot: drives are mapped to SITEDC
                          i can browse to \\SITEDC
                          i can net view \\SITEDC and net use \\SITEDC
                          i can browse the network and click into SITEDC, which also doesnt work when \\SITEDC doesnt work on the broken clients

                          Comment


                          • #14
                            I wonder is the WINS Servers are not replicating correctly and causing a conflict somewhere. Check the Replication numbers and see if they match (damn I hope I have remembered that right), assuming that they are Replicating.

                            You mentioned way, way above somewhere that you map the drive using a logon.bat scripting. Have you considered mapping them via a GPO?

                            Prior to the motherboard replacement, did the Windows 8 machines always get the drive mappings? (a curiosity question, are the workstations Windows 8 or 8.1? )
                            1 1 was a racehorse.
                            2 2 was 1 2.
                            1 1 1 1 race 1 day,
                            2 2 1 1 2

                            Comment


                            • #15
                              Originally posted by biggles77 View Post
                              I wonder is the WINS Servers are not replicating correctly and causing a conflict somewhere. Check the Replication numbers and see if they match (damn I hope I have remembered that right), assuming that they are Replicating.

                              You mentioned way, way above somewhere that you map the drive using a logon.bat scripting. Have you considered mapping them via a GPO?

                              Prior to the motherboard replacement, did the Windows 8 machines always get the drive mappings? (a curiosity question, are the workstations Windows 8 or 8.1? )
                              yes, prior to the motherboard update [which again, was for a VMware host] everything worked perfect. this was a physical server 2008r2 server that was a p2v conversion but we didnt have any issues after the conversion several months ago.

                              i have considered gpo. most of the things i consider updating get a thumbs up from my boss, a few things dont. that one hasnt, pretty much arbitrarily--i might try a gpo just for that site, if it works id be allowed to update the others. /then would ask forgiveness

                              all machines are 8.1 Update 1 and get windows updates regularly, fwiw.

                              Comment

                              Working...
                              X