Posted by Bob A on February 07, 2014 at 14:15:50:
what happened first:
disk crashed, so a repurposed (so I've been told) PC was dragooned into service (which was Windows XP)
the "new" PC had the latest and greatest COMET downloaded today (by others) onto the C:\COMET folder
what's happening now....
Node for "new" machine is WS4... WS4 can't print to LP1 (Raw, Line printers), but can print to SPL (DocMgr Spoolers)
however it's not the configuration at fault because WS5 and WS6 can log on as node WS4 and print everywhere
also... WS4 can log on as WS5 and WS6 and can print to SPL, but not to LP1... so I think I've eliminated that configuration is at fault in this fashion.
What I can't interpret/understand:
is there a compatability problem because all workstations have vintage 2012 COMET locally if they're XP and the latest version if they're Windows 7.... only this one has a problem with XP locally and latest COMET for connections
I went to the security server and found there were two WS4 users active... I can't figure if this is some renegade session that's been active on its own for 08h40 (i.e. since about 08h30 AM)... seems like something logged on to this morning and then something happened
Any suggestions would be most welcome.
my first thought would be to re-install the local COMET for the WS4 workstation, but maybe an earlier version (like the 2012 version elsewhere)... but I will confess that this is strictly grabbing at my only straw.....
Post a Followup
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.