Your first post was mentioning quickbooks online, second was the recommendation for a business class router.Sorry you don't understand. Read my posts. I leave in your hands.
If the secondary router was also an Asus (like an RT-AC66U_B1) then it would be trivial to use its Network Services Filter to create those rules automatically.Would need some iptables rules though to restrict the secondary router clients accessing the primary clients. Basically a set of rules allowing internet access and thats it.
If it were me... because your Quickbooks PC doesn't need access to other clients on the rest of your network, Id put a second router behind your AC88U with a VPN server running on that second router dedicated for your accountant, then forward the outside VPN connection from the first router to the second (port forward)
This way your accountant can VPN into that second router and access that QB PC, have zero access to your primary network and if you create a static route from your primary to your secondary router all your clients on the primary network can access the PC on the second one if needed.
If the secondary router was also an Asus (like an RT-AC66U_B1) then it would be trivial to use its Network Services Filter to create those rules automatically.
Redacted
I deleted that comment because it was wrong. I forgot for a moment that he was RDPing onto the PC.Wouldnt the fact that the accountant is remote connected (2 layer connection RDP through the VPN tunnel) into the PC on the second router, wouldn't that PC the accountant is RDP'd into still be able to access the primary network? The second router is essentially only seeing requests from the PC hardwired to it which would be bypassing the VPN rules?
I guess he could lose the VPN connection entirely and rely on the RemoteDesktop encryption (direct port forward of RDP to PC on secondary, Id frown upon this myself) or he'd have to setup IPtable rules to do it the 2 layer way? Sound right?
Thank you. This makes perfect sense to me. I have a question re: static routes.
I do not know how to configure a static route from the primary AC88U network to the new Quickbooks PC -- but this is exactly the second part of what I need to do. Can you explain how I would configure this? Would the Network Host = IP address of the Quickbooks PC, the netmask = 255.255.255.0, the Gateway = the AC88U, and the interface = LAN? What would the metric be set to?
Why are you using static routes? You don't need any.Thank you. This makes perfect sense to me. I have a question re: static routes.
I do not know how to configure a static route from the primary AC88U network to the new Quickbooks PC -- but this is exactly the second part of what I need to do. Can you explain how I would configure this? Would the Network Host = IP address of the Quickbooks PC, the netmask = 255.255.255.0, the Gateway = the AC88U, and the interface = LAN? What would the metric be set to?
Don't get an RT-AC66U it's old, obsolete and too slow as a VPN server. The RT-AC68U is the same as the RT-AC66_B1.The secondary router will be either an AC66U or AC66U_B1. If I use the configuration above, would I still need this ? If so, how would I use/configure the Network Services Filter to configure these rules?
Why are you using static routes? You don't need any.
Sorry, I must have missed that part. I thought the idea was to have the Quickbooks PC completely isolated from everything.If he wanted a PC on his 'private' network to be able to access that Quickbooks PC he'd need one on his primary router? No?
Why are you using static routes? You don't need any.
Understood. I have access to an AC66_B1 in my office which I will use.Don't get an RT-AC66U it's old, obsolete and too slow as a VPN server. The RT-AC68U is the same as the RT-AC66_B1.
Sorry, this is out of my sphere of knowledge. I thought we were talking about RDPing to a PC running a single-user application. Now we seem to be talking about some sort of client/server setup. Does that work across subnets? What ports does it use? Sounds like you will have to use the static route method.This was to solve a second problem (not mentioned in my original post), that it would be good to be able to access the QB PC from the primary network. The reason for this is that the "best" way to do the configuration is to have the QB instance running on the primary network access the QB data file on the standalone Quickbooks PC. This will allow for a nice multi-user environment - me and my accountant. The accountant can use QB via VPN and RDP on the QB-only PC and I use QB on my PC using the multi-user QB data file on the QB-only PC (Quickbooks has some configuration quirks when running in multi-user mode ).
Now we seem to be talking about some sort of client/server setup.
Correct!My grasp of it is the accountant RDP's in and uses the QB software on that PC, meanwhile the OP can run QB on a separate PC on the primary network and access the same database (which is on the QB PC) is all.
Yep. Personally I wouldn't even specify anything for the source IP, only the destination network (192.168.1.* or 192.168.1.0/24 depending on which firmware you're using). That way you're blocking everything.Using the Network Services Filter
I think... on your secondary router
It would be a Blacklist of the source IP of your QB PC, Port range empty (as in all), destination IP 192.168.1.0 (or whatever your primary router LAN is). Pretty sure its that easy.
Do we know how the database is accessed? Does it use SQL*net for example, or maybe it's just in an SMB shared folder?My grasp of it is the accountant RDP's in and uses the QB software on that PC, meanwhile the OP can run QB on a separate PC on the primary network and access the same database (which is on the QB PC) is all.
Someone can call me out me out if Im wrong on this (cough cough Colin)
Using the Network Services Filter
I think... on your secondary router
It would be a Blacklist of the source IP of your QB PC, Port range empty (as in all), destination IP 192.168.1.0 (or whatever your primary router LAN is). Pretty sure its that easy.
.
Also I think if you had a static route from primary to secondary you could get away with the VPN on the primary and then RDP to the secondary and utilize the VPN performance that way. And then disallow client -client so the VPN cant access primary clients
See my previous post. You would need two rules, one for TCP and one for UDP. Ignore the other protocol options.I am looking at the Network Service page right now. Are you able to tell me a) would the destination port range also be blank? , and b) what protocol I would use (there are a bunch of choices (TCP, TCP SYN, TCP ACK... UDP))?
See the explanation at the top of that GUI page. Basically you're stopping devices on the LAN from making a connection to anything on the primary network (but not vice versa).Also, can you explain what exactly this is doing? Is it preventing any IP traffic from the Quickbooks PC from flowing to the primary router?
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!