NETWORK PRINTING PROBLEMS 1

[ozispimp]

ok, i'm going to do my best to give all info possible.

first we're running a windows 2000 server with 8 workstations. those 8 workstations are seperated into groups of 4.. we'll call one of them A the other B. now, group A and B both have their own hp laserjet printers.

also know that we have to logon through a domain. now this is the problem.

group computers B prints everything perfect, they can print to both printers, on A and B.. but when i go over to the A group of computers, i can not print to the A printer, but i can print to the B printer. when i try to print to the A printer it says "unknown system error" when i go into our accounting software, it says "not enough hard drive space to complete action" even though, there's 8 gigz on there.. then i go to aol, same EXACT problem. but then i go into microsoft word, yet everythings ok.

everything's running through tcp/ip, and i just can't understand why its not working.. we haven't installed any new software.. it was working a week ago.. always gave a problem once in a while, all i had to do was remove the printer from the printer settings, then add it in again.. and its fine, not this time.

i don't feel like formatting 4 computers just to get the printers working.. anyone got any ideas at all??

 

[sobak]

I ran into this exact same problem....but on a Novell Network. The problem was a rights issue on the Novell Server. Although our setup is not the same, I received the exact same error (go figure, it couldn't say "access denied&quot Don't know if this will help, hope it does...

david e
*end users are just like computers, some you can work with...others just need a simple reBOOTing to fix their problems.*

 

[ozispimp]

i actually finally figured it out.. i went to the server and typed

w32tm /s

this is the error message i got on the printer.


Because of repeated network problems, the time service has not been able to find a domain controller to synchronize with for a long time. To reduce network traffic, the time service will wait 960 minutes before trying again. No synchronization will take place during this interval, even if network connectivity is restored. Accumulated time errors may cause certain network operations to fail. To tell the time service that network connectivity has been restored and that it should resynchronize, execute "w32tm /s" from the command line.

so everything's working great..

 

[sobak]

Cool glad that you got it fixed.... david e
*end users are just like computers, some you can work with...others just need a simple reBOOTing to fix their problems.*