[mcrussell]

Given we are talking about remote here, it's probably the remote setup you are using is not supporting RPlus or something else is screwed. Hard to tell something without knowing anything about said setup.

Apologies, when I say remote, I mean ISTA PC & ICOM are local to the car, I am just remoting in with Teamviewer.

Its very strange though as some others dont see this issue.

Ive also seen issues with AOS & Offline ISTA when trying to update ICOM with connection manager, ended up having to log into ICOM direct from Chrome & use the ICOM GUI

[NeRkO20]

Nothing similar happens for me.

---

Is your ICOM actually resetting (like all leds going off, then back in boot order)?

They have been remote sessions so couldnt see them, however if you monitor iTool it disappears then comes back after a few seconds with its 169.xx IP instead of the 192 IP it had

Since ISta .4.46 there is no IP 192.168.4.1 ( I downgraded to 4.45.xx and got again 192.168.4.1)
From ista 4.46 and newer I always get 169.xxx.xx

And yes, I have recognized too this with my Icom Next (original) and latest FW

You are wrong! There was no 192.168.4.1 in FIRST releases of 4.46 due to a bug. Now it's back and fully operational for quite some time!

I think u missunderstood me. Never said it worked with 4.46!
I said it worked for me UNTIL 4.46 (so with latest 4.45 I got with local connection 192.168.4.1) aufter update to 4.46 and now to 4.47 I don´t get 192.168.4.1 for some reason....

But maybe you have a solution?

[Node]

Nothing similar happens for me.

---

Is your ICOM actually resetting (like all leds going off, then back in boot order)?

They have been remote sessions so couldnt see them, however if you monitor iTool it disappears then comes back after a few seconds with its 169.xx IP instead of the 192 IP it had

Since ISta .4.46 there is no IP 192.168.4.1 ( I downgraded to 4.45.xx and got again 192.168.4.1)
From ista 4.46 and newer I always get 169.xxx.xx

And yes, I have recognized too this with my Icom Next (original) and latest FW

You are wrong! There was no 192.168.4.1 in FIRST releases of 4.46 due to a bug. Now it's back and fully operational for quite some time!

I think u missunderstood me. Never said it worked with 4.46!
I said it worked for me UNTIL 4.46 (so with latest 4.45 I got with local connection 192.168.4.1) aufter update to 4.46 and now to 4.47 I don´t get 192.168.4.1 for some reason....

But maybe you have a solution?

I understood you perfectly. And still stand by my statement that you are wrong. Again, FIRST versions (like two) of 4.46 have this bug that they fail to enable ICOM's internal DHCP server, but AT LATEST in 4.46.40 is was FIXED! And is working without ANY ISSUE since.

https://cartechnology.co.uk/showthread.p...#pid681031

[NeRkO20]

OK, then there is an issue on my side. I didn´t change anything except I am using the patched DLL to be able to use old tools too.
For me it doesn´t work...but I have have 2nd laptop at 4.45 fresh install...maybe I try to update up to 4.47 and check...maybe there it will work

[NeRkO20]

Just a small update on this topic/my issue here.
I was using the patched DLL file...then I removed that and copied from ISTA\Ediabas\BIN all files to c:\Ediabas\Bin (overwritten all files) - like described by @Sedoy.

After that ISTA 4.47.x is locating ICOM faster and DHCP works....
The only thing I didn´t mange is to be able to use STANDARD TOOLS during an ISta session. I knwo I have to "adjust" some INI files, but just tried it once on a E Series Car....
So I will search for a solution as soon as I will have time for that and a E-Series Car.

At the moment I am using 2 EDIABAS folder like (EDIABAS_E_Series, EDIBAS_ISTA) and I am renaming that one I need into "EDIABAS"...