Sure, why wouldnt you? Depending on what routers your have theres no reason you couldnt
So on the network, assuming that 192.168.0.1 is the router, 192.168.1.1 is your router, 192.168.0.2 is a client on the first lan, and 192.168.1.2 is the server
Easy / correct option
Router 1 needs a static route adding so it knows that 1.1/24 is hanging out off a port thats plugged into it, then it will just work. https://www.linksys.com/id/support-a...icleNum=135048
Medium / Eh option
If you want to keep nat, (bad idea as you allready know!) , then you may be able to do it if 192.168.0.1 supports DNAT or Dynamic routing.
If dynamic routing, (try this first it may "just work") : if you have plugged the routers in the correct way *(client port on 192.168.0.1 to the WAN port of 192.168.1.1) and both routers support whatever random protocol the router manufacture chose, you may only need to add a rule on 192.168.1.1 to forward SMB to the server and it will work.
For DNAT : If it supports DNAT, you can add a nat rule to forward the traffic from 192.168.0.1 to 192.168.1.1 and then add another DNAT onto router two to forward the traffic onto your server. Most consumer routers will set up a rule to forward the traffic back, and as SMB is all client initated, it should all be NAT safe and work.
Super Easy method, Just get 2X 10 quid wireless adapters from Amazon, connect one to Lan 1, one to Lan 2, and dual host the sever. Turn off routing on windows server to prevent network insanity and boom done, lan 1 connects to lan 1 wifi adapter, lan 2 connected to lan 2 wifi adapter
Also the Networks can be "the same" if your router supports it, is called super netting and it lets you have a /24 over all, and then each router just manages a /25.