Posts Tagged ‘windows’

Using an Old Printer with Windows Vista – and other Vista issues.

Thursday, August 28th, 2008

So, I bit the bullet and got a new PC with Microsoft Windows Vista.

Yes, like every informed geek, I expect a few issues.  However, sooner or later I will need to support Vista at client sites; besides, XP is getting on in years.

Today’s post is mainly about getting my old, but reliable, Brother HL-1030 to work in Vista.  The Brother laser printer is shared over the network by a Windows XP machine.

Some inter-related problems when trying to map this printer in Vista:

Immediately after trying to map the printer, this error comes up: “The printer driver is not compatible with a policy enabled on your computer that blocks NT 4.0 drivers”.  The Microsoft KB describing this, with no real work around other than “find a compatible driver”, is KB931719. Honestly, given the error message, wouldn’t you expect the KB article to provide a way to change the local policy?

Vista has no built in driver for my old HL1030, nor are there compatible drivers on the web.

On the driver front, a quick Google search told me that the built in Vista driver for the Brother HL-2030 would work fine.  But how do I use it? Every time I try the add printer wizard, it tries to install the incompatible point-and-click NT4/2K/XP drivers.

* Update – 2009-04: I had some intermittent problems with the HL-2030 driver, once in a while a page would not print completely and would cause the printer to require manual intervention to get it going again.  A quick search turned up this page which suggested using the Vista built in driver for the Brother HL-1430.  I’m trying that now.

So, I used an old trick. I faked a local port for the printer. I don’t remember the terminology, but I do recall this mapping system being common in the past – maybe with Novell or DOS?

Anyway, create a new local port using the share name, e.g. \\server\brother. You will be prompted to pick a driver. In my case, using the Brother HL-2030 driver does indeed work fine.

Some other Vista problems that I’ve had to resolve:

I’ve disabled User Access Control.  I can’t officially recommend this to other people, but it just doesn’t jive with me.

I’ve removed all but the US keyboard from my keyboard settings. Canadian PC’s (maybe it’s dependent on the regional settings?) have English, French and a “combo” keyboard mapping installed by default.  That’s fine until you accidentally hit the hot-key to switch to the French format – for some reason you do not get a confirmation prompt (!?!).  It happened to me on day two with this computer.  I’ve previously helped others fix this too.  While you’re at it, those with Intel Graphics, disable the hot-key that rotates the screen – everyone stumbles on that one eventually.

I had issues with an Access “.mdb” database on a network share that I use for tracking stuff. The resolution for that was to add the “serving” machine’s host name to my Internet trusted zone.  Adding only the IP address did not work, despite a MSKB Knowledge Base article I found.

I’m sure more Vista issues will pop-up.  But, so far, it’s been manageable.  I quite like the new 3-D flip task thing and the search tool.

Fixing the Time in Windows

Thursday, February 14th, 2008

In theory, Windows XP in a home (i.e. non-domain) setting should have no troubles keeping its time accurate. All you need to do is enable the “Internet Time” option so that it synchronizes with a network time protocol (NTP) server. It looks so easy, but it turns out that it’s really not bullet proof.

Most users should try a different NTP server first. The default time.windows.com server is heavily overloaded, and it’s hard to consistently get a sync. Try pool.ntp.org – that’s actually a network of machines that share the load.

But that’s not the solution in this blog post. IMHO, NTP is unusable in many small network environments because of firewalls and network address translation (NAT). Even the built-in Windows firewall can block NTP traffic which operates on UDP port 123.

Most home PCs connect to the Internet through a small, inexpensive router from the likes of D-Link, NetGear, Linksys, etc. Many of these block NTP or don’t work with it properly. This used to be a common problem with NATs. Port forwarding UDP port 123 to a computer works for some people, but that only works for one computer. And it didn’t work on the two routers I tested with today.

My solution that is generally bullet proof? Use a protocol that is TCP based. I don’t want to get too technical, suffice it to say that the chances of a TCP protocol working with all NATs is higher than that of UDP. Luckily, I found a perfectly good protocol and client (my backup plan was to write a crazy script to screenscrape a web page). It’s called DAYTIME it’s actually older and technically inferior than NTP, but what’s a second or two of accuracy if it works?

Now for a basic client, one might as well go to the source: http://tf.nist.gov/service/its.htm. It’s free, as functional as it needs to be, open source, and provided courtesy of a US government agency.

I setup a this as a weekly time update job on 10 small retail store POS networks through a generic maintence scripting system that is already in place: “nistime-32bit.exe Once -s5”. That’s it. It runs the time client, fixes the time, then exits. There are other options, but for this client, one time synchronizaton per week should be more than enough.

The moral of the story? UDP is over-rated in an Internet that is flooded by little home routers.