Toshiba Connectivity Issues

[ITGuy]

I have a Toshiba Copier (ES 800 series) connected to the network via a static IP. For whatever reason, it will no longer speak to the network. I can't print to it, I can't access it, I can't even ping it. I've tried changing the IP but nothing happens. The settings are all correct as far as I can tell, but for whatever reason it and the network will not speak to one another.

I've tried starting and stopping related services in Windows, but nothing changes. Hardware all seems to check out as well.

The problem started a week or so ago when the darn thing simply stopped working. It was fine before -- I could print to it, ping it, etc. But it randomly stopped working for no apparent reason -- all of the settings are the same. This apparently used to happen under the old IT person too and there was some work-around to get it working again. My gut tells me it is a problem specific to Toshiba, but I could be wrong.

Any thoughts?

[Mr Spock]

I have over 30 of these in the field and have not heard about this issue yet and all of these are connected.
Which version of winblows are you using?
Is it installed on the server and shared out or locally on each pc?
Which version firmware (user function>user>list>function on the top of the print out)?
Which driver version?
What hubs/switches are you using?

[SalesServiceGuy]

Did you try to reinitialize the NIC card. 08-693.

Power off the copier. Hold down both 0 + 8 key. Power on. Release when you hear a beep.

Do a 1119 Clears RAM, 947 Updates NVRAM flags and 693.

[Brian.Owens]

If this has been an on going sporadic issue it could be the firmware.

[blackcat4866]

A simple test would be to see if you can print from your laptop via crossover.

If yes, it's a network setting. If no, it's a printer issue. =^..^=

[emujo]

Unfortunatley, the NIC is part of the SYS bd...every time I've had this problem, it required a SYS bd replacement. You probably have blown the inputs to the NIC due to a surge, syptoms would be the NIC initializes properly at power on, but no connect lights on either the MFP NIC or the laptop/workstaion/switch it id connected to. You might want to add/replace a quality surge protector that will handle both AC and ethernet connections. Emujo

[fausto1981]

Try resetting the NIC just like the "SalesServiceGuy" said...

Did you try to reinitialize the NIC card. 08-693.

Power off the copier. Hold down both 0 + 8 key. Power on. Release when you hear a beep.

Do a 1119 Clears RAM, 947 Updates NVRAM flags and 693.

Check for any bent pins ont he NIC, you can also try putting the machine on DHCP and see if it picks up and IP address, bring a laptop and put the laptop on the same network range and hook it up with a cross over cable, see if you can connect to the machine or ping it at least.

[NeoMatrix]

[TCP/IP Printer Port Reset ]

Try windows <start> | printer and faxes | right click anywhere < properties> | ports | <add port> |

:: Printer Ports Menu ::
-- Available port types : --
Click < stardard TCP/IP> | < "New port..." >

Type your current Printer IP address and click <ok>
{The default printer name will match your IP you put in as you type, don't worry it's fine.}
Go back to the Ports Tab dialog.
Click on the new port/ip address name you just created.

{if you can't see the printer IP address name you created; drag the Port column header separator to the right.}
eg. Port >>>> | Description | Printer

Important, Click on <apply>
Noooowwwwww!.... If your printer drivers are working correctly the new port IP you created will Automatically pick up your printer and change to the default name of your printer. If this happens congratulations you have a working printer again.


HTH
GDM

[laercio.garcia]

If you send a ping will the machine respond to it? What do you mean with 800 series? Is it an es810? 850? 855? These models have very different types of controllers...

[TheOwl]

Silly question but is the copier responding via laptop? If so, are you running VLANS? If so, is the machine running on the same VLAN.

As already suggested by other users here, a test using a laptop direct to the machine will tell you if it is a machine or network related error (except on rare cases where the laptop has issues). Make sure you try this first and then go from there.