Loading…
1
Three hours on a printer driver, turned out to be a DNS thing
Spent half my Tuesday at a client site in Portland fighting a Brother printer that wouldn't grab the right driver on any workstation. Reinstalled it four times, swapped cables, checked the spooler, the whole deal. Turns out their DNS server had a stale record pointing to an old IP for the printer. One flush and a reboot fixed it, I felt dumb but also kinda proud. Anyone else chase ghosts for hours only to find it's a network setting?
0 comments
Log in to join the discussion
Log In0 Comments
No comments yet
Be the first to share your thoughts on this discussion.