Redirection of lpt1: problems...

[Sean Rector]

Windows XP Client
Windows 2000 SBS Server
Server has the printers defined

We use a batch file to redirect lpt1: to the shared
printer on the server - this is for a DOS app that only
prints to lpt1:.

The file sends the following commands:

net use lpt1: \\svr_name\printer
echo You are connected to printer PrinterX
echo
echo
echo Press any key to disconnect
pause
net use lpt1: /delete /y

When it issues the 1st line, it gives an error of "Invalid
password for \\svr_name\printer" and asks for username and
password - what ever is given, gives a System Error 5 and
it doesn't redirect lpt1 to the shared printer. The
machines that have already been set up do not give this
error with the same batch files, and the user is in the
Domain Users group, which has Print and Manage Documents
permissions on all printers.

Ideas? Please email to (e-mail address removed).

thx!

 

[Marina Roos]

Have you tried without spaces in the servername?

Marina

 

[Sean Rector]

There are no spaces in the server name...

\\svrdc01\printer3 is the path

 

[Marina Roos]

Is the user member of the local administratorgroup? In other words, if the
administrator would login on the client, does the batchfile work?

Marina

 

[Sean Rector]

When the Administrator logs in, the batch file works.
When another user logs in, who is only in the Dom Users
group (and not in the local system Admin's group), the
batch file works. I've even placed this particular user
in the local system Power User's group, to no avail.

 

[Marina Roos]

So can you pin this down to the user or the machine? If you try this
batchfile with the user logged in on another machine, will it run then?

Marina

 

[Sean Rector]

Elevating the user to local system administrator resolved
the problem.

Not the solution I wanted, but it works.

 

[Desert Denizen]

There used to be a KB artible on MS the mentioned that systems that
had been upgraded to Win2K as apposed to a clean install had problems
(bug) with permissions for power users in that they were unable to
install apps, change system settings etc. I have been unable to
locate thsi article again. Perhaps someone else has seen it . . .
--W