TCP/IP

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • 4raddoo
    Technician
    • Oct 2011
    • 30

    #1

    [Misc] TCP/IP

    How can i reset my tcp/ip on canon ir3100cn copier machine i just lost that please can someone help me now i am waiting right here with my machine
  • spectraindo
    Trusted Tech

    250+ Posts
    • May 2008
    • 313

    #2
    Re: TCP/IP

    Press Additional Functions - System Settings - Network Settings - TCP/IP Settings
    That is the basic settings for resetting TCP/IP Settings, it maybe slightly different.

    Comment

    • songela
      Trusted Tech

      Site Contributor
      100+ Posts
      • Mar 2008
      • 216

      #3
      Re: TCP/IP

      Originally posted by 4raddoo
      How can i reset my tcp/ip on canon ir3100cn copier machine i just lost that please can someone help me now i am waiting right here with my machine
      It seems you are not sure of what to ask for,

      1. If you RESET a certain parameter, you return it to ZERO, or to a default value.
      If you LOST it, it is as good as HAVING NONE, you have achieved a RESET already.

      2. What I guess is that, you want to RECONFIGURE the tcp/ip settings and you can't remember the previous value.
      If that is the case then let us know.
      As well you'll need to tell what kind of network environment is used i.e. a peer-to-peer, connected via a switch OR via a switch and router.

      3. For the sake of time, read the Network Adapter settings of your PC, it will give you a hint of how to coin a tcp/ip address for the ir3100cn

      Comment

      • DAG COPIERS & COMPUTERS
        Senior Tech

        500+ Posts
        • Oct 2010
        • 860

        #4
        Re: TCP/IP

        Google canon europe for instant download of 'network guide/user manual' for your machine.

        Comment

        • Hansoon
          Field Supervisor

          Site Contributor
          2,500+ Posts
          • Sep 2007
          • 3327

          #5
          Re: TCP/IP

          @4raddoo: Guy, judging from all your previous posts and your fuzzy question right now, your in dire need of a tech. Obviously you are not able to formulate a question others can understand without having to guess about your intentions.

          Hans
          " Sent from my Intel 80286 using MS-DOS 2.0 "

          Comment

          • teckat
            Field Supervisor

            Site Contributor
            10,000+ Posts
            • Jan 2010
            • 16092

            #6
            Re: TCP/IP




            Printers just don't have the TCP/IP missing one day/ what did u or were u doing to the printer/
            u have a Fiery connected ? then print out a Configuration page under printer tab


            or
            just print out a P PRINT > USER DATA
            **Knowledge is time consuming, exhausting and costly for a trained Tech.**

            Comment

            • teckat
              Field Supervisor

              Site Contributor
              10,000+ Posts
              • Jan 2010
              • 16092

              #7
              Re: TCP/IP

              Originally posted by 4raddoo
              How can i reset my tcp/ip on canon ir3100cn copier machine i just lost that please can someone help me now i am waiting right here with my machine
              ================================================== ========================
              **Knowledge is time consuming, exhausting and costly for a trained Tech.**

              Comment

              • 4raddoo
                Technician
                • Oct 2011
                • 30

                #8
                Re: TCP/IP

                My brother, the problem is that i use to print directly from my computer. But the copier machine is indicating that i should tcp/ip. Please help me to return to the default settings thank you
                Originally posted by songela
                it seems you are not sure of what to ask for,

                1. If you reset a certain parameter, you return it to zero, or to a default value.
                If you lost it, it is as good as having none, you have achieved a reset already.

                2. What i guess is that, you want to reconfigure the tcp/ip settings and you can't remember the previous value.
                If that is the case then let us know.
                As well you'll need to tell what kind of network environment is used i.e. A peer-to-peer, connected via a switch or via a switch and router.

                3. For the sake of time, read the network adapter settings of your pc, it will give you a hint of how to coin a tcp/ip address for the ir3100cn

                Comment

                • 4raddoo
                  Technician
                  • Oct 2011
                  • 30

                  #9
                  Re: TCP/IP

                  Simply as this the copier machine is indicating to check tcp/ip because i can print directly from my computer through internet hub please help me
                  Originally posted by hansoon
                  @4raddoo: Guy, judging from all your previous posts and your fuzzy question right now, your in dire need of a tech. Obviously you are not able to formulate a question others can understand without having to guess about your intentions.

                  Hans

                  Comment

                  • teckat
                    Field Supervisor

                    Site Contributor
                    10,000+ Posts
                    • Jan 2010
                    • 16092

                    #10
                    Re: TCP/IP

                    TCP.JPG


                    The most common and frequent cause or reason for these messages to appear are as follows:

                    1) The Canon device is not physically or properly connected to the network.
                    2) The Canon device and the customers network are not properly negotiating a valid network connection, speed and/or duplex.
                    3) Possible compatibility issue with customers hub / switch.
                    4) Bad Ethernet cable or network drop.

                    Check the TCP/IP Settings Message:

                    1. If the Canon device is plugged into the network, check for a possible duplicate IP address.
                    2. If the Canon device is not intended to be connected to the customers network, you may configure the device as follows:

                    press Additional Functions > System Settings > Network Settings > TCP/IP Settings > IP Address Settings and enter any dummy static IP Address, Subnet Mask and Default Gateway. Be sure to disable DHCP, BOOTP, and RARP.

                    Check the Network Connection/Settings/Printer Message:

                    a. Make sure that that the Canon device is properly connected to the network and/or try a different network drop.
                    b. Reboot the Canon device.

                    if steps a and b above do not resolve the issue, you may then try configuring the device as follows:
                    Press Additional Functions> System Settings> Network Settings> Ethernet Driver Settings> Auto Detect> OFF. Reboot the Canon device. This stops the Canon device from trying to negotiate the Ethernet Settings for communicating with the network.

                    c. If the device is properly communicating on the network (able to open the RUI and print), and you are seeing this message erroneously on the imageRUNNER C2620/C3100/C3170/C3200/C3220/C5800/C6800/C5870/C6870 models only,

                    if step c above is true, then you may try configuring the device as follows:
                    In service mode (LEVEL 2) COPIER > OPTION > BODY > NWERR-SW. Configure the value of NWERR-SW from [1] to [0] and Reboot the copier.
                    - [1] Sets message to display.
                    - [0] Sets display off.

                    **Knowledge is time consuming, exhausting and costly for a trained Tech.**

                    Comment

                    • teckat
                      Field Supervisor

                      Site Contributor
                      10,000+ Posts
                      • Jan 2010
                      • 16092

                      #11
                      Re: TCP/IP

                      Originally posted by 4raddoo
                      Simply as this the copier machine is indicating to check tcp/ip because i can print directly from my computer through internet hub please help me
                      ================================================== ========================
                      Network Troubleshooting TCP/IP Checklist

                      the best steps to take in troubleshooting TCP/IP connectivity on a Windows 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.



                      Windows 2000

                      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.

                      **Knowledge is time consuming, exhausting and costly for a trained Tech.**

                      Comment

                      • songela
                        Trusted Tech

                        Site Contributor
                        100+ Posts
                        • Mar 2008
                        • 216

                        #12
                        Re: TCP/IP

                        Originally posted by teckat
                        ================================================== ========================
                        Network Troubleshooting TCP/IP Checklist

                        the best steps to take in troubleshooting TCP/IP connectivity on a Windows 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.



                        Windows 2000

                        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.

                        I believe you are more than generous teckat.
                        It is a pleasure to have you here all times around contributing tirelessly, can we pray for your well being!

                        Comment

                        • teckat
                          Field Supervisor

                          Site Contributor
                          10,000+ Posts
                          • Jan 2010
                          • 16092

                          #13
                          Re: TCP/IP

                          gandhi-live-and-learn.jpgthank you
                          **Knowledge is time consuming, exhausting and costly for a trained Tech.**

                          Comment

                          Working...