I had this issue today on a brand new RU7100. It worked yesterday. I did a SW upgrade on the unit. Did not try it again till today and the Wifi would not see any SSIDs for networks in my home. Based on responses to this thread, I did a UPRP. Un Plug Re Plug would be the technical term. I left it unplugged for 5 minutes. When it came back, it could see the SSIDs in my home. Amazing there is no simple fix for this in the network reset. I was getting very close to packing the thing back up and taking it back to where I got it. Hopefully, it wont do it again. Only about 2 hours wasted trying to figure what was wrong.
Well, now its a couple hours later and I just checked the TV and it is not working anymore. This is a real bummer because I have always liked my Samsung TVs. I guess I will try calling Samsung to see if they have a fix, but if its any kind of runaround, this puppy is going back. Really sad that this kind a quality issue has popped up with a company that I used to really like.
Update on Day 3: I called Samsung today and they tell me they have now fixed my problem.
To restate what I was seeing, my TV would lose its ability to connnect to Wifi after a few hours. I could not tell if it was after I turned it off and on or what. It would just lose it internect connection, and not show me any of the Wifi SSIDs in my home.
Samsung had me reset the TV, which was to hold the power button for 5 seconds, with the TV on. After doing that, i was able to see the SSIDs again. They had me reset and then add back my wifi connection. Well I have done that before, but did it again here. At that point, they could connect to my TV to see what was going on. They told me there was one other thing that could be done to resolve this issue. That was to turn off "Instant On". I asked what the impact of that would be on the TV and they said it would really not impact anything. So I said to turn it off. They had to do that as it is not a user accessible area of the configuration. So far so good. If you dont see a new post from me, that will have been the resolution for my issue.
... View more