I think I never had this issue with 2830 & 2925 models.
Connection to the server (who is located in Lan1 192.168.10.1/24) from other (V)Lans are listed as originating from the router ip address 192.168.10.1 and not the actual IPs of the PCs.

Right at this moment I am connecting with remote desktop to the server using my PC in Lan2 with ip address 192.168.169.131
Running a

Code:

C:\Users\Administrator>netstat -n | find ":3389" | find "ESTABLISHED" TCP 192.168.10.199:3389 192.168.10.1:55342 ESTABLISHED

This is making the windows firewall pretty useless. Running a netstat -n reveals that connections originating from within the same Lan are listed OK with the actual ip address of the PCs whereas all connections from the other Lans are listed as originating from 192.168.10.1
I suspect this might be a reason why the girls in the other department keep complaining to me that when one of them turns off her PC the others that have files from the shared server folder open are "kicked" out.

Any thoughts about this? Is this sort of bug or what?

P.S Connections from ipsec tunnels are not affected by this and they are listed with actual ip addresses.
Connections from ssl vpn tunnels are affected also.