Print script not playing ball

[bondbill2k2]

This morning I came into work to find the printers were not being mapped to staff machines, the staff logon script is as follows:

 

reg delete "hkcu\printers\connections" /f

rundll32 printui.dll,PrintUIEntry /u /in /n\\servername\staff_room$

rundll32 printui.dll,PrintUIEntry /u /in /n\\servername\library$

rundll32 printui.dll,PrintUIEntry /u /in /n\\servername\science$

rundll32 printui.dll,PrintUIEntry /u /in /n\\servername\col_it_room$

rundll32 printui.dll,PrintUIEntry /u /in /n\\servername\Maths$

rundll32 printui.dll,PrintUIEntry /u /in /n\\servername\curriccentre$

rundll32 printui.dll,PrintUIEntry /u /in /n\\servername\cLT$

rundll32 printui.dll,PrintUIEntry /u /in /n\\servername\IB_SCB$

rundll32 printui.dll,PrintUIEntry /u /in /n\\servername\AblockCLT$

rundll32 printui.dll,PrintUIEntry /y /n\\servername\staff_room$

rundll32 printui.dll,PrintUIEntry /u /in /n\\servername\Art$

 

 

This has always worked in the past but as of this morning users recieve an error "Windows cannot connect to the printer. Either the printer name was typed incorrectly, or the specified printer has lost its connection to the server"

 

Clients can reach the server ok and the print server can print to all networked printers.

 

 

Update:

It appears admin side of the network can print still, and I tryed running via the curric server for emergency circumstances without any issues. It appears its just the connection between curric clients and the print server

Edited June 21, 2011 by bondbill2k2

[lionsl2005]

i had the similar situation but that time user roaming profiles were not loaded properly. it happened to a particular user.

[Steve21]

Update:

It appears admin side of the network can print still, and I tryed running via the curric server for emergency circumstances without any issues. It appears its just the connection between curric clients and the print server

 

Have you tried connecting to it directly? Just using it as "run" the server/print name etc.

 

Just to ensure it can actually connect. Might be nothing wrong in the script, and just lost access to view/connect for some reason.

 

Steve

[bondbill2k2]

Yep I tried this with no luck so I ruled out the script. Sorted now but I've no idea why the cause of this problem had even occured.

 

Our curric subnet is 255.255.248.0.....the curric NIC on the print server was for some reason set to 255.255.248.0, changed it back to 248 and its fine but why it wrong i've no idea and neither does the network manager who locked up last night