none
Sometimes unable to access a server from 2008R2 using by netbios name

    Question

  • Hello,

    We have a Terminal server (Windows Server 2008R2) When we try to connect to the shared folder using the netbios name, it didn't work. It worked when we used the fqdn name. Strangely, this happen only once in awhile.  Anyone know why this happened and how to fix this issue for good?

    We are able to access other servers bij netbios names. The server that we aren't able to access isn't always the same server. We have this problem on multiple servers.

    The servers have the same thing in common:

    The servers are virtual and running on a Windows Server 2008 R2 Hyper V servers.

    They are Windows Server 2008 R2 with terminal services installed.

    When we restart the Workstation service everything is working again.

    When we add the name in the host file it's still not working.

    Please let me know if you need more information. Any suggest are welcome.

    Remco

    Friday, December 24, 2010 10:38 AM

Answers

  • I've contacted Microsoft. There are some hot fixes availible.

     

    As just discussed please install the below hotfixes for your W2K8 R2 machine. You can download these via http://support.microsoft.com/kb/<number> where you use the below numbers.

    If you are downloading them using another OS you might need to select manually that you want the Windows 7/Windows 2008 R2 x64 version of this hotfix. If you download them from the target OS it will show the correct version to download.

    <number> - component to update
    2444558 for Mrxsmb10.sys
    982860 for Mrxsmb20.sys and Mrxsmb.sys
    2383928 for Win32k.sys
    2398906 - kernel files

    As some of the components were also updated via security updates it is possible that you receive the message that one or more hotfixes were not applicable to your system. Please let me know if that happens and for which hotfixes

    After installation of the hotfixes you need to reboot the system.

    Please let me know if you have any questions or issues,

    We have installed these hot fixes and are monitoring the system know.

    • Marked as answer by Remco Hooijer Thursday, December 30, 2010 3:09 PM
    Thursday, December 30, 2010 3:09 PM

All replies

  • Please make sure that NetBIOS over TCP/IP is enabled.

    Also, make sure that the DNS suffix search list is well configured and that there is no firewall /router blocking the NetBIOS traffic.

     


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

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Friday, December 24, 2010 12:44 PM
  • NetBIOS over TCP/IP is enabled.

    Also the DNS suffix is configured properly. Firewalls are disabled on all servers.

    We have also configured WINS. All these changes/options have no effect on the problem.

    Friday, December 24, 2010 12:48 PM
  • Hi Remco,

    Make sure the Workstation service is running on the local computer while Server service is running on the remote computer.

    Can you post exact error message and errors in the event logs.

     

    Thanks.

    Friday, December 24, 2010 2:52 PM
  • These services are running, there are no event related to this problem.
    Friday, December 24, 2010 3:17 PM
  • Hello,

    When the proble occurs:

    1. Ping the Server's NETBIOS name.

    2. If is responds, is the IP address the correct one for the server?

    3. If it times out, what's the IP address it's trying to reach?

    When the problem occurs, you can access the shared folder using the FQDN without having to restart the workstation service. Is that right?

    After the problem occurs, tombstone the WINS records and try again. What is the result?

    Consider turning OFF WINS server. WINS is a thing of the past.

    Also, the shared folder is is on a server with a static IP, right?

    Also, there are no name conflicts on the network, right?

    When the problem occurs, what happens if you flush the resolver cache and try again?

    When you ping the server name, here's what Windows does*:

    1. Checks it is own name.
    2. Checks the cache.
    3. Checks the HOSTS file
    4. Suffix the Suffix configured on the machine, then query DNS again
    5. Check WINS
    6. Broadcast
    7. LMHOSTS

    * I took this list from a blog post by Ace Fekay. Thanks, Ace!

    Miguel


    Miguel Fra / Falcon IT Services
    Computer & Network Support, Miami, FL
    Visit our Knowledgebase and Support Sharepoint Site

    Friday, December 24, 2010 4:30 PM
  • We can ping by netbios name, thats no problem. It returns the correct ip adres

    We can indeed access the server shares bij FQDN, so you're correct about that.

    Tombstone the WINS records doesn't make any differents. Remember that we just turned WINS on after the problem occurs. So WINS turning of is also not the issue.

    The servers ip adres are indeed static. And I know for sure that there are no name conflicts.

    We have flushed the Servers dns cache and the local DNS cache. Both doesn't make any difference

    We have also set the server netbios name in the host file. even this doesn't make any differnce.

    So it doesn't look like a dns problem. When we access the share we are using the SMB protocol. I think the problem is some in there.

    Please let me know if you have any more ideas!

    Friday, December 24, 2010 5:47 PM
  • Hello,

    please post an unedited ipconfig /all from the problem server and the DC/DNS servers of the domain.


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Friday, December 24, 2010 10:27 PM
  • Hello,

     

    Can you telnet on port 445 to the server when the problem occurs from the TS? How about from another WS on the network thats not the TS?

    Do you have IDS firewall? Can you check your firewall logs?

    Have you checked both the TS and the File server logs for errors during the time this problem occurs?

     

    Miguel


    Miguel Fra / Falcon IT Services
    Computer & Network Support, Miami, FL
    Visit our Knowledgebase and Support Sharepoint Site

    Saturday, December 25, 2010 7:40 AM
  • Hi,

     

    Thanks for posting here.

     

    What’s the particular system prompt when access remote server via netbios name? please post the error ID and message here.

    Have you deployed any third party networking or security software on your servers ? like AntiVirus or AntiMalware software.

     

    If it works with access shared folder via FQDN and IP address , I suspect that name resolution is the cause of this issue, you may start troubleshooting with the mentions in the links below :

     

    How To Diagnose and Test TCP/IP or NetBIOS Network Connections in Windows 2000

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

     

    Troubleshooting networks without NetMon

    http://blogs.technet.com/b/askds/archive/2007/12/18/troubleshooting-networks-without-netmon.aspx

     

    Meanwhile, you could also trying restart TCP/IP settings with following the article below on this terminal server:

     

    How to reset Internet Protocol (TCP/IP)

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

     

    Thanks.

     

    Tiger Li


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Tiger Li Tuesday, December 28, 2010 3:09 AM
    • Unmarked as answer by Remco Hooijer Wednesday, December 29, 2010 11:16 AM
    Monday, December 27, 2010 8:09 AM
  • The system error that we are getting is:

    System error 53 has occurred.

    The network path was not found.

    We've have no third party security software installed.

    We are almost able to do anything except accessing the server by netbios name.

    I'll try the restart TCP/IP settings when no body is working on the server.

    Tuesday, December 28, 2010 7:56 AM
  • Hello,

    please provide the ipconfig /all output from the server and client so we can verify some settings.


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Tuesday, December 28, 2010 1:11 PM
  • ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : SERVER03
       Primary Dns Suffix  . . . . . . . : DOMAIN.local
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : DOMAIN.local

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Ada
    pter
       Physical Address. . . . . . . . . : 00-15-5D-05-3B-00
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::55c6:8814:62a7:ea4a%11(Preferred)
       IPv4 Address. . . . . . . . . . . : 172.16.0.26(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . : 172.16.0.5
       DHCPv6 IAID . . . . . . . . . . . : 234886493
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-91-22-42-00-15-5D-05-3B-00

       DNS Servers . . . . . . . . . . . : 172.16.0.20
       Primary WINS Server . . . . . . . : 172.16.0.20
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{5A9659E8-085A-4505-83C9-DDEACA8D579F}:

       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

    Tuesday, December 28, 2010 1:52 PM
  • Doesn't seem to do the trick. We will keep looking.
    Wednesday, December 29, 2010 11:16 AM
  • Even I am having the same issue.

    Thursday, December 30, 2010 3:05 PM
  • I've contacted Microsoft. There are some hot fixes availible.

     

    As just discussed please install the below hotfixes for your W2K8 R2 machine. You can download these via http://support.microsoft.com/kb/<number> where you use the below numbers.

    If you are downloading them using another OS you might need to select manually that you want the Windows 7/Windows 2008 R2 x64 version of this hotfix. If you download them from the target OS it will show the correct version to download.

    <number> - component to update
    2444558 for Mrxsmb10.sys
    982860 for Mrxsmb20.sys and Mrxsmb.sys
    2383928 for Win32k.sys
    2398906 - kernel files

    As some of the components were also updated via security updates it is possible that you receive the message that one or more hotfixes were not applicable to your system. Please let me know if that happens and for which hotfixes

    After installation of the hotfixes you need to reboot the system.

    Please let me know if you have any questions or issues,

    We have installed these hot fixes and are monitoring the system know.

    • Marked as answer by Remco Hooijer Thursday, December 30, 2010 3:09 PM
    Thursday, December 30, 2010 3:09 PM
  • Hi Remco,

    We are experiencing the exact same problems but only on the server itself. After restarting the TCP/ip Netbios Helper it starts working again. I've allready made an article elsewhere on the forum see http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/a49f71f7-5090-4129-9fd8-319c77b54e0a

    But I am very curious if the solutions work out as you say. We have disabled SMB 2 in the registry as this is required by the dental application we are using. So we've found the following http://support.microsoft.com/kb/2194664 as that might have been our problem.

    Hope to hear from you if the solution works.

    Wednesday, February 02, 2011 8:58 AM
  • Yep it worked for us. After the updates there were no errors while first is appeared every 1 or 2 days.

     

    Wednesday, February 02, 2011 9:04 AM