romon policy was not mark
TNKS!!!We know that already. Thanks for not reading before posting.
See blog.mikrotik.com/security/ for more info.
I'm using Windows Server 2003 R2 x64...What SMB server are you using? If Windows, what is the version? I have a hard time thinking this is a ROS issue as I have a SMB server at home (NAS) and I have no issues what so ever with SMB traffic.
About MAC changing on hypervisor side...You already have an answer in this topic. Please try to do what others suggested.
okPlease either make a new topic about this other issue, or make a new support ticket. You started with inability to change MAC address. Now that you were told what you have to do, you have switched to another problem
Sorry, this is a weak argument! People spend money for raw product that works not correct yet!yet we have thousands in production.
Yes i used it... and file shares beyond VLANs was lost availability every few seconds!your CHR should be using VMNET3 interfaces, not e1000.
Thats because of this file shares beyond VLANs broke availability every few second on CHR???Because your old x86 platform used a generic e1000 interface.
Answer from support:And what about to set the mac address in hypervisor?
I wrote a letter to support. Still wayting...And what about to set the mac address in hypervisor?
Thank you very muchrc10 fixes crash
OK. You are right. The only thing i have now - deleting script. I'll try. Thank you!Deleting at boot with script gives operationally the same thing - so I don't see how that's "not a solution"
Yes, it's a work-around, but it's a viable one.
Sorry, you don't understand what i need. But tnks for trying.I think you can accomplish the same by adding them disabled. That way they will be stored but not in effect until you enable them.
I very appreciative your affort for help, but... it's NOT a help. Sorry!You could write a script and use netwatch... when server 1 stops responding to pings then switch to server 2. I don't know of a built in way to do it.