When I reboot my PC or turn it off and on it takes hours for my Network Shares to work again. I can access youtube and I can access my wd live from my PC bit when I press on the Network Shares icon nothing happens. After several hours it will start working. I have tried unplugging the wd live for hours, resetting with paper clip and nothing works. Any ideas on what’s wrong?
That generally indicates a problem with the Master Browser on your network. It can be VERY difficult to troubleshoot, but it’s possible.
Generally, you need to find out which system is acting as Master Browser by going to one of the PCs and opening a CMD window and enter
net view
It will give a list of visible devices that are advertised on the net.
Then you need to do
nbtstat -a (name)
where name is each of the names from the first command.
ONE of them MUST have the name __MSBROWSE__ in its list.
That machine is the master browser, and most likely, the problem is there.
TonyPh12345 wrote:
That generally indicates a problem with the Master Browser on your network. It can be VERY difficult to troubleshoot, but it’s possible.
Generally, you need to find out which system is acting as Master Browser by going to one of the PCs and opening a CMD window and enter
net view
It will give a list of visible devices that are advertised on the net.
Then you need to do
nbtstat -a (name)
where name is each of the names from the first command.
ONE of them MUST have the name __MSBROWSE__ in its list.
That machine is the master browser, and most likely, the problem is there.
After I do this what do I look for? I am on Windows 7. This is the only device on my network that does this. The other ones work within 2 minutes.
-
When the LIVE comes on, it immediately sends a broadcast out to the entire network to locate the master browser. It continues to do this repeatedly until it gets a response.
-
When it receives a response, it asks the master browser for a list of all servers on the network.
-
After it receives that list, it goes to every server and gets a list of shared folders.
If you’re not seeing your server in the list, then any ONE of those is failing.
So, the answer to your question is, “It Depends on what you find.”
TonyPh12345 wrote:
- When the LIVE comes on, it immediately sends a broadcast out to the entire network to locate the master browser. It continues to do this repeatedly until it gets a response.
- When it receives a response, it asks the master browser for a list of all servers on the network.
- After it receives that list, it goes to every server and gets a list of shared folders.
If you’re not seeing your server in the list, then any ONE of those is failing.
So, the answer to your question is, “It Depends on what you find.”
I did what you said and here are the results:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Chuckd3>net view
Server Name Remark
\CHUCKD3-PC
\WDTVLIVE WDTV LIVE
The command completed successfully.
C:\Users\Chuckd3>nbtstat -a chuckd3-pc
Local Area Connection:
Node IpAddress: [192.168.1.64] Scope Id:
NetBIOS Remote Machine Name Table
Name Type Status
---------------------------------------------
CHUCKD3-PC <00> UNIQUE Registered
WORKGROUP <00> GROUP Registered
CHUCKD3-PC <20> UNIQUE Registered
WORKGROUP <1E> GROUP Registered
WORKGROUP <1D> UNIQUE Registered
…__MSBROWSE__.<01> GROUP Registered
MAC Address = 00-1A-92-0A-FF-2B
Wireless Network Connection:
Node IpAddress: [192.168.1.68] Scope Id:
NetBIOS Remote Machine Name Table
Name Type Status
---------------------------------------------
CHUCKD3-PC <00> UNIQUE Registered
WORKGROUP <00> GROUP Registered
CHUCKD3-PC <20> UNIQUE Registered
WORKGROUP <1E> GROUP Registered
MAC Address = 00-C0-A8-D1-F6-79
Wireless Network Connection 2:
Node IpAddress: [0.0.0.0] Scope Id:
Host not found.
C:\Users\Chuckd3>nbtstat -a wdtvlive
Local Area Connection:
Node IpAddress: [192.168.1.64] Scope Id:
NetBIOS Remote Machine Name Table
Name Type Status
---------------------------------------------
WDTVLIVE <00> UNIQUE Registered
WDTVLIVE <03> UNIQUE Registered
WDTVLIVE <20> UNIQUE Registered
WORKGROUP <1E> GROUP Registered
WORKGROUP <00> GROUP Registered
MAC Address = 00-00-00-00-00-00
Wireless Network Connection:
Node IpAddress: [192.168.1.68] Scope Id:
NetBIOS Remote Machine Name Table
Name Type Status
---------------------------------------------
WDTVLIVE <00> UNIQUE Registered
WDTVLIVE <03> UNIQUE Registered
WDTVLIVE <20> UNIQUE Registered
WORKGROUP <1E> GROUP Registered
WORKGROUP <00> GROUP Registered
MAC Address = 00-00-00-00-00-00
Wireless Network Connection 2:
Node IpAddress: [0.0.0.0] Scope Id:
Host not found.
Registered: Friday
0
Re: Can’t find WD Live Plus after PC reboot[ New ]
Options
- Edit Reply
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Accept as Solution
- Email to a Friend
- Report Inappropriate Content
yesterday PM
TonyPh12345 wrote:
- When the LIVE comes on, it immediately sends a broadcast out to the entire network to locate the master browser. It continues to do this repeatedly until it gets a response.
- When it receives a response, it asks the master browser for a list of all servers on the network.
- After it receives that list, it goes to every server and gets a list of shared folders.
If you’re not seeing your server in the list, then any ONE of those is failing.
So, the answer to your question is, “It Depends on what you find.”
I did what you said and here are the results:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Chuckd3>net view
Server Name Remark
-------------------------------------------------------------------------------
\CHUCKD3-PC
\WDTVLIVE WDTV LIVE
The command completed successfully.
C:\Users\Chuckd3>nbtstat -a chuckd3-pc
Local Area Connection:
Node IpAddress: [192.168.1.64] Scope Id:
NetBIOS Remote Machine Name Table
Name Type Status
---------------------------------------------
CHUCKD3-PC <00> UNIQUE Registered
WORKGROUP <00> GROUP Registered
CHUCKD3-PC <20> UNIQUE Registered
WORKGROUP <1E> GROUP Registered
WORKGROUP <1D> UNIQUE Registered
…__MSBROWSE__.<01> GROUP Registered
MAC Address = 00-1A-92-0A-FF-2B
Wireless Network Connection:
Node IpAddress: [192.168.1.68] Scope Id:
NetBIOS Remote Machine Name Table
Name Type Status
---------------------------------------------
CHUCKD3-PC <00> UNIQUE Registered
WORKGROUP <00> GROUP Registered
CHUCKD3-PC <20> UNIQUE Registered
WORKGROUP <1E> GROUP Registered
MAC Address = 00-C0-A8-D1-F6-79
Wireless Network Connection 2:
Node IpAddress: [0.0.0.0] Scope Id:
Host not found.
C:\Users\Chuckd3>nbtstat -a wdtvlive
Local Area Connection:
Node IpAddress: [192.168.1.64] Scope Id:
NetBIOS Remote Machine Name Table
Name Type Status
---------------------------------------------
WDTVLIVE <00> UNIQUE Registered
WDTVLIVE <03> UNIQUE Registered
WDTVLIVE <20> UNIQUE Registered
WORKGROUP <1E> GROUP Registered
WORKGROUP <00> GROUP Registered
MAC Address = 00-00-00-00-00-00
Wireless Network Connection:
Node IpAddress: [192.168.1.68] Scope Id:
NetBIOS Remote Machine Name Table
Name Type Status
---------------------------------------------
WDTVLIVE <00> UNIQUE Registered
WDTVLIVE <03> UNIQUE Registered
WDTVLIVE <20> UNIQUE Registered
WORKGROUP <1E> GROUP Registered
WORKGROUP <00> GROUP Registered
MAC Address = 00-00-00-00-00-00
Wireless Network Connection 2:
Node IpAddress: [0.0.0.0] Scope Id:
Host not found.
Any particular reason you have THREE networks set up on your PC?
Also, provide the output of
ipconfig /all
TonyPh12345 wrote:
Any particular reason you have THREE networks set up on your PC?
Also, provide the output of
ipconfig /all
I didn’t know I had 3. It only shows 1 in my network explore. Here is the ipconfig:
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter Local Area Connection* 11:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter 6TO4 Adapter:
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 . . . . : Yes
Tunnel adapter Reusable Microsoft 6To4 Adapter:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 13:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #5
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 12:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #4
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 16:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #8
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 14:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #6
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 15:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #7
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 19:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #11
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 17:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #9
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 18:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #10
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 27:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #19
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 20:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #12
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 21:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #13
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 32:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #24
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 22:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #14
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 23:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #15
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 24:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #16
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 25:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #17
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 26:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #18
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 28:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #20
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 29:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #21
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 36:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #28
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 30:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #22
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 31:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #23
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 33:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #25
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 34:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #26
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 35:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #27
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 40:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #32
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 37:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #29
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 38:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #30
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 39:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #31
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{BE49DD38-C298-4B15-915E-D7166BA65718}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
C:\Users\Chuckd3>
Alright, here’s what you need to try.
Reboot your PC into SAFE MODE.
Go into DEVICE MANAGER.
Expand “NETWORK ADAPTERS” section.
You will likely see a LOT of entries.
Click EVERY ENTRY, and hit the DELETE key (or, RIGHT CLICK and select UNINSTALL).
** NOTE: Some will NOT uninstall. They are WAN MiniPort with several different names (mine has 8 that will not uninstall, but that’s OK.)
Reboot back into “Normal” mode.
When you REBOOT, your DEVICE DRIVERs will be Re-Installed for your Network Card.
You will now need to go make sure the configuration for IP is correct, and also make sure that the profile is set to allow Sharing, turn off Password Protected Sharing, etc, just like you checked before.
They may get set back to “Defaults,” which turns ON Password Protected Sharing and turns OFF Network Discovery.
TonyPh12345 wrote:
Alright, here’s what you need to try.
Reboot your PC into SAFE MODE.
Go into DEVICE MANAGER.
Expand “NETWORK ADAPTERS” section.
You will likely see a LOT of entries.
Click EVERY ENTRY, and hit the DELETE key (or, RIGHT CLICK and select UNINSTALL).
** NOTE: Some will NOT uninstall. They are WAN MiniPort with several different names (mine has 8 that will not uninstall, but that’s OK.)
Reboot back into “Normal” mode.
When you REBOOT, your DEVICE DRIVERs will be Re-Installed for your Network Card.
You will now need to go make sure the configuration for IP is correct, and also make sure that the profile is set to allow Sharing, turn off Password Protected Sharing, etc, just like you checked before.
They may get set back to “Defaults,” which turns ON Password Protected Sharing and turns OFF Network Discovery.
This seems to have fixed the wd live tv plus problem but now I have no wireless capability. Please help!
I got the wireless network to work but the wd live is still doingthe same thing. It loses network shares after pc reboot.
Why are you using both WIRED and WIRELESS?
TonyPh12345 wrote:
Why are you using both WIRED and WIRELESS?
I use wired for the wd live plus and I use wireless for my wife’s laptop.
That’s out of my reach. I don’t have any experience doing Windows Networking when Win7 is acting as a bridge between networks.
Sorry…
The problem with doing multiple interfaces on the same subnet is that the PC really has no idea which interface to send a packet out to.
Anyone else Have any ideas?
TonyPh12345 wrote:
That’s out of my reach. I don’t have any experience doing Windows Networking when Win7 is acting as a bridge between networks.
Sorry…
The problem with doing multiple interfaces on the same subnet is that the PC really has no idea which interface to send a packet out to.
Thanks for the help. This was the problem. Running a wired and wireless network on the same Windows 7 machine confuses the hell out of the WD TV LIVE PLUS. I deleted the wireless network and the live plus works perfectly. Thanks again!
I did find a solution to my similar experience but there were some differences in my setup…
-WDTV Live (not Plus)
-nbtstat told me which PC was MSBROWSE
-the MSBROWSE PC is a WinXP Pro machine with one LAN card and one incoming VPN connection which was not active
-using nbtstat: MSBROWSE shows up twice: once in the LAN list and once in the RAS (Dial In) (incoming VPN) list
-I deleted the incoming VPN connection so MSBROWSE shows up in only one list…
_ voila _, problem solved, WDTV can now see the network shares on both PCs on the LAN.
Similar to Alvind4, multiple interfaces on the MSBROWSE PC somehow gives trouble for WDTV seeing network shares.
Thanks to Tony and the other posters.
More useful info about this, how to keep MSBROWSE from running on a given (multihomed) PC:
from: http://support.microsoft.com/?id=191611
To prevent multihomed Microsoft Windows NT servers from becoming browser servers, follow these steps:
- Click Start , point to Settings , click Control Panel , and then double-click Services.
- Click Computer Browser , click Properties , and then click Manual.
- Click OK , click Close , and then restart the computer.
