Canon networking trouble - iRc4080i + iR2200

[Guest]

Hey all, thanks for anyone taking the time to check this out.

Alright, so I've got two Canon machines I seem to have struck out on, considering my background in networking. The first issue is a Canon iR c4080i that I just moved to a new location. Worked fine in the old location. Moved to a new field office location, and now get no connectivity out of it. It seems like it's taking the ipv4 settings I'm putting in, because they'll show up on a settings print out, but don't really seem to stick. Can't ping to or from it. Checked cable, getting perfect connectivity to the plug it's using. Seems like it's not listening for DHCP either when the box is 'checked' because leaving the boxes blank and rebooting the machine leaves me with the "check tcp/ip" error message. Looking in the gap of the slot next to the NIC as soon as the cable is plugged in I can see a link/act light flash a bit. To me, it seems like it's working like it should be, but I seem to be having some trouble at the user panel. Is there some special trick to this damn thing I'm missing?

Second machine. Canon iR2200. Sent that machine out from the stockpile to another field office, only to find out the reason it went to the stockpile was because it lost comms at the network card. Just my luck. Card has two link/act lights (green/amber), and as soon as the cable is plugged in, both lights come on solid and stay. Had a spare 2200, or 3200 something like that (similar looking machines and identical NICs) so I swapped the cards which looked identical aside from the differing MACs hoping for a quick fix, no dice. Same lights stay lit.

Someone please tell me I'm pulling a rookie move with these things and there's something stupid I missed. If I have to call a copier tech out to fix it for a firmware/software update or something, so be it, as the it admin for my company I've got a million other things to worry about, but if you guys have a relatively easy solution for something stupid I'm doing, hopefully I can save a few bucks on my budget.

Thanks a lot guys!

[vigour]

Re: Canon networking trouble - iRc4080i + iR2200

try to print from your laptop hooked up directly to machine first, and take it from there

[teckat]

Re: Canon networking trouble - iRc4080i + iR2200

Power on the copier holding down the 2 & 8 keys (download mode). Now try pinging the copier with 172.16.1.100. If the machine reply's this means the network board is good, if it does not reply first check your cable and IP address on the PC being used.
If both check out OK or you can ping something else on the network check the NIC card.

If the unit pings correctly when powered on in download mode but not in normal mode, one cause of the problem was found to be an option in TCP/IP settings turned on.
To resolve the problem go to Additional Functions > System Settings > Network Settings > TCP/IP Settings > and turn OFF Permitted Receiving MAC Address Settings.
Next power cycle the copier and try to Ping it.
----------------------------------------------------------------------------------------
The PING utility is used to verify connectivity between the imageRUNNER and other network equipment. The feature can be found under the following:

•Additional Functions > System Settings > Network Settings > TCP/IP Settings > PING Command.
To PING a device on the network:
1. Press the Additional Functions.
2. Press System Settings.
3. Press Network Settings.
4. Press TCP/IP Settings.
5. Press PING Command. Type in the IP Address you want to PING. (NOTE: you can only ping by IP Address and NOT hostname)
6. Press Start. If there is a reply, the message will be 'Response from the host'. If no reply, then the message will be 'No response from host'.

* There is also a PING command test in Service Mode.

Copier > Test > Network > PING

If you get a 'No Response From Host' message as the result, it means that the PING failed. The copier never received a response from the host at the destination ip address.

To test that the copier is functioning correctly, you can attempt to PING the loopback address 127.0.0.1. If this also generates the 'No Response From Host' message, then there may be a problem with the copier's NIC. You can try the following to troubleshoot the NIC:
- Reboot the copier.
- Re-seat the RJ45 of the network cable.
- Try another network cable.
- Re-seat the NIC in the copier.
- Try clearing the MMI in Service Mode on the copier. Reboot and reconfigure the copier.
- Try formatting the HD and reinstalling system software on the copier.

PC's may have firewalls running that block ping requests. Verify the pc you are attempting to ping will reply to a ping from another pc on the network.

-------------------------------------------------------
In a Windows TCP/IP environment, network configuration problems inevitably arise. Often the problem can be traced to an improperly configured TCP/IP setting, but finding the culprit can be difficult. Below are some steps to help determine where the problem exists:
1. What stopped working? The client, server, or the printer? Ask around to learn if the outage is affecting others or just a single desktop.
2. If the server stopped working, you should notice other co-workers with similar problems. If this is the case, focus on fixing the server.
3. If a single client PC has stopped responding to the network, ask the user whether new software was just loaded or any recent changes have been made to the system, including the installation of service packs, new Internet software, video games, and so on.
4. Check the physical network. The physical topology of your network is most prone to failure. In fact, most network problems are often due to Physical Layer failures (cabling, etc).
5. Is it plugged in? Check all network cable connections. Start at the NIC. Is there a green link light? Check the wiring closet to see if someone "borrowed" the patch cable. Check the hub to see if the system is getting a link across the cable.
6. If you don't have a cable tester, get one. Cabling is very susceptible to electricians, cleaning people and so on.
7. Start PINGing. Windows TCP/IP has the PING command built in. In a typical network you have this order (client->gateway->server) or (client->gateway->internet). First, attempt to PING yourself from the Windows command prompt. Your local "loopback" address for such testing is 127.0.0.1.
Example:
C:\WINDOWS>PING 127.0.0.1
PINGing 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<10ms TTL=32
Reply from 127.0.0.1: bytes=32 time<10ms TTL=32
Reply from 127.0.0.1: bytes=32 time<10ms TTL=32
Reply from 127.0.0.1: bytes=32 time=1ms TTL=32
PING statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milliseconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
If you do not receive a successful PING from yourself, in Windows, try re-installing the TCP/IP protocol from the Network Control Panel or the Network Interface card drivers.

8. If PINGing your loopback worked fine, then try PINGing someone who is on the same subnet as your PC. Be sure the target IP address being PINGed is a valid IP address assigned to a system; otherwise, you'll receive errors. Use the Start | Run | IPCONFIG command to learn your NT/2000 machine's IP configuration (use WINIPCFG with Windows 9x).

WINDOWS SYSTEMS

* IP Config provides valuable information about what network you are on, as well as your gateway address.

9. If you can PING someone on your local subnet, move on to the next step. If you can't, you're probably experiencing a Physical Layer failure. The usual suspects are bad cables or a NIC gone bad (they do that sometimes). With loopback, you were just testing the inner workings of the TCP/IP protocol stack; with PINGing on your local subnet you tested for failure on the failing machine. Try replacing the network card and using a new patch cable.
10. The next problem area is the gateway. Find the IP address of your gateway. You can find this in the IPCONFIG screen with NT systems (WINIPCFG for Windows 98).
11. If you don't have a gateway configured, then one will not show up in WINIPCFG, and this is a problem if you are connecting to another network. In Windows, locate Start | Settings | Control Panel | Network | TCP/IP | Gateway and add your gateway. This is your local interface on your router.

* PING this address; this will prove a solid connection from your PC to the gateway. If you have
made it this far, the PC is working, the cabling is working, and the router (gateway) interface is
working. You can skip to the next section.
* However, if you receive no response from the gateway, and you have one configured, it's time to
call the Network Administrator. Your router is improperly configured. It must have a local
interface (IP address) on your subnet to listen to the traffic on your network. If there is no
interface, have the router administrator add one. If it has one but has stopped working, it could
mean you're experiencing a router failure, and others will be affected as well. Conversely, the
router administrator may have loaded an old config; check with the administrator to make sure
this isn't the case.
12. The final step is through the gateway. PING something that is on the other side of the gateway. In an intranet, PING a printer on a remote subnet. On the Internet, PING Canon USA (128.11.96.121). If you do so successfully, you should not have a problem. If you can't get to a particular system in your network or on the Internet, that resource may not be available or the router's routing table may be misconfigured.