failure printing to intel 10-100 print servers

  • Thread starter Thread starter bfarabaugh
  • Start date Start date
B

bfarabaugh

This morning no one can print to those networked printers connected
through intel 10/100 print boxes. We are win 2K Small Business. those
printers which are connected through pcs or thru HP print boxes work
okay. The intel devices are pretty old. How likely that all of them
would quit the same time? They display blinking green lights
indicating communications but the prin jobs arent delivered to the
printers and pinging them gets a timeout. I've restarted the server
and also the TCPIP print service. Does this make sense to anyone?
 
Are they configured with static addresses?

Can you view them with the Intel Netport software?

If you can't ping the devices I don't see how the server would be able to
send data.


Print a device Diag page and verify the device has the same address that you
think it should (little button on the side of the print server device).

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Thanks for replying.
The problem is intermittent. I can rest and update the device use
netport manager and it will work okay briefly then suddenly break
again. One netport does apear at all when I do a find in the netport
software. We think they might have been damaged by a power surge over
the weekend. It almost acts like the flash ram is faulty. they are
older hardware (1997-98) and maybe the circuitry is less able to
handle these occurrences than the newer devices. several replacement
print servers are on order. network is functioning okay at te
locations where these print servers are installed, so we have more or
less ruled out network issues.
 
Yeah but if the print server can't ping them, this is not a printing issue
either.

On a Win2k machine that has netport manager add the NetBeui protocol
(please no one boo). Move the undiscovered Netport onto the same subnet as
the Netbeui machine. Launch the NetPort application and search for the
device. I have had issues with discovery on TCP but NetBeui always found
them. Now you can verify the TCP/IP information. If NetPort can't find the
device, it's probably toast.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top