Windown

I just recently wrestled with my little smb setup here to tighten the grip on who might be accessing my share. My intention is to simply share my own smb share I have running in VmWare with my XP host. My XP host is logged into a domain server not to the local machine. The Linux I have installed in VmWare is FC5 running from USB drive and using the NAT networking setting. My company has blocked DHCP to only those machines authenticated with by the domain server. I originally used the KDE Control Center to setup my smb sharing homes.

I somehow got "voluntwisted" into fixing a coworkers Sony laptop. Well okay maybe it was my own doing. I love to recover data from presumed dead hard drives. His had been dead and powered up for so long, I presumed it was toast like so many laptop drives usually are. Much to my surprise it was mountable using an old Live Knoppix disk. So I simply plugged in my USB drive and with MC I did mass copies to it. Since it was a bad disk it did take about 8 hours to move about 2GB of data (music and pictures).

So next the coworker produced a replacement drive. One dilemma though... he didn't have his recovery CD's since he just moved here and having a tough time finding anything really. So I thought I'd try using my home Dell PC. OEM CD's tend to require you to use their own hardware to do the installs so my XP Home disk would have to be installed using my PC. Ordered a laptop to IDE converter from RadioShack online; as they don't carry them in the stores. All is well. Got that installed and next I plopped it back in the Sony. No go. CRAP! It's an AMD. I used an Intel PC not to mention possible disk parameter differences. Back to the drawing board.

Damn those company computer guys!

As usual with most tech support I deal with they tend to have you rehash much of what you already have done; assuming you are technically savvy yourself. It infuriates me further to have to jump though their hoops to get any cooperation. The first reply this morning from IT is to "power down the printer and retry the same documents and report what the error logs say". Well the only thing that proved was that this issue did not produce those error logs. Those errors were probably legit.

So on my own I attempt to print to file and use DOS to copy the file to the device. Here I get "The system cannot write to the specified device." This sounds like a write permissions problem. Just before I even got the email off to report this to them, I got a message back stating they changed the spool settings and reboot our server.

I've been able to print to our Lanier multi function printer all morning. This afternoon, my coworker starts having trouble printing to any printer on the network. He can print Word documents fine but nothing graphical. I tested and can't print graphics either now. I keep getting a balloon pop-up saying it failed consistently until it is removed from the spool.

Well with my history in dealing with IT issues in our corporate world IT team hasn't been pleasant recently. So I decided not to dig too deep and called, left a message with them. I mentioned the error logs on the printer show different errors stating the stapler failed or the hole punch failed. Since this is a problem on at least three Windows boxes and two network printers I suspected the Windows server as the culprit. In my VMWare Player running Linux, I can print directly just fine.