LiveTV Hub - Missing Files

Sorry Guys, I have read other posts, but none seem to have the same issues as me.

I have a problem with my HUB.  I have a Seagate go-home network drive on my network.  I can see the drive on my network and add files to it, no issue.  I can see my hub on my network; I can also add files to it, no issue.

When it comes to playing the files on the drive, I can see them as a media server, but the HUB says that there is no media in the file.  My drive does not show up as a network share.  I have all permissions set to everyone and full permissions

Any ideas?

Make sure the WORKGROUP names match.

Make sure the “Master Browser” is functional on your network.

Workgroups match…Not sure what “Master Browser” is!


This is how to find possible problems with the Master Browser on your network, which will affect when and what servers appear on your WDTV Network Shares.

On one of your PCs, open up a “Command” window.

(In Win Vista and Win7, click the Orb, and in the search box, type CMD. An icon will appear above the box that says cmd.exe. Click it, and a Command window will open.)

(In WinXP, Click START, then RUN…, and in the box, type CMD. A Command Window will open.)

In the command window, enter the command “net view,” like this:

C:\Users\Tony>net view
Server Name Remark

\BIGNAS1 Big Freakin’ NAS Server 1
The command completed successfully.

In my example, there are four active devices that Windows has discovered.

Now, for EACH of those, issue the command “nbtstat -a (name)” for example:

C:\Users\Tony>nbtstat -a bignas1

Local Area Connection:
Node IpAddress: [] Scope Id: []

NetBIOS Remote Machine Name Table

Name Type Status

BIGNAS1 <00> UNIQUE Registered
BIGNAS1 <03> UNIQUE Registered
BIGNAS1 <20> UNIQUE Registered
…__MSBROWSE__.<01> GROUP Registered
WORKGROUP <00> GROUP Registered

So, we got lucky here, the FIRST system, BIGNAS1, indicates that it is the master browser, since it lists the name …__MSBROWSE__.

You need to find out WHICH system is your master browser. If none of these steps work as described, then the issue is likely on your PC itself, and that will require substantial additional troubleshooting.