, Thanks for posting here. Incorrect NetBIOS browsing is the issue if we can browse NAS via FQDN . Please first verify the master browser host in this network with following what Ace mentioned in the old thread below, thread which discussed a similar scenario like yours. Links of good articles that discussed on how to troubleshoot such issue could also be found form this thread: http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/a986e70d-39b0-46a9-8ce0-7f015ddd8532/ Regards, Tiger Li TechNet Subscriber Support in forum If you have any feedback on our support, please contact tnmff@microsoft.com. 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.

, Thanks for posting here. Incorrect NetBIOS browsing is the issue if we can browse NAS via FQDN . Please first verify the master browser host in this network with following what Ace mentioned in the old thread below, thread which discussed a similar scenario like yours. Links of good articles that discussed on how to troubleshoot such issue could also be found form this thread: http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/a986e70d-39b0-46a9-8ce0-7f015ddd8532/ Regards, Tiger Li TechNet Subscriber Support in forum If you have any feedback on our support, please contact tnmff@microsoft.com. 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. That post all relates to Wk3 servers. My issue is with 2k8 R2 servers which neither support NETDIAG nor any of the other 2k3 support tools. However since yesterday, I rebooted the bad server and it now has a full list of devices on its network segment which is strange because network discovery is turned off and the Computer Browser service is disabled (which I think is the default for 2k8 R2). What else can be populating the Network Folder?Hibs Ya Bass!

, Thanks for posting here. Incorrect NetBIOS browsing is the issue if we can browse NAS via FQDN . Please first verify the master browser host in this network with following what Ace mentioned in the old thread below, thread which discussed a similar scenario like yours. Links of good articles that discussed on how to troubleshoot such issue could also be found form this thread: http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/a986e70d-39b0-46a9-8ce0-7f015ddd8532/ Regards, Tiger Li TechNet Subscriber Support in forum If you have any feedback on our support, please contact tnmff@microsoft.com. 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. That post all relates to Wk3 servers. My issue is with 2k8 R2 servers which neither support NETDIAG nor any of the other 2k3 support tools. However since yesterday, I rebooted the bad server and it now has a full list of devices on its network segment which is strange because network discovery is turned off and the Computer Browser service is disabled (which I think is the default for 2k8 R2). What else can be populating the Network Folder?Hibs Ya Bass!

Hi, Thanks for posting here. These utilities can still work on Windows Server 2008 host with no problem , we can get it form supports tools kits of pervious versions: NetBIOS browsing across subnets may fail after upgrading to Windows Server 2008 http://blogs.technet.com/b/networking/archive/2008/07/25/netbios-browsing-across-subnets-may-fail-after-upgrading-to-windows-server-2008.aspx And the mechanism on Windows Server 2008 or other above versions is same as what it did on previous versions http://technet.microsoft.com/en-us/library/cc737661(WS.10).aspx 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.

Hi, Thanks for posting here. These utilities can still work on Windows Server 2008 host with no problem , we can get it form supports tools kits of pervious versions: NetBIOS browsing across subnets may fail after upgrading to Windows Server 2008 http://blogs.technet.com/b/networking/archive/2008/07/25/netbios-browsing-across-subnets-may-fail-after-upgrading-to-windows-server-2008.aspx And the mechanism on Windows Server 2008 or other above versions is same as what it did on previous versions http://technet.microsoft.com/en-us/library/cc737661(WS.10).aspx 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.

I have two Wk8 R2 servers configured pretty much identically (the NICs are certainly identical). On one machine (lets call it the good server) I can browse to a NAS device on our network using \\devicename\share on the other server (lets call it the bad server) I need to add the DNS suffix like this \\devicename.domain.com\share. If I enter only \\devicename\share i get an "network path not found" error. Both servers are member servers on the domain and have the same primary DNS suffix. On the good server I see the NAS device in the Network Folder in Explorer; on the bad server the NAS device does not show up at all in the Network Folder Strange, no? If disable Netbios on the good server I can still browse to the NAS device using \\devicename\share but on the bad server I get a new error saying "a device attached to the system is not functioning". I've flushed my DNS cache on both machines also. I can ping devicename on both servers without the DNS suffix successfully. Network discovery is turned OFF on both servers. Any ideas what is causing this? Hibs Ya Bass!

, Thanks for posting here. Incorrect NetBIOS browsing is the issue if we can browse NAS via FQDN . Please first verify the master browser host in this network with following what Ace mentioned in the old thread below, thread which discussed a similar scenario like yours. Links of good articles that discussed on how to troubleshoot such issue could also be found form this thread: http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/a986e70d-39b0-46a9-8ce0-7f015ddd8532/ Regards, Tiger Li TechNet Subscriber Support in forum If you have any feedback on our support, please contact tnmff@microsoft.com. 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. That post all relates to Wk3 servers. My issue is with 2k8 R2 servers which neither support NETDIAG nor any of the other 2k3 support tools. However since yesterday, I rebooted the bad server and it now has a full list of devices on its network segment which is strange because network discovery is turned off and the Computer Browser service is disabled (which I think is the default for 2k8 R2). What else can be populating the Network Folder?Hibs Ya Bass!

, Thanks for posting here. Incorrect NetBIOS browsing is the issue if we can browse NAS via FQDN . Please first verify the master browser host in this network with following what Ace mentioned in the old thread below, thread which discussed a similar scenario like yours. Links of good articles that discussed on how to troubleshoot such issue could also be found form this thread: http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/a986e70d-39b0-46a9-8ce0-7f015ddd8532/ Regards, Tiger Li TechNet Subscriber Support in forum If you have any feedback on our support, please contact tnmff@microsoft.com. 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.

Hi, Thanks for posting here. These utilities can still work on Windows Server 2008 host with no problem , we can get it form supports tools kits of pervious versions: NetBIOS browsing across subnets may fail after upgrading to Windows Server 2008 http://blogs.technet.com/b/networking/archive/2008/07/25/netbios-browsing-across-subnets-may-fail-after-upgrading-to-windows-server-2008.aspx And the mechanism on Windows Server 2008 or other above versions is same as what it did on previous versions http://technet.microsoft.com/en-us/library/cc737661(WS.10).aspx 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.