Thanks for the recommendation idlemind, I will dive into that.
I actually got my issue solved this afternoon. The answer was to add a filter rule to forward "new" connections from the vlan (source) address.

Sounds like you have a MTU problem on your network

I thought about that and went down that path. I tried this with high hopes: https://stevedischer.com/pmtu-and-mss-d ... -mikrotik/
but it did not solve my problem either.

The arp=proxy-arp, at one time I had a satellite location using dial-in and never changed that.
I've tried disabling everything from the entry you mention down in the filter and still no joy. The mangle entries are dynamic

If the server is on the same vlan then the users just need the VLANIP to gain access. If the server is not on the same vlan, chances are there is no layer2 access. If the server is on a different lan and depending upon firewall rules, there may not be layer3 access. Is there a forward filter rule l...

I have several vlans under a bridge in a trunk/access setup and working well. except that anything connected on a vlan cannot connect to our local exchange server on the main lan or email in outlook setup as ssl. I have internet, can ping each vlan and navigate to shared folders. Any help is appreci...

Update when smooth, but NAT rules no longer work.

I now have internet on all ssid's. The only thing I changed from the last config was to change ether3 port to pvid=2. This made my other ssid's lose internet and only dole out the IOT pool, so I changed ether3 port back to pvid=1 and all ssid's get internet now with the correct ip pools. I don't und...

I did notice and change the interface. I tried both ways on the bridge vlan - I do need ether 3 on vlan1 - still no internet on IOT. Here is current: /interface bridge add name=bridge1 vlan-filtering=yes /interface ethernet set [ find default-name=ether1 ] advertise="10M-half,10M-full,100M-half...

That's why I didn't post it to begin with. I deleted to start over and hadn't gotten back to it. I had hopes someone knew an easy fix. So tried again - I'm still getting an address from vlan, but no internet and can ping vlan gateway. # aug/18/2019 15:34:37 by RouterOS 6.45.3 # software id = xxxxxx ...

I have deleted all the setup for vlan except for what's in the firewall, hoping maybe someone knew a fast fix, but here it is # aug/18/2019 11:03:53 by RouterOS 6.45.3 # software id = xxxxxxxx # # # /interface bridge add name=bridge1 vlan-filtering=yes /interface ethernet set [ find default-name=eth...

I've been trying for a couple of days now to get a Vlan setup with no success. I have an x86 RouterOS v6.45.3 setup interface bridge1=ethernet2,ethernet3 (only 3 nic ports). TP-Link unmanaged 24 port switch on ethernet2 and an EnGenius AP on ethernet3. I added a vlan interface with vlan#2, AP has vl...

Thank you mkx - We do only have one WAN IP. That first rule should actually be on the LAN only and was the straw. Once I moved it to the bottom everything else worked as it was before. The other rules with 5xxx are all different ports going to different machines and do forward successfully now. I st...

I inherited a hex router and recently changed ISP's from fiber to cable/RIP and some services are not connecting after changing the ip, namely remote access by ip & port and OWA. Can someone take a look at this and tell me if they see where the issue is? Or maybe I should reset and start over, b...

Eventually that is my goal, but I'm moving from one server to another and they both have mail queues at the moment, so I was hoping I could find someway other than moving the rules back and forth until I get that in place.

I have that rule already, but I cannot but two ip addresses in the action tab "To address". And if there are two rules for the same ports, it only uses the top one, so if the main server is down, the failover server doesn't have port 25 open. Is there any workaround for this?

I have two exchange servers in my network for failover (one one public ip) - how do I setup port forwarding for ports 25 & 443?

I've tried putting in user and password, server and port. and a from address - it all gives me the same result.

It sends just fine from the email window, I'm at a loss on what to try in a script.

Still having this problem, nobody has an idea?

Do you still have the service accepted for both tcp and udp port 53 in the firewall filter rules with the above filter rules?

My settings are still in there. here is the log first one failed from a terminal window, the second one successful from the email, send email window: 09:34:59 system,info log rule added by 09:36:27 e-mail,debug recv: 220 SMTP OK 09:36:27 e-mail,debug send EHLO [192.168.0.1] 09:36:27 e-mail,debug rec...

Since the update to 6.33.3 I have not been able to send my scheduled email. I can however, go into tools-email and send email successfully through that window. When using the terminal I always get "Error sending email <Backup> AUTH method not supported. Here is my script: /tool e-mail send file...