ir105 + network problam

**iust** · 05-10-2011

hi
I setup one set ir105+ on my network and inistal netscape printer and scaner works on network very well but when i want to open this copier page by IE , mozila ....
"cannot display this page" is apeared. (I type ip add.)+(I turn off firewall )
help please?

**teckat** · 05-10-2011

Originally Posted by iust

hi
I setup one set ir105+ on my network and inistal netscape printer and scaner works on network very well but when i want to open this copier page by IE , mozila ....
"cannot display this page" is apeared. (I type ip add.)+(I turn off firewall )
help please?

do this in IE
Make sure to Un-check this box
"Use a proxy server for your LAN" (tools>internet options>(connections)>(LAN settings).

in Mozilla
under Options/Advanced>Connection settings>select> the use system proxy button

You receive an error message in Internet Explorer: "Internet Explorer cannot display the webpage"

also>in>Additional Functions>System Settings>Network Settings>TCP/IP>screen 3 of 5>Multicast Discovery=select>Disable
power off/on printer

**teckat** · 05-10-2011

Testing for an IP Address Conflict for Duplicate IP Address

Step-by-step instructions with screen shots on how to properly test for a possible duplicate IP address or IP address conflicts on a network. Two methods are discussed:

Method 1 - Ping the Device, Unplug the Device, and Ping the Device Again (DO NOT USE):

This method is the most popular way of testing for a duplicate IP address on a network. Unfortunately, this is not the best way to test for an IP address conflict, as it can lead to INCORRECT conclusions. It is highly recommended that you use Method 2 instead. Step 1: Type the command ping <ip address of the device> .

You then get a response from what you think is the device that you are testing.

Step 2: You then go to the printer (or device) and disconnect the Ethernet cable from that printer (or device)
Step 3: Type the command ping <ip address of the device> .

You then ping the device again and this time you get no response from the ping.

So, now you believe that you don't have any duplicate IP address or IP conflicts on your network and you believe that the IP address that you just pinged is the one going to the device that you are testing.
THIS CONCLUSION MAY NOT BE CORRECT:
All that you just proved or tested is that the network card in the device that you pinged is working and responds to a ping request. You have not necessarily tested for duplicate IP address or IP conflicts on the network.
Method 2 - Using the ARP Table (USE THIS METHOD):
The PROPER METHOD of testing for a duplicate IP address or IP address conflicts is to perform the following:
Step 1: Type the command ping <ip address of the device> .

You then get a response from what you believe is the device that you are testing.

Step 2: Type the command arp -a .

A list of the IP address to MAC address mappings (the ARP table of the PC) will display.

Step 3: Write down the MAC address that responded to the ping command of that IP address.
Step 4: Remove or disconnect the network cable that is connecting the printer (or device) to the network.
Step 5: Type the command arp -d <ip address of the device> .

This will remove the IP address to MAC address mapping that you just pinged from the computer's ARP table. If you don't perform this important step, the computer will no longer look for the IP address that you are pinging. It will now only look for the reply from the MAC address of the IP address that was last associated with that IP address.

Step 6: Type the command ping <ip address of the device> . Did any device respond to this ping?

Please keep in mind that if there is another device on the network that is using the same IP address, it will take a while for that device to regain control or begin to responding to the ping command. It is suggested that you wait at least 10 to 15 minutes. Also keep in mind that if this problem is not happening several times on a regular daily basis, it will be more difficult to find.

In this example after performing the above steps and waiting a few minutes, we were able to identify that some other device did begin to respond to the ping command that we were troubleshooting. Being that the original device is still disconnected from the network as per step 4, nothing should ever respond to the ping command for the IP address of the original device.

Step 7: Look at the MAC address (Physical Address) that now responded to the ping command (if any), while the original device was disconnected, via the arp -a command. If the MAC address is different from the original MAC address you wrote down in step 3, then there is a different device using the same IP address (a duplicate IP address).

Write down the MAC address (Physical Address) that corresponds with the IP address (Internet Address) that responded to the ping command when the original device was still disconnected from the network. This will be your only proof that some other device is configured with the same IP address that was assigned to the original device.

By looking at the first six (6) characters of the MAC address, you can now identify who the other device's manufacturer is. You can then begin to look around the office with the customer's network administrator for the device using the duplicate IP address.

In the example, we are now able to identify that the first six (6) digits of the MAC address that is now responding to the ping command are 00-0b-cd. According to the attached file MAC_Address_List.pdf, this is a Compaq device of some kind, not a Canon device. After searching the customer location, it was determined that a Compaq Desktop PC was using the same IP address as the Canon device.

**mrfixit51** · 05-10-2011

I have occasionally had to clear the cache files for Internet Explorer to view some of the connected copiers out there. Also make sure RUI is installed on the copier system software, and I recall the RUI access can be turned off in service mode somewhere???