Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

REDMOTE - update can't connect to Redmote to update

Oh, yes, please do listen to Trent there, very important to reset the network setting back to DHCP afterwards...depending on how your local network is configured, not reversing the manual assignment of IP address for the RNDIS device could keep your computer from accessing the internet afterwards.

It's meant to be temporarily used, only while actually updating your REDmote.

My apologies for not mentioning how to back out of the manual settings.
 
FIXED - I had the same problem where my RedMote wouldn't connect to the Mac, even though it did in the past.

I was able to fix it by deleting the RNDIS/Gadget reference in Network using the minus sign in the bottom left. I then added it back in using the plus sign. It instantly connected with no problems.

Must have been some kind of legacy thing from connecting it before. Hopefully this will help get someone else back up and running.
 
Thanks Mark, that fix worked for me. However, one thing I did notice (at least in Win 7 which is what I am using): There was no need to set back to DHCP afterwards because the Redmote shows up (when plugged in through the USB as directed) as Internet Connection 5 on my computer and consistently shows up as that any time I plug it in. This Internet Connection 5 disappears after the redmote is unplugged. The other internet connections are unaffected by the settings I put in for IP and subnet mask so Internet and regular network access were not affected at least in my case. I'll leave it this way for now so any time we need to do redmote upgrade it will be ready to go but if anything happens to our network, I can always change it back.
 
Richard Andrewski said:
Thanks Mark, that fix worked for me. However, one thing I did notice (at least in Win 7 which is what I am using): There was no need to set back to DHCP afterwards because the Redmote shows up (when plugged in through the USB as directed) as Internet Connection 5 on my computer and consistently shows up as that any time I plug it in. This Internet Connection 5 disappears after the redmote is unplugged. The other internet connections are unaffected by the settings I put in for IP and subnet mask so Internet and regular network access were not affected at least in my case. I'll leave it this way for now so any time we need to do redmote upgrade it will be ready to go but if anything happens to our network, I can always change it back.
Click to expand...

The reason you should set it back to DHCP is in case we change the default subnet of the REDmote in the future so it won't conflict with so many local networks. The DHCP setting will work with the new (v4.0.8) REDmote code that was just released.
 
For me, following the instructions in the Scarlet & Epic manual solved the problem. Specially sticking to the manual IP settings did it for me.

redmote_mac_ip_settings.png


Hope this info helps - not sure if your problem was already solved.

Cheers,

Martin.
 
I am still struggling to get our Redmote to connect in the utility. I just updated our Epic-M firmware with the latest version today, re-downloaded the DSMC Resources and pulled down the latest REDmote firmware today as well. In network it says its connected and I have manually entered in the IP and Subnet, but the REDmote utility keeps saying "Unable to connect to the attached device"

REDmote v3.1.8
DSMC Resources v3.2
Mac
 
I am right in Mainland, had to try for upgrade many times too, still not work....
sine i had been upgraded many of Remote last few months, this the first times I had upgrade problem here...
 
You must log in or register to reply here.
Back
Top