Canon R1 ethernet connectivity issue (wired)

[scottburgess]

I'm trying to configure an R1 to talk to the EOS Utility on my computer. I can't seem to get anything going with the RJ-45 port despite following directions in the Advanced User Guide. The camera software thinks everything is working, and the network light flashes appropriately, but when I get to the stage of starting the EOS Utility software, the camera doesn't see it. Also, my router doesn't add the camera to the LAN active device list--the MAC Address shows up but it is shown as inactive. I tried changing network ports, resetting the camera's network settings, and still can't connect.

Is it a problem with a bad RJ-45? Has anyone else connected to EOS Utility via a wired LAN? Did the Advanced User Guide instructions work for you?

Scott

 

[koenkooi]

I'm trying to configure an R1 to talk to the EOS Utility on my computer. I can't seem to get anything going with the RJ-45 port despite following directions in the Advanced User Guide. The camera software thinks everything is working, and the network light flashes appropriately, but when I get to the stage of starting the EOS Utility software, the camera doesn't see it. Also, my router doesn't add the camera to the LAN active device list--the MAC Address shows up but it is shown as inactive. I tried changing network ports, resetting the camera's network settings, and still can't connect.

Is it a problem with a bad RJ-45? Has anyone else connected to EOS Utility via a wired LAN? Did the Advanced User Guide instructions work for you?

Scott

Does the network port support the speeds the camera supports and vice versa?
I recently found out that my main switch has 1G/10G ports, not 100/1G/10G.
And the 2.5G port on a company device can’t drive ‘long’ cables that use aluminium wires (‘copper clad’ is the red flag you need to watch out for).
The R1 supports faster than 1G speeds, which means it isn’t as plug and play as people (rightfully) expect.

So try a different, shorter cable, that should show if it works at all or not.

 

[YuengLinger]

I'm trying to configure an R1 to talk to the EOS Utility on my computer. I can't seem to get anything going with the RJ-45 port despite following directions in the Advanced User Guide. The camera software thinks everything is working, and the network light flashes appropriately, but when I get to the stage of starting the EOS Utility software, the camera doesn't see it. Also, my router doesn't add the camera to the LAN active device list--the MAC Address shows up but it is shown as inactive. I tried changing network ports, resetting the camera's network settings, and still can't connect.

Is it a problem with a bad RJ-45? Has anyone else connected to EOS Utility via a wired LAN? Did the Advanced User Guide instructions work for you?

Scott

Have you considered updating drivers/firmware for your ethernet card on your computer?

 

[OldDudePhotog]

Have you tried connecting the camera directly to the computer? I rarely shoot this way but when I do I directly connect it to my computer instead of through a switch/router. The computer and camera should auto-assign an APIPA address on each device (169.254.x.x/16 range).

 

[scottburgess]

Does the network port support the speeds the camera supports and vice versa?
I recently found out that my main switch has 1G/10G ports, not 100/1G/10G.
And the 2.5G port on a company device can’t drive ‘long’ cables that use aluminium wires (‘copper clad’ is the red flag you need to watch out for).
The R1 supports faster than 1G speeds, which means it isn’t as plug and play as people (rightfully) expect.

So try a different, shorter cable, that should show if it works at all or not.

I run a recent gaming router, quite fast. Tried connecting both to an accessory switch connected to the router, and to the router directly. Both those and the computer support 1G+ transfer rates which the camera should be capable of syncing to. I'm connecting the R1 with a flat CAT-7 cable to the router currently.

I ordered a CAT-8 cable as a main connector, though I doubt that will do anything to fix the issue.. But I am sitting next to the router, so distance isn't the problem. Computer, router, and R1 camera are all connected via short, flat CAT-7 cables. The cable connecting the camera is a recent buy and used to connect another computer, so I know it works.

Have you considered updating drivers/firmware for your ethernet card on your computer?

Umm, this isn't a W98 box, and I'm sure the computer isn't likely at issue as it functions perfectly with a wide range of other things. And the drivers are current (mobo, not an ethernet pci card). And before someone asks, according to the Advanced User Guide, my version of Win10 (fully updated) is more than sufficient, and I updated EOS Utility 3 before the camera even got here.

Have you tried connecting the camera directly to the computer? I rarely shoot this way but when I do I directly connect it to my computer instead of through a switch/router. The computer and camera should auto-assign an APIPA address on each device (169.254.x.x/16 range).

Now this seems like a good idea, as it eliminates the router as a source of problems. Isolation of the issue is key, and if it is a problem with the network card in the camera I'd like to figure that out asap. Taking the router out of the equation is worth trying. I'll order a crossover cable as I probably should have one around anyway.

I spent some time trying to connect wirelessly to the network using WPS-PBC, which should be pretty simple but also didn't work. Like with the wired setup, the camera was identified and added to the router's list of devices, but the camera couldn't establish and maintain a connection nor connect to EOS Utility on my main computer. Makes it seem more likely to be a bad comm chip in the camera or firmware problem.

To be clear: I'm not using this to shoot with yet, just trying to connect to the EOS Utility as a primary means of downloading images and updating firmware. Also, my camera shipped with firmware 1.0.0. So perhaps the early firmware is the problem?

Has anyone hooked an EOS R1 up to a LAN via ethernet and connected it to EOS Utility on WIN10? I'd like to know if that works for someone else, or if the only workable configuration is a direct connection with a crossover cable.

 

[scottburgess]

Quick addendum...

I connected via the USB cord, then downloaded and installed firmware 1.0.1. Supposedly this firmware "improves networking stability," but after testing the camera's ability to connect via wired and wireless, all I can say is that I'm disappointed because the behavior described above was still the same.

So, I'll add this to the list of questions: contact Canon or send it back to Adorama?

 

[YuengLinger]

If you are still running windows 10, it isn’t the newest machine in the neighborhood is it? Can you try somebody else’s?

OK, so it’s not a card. We’ll call it your network interface controller. Did you actually check to see if there are updates for ethernet drivers? Compare what’s available to what’s on your machine?

I’m surprised you think Windows 98 was the last version that needed updating.

Troubleshooting involves eliminating obvious problem points before ordering more stuff, such as a crossover cable.

Carry on!

 

[OldDudePhotog]

I run a recent gaming router, quite fast. Tried connecting both to an accessory switch connected to the router, and to the router directly. Both those and the computer support 1G+ transfer rates which the camera should be capable of syncing to. I'm connecting the R1 with a flat CAT-7 cable to the router currently.

I ordered a CAT-8 cable as a main connector, though I doubt that will do anything to fix the issue.. But I am sitting next to the router, so distance isn't the problem. Computer, router, and R1 camera are all connected via short, flat CAT-7 cables. The cable connecting the camera is a recent buy and used to connect another computer, so I know it works.


Umm, this isn't a W98 box, and I'm sure the computer isn't likely at issue as it functions perfectly with a wide range of other things. And the drivers are current (mobo, not an ethernet pci card). And before someone asks, according to the Advanced User Guide, my version of Win10 (fully updated) is more than sufficient, and I updated EOS Utility 3 before the camera even got here.

Now this seems like a good idea, as it eliminates the router as a source of problems. Isolation of the issue is key, and if it is a problem with the network card in the camera I'd like to figure that out asap. Taking the router out of the equation is worth trying. I'll order a crossover cable as I probably should have one around anyway.

I spent some time trying to connect wirelessly to the network using WPS-PBC, which should be pretty simple but also didn't work. Like with the wired setup, the camera was identified and added to the router's list of devices, but the camera couldn't establish and maintain a connection nor connect to EOS Utility on my main computer. Makes it seem more likely to be a bad comm chip in the camera or firmware problem.

To be clear: I'm not using this to shoot with yet, just trying to connect to the EOS Utility as a primary means of downloading images and updating firmware. Also, my camera shipped with firmware 1.0.0. So perhaps the early firmware is the problem?

Has anyone hooked an EOS R1 up to a LAN via ethernet and connected it to EOS Utility on WIN10? I'd like to know if that works for someone else, or if the only workable configuration is a direct connection with a crossover cable.

you probably will not need a crossover cable, most modern network interface cards have a feature called "auto MDIX" that will electrically "rearrange" the pinouts to allow point-to-point connections, also gigabit connections have a different arrangement of sending/receiving on the wires than 100m connections, which use 4 in each direction. When I connect, I've always just used a straight-through cable and have not had any issues, either that or the cable I have is Xover, and I just dumb-lucked into it, which is very unlikely.

 

[OldDudePhotog]

I run a recent gaming router, quite fast. Tried connecting both to an accessory switch connected to the router, and to the router directly. Both those and the computer support 1G+ transfer rates which the camera should be capable of syncing to. I'm connecting the R1 with a flat CAT-7 cable to the router currently.

I ordered a CAT-8 cable as a main connector, though I doubt that will do anything to fix the issue.. But I am sitting next to the router, so distance isn't the problem. Computer, router, and R1 camera are all connected via short, flat CAT-7 cables. The cable connecting the camera is a recent buy and used to connect another computer, so I know it works.


Umm, this isn't a W98 box, and I'm sure the computer isn't likely at issue as it functions perfectly with a wide range of other things. And the drivers are current (mobo, not an ethernet pci card). And before someone asks, according to the Advanced User Guide, my version of Win10 (fully updated) is more than sufficient, and I updated EOS Utility 3 before the camera even got here.

Now this seems like a good idea, as it eliminates the router as a source of problems. Isolation of the issue is key, and if it is a problem with the network card in the camera I'd like to figure that out asap. Taking the router out of the equation is worth trying. I'll order a crossover cable as I probably should have one around anyway.

I spent some time trying to connect wirelessly to the network using WPS-PBC, which should be pretty simple but also didn't work. Like with the wired setup, the camera was identified and added to the router's list of devices, but the camera couldn't establish and maintain a connection nor connect to EOS Utility on my main computer. Makes it seem more likely to be a bad comm chip in the camera or firmware problem.

To be clear: I'm not using this to shoot with yet, just trying to connect to the EOS Utility as a primary means of downloading images and updating firmware. Also, my camera shipped with firmware 1.0.0. So perhaps the early firmware is the problem?

Has anyone hooked an EOS R1 up to a LAN via ethernet and connected it to EOS Utility on WIN10? I'd like to know if that works for someone else, or if the only workable configuration is a direct connection with a crossover cable.

Another question I have is, are you connecting the camera to the switch/router-switch combo via a wired connection and using your other machine wirelessly? I cannot see anything in your posts to lead me to this, but I felt it worthy of asking. The reason I am asking is I run an enterprise wireless system in my house (I work in and teach IT at a local college) and have run into an issue with my wireless system doing weird things with multicast translations from wifi to physically connected devices because I run IPv6 internally and tunnel IPv4 when I need to. You may be running into the same issue and not even realize it, a way to test it is to temporarily disable IPv6 on your desktop/laptop to see if it makes a difference. This recommendation is wading into the weeds a bit but is easy enough to test.

 

[scottburgess]

you probably will not need a crossover cable, most modern network interface cards have a feature called "auto MDIX" that will electrically "rearrange" the pinouts to allow point-to-point connections, also gigabit connections have a different arrangement of sending/receiving on the wires than 100m connections, which use 4 in each direction. When I connect, I've always just used a straight-through cable and have not had any issues, either that or the cable I have is Xover, and I just dumb-lucked into it, which is very unlikely.

I didn't think the R1 could support auto MDIX, but did an experiment this morning to see what would happen if I disconnected the computer from the LAN and hooked the two together. I also shut down all firewalls and virus software for good measure. The results appeared to be the same as on the network: the computer sees the camera attached, but the camera still cannot connect to the EOS Utility on the computer. So apparently it should support auto MDIX, but no progress was made.

Another question I have is, are you connecting the camera to the switch/router-switch combo via a wired connection and using your other machine wirelessly? I cannot see anything in your posts to lead me to this, but I felt it worthy of asking. The reason I am asking is I run an enterprise wireless system in my house (I work in and teach IT at a local college) and have run into an issue with my wireless system doing weird things with multicast translations from wifi to physically connected devices because I run IPv6 internally and tunnel IPv4 when I need to. You may be running into the same issue and not even realize it, a way to test it is to temporarily disable IPv6 on your desktop/laptop to see if it makes a difference. This recommendation is wading into the weeds a bit but is easy enough to test.

I minimize my wireless footprint and try to keep such stuff turned off--so the camera, computer and router connect with cables only. And I already had checked to make sure IPv6 was uniformly turned off (my ISP still hasn't switched over yet, so while my equipment supports IPv6, I'm on an IPv4 subnet for now).

I’m surprised you think Windows 98 was the last version that needed updating.

I'm surprised you think modern mobos lack ethernet ports. I can't recall even seeing one without in decades.


Okay, folks, at this point I'll call Canon support asap and see what they have to say. I suspect they will walk me through some stuff over the phone, but won't know until I try. If I don't get a quick resolution that way, the body is headed back to the retailer.

I would still like to hear if anyone can confirm that they can establish a wired or wireless network connection to the EOS Utility. And I still welcome any suggestions should someone have a flash and think 'this is a good explanation for the behavior, have you tried this?'

Thank you all for your support.

Scott

 

[OldDudePhotog]

I didn't think the R1 could support auto MDIX, but did an experiment this morning to see what would happen if I disconnected the computer from the LAN and hooked the two together. I also shut down all firewalls and virus software for good measure. The results appeared to be the same as on the network: the computer sees the camera attached, but the camera still cannot connect to the EOS Utility on the computer. So apparently it should support auto MDIX, but no progress was made.

If the R1 supports gigabit ethernet then autoMDIX is required, the fastest anything can go without it is 100m. I have not used the R1 with ethernet yet but have my R3. I have my stuff out now after having just returned from a Boy Scout crossover that I shot. I'll test it here shortly. I'm using a MAC with an adapter but it should still work if it is going to.

 

[OldDudePhotog]

Initial testing is that the camera is assigning my MAC an ip address 172.16.42.10 but the EOS utility never connects. I'll try troubleshooting it and see where I get with it. I have a generic USB-C to Ethernet adapter, so that could cause an issue.

Edit: I cannot get my R1 to connect to my MAC. I see the IP address and can ping it but EOS Utility never sees it. I even tried wifi and same thing. Perhaps someone else on here can test, if all 3 of us cannot connect then it is a repeatable pattern.

Edit #2: I fired up wireshark on my MAC, I can see traffic to/from the camera but EOS utility never connects to camera or does anything. I also discovered my IP address was set manually, I reset to DHCP and am getting the expected APIPA address.

 

[OldDudePhotog]

I found the charger for my Windows 11 laptop and was able to download EOS utility to it, connect the camera via a straight-through cable, and do some things with it. I did not have a lens on it, but I was able to transfer files from the camera to the laptop.

 

[scottburgess]

I found the charger for my Windows 11 laptop and was able to download EOS utility to it, connect the camera via a straight-through cable, and do some things with it. I did not have a lens on it, but I was able to transfer files from the camera to the laptop.

Thanks, OldDudePhotog! Interesting that MacOS didn't handle things well, but thank you for confirming that at least the R3 works fine on Win11.

 

[OldDudePhotog]

Thanks, OldDudePhotog! Interesting that MacOS didn't handle things well, but thank you for confirming that at least the R3 works fine on Win11.

I am not surprised the MAC didn't work correctly, this is an ongoing thing with Apple and Canon software. Every time Apple does an update it breaks all sorts of things, this seems especially true with the MX series processors. I can think of a few programs that won't work at all since the switch from Intel, even after several years. I will try to mess with it some more today before I put my cameras away.

 

[jfr0317]

@OldDudePhotographer On a Mac, go to the Applications folder then the Canon Utilities folder, then the EOS Utility folder, and then double-click the EOS Utility icon. This will launch the program but also trigger several permission requests including access to other devices on the network. After doing this once, you can thereafter open EOS Utility as you would any other program and have it see your connected camera.

I had to do a Google search to find this info which was in a Canon Community forum.

 

[OldDudePhotog]

Update number, whatever it is. After letting the windows desktop update last night, I cannot get past the splash screen on EOS utility. The LAN light on the camera is solid showing connection but I get nowhere now.

 

[OldDudePhotog]

@OldDudePhotographer On a Mac, go to the Applications folder then the Canon Utilities folder, then the EOS Utility folder, and then double-click the EOS Utility icon. This will launch the program but also trigger several permission requests including access to other devices on the network. After doing this once, you can thereafter open EOS Utility as you would any other program and have it see your connected camera.

I had to do a Google search to find this info which was in a Canon Community forum.

I have done this and it does not present any permissions settings. I have also dug through the settings looking for the individually and cannot find any references. I plan to add them manually later today to see if that helps.

 

[OldDudePhotog]

I have done this and it does not present any permissions settings. I have also dug through the settings looking for the individually and cannot find any references. I plan to add them manually later today to see if that helps.

I deleted and reinstalled EOS-U and it prompted me for permissions. After that I was able to connect my camera and shoot pictures with it and it saved them to a folder I specified. This was on my MAC, my windows 11 PC is still not working. Last time I did this I do not recall it being this difficult to set up but it has been a couple of years since I did it this way.

 

[scottburgess]

I have done this and it does not present any permissions settings. I have also dug through the settings looking for the individually and cannot find any references. I plan to add them manually later today to see if that helps.

Well, I may be able to help you slightly even though I couldn't help myself. Let me explain...

Today I was curious why the wireless network never asked for a password. So prowling through the manual I found that one can configure the wireless settings manually, which one needs to do on a password network. Sure enough, there was a password option and I edited the wireless configuration to add the network password. At last, the camera was showing as active on the network! But my hopes were dashed when I tried again to connect to the EOS Utility as it simply couldn't make the connection. And that doesn't explain my wired problems either as one doesn't need a password when directly connected to the LAN via CAT-7.

So perhaps there is a menu setting for fixing your issue, OldDudePhotog. At least check out p. 831 forward in the current version, titled Connecting to Detected Networks.

I was pondering whether this might be a firmware issue, as solid state devices often have bad bits. BUT: it seems unlikely that Canon would load the software without doing a checksum to ensure it had been copied accurately. And since I did the update myself and saw no errors, I could only believe that an SSD was the problem if such an error were intermittent. At the same time, I have no idea if Canon uses ECC features on their code/data.

I am wondering what OS to use if I do a build. Win11 is officially beyond end of life, with no Win12 in sight (probably not available until next year!). And I don't know if there will be advanced ECC features in the professional or enterprise versions of Win12, but those would be a consideration from my perspective. As disk densities climb, I'm seeing more errors from stored data and programs and I would like to have some means to address it. As it is, I will have to eventually run some image recovery software on a few hundred old image files when I have the time.

Scott