Thanks for your response!
Look harder ie under Administration group
I'm looking really really hard, and I might possibly be blind because I still don't see it. I see:
Administration- Backup or restore
- Create reinstallation disk
- View log files
- Mail log file analysis
- System monitoring
- Reboot or shutdown
None of those look like they have anything to do with printers. System Monitoring lets me get to a couple performance-type graphs (cpu/mem, load). Did I maybe install the LPRng incorrectly? I can get to an LPRng screen using the alternate URL I mentioned.
That's suggestive that your printer is connected correctly and is functioning etc, so it seems like the Windows XP printer driver version may be the issue. As I suggested earlier, download & update the printer driver to the latest version.
They are currently printing to that printer successfully by going straight to it (tcp/ip 9100 printing), so I believe the driver to be fine (and up to date), but for a particular DOS program we need to be able to redirect LPT1 or LPT3 to go to that printer, i.e. via our SME server. Using the same driver that's working already but changing the port to go to the UNC path or a redirected LPT3 leads to the problem I'm having. Alternatively if there's an easy way to get LPT3 redirected to a port 9100 printer without going through a print server like SME, I'm all ears (eyes).
Only logged in authenticated users have access to the printers, so are your users logging in to Win XP with a user name & password ?
Correct, our users are signing in to the domain using their network userid and password. I was testing using an administrator network account.
So I'm back to trying to figure out why it's not working. I did try a different printer (an HP 4100) and got it to work. I know SME used to have a bug whereby having the letters "off" anywhere in the server name or printer share name led to erroneous offline conditions (SME was looking for the work "off" in something and thought it meant the printer was offline). I don't know if that bug or a similar one still exists that might explain this, but the word "off" doesn't appear in our server or share name.
Any other ideas? I sure appreciate your trying to help! And I hope this information can be useful to anyone else who runs into a similar problem and is trying to troubleshoot it.