Windows 7: Ping -t "request time out" on a network HP k8600 printer.

Hi all,

I have recently installed a network printer and had many problems. I've changed the IP address 3 times to resolve and still cannot. When I do a continuous ping to the printer (approximately 100, I had 4 request time outs). The 4/5 clients using the printer are having problems printing to it. I'm sure that request time outs are the problems behind this.

I did a tracert, and it seems to find the printer, but a * came up into one of the hops...



Any help


Thanks
Damian

What is the printer's ip-address? And what ip-address has a client? Connected to same router?

The printer's IP-address is 10.0.0.195 and client's IP address are in that same scope. They're connected to the same switch!

I'm still pinging the printer, and out of about 500 hops in "request timed out" once? Is this still a worry? Will this still affect their printing. (Sorry, little knowledge of pinging)

Ping sends just a small package to an ip address. That ip address responses back something like "receieved". Mainly used to check if system is still alive, or if routing to that system and from that system to you is correct.

When using TCP a network package is send to a device. The device receives it and acknowlege it. If no acknowlegement... package will be resend.

Is printing using UDP or TCP? Is it printing at all?

So... will it still affect their printing? I've left the ping on around 30 minutes and no "request timed out" with a new cable... So it could be a cable problem? EDIT: I've just had one..

Sorry, I should of explained better. They sometimes can print, and sometimes they can't print. Then the jobs get stuck in the spoiler and then they won't be able to print atall until the jobs deleted from the spoiler. Or they have to torubleshoot the device (the yellow symbol on the device itself through "devices and printers")

It's TCP isn't it? As i've set a static IP address on that printer.

So it's defiantly something Network related...

I assume it's TCP but 'not for sure. UDP is mainly used for stuff where missing a package doesn't care. For example streaming video.

I don't have a solution

Okay Thanks anyway. Well I've put in this new cable and most of the packets are sent. But in the last 45 minutes while the ping's happening... I've had 2 "request timed out". Am I supposed to be worried by this? After 45 minutes, is this normal...?

I'm pinging a printer that has no problems also, and I've had 1 "request timed out"... So I'm guessing it isn't too much to worry about?

Thanks
Damian

Not much to worry about. You can configure those kind of printers to be visible from the internet (of course you have to forward the releavnt tcp port in router). If someone from northpole prints on your printer it works. so it must be TCP.

And ping sometimes fails. Sure it's a switch and not a hub?

It fails when printing from multiple pc's. Problem is on same time or random? Related to print from EXCEL, WORD so it's application dependend? Same document fails but later succesfull?

All pc's in home that have print problems are using Windows 7?