Brother MFC-L2700DW Driver Installation fails: error code 0x000003eb  

This printer is connected to my network via Ethernet cable.
The Brother software (MFC-L2700DW-inst-C1-US.EXE) displays the error code (0x000003eb), but reports successful installation at the end of the process
It is listed among my printers in control panel, but when I try to print anything, Windows says the printer's driver is not installed.
Brother technical support agent suggested that I run the software with Antivirus and Windows Firewall disabled, which I did to no avail, receiving the exact same result as with those facilities enabled.

My network comprises three computers, all running Windows 7 Home Premium.

CPU4 is running 32-bit Windows, whereas the other two are 64-bit. I have not yet tried to install the Brother software on CPU4.

CPU7, my main workstation, is the one on which the Brother software installation has so far failed, even after following the scenario prescribed by rvcjew. Aside from repeating the setup for the Ethernet connection type, I also tried setting it up to use the USB connection. Again, the printer shows up in control panel, and its properties assert that it is successfully installed, online, and ready, but when I try to print anything I get an error message saying that the driver is not installed.

CPU8, which is used mainly as an entertainment center, has much less software installed than CPU4 or CPU7. The Brother software installed on CPU8 with no errors, and successfully printed a test page.

I have observed that the Brother software creates numerous log files, so my next step will be to compare the logs on CPU7 & CPU8, to see if I can find any clue as to how the two installations differed.

I will report back later today, after I wrangle my four canine companions to the vet clinic for their flu vaccine booster shots.

After trying rvcjew's tips, which did not fix anything, I did some further searching on th internet, and came across the following article: http://thebackroomtech.com/2010/08/2...printer-error/
The author presents several plausible scenarios, but none of them worked for me. I mention it here only because it might be of use to others.
Yesterday I spent another two hours on the phone with Brother tech support, which concluded with the agent's saying that the problem is not with Brother's software, but rather that something is wrong with my Windows installation.
Today I spent over four hours in a remote support session with Microsoft Level 1 and Level 2 agents.
The latter concluded, after dithering all around my computer with seemingly random stabs at the problem, by asking me to download a 4.5GB ISO image that he plans to use tomorrow to repair my Windows. So far, all he has managed to accomplish is to delete the two working printers I started the day with. The Brother MFC-L2700DW makes a very effective paperweight.

Since you successfully installed the printer software on CPU8, why not leave it connected to that computer, then share it to the other computers from there?

mrjimphelps said:

Since you successfully installed the printer software on CPU8, why not leave it connected to that computer, then share it to the other computers from there?

I tried that already, and CPU7 is unable to install the drivers.

rvcjew said:

Being multifunction it some times requires the drivers from the manufacture and not generic to do things like scan from it. Otherwise I would agree.

I have been working exclusively with the drivers downloaded from the Brother website.

Today I spent 12 hours online and on the telephone with a series of halfwitted drones who identify as Microsoft Level 2 Support Agents.
The concept of forensic analysis as a means of diagnosing and repairing product failure is evidently quite foreign to the Microsoft culture.
It is almost amusing to converse with an earnest young dude in India who speaks too rapidly in an accent that my poor brain must struggle to decipher, but the humor really escapes me. I am just too tired and exasperated by the whole experience.
After the usual round of bumbling & fumbling, the last of these clowns decide the thing to do would be to reinstall Windows.
The result so far is about what I have come to expect from these clueless losers: A Windows installation that is "not genuine" due to the disappearance of its product key; an Office Professional suite that is completely nonoperational; Internet Explorer Version 8 that fails to update to Version 11; miscellaneous other programs on my computer that are damaged or disabled; and all of this after a fresh install followed by MORE THAN 200 IMPORTANT UPDATES.
Is there perhaps something deeply rotten about a software product with more patches than a cubic mile of Raggedy Ann dolls?
As I sat there gazing at my monitor, I envisioned how it would be if Microsoft were in the business of manufacturing automobiles:
They would initiate an average of 13.2 product recalls per day, accounting for 73% of their payroll.
If your two- or three-year old sedan got a flat tire, the product service specialist would opine, "Well, sir, that left rear tire does seem to be flat on the bottom. Our technology is not yet to the point where we can effectively diagnose the situation. That feature has been announced for the MicrosoftWagen Version 27.12, scheduled for RTM in 2020."
Then he would send your vehicle to the crusher and build you a new one from scratch. This replacement would not be quite the same as the original, but it is well known that very few MicrosoftWagen owners ever actually use their windshield wipers, and also that a single headlamp is more than adequate for most purposes.
This will really be the vehicle owner's fault anyway, as he should have known better than to run over that thumbtack in such cavalier fashion.
Microsoft.Top.Men: how do you guys sleep at night, I wonder? You rake in billions of dollars from us every year, and you haven't got the decency to address your American customers in the good, old American language? And you just aren't competent enough to turn out products of more than mediocre quality in the first place?
It's been a bad day, and we have not even got to the point where we try once again to install my Brother MFC-L2700DW.
I have instructed my minions to begin preparing a litany of curses & imprecations to be called down upon both Brother and Microsoft in the near future.