However, I thought maybe I should bring more attention to it than sitting at the end of a thread, falling down the line.
The fix in the other thread consisted of simply adding a Static IP to your WDTV unit. It worked for some, but unfortunately it didnt work everyone, including me. So after reading many posts around the net I found a fix that worked for me and may work for others. I found it on this very forum titled Re: Network Shares Drop
Basically, all youâre doing is adding on to your Workgroup name from WORKGROUP to WORKGROUP-PC
You can add anything but you do need to add the âdashâ (-) and something else. Give it a try and see if that works for you to get connected to your Network Shares again.
*I did NOT however have to change the name in my WDTV unit unlike the poster said in the last link.My WDTV settings still say WORKGROUP
Â
I do not know how it is working, but it is and thatâs all I care about !
One thing I did notice was my HP Color LaserJet 3000 was showing offline (hooked up via RG45) when it was fine before. So I checked itâs IP in my router settings and saw that it had changed. So I simply changed it to that IP in the Printer Properties/Ports and all is good. You may have to do this if you have networked printers or other devices.
I am not running any other software. I simply stream from my PC to the WDTV Live Plus via network cable with my router (EA3500) being the âmiddle manâ
I have still not run into any issues using this âfixâ. Fact my kids are streaming a movie as I type this.
No, what Iâm saying is that WORKGROUP works for me as well as any other random name. And Iâm suspecting that your approach which the dash simply worked because you switched to a different workgroup.
Iâm posting here because I had network problems that I solved without your solution, simply because Fix #2 isnât one. Adding a dash to the workgroup is not necessary. It rather worked for you because you changed the workgroup on several devices which probably made your router re-recognize them. My router was confused by all the WDTVs popping up on my network and once I deleted all network info and set it to assign the same IP to each device on every connect, it worked.
I ONLY changed WORKGROUP to WORKGROUP-PCÂ on my computer I share from. I did NOT change ANYTHING ELSE on any other device.
Also. If this fix was not for you, then why did you post ? If you didnt need to do anything then why bother saying you didnt need to do my fix ? If another fix worked, then good for you. Just because my fix wasnt used doesnt mean it didnt work for me or for anyone else.
This fix was for those (like me) who tried static IP and it didnt work. If that one worked for you then good. No need to come in here and say this one didnt work if you didnt even need to or even try it. Itâs not like this was an opinion poll âŠ
WDTV619 wrote:
I ONLY changed WORKGROUP to WORKGROUP-PC on my computer I share from. I did NOT change ANYTHING ELSE on any other device.
Which makes this even more unlikely to be the reason of fixing the problem. Iâd be interested to see if anyone here chimes in claiming it also worked for them.
Iâm with Techflaws on this one. If the name of the workgroup is âWORKGROUPâ changing the workgroup on the WD to âWORKGROUP-PCâ should actually prevent the WD from accessing the workgroup named âWORKGROUPâ itâs interesting that this works for you
I also never claimed WHY it worked but that it just did.
One day my network shares were no longer available. I tried everything from resetting WD to giving the WD a static IP and made changes in my router. Nothing worked. I read another thread on here about changing WORKGROUP name on the computer that the shares are on and it worked.
Again. I made NO changes to router or WD when this change was made. I had set those devices back to what they originally were before changing WORKGROUP.
I get upset when my words are misunderstood and replies end up confusing others who may want to know what I did.
Many people do not read full threads and go straight to the last post and if they read what you guys thought you read, then it can create problems.
As far as my solution and how it should not work, again, I do not know how or why, but it just does.
I have been using this âfixâ for nearly a week now and have yet to have any issues getting to my network shares on my PC.
All I can say is try it. No harm in that, is there ? If it works. Great. If I doesnât, then change it back. I did the same when looking at othersâ so called solutions/fixes.
So far this thread is filled with âthis should not and can not workâ and yet here I am saying it does because I am using the âfixâ !
Donât take offense but Iâm with Techflaws on thisâŠIâll bet you could have changed the workgroup name to anything (except WORKGROUP) and it would have worked. The dash had nothing magical about it. The act of changing the name âflushedâ and re-initialized something that made things be recognized again. Iâll bet if you change it back to WORKGROUP on your PC itâll still work.
I can understand the dash issue. Fact I probably should have not said it needed a dash.
I also think I will try and put it back to just WORKGROUP (been wanting to actually try that) and see if things stay the same (network shares available)
My so-called anger about the replies was because I was sort of being told this can not work and should not work, when I was sitting here experiencing it work ! I didnât know how or why, I just know it was working and I was able to stream my stuff again after loosing network shares. I was also a little upset when people werenât reading my posts correctly and that may have confused users. I stated many times that I only change the name on my PC and it was being relayed that I changed the name on all sorts of devices.
I just figured I would share this âfixâ, be it temporary or whatever so users could stream on their network once again until WD can figure out how to put a fix.
It just didnât make sense unless of course being in the same workgroup wasnât necessary anymore. So I started up the LIVE without being connected to the network and set itâs workgroup to WORKGROUP while all other devices on my network stayed on STRAYLIGHT. And what can I say, despite being in the different workgroups the LIVE could connect to my NAS shares immediately.
