Can't Printer to Network Printer.. mostly

Over the last week, computers are no longer able to print to the SAVIN9020 on the domain. At this point only one computer can still print. Each computer is on the domain as is the Printer.

They are each connecting to the printer directly with an IP, not through a print server. They can ping the printer, but they cannot print. However one computer works fine.

Even stranger, if you plug a laptop into the printer directly it prints, however then it is not on the domain. Anyway the 'domain' and/or 'firewall" is blocking them from printing even if they are going directly to the printer and not to the server as a print spooler?

btw, server can not print either.

I have tried changing drivers, deleting and re-adding printer nothing seems to work.

Server: Windows 2003
Computers: Windows 7
Printer: Savin 9020
SocomAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

joelsplaceCommented:
Can they ping the printer?  Have you power cycled the printer?  I've had some really weird problems with DNS issues with large copier/printers.  Are they actually using the IP and not the DNS name?
I had a similar problem one time and had to remove the NIC from the printer and push a reset button on the NIC.  I don't remember the brand.
0
joelsplaceCommented:
I've never had a firewall issue with direct IP printing but you could turn it off to test.
0
pjamCommented:
Be assured that 32-bit & 64-bit drivers are identical versions.  IE PCL 6 Universal version 5.24
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

joelsplaceCommented:
I noticed that you said you deleted and re-added the printer.  Did you delete the port also?  Is the port a normal Windows created TCP/IP port or something setup by Savin?  I've had issues with HP TCP/IP printer ports.
0
SocomAuthor Commented:
update:

the only computer always printing is a 64bit driver/machine.

on any of the 32bit computers when a print is in the queue but not printing, unplugging the network cable from the printer and plugging it back in, the item in the queue prints.

when I deleted and added the printer on the server, I created an new port. didn't help. Windows Generic Port

tried multiple drivers, PCLS 6, PCL5 and the Universal, same issue.

They are using IP and NOT DNS
They can ping the printer
We have cycled the power on the printer, on the computer, on the server and on the switch.

Could it be a bad switch? only allowing one computer through? Never seen that before.
0
pjamCommented:
Have you tried another patch cable?
Have the outlet certified?
Try another Switch Port and jumper Patch cable?
0
SocomAuthor Commented:
Yes tried another patch cable, also tried another port on the switch. Did not try another jumper cable. We are in the process of putting in a replacement switch.
0
SocomAuthor Commented:
Update: New Switch didn't fix it, new jumper cable didn't fix it.

Anything else I can try other then a pad JetDirect card? and can you have a bad JetDirect Card that prints for one person and not another? And why when you unplug the cable and plug it back in does it print?
0
joelsplaceCommented:
I'll bet you have an IP address conflict.  Try unplugging the printer and ping it.  If you can still ping it something else has that IP.
Have you checked for firmware updates for the printer?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
SocomAuthor Commented:
Cannot believe I didn't thing of that, sometimes its the obvious you miss. The problem was an IP address conflict. Thank you for waking me up!
0
joelsplaceCommented:
That always trips me up too.  Notice it wasn't the first thing I proposed but it should have been from the symptoms.
Thanks,
Joel
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.