Printer logon script has partially failed

  • Thread starter Thread starter SAKWOYA
  • Start date Start date
S

SAKWOYA

Hi
We have a small Server 2000 network that has two networked printers.
These were called by a logon batch file with the following two lines:

rundll32 printui.dll,PrintUIEntry /y /u /in /n \\servername\HPBW2200 /q
/y
rundll32 printui.dll,PrintUIEntry /u /in /n \\servername\HPC4600 /q

Recently the first printer (HPBW2200) has stopped mapping - the second
still loads correctly. I have tried every last thing that I can think
of - nada!

Any ideas?

Graeme

p.s. i have tried the following:
Uninstall and reinstall network printer
Manually run the rundll32 command from the command line - it works
first time
Error logs show nothing
Change printer IP number
 
Hi
We have a small Server 2000 network that has two networked printers.
These were called by a logon batch file with the following two lines:

rundll32 printui.dll,PrintUIEntry /y /u /in /n \\servername\HPBW2200 /q
/y
rundll32 printui.dll,PrintUIEntry /u /in /n \\servername\HPC4600 /q

Recently the first printer (HPBW2200) has stopped mapping - the second
still loads correctly. I have tried every last thing that I can think
of - nada!

Any ideas?

Graeme

p.s. i have tried the following:
Uninstall and reinstall network printer
Manually run the rundll32 command from the command line - it works
first time
Error logs show nothing
Change printer IP number
I'm not exactly sure what you are trying to do. Are you trying to map
these printers to virtual network ports (i.e. LPT3)? If so, use:

net use lpt3: \\servername\HPBW2200

If I'm not understanding your request, please be clearer.

I hope that I was able to assist you.
 
Andreware said:
I'm not exactly sure what you are trying to do. Are you trying to map
these printers to virtual network ports (i.e. LPT3)? If so, use:

net use lpt3: \\servername\HPBW2200

If I'm not understanding your request, please be clearer.

I hope that I was able to assist you.

The batch file above was set under the Windows 2000 Server Group Policy
to run under Computer Configuration > Windows Settings >Scripts
(Startup/Shutdown) > Startup. It is supposed to make the WinXP client
machines pick up the two networked printers and set one as the default.

It no longer works for one of the printers - I am seeking suggestions
as to why this may have happened

Graeme
 
The batch file above was set under the Windows 2000 Server Group Policy
to run under Computer Configuration > Windows Settings >Scripts
(Startup/Shutdown) > Startup. It is supposed to make the WinXP client
machines pick up the two networked printers and set one as the default.

It no longer works for one of the printers - I am seeking suggestions
as to why this may have happened

Graeme
I'm not sure why that would happen. Do the clients still have
read/write access to it? If you type \\servername\HPBW2200 into the
Start->Run box, does it come up anything?

I was saying that I have never used RunDLL32 to connect to a shared
printer. My startup script looks something like this:

@echo off
net use n: \\namerica1\outlook
copy n:\mapi32.dll c:\windows\system
net use n: /delete
net use lpt3: \\keyt\hp

After some research, I found that you should probably take off /q (quiet
mode) so that we can see the errors that may be coming up. Plus, it
seems you have two /y's on one line.

I await your reply.
 
Andreware said:
I'm not sure why that would happen. Do the clients still have
read/write access to it? If you type \\servername\HPBW2200 into the
Start->Run box, does it come up anything?

I was saying that I have never used RunDLL32 to connect to a shared
printer. My startup script looks something like this:

@echo off
net use n: \\namerica1\outlook
copy n:\mapi32.dll c:\windows\system
net use n: /delete
net use lpt3: \\keyt\hp

After some research, I found that you should probably take off /q (quiet
mode) so that we can see the errors that may be coming up. Plus, it
seems you have two /y's on one line.

I await your reply.

Hi

Thanks for the /y pointer - that was one of the problems (the second /y
on the same line seems to throw the client PCs off the scent).
Rewriting the batch file as shown helped:

rundll32 printui.dll,PrintUIEntry /in /n \\servername\HPBW2200 /q
rundll32 printui.dll,PrintUIEntry /in /n \\servername\HPC4600 /q
rundll32 printui.dll,PrintUIEntry /y /n \\servername\HPBW2200 /q

This still did not work - I then used Group Policy to apply the batch
file as a user logon script which works fine - I still have no idea as
to why it failed as a computer logon script.

GT
 
Back
Top