After I made the FDRP automoatic, I was then able to see other computers but still could not access them. That's when I get the Acess Denied messages. So, that step did so something for me.
The net is littered with this same problem so I'm convinced its a Microsoft problem even if it does work for some folks.
Like Beerlord, I was having exactly the same issues even after doing all of the recommended things that are supposed to work and clearly do work for some, but not all. That's why I went to assigned IP's and corresponding hosts files (see my post from May 10). It may not be the ideal solution but it has solved the problem for me. The workgroup now works either with password-protected sharing or without, as you prefer. I once heard a very famous person in my field say, "Given a choice between finesse and brute force, always choose brute force." Kind of applies here, I think.
I didn't even think about assigning IP's. I had already done that years ago but I guess it's possible that my static IP could have changed to something else. I'll check when I'm back in town and see if that's it.
I don't think an Windows update would change a static IP and I know my router hasn't changed so I'm already scratching my head but this is a good idea that I've yet to see in all the searching I've done.
It's a damn shame that you have to do this to get this working properly.
Ha, I remoted in and it appears that at least one of my systems has nothing at all in the host file but I will definitely try this out when I am back home.
I'm having some good laughs about all of this now.
I got my son to do this for me while I'm out of town and it worked! Wow, the thought of the host file never, ever even entered my mind.
pbcopter, thanks for the great fix and thanks Access Denied for all the time and help you put into this. I'm going to mark this solved with all the thanks and gratitude in the world. Beer's are on me!
Quote
