I have been a computer consultant for decades ans I have NEVER heard this simple, singular issue addressed with other than MS pros cattily pretending to explain it away in words that mean nothing to the rest of us.
I have had to radically emasculate several networks of security issues in order to get beyond this absurd barrier to the transfer of files over even the most simplistic of networks The pompous and non-assistive pretentious BS that MS experts vomit all over the web only adds insult to injury.
I have two computers, a desktop and a notebook. Both are running Win 7 Home Premium. They both can see and use the files on the other but I CANNOT COPY OR MOVE ANY FILES FROM ONE TO THE ANOTHER.
I would be delighted to have someone tell me how I might accomplish that/ they are even empowered to include in their explanation what a complete idiot I am not to have known how to do that before now.
Whip me. Denigrate me. Shame me before the world for my inability to understand how I might accomplish a task that should be a basic function of any network connectivity, but stop using such cryptic and unintelligible terms to describe the indescribable methodology as to pretend "the rest of us" might be able to grasp and implement them. In case you "experts" haven't noticed, NOBODY GETS IT!!
You're a computer consultant? I have my doubts on that, I'm certrainly not. I wouldn't class myself as an expert or even a pro, but I have been transferring files between computers using the network for years and know how to setup permissions so anyone from specific people to complete strangers can read my files and sometimes write files to my computer.
But since you're having a very good rant, I am disinclined to acquiesce to your request.
Thanks for the offering but Homegroups do nothing for me. Nor do such supercilious responses as have been tossed out here. Computer Consultants have real clients in the the real world for whom homegroups are not adequate on a lot of levels. I am well aware of assigning permissions and taking ownership but, while those might work in the loosened security of a "homegroup", the level of difficulty goes up significantly when one needs to configure a workgroup or a domain.
"I am disinclined to acquiesce to your request."
I can't imagine how anyone could be so condescending while simultaneously offering nothing to credential his pretense of expertise. Even using their denigration of others to hide their ignorance of how to resolve the issue. I'm impressed.
I would welcome someone with a real answer but I find misplaced and merit-less disparagement a poor substitute for actual, usable information. I know there are common issues that often create problems re the interfacing of the various computers on any "network", no matter how small. One that frequently comes up occurs when some systems the client buys on their own are "Home" versions of Windows. Another common problem that complicates things are differing OS's, e.g. XP vs Win 7, firewall configurations and Anti-virus settings are common causes. All of these adds degrees of difficulty to meshing systems, but it's more than that with Microsoft.
Mind you, I did not mean to imply that I was unable to get through this particular flaming hoop on the scores of occasions when it was thrown in my path. Had I not been able to do so, I would not have had the same clients for 20+ years. What I was "ranting" (?) about is that MS has rarely offered a fix for this too routine problem, and it seems to occur whenever even the slightest of variables shift on many different networks
I am not only happy, I am eager, to admit ignorance on this subject. I think I did as much just by posting my question. When the "answers" I receive, however, not only have no application in my circumstances, or are non-existent, and all that's left is derogatory comments, that serve no one except perhaps, the chest-puffers who post such things.
I am keenly aware that this sniping at others is a far too frequent occurrence on a vast number of forums, but it annoys me every time that it does.
BTW, here's just one example from hundreds all over the web, from another "expert" who finds that to be true as well. Like me, Leo has enough experience in the field that he knows he doesn't know everything, or that anyone could. He doesn't pretend that the fact that he has been able to wrestle it to the ground and make it work, qualifies him as all-knowing because he once connected two computers on a "homegroup". He does know, however, from the hundreds of circumstances where he was able to get past MS's severe limitations, that MS has severe limitaions and there is no pat, one size fits all, answer........
Windows networking is difficult, to put it mildly.
I'm still waiting for a meaningful, on-point response, but I fear it will not be forthcoming. I say that largely because the simple fact is that MS abjectly fails its user base in providing work-arounds or tech papers that actually address the problems that come up all the time.
I have developed work-arounds for this problem on the too-many occasions when it has come up, but they are too-specific bandages that only help one or two users at a time. MS owes its users a better system, or at least some substantive support on this ages-old one.
Wow. What a fun rant to read! I have your back Cuidate. No one can know everything about tech, and especially not when it dosn't act logically. I had this issue when attempting to upload files via "explorer mode" to a sharepoint page. I restarted the WebClient service. Then closed out and reopened everything. Problem solved. Just a note too. The WebClient service showed as started and no errors so it's best to restart it anyways. It just takes a second.
As a former COBOL Programmer, then Chief of Data Processing who retired then went to work for a local University's Computer Science Department as a Windows Server Systems Administrator, and now retired again, for over a year... I have used this web site to help resolve issues I've encountered for many, many years. And I thank you for sharing your expertise.
I must state that I was also very offended by the narrow mindedness and just plain snobbery displayed by ss202sl and pauls3743. It was immature, unprofessional and not worth the time it took me to read it.
I do THANK cuidate for his exceptional, well composed and in my opinion, brilliant response. This person (cuidate) has lived a few years and had a few experiences that others should learn from.
I looked at the link he provided and found that it answered the problem I was experiencing. I have been out of the field for just over a year and find that my knowledge is already 'stale-dated' and rusty as compared to what I used to be able to do. A consultant deals with a myriad of problems that I didn't have to deal with and I sympathize with this situation and basically berate the 'mental midgets' who consider themselves 'legends in their own minds' as childish and ignorant.
cuidate - that was a great response.
What people need to understand (ss202sl/pauls3743) is that most if not all error/informational messages generated are *catchalls* which do not necessarily pinpoint the cause.
The mistake people make is thinking that it is the same cause for every occasion of the symptom (message).
I am sure ss202sl/pauls3743 have done some good troubleshooting in their time but they need to have some humility and some respect (which will come with age hopefully) and if they deign to revisit this thread they should also gain some wisdom.