Announcement

Collapse
No announcement yet.

Windows 2008 R2 Cannot Access Network Shares By Namespace

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

  • Windows 2008 R2 Cannot Access Network Shares By Namespace

    I setup a new W2K8 R2 server in order to test Remote Desktop Services, and that all went swimmingly, but after I joined it to the test domain and logged in as the domain admin, the netlogon script didn't run.

    Tried to go to the NETLOGON share using the domain name, but that reports \\testdomain\NETLOGON is not accessible. A device attached to the system is not functioning.

    However, going via the server name, \\testdc1\NETLOGON was fine.

    Ran the batch file, but still no mapped network drives, so I ran it inside an elevated command prompt instead. Every NET USE command returned System error 53 has occured. The network path was not found.

    But I can connect to the underlying server shares of the folder targets directly using \\servername\sharename.

    Very strange result.

    Another 2K8 R2 server I have in that test domain has no problems with accessing network shares via the namespaces.

    I Googled it of course, found a long thread from last year and did things like disable IPv6, TCP Chimney/Offload, RRS, and enable the various services to allow network discovery on the domain network, plus a bunch of other stuff I don't remember off the top of my head.

    Anyone else seen this issue, and resolved it?
    Last edited by TokyoBrit; 23rd March 2011, 10:50.

  • #2
    Re: Windows 2008 R2 Cannot Access Network Shares By Namespace

    sounds like a dns or firewall issue to me.

    - is the server properly registered in dns? can you resolve it through nslookup?
    - is file and printer sharing enabled and accessible through the firewall?

    Comment


    • #3
      Re: Windows 2008 R2 Cannot Access Network Shares By Namespace

      Cheers the for reply. Has me thinking. It's possible I guess. Unlike the other W2K8 server, this one is dual-homed, with one IF on the test DMZ.

      I've configured the external IF to not register, so only the internal IP is registered in DNS on the test DC. NSLOOKUP resolves that fine.

      Will check into file and printer sharing some more. I don't have it enabled, since it is for sharing files and printers on the local server, which I'm not doing, but it might have a knock-on affect.

      Hmm. If it was needed though, then I would expect the \\servername\sharename network shares to not work either, but they do. Does DFS use a different mechanism (ports/protocols) for it's shares?

      Comment


      • #4
        Re: Windows 2008 R2 Cannot Access Network Shares By Namespace

        What is the output of nslookup testdomain command ?
        Br,
        Csaba
        Regards,
        Csaba Papp
        MCSA+messaging, MCSE, CCNA
        ...............................
        Remember to give credit where credit is due and leave reputation points where appropriate
        .................................

        Comment


        • #5
          Re: Windows 2008 R2 Cannot Access Network Shares By Namespace

          Does the ping testdomain command return the ip address of the domain controller? It sounds like some dns issue.
          gerth

          MCITP sa, ea & va, [email protected]

          Comment


          • #6
            Re: Windows 2008 R2 Cannot Access Network Shares By Namespace

            Install this hotfix from Microsoft;

            KB2194664

            I've had a similar issue on both Windows Server 2008 R2 and Windows 7 Clients, this update has resolved the issue for me.
            Last edited by rob123; 23rd March 2011, 16:27. Reason: Typo

            Comment


            • #7
              Re: Windows 2008 R2 Cannot Access Network Shares By Namespace

              Originally posted by netxt View Post
              What is the output of nslookup testdomain command ?
              That returns the IP addresses of the 2 DC's in the test domain:

              Code:
               
              Server:  testdc.testdomain
              Address:  192.168.18.7
               
              Name:    testdomain
              Addresses:  192.168.18.7
                        192.168.19.7
              The testdomain simulates 2 sites, with a DC in each one and site links defined in AD.

              Comment


              • #8
                Re: Windows 2008 R2 Cannot Access Network Shares By Namespace

                Originally posted by gerth View Post
                Does the ping testdomain command return the ip address of the domain controller? It sounds like some dns issue.
                It could be. AD is very susceptable to DNS issues. Just one little thing and a whole slew of problems arise, but as it happens, the ping works:

                Code:
                 
                Pinging testdomain [192.168.18.7] with 32 bytes of data:
                Reply from 192.168.18.7: bytes=32 time<1ms TTL=128
                Reply from 192.168.18.7: bytes=32 time<1ms TTL=128
                Reply from 192.168.18.7: bytes=32 time<1ms TTL=128
                Reply from 192.168.18.7: bytes=32 time<1ms TTL=128
                 
                Ping statistics for 192.168.18.7:
                    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
                Approximate round trip times in milli-seconds:
                    Minimum = 0ms, Maximum = 0ms, Average = 0ms
                I'm wondering if it's because the default gateway is set for the external adapter, while the internal adapter uses a persistant static route.

                Comment


                • #9
                  Re: Windows 2008 R2 Cannot Access Network Shares By Namespace

                  Originally posted by rob123 View Post
                  Install this hotfix from Microsoft;

                  KB2194664

                  I've had a similar issue on both Windows Server 2008 R2 and Windows 7 Clients, this update has resolved the issue for me.
                  Yes. I had seen that before. It was the main solution to a long thread about this issue, and I had hoped it would work for me, but there are 3 problems with it:

                  1) I cannot access the network shares using the namespace even after immediately restarting the server.

                  2) I can always access the remote server using either its FQDN or IP address, which is the issue that 2194664 addresses.

                  3) When I run the Windows6.1-KB2194664-x64.msu, it says "The update is not applicable to your computer".

                  --------------------------

                  Never mind about 3). Because I installed Windows Server 2008 R2 SP1, the mrxsmb10.sys driver file is version 6.1.7601.17514, which is newer than the version that the hotfix installs.

                  It has to be something else.
                  Last edited by TokyoBrit; 24th March 2011, 04:49.

                  Comment


                  • #10
                    Re: Windows 2008 R2 Cannot Access Network Shares By Namespace

                    I installed the DFS tools for RSAT onto both W2K8 servers and ran:

                    dfsutil diag viewdfspath \\testdomain\public

                    On the working server, this responds with:

                    Code:
                     
                    The DFS Path <\\testdomain\public> resolves to -> <\\testfile\public>
                    \\testfile is a VM of Windows 2003 Storage Server.

                    On the problematic server, the same command responds with:

                    Code:
                     
                    Destination Path <\\testdomain\public> is inaccessible
                    Could not execute the command successfully
                    SYSTEM ERROR - A device attached to the system is not functioning.
                    Nothing written in the event logs about this problem, so I don't have a lot to go on.

                    Comment


                    • #11
                      Re: Windows 2008 R2 Cannot Access Network Shares By Namespace

                      Originally posted by TokyoBrit View Post
                      That returns the IP addresses of the 2 DC's in the test domain:

                      Code:
                       
                      Server:  testdc.testdomain
                      Address:  192.168.18.7
                       
                      Name:    testdomain
                      Addresses:  192.168.18.7
                                192.168.19.7
                      The testdomain simulates 2 sites, with a DC in each one and site links defined in AD.
                      OK, so this is probably your issue. How have you setup your sites? Have you configured the sites in ADSS? Is the 192.168.19.0 network your DMZ? If so then that DMZ IP address was registered in DNS at one point. If you don't want your DMZ address in DNS then you should go through and delete the addresses for your DMZ adapter. Then try connecting to the domain name again.
                      Regards,
                      Jeremy

                      Network Consultant/Engineer
                      Baltimore - Washington area and beyond
                      www.gma-cpa.com

                      Comment


                      • #12
                        Re: Windows 2008 R2 Cannot Access Network Shares By Namespace

                        Not discounting a DNS issue, but the AD sites are configured correctly.

                        The test DMZ is a different subnet, and does not hold a DNS server, nor do I register the WAN IP in DNS.

                        But to make things clearer, here is my IPCONFIG:

                        Code:
                         
                        Windows IP Configuration
                           Host Name . . . . . . . . . . . . : testsrv3
                           Primary Dns Suffix  . . . . . . . : testdomain
                           Node Type . . . . . . . . . . . . : Hybrid
                           IP Routing Enabled. . . . . . . . : No
                           WINS Proxy Enabled. . . . . . . . : No
                           DNS Suffix Search List. . . . . . : testdomain
                         
                        Ethernet adapter LAN:
                           Connection-specific DNS Suffix  . : 
                           Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Adapter #1
                           Physical Address. . . . . . . . . : 00-15-5D-00-52-11
                           DHCP Enabled. . . . . . . . . . . : No
                           Autoconfiguration Enabled . . . . : Yes
                           IPv4 Address. . . . . . . . . . . : 192.168.18.213
                           Subnet Mask . . . . . . . . . . . : 255.255.255.0
                           Default Gateway . . . . . . . . . : 
                           DNS Servers . . . . . . . . . . . : 192.168.18.7
                           NetBIOS over Tcpip. . . . . . . . : Enabled
                         
                        Ethernet adapter WAN:
                           Connection-specific DNS Suffix  . : 
                           Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Adapter #2
                           Physical Address. . . . . . . . . : 00-15-5D-00-52-13
                           DHCP Enabled. . . . . . . . . . . : No
                           Autoconfiguration Enabled . . . . : Yes
                           IPv4 Address. . . . . . . . . . . : 192.168.17.213
                           Subnet Mask . . . . . . . . . . . : 255.255.255.0
                           Default Gateway . . . . . . . . . : 192.168.17.1
                           NetBIOS over Tcpip. . . . . . . . : Disabled
                        And I have a single persistent route to access the internal network:

                        Code:
                        Persistent Routes:
                          Network Address          Netmask  Gateway Address  Metric
                             192.168.18.0    255.255.255.0   192.168.18.213       1
                        If DNS were really up the spout, I doubt I would be able to access the other servers via their FQDN, nor would I be able to login to this new server using a domain account. The only thing that doesn't work is accessing a DFS namespace from this server.

                        It's like the new server has no idea what DFS is, or knows how to enumerate DFS shares.

                        Comment

                        Working...
                        X