Hi,

actual we have a problem with slow ip connections. We use the same
configuration at 58 x RB 433 AH. Ethernet Port 1 connected to a node
with speed = 10Mbps, half duplex, auto negotiation = off, same network
but no ping --> no connection possible. On 4 other (older) 433 AH
bords are no problems on that. The only different of our "newer" and
"older" boards seams to be the IP 175c (older Boards) and IP 175d
(newer boards) chip. What can we do? Its a problem in a big projects
--> notice 58 of the RB 433AH

regards,
maxeschm

why would somebody use 10mbps half duplex?

Are you running the same version of RouterOS on all?

Are you running the same version of RouterBoot on all? MT would have made a new version to support the IP175d.

Tom

Hi,

10 Mbps full duplex is also no problem for the nodes. But this configuration also doesnt work with the 175d.

And yes, we try our configuration with OS4.6 and 4.9 and we get the same result. 175c works fine, 175d doesnt work.

rg,
maxeschm

Hi,

10 Mbps full duplex is also no problem for the nodes. But this configuration also doesnt work with the 175d.

And yes, we try our configuration with OS4.6 and 4.9 and we get the same result. 175c works fine, 175d doesnt work.

rg,
maxeschm

You didn't answer my question about RouterBoot so I'll suggest it again.

On one of the newer units, open a new terminal and type:

'system routerboard print'

It will show you the current running RouterBoot (firmware) version and the upgrade version available.

If the upgrade is a higher version number then type

'system routerboard upgrade'

Then reboot the router and see if there is any difference.

Tom

Hi Tom,

sorry that i don't understand you idea at frist. I will try your proposal and post the result in the course of this day.

rg,
maxeschm

Hi all,

no changes (also no changes with firmware upgrade to 2.26). The ip175c works - the ip175d not.
Any other ideas?

rg,
maxeschm

You may have a look on this topic:

http://forum.mikrotik.com/viewtopic.php ... lit=IP175D

Also, MT support said that is not possible revert IP175D features off without hardware modification... Im kinda suspect that some weird problems we have are cuz of that damn chip, but unfortunately we can't switch dozens of RB. It's frustrating.

Hi Ozelo,

so i can't do anything? It seems what we have to send all 60 RBs back to Mikrotik.

Hi at all,

it seems that this problem with 175D is no a singular case, there are a lot of forum topics (not only at MT forum) around the 175D problems.
But that is not the problem - the problem is the reaction of MT and their unreasonableness.

You get only a lot of lame excuse:

- Currently we are unable to reproduce any problems
- It seems there is a compatibility
- A solution here would be using switch in between

Sorry but thats not the right way!

br,
maxeschm