10-05-2011 06:34 AM
I accept the fact that this problem does not affect everyone with a Homegroup ..YET...
The reason I say YET ..is that at the moment this problem is occurring with upgrades from 11 to 12 (downloaded upgrades generally)
Once Nis 2012 becomes available in the shops like mine , I suspect this WILL become a major problem....
We are in the "change over period" of the year in retail for Symantec products where the new version is drastically expensive for OEM or RETAIL versions but once the price drops substantially in the next month to six weeks , I suspect we will see a lot more people with Homegroups with this problem , although hopefully Symantec will have figured out why NIS2012 is doing this and introduced a fix in the first lot of updates that an NIS2012 runs after a fresh install.
All the best Brett :)
10-05-2011 06:49 AM
The fact that DLNA (Media Streaming) stops working when performing a standard upgrade installation will most probably cause some buzz too ;-)
Since remote desktop still work homegroup functionality is not critical for me but DNLA is
Probably a good idea to add the solution to this in the FAQ asap
10-05-2011 12:18 PM
Is your DNLA a part of a homegroup or workgroup process ?
In other words, do you need a Homegroup for Dnla streaming ?
All the best Brett :)
10-06-2011 08:09 AM
No DNLA works without homergroup - as far as i understand streaming of files with DNLA, Allshare etc. work without homegroup setup but moving files between computers is what i used homegroups for only work with remote desktop (tsclient) atm.
11-10-2011 07:42 AM
I found this thread when I upgraded both my desktop and laptop (both Win 7 - 64 Bit) to NIS 2012 and Homegroup suddenly stopped working. I was eventually able to get it working again by removing the homegroup, setting the trust levels to Full Trust within Norton for the other computer (on the Desktop set the Laptop to Full Trust and vice versa) and recreating the Homegroup from scratch as had been explained in earlier posts.
However I just noticed that it all stopped working again. Nothing has been changed other than a number of the monthly Microsoft patches were just installed, but I can't say for certain whether the Homegroup stopped working again after or before those were installed.
At this point I can't even get Homegroup to work on just the desktop itself. I have multiple accounts on the desktop computer for the different members of my family and we each share our music, pictures and some documents with each other using the Homegroup.
Now however even after removing the Homegroup, rebooting, recreating the Homegroup and then using each account to indicate which libraries to share, nothing shows up. It says the Homegroup is active, but when you go to any account and trying opening up the Homegroup in Explorer it simply says that No Other Users Have Joined and thus doesn't show any of the other accounts or their libraries.
This is really frustrating. As mentioned earlier Windows itself indicates that this is due to a network issue with the non-windows firewall. I can't think of what I can change in Norton to open up security between accounts on the same computer. Setting Full Trust for the laptop was one thing as that meant Norton allowed connections to be made between the computers, but now it seems like it won't even allow connections between accounts on the same computer. Any help is greatly appreciated.
12-06-2011 05:34 PM
I had the same problems: desktop was version 18 ( 2011) and had a homegroup started. Laptop was brought in and NIS version 19 (2012) installed. then homegroup tried and failed. both computers are identically named, visible on Norton map and trusted settings on both. did not work.
Then followed these instructions provided by bret928s2 and they worked. Perhaps can now turn on share control and set to "shared" and they may still keep working.
Thanks Bret928s2 for solving and posting the solution.
And a thumbs down to norton for making this so hard, I wasted a whole afternoon on this.
12-07-2011 01:09 PM - edited 12-07-2011 01:10 PM
Same problem here. I did all that Brett said, but also had to reboot my router to get it to work. It's only been a few minutes so hopefully problem doesn't re-occur.
12-11-2011 07:31 AM
Problem has returned. I must admit I am not amused. I uninstalled my Webroot because it had the same problem and they weren't resolving it. I chose Symantec AT A HIGHER PRICE because I can't be bothered by this stuff and expected more from a compnay like Symantec.
I have suffered with this for weeks because everyone deserves a chance to identify and repair a problem but this is getting ridiculous. I may need to check out other alternatives real soon.