1

I have 2 offices which are literally across the road from each other which I have 1 DC at in each office. We have setup a VPN site link between both DC's via RRAS. I have setup DFS-R and have got Group policys all up to date with serving each clients at each locations.

DFS-R copies files from Site A in real time over to server at site B and clients at site B see changes in about 1 minute (Obv. dependent on file size) but this works for us. Clients can cross the road, login and get their files in either site.

The issue I am having now is that I want to share printers.

I could just deploy the printers as I have done in each site via group policy however clients at site B (on 192.168.0.0) cannot ping printers on site A (192.168.1.0) hence can't print to them.

Both servers can ping each other, printers and clients on the other site just the clients at either end of the servers cant ping anything else except those in their own site.

I have a funny feeling its something to do with DNS and NAT possible but after setting all this up I have now stepped out of my comfort zone.

Any help would be much appreciated.

Thanks in advance.

  • It's probably not NAT or DNS. Do the printers have a Default Gateway configured in their network configuration? If not, then they won't be reachable from a different subnet. – joeqwerty Apr 27 '15 at 11:57
  • Yes they do. Ip of one is 192.168.1.6 subnet 255.255.255.0 and gateway of 192.168.1.1 – weazel91 Apr 27 '15 at 12:08
  • Should my clients which are connected to server2 in site B be able to ping clients which are connected to server1 in site A if server1 and 2 have a VPN between them? – weazel91 Apr 27 '15 at 12:13
0

After further discussion, the situation is that server A in site A makes a VPN connection to Server B in Site B allowing server A to access Site B's resources. Server B does the reverse.
The VPNs are established using RRAS

The correct solution here would be to configure RRAS to use LAN and demand dial routing, and then set up a Demand Dial interface on each server which will connect both networks together with the servers handling routing between.

Since the default gateway for the clients is currently their ISP router, it will be necessary to either change the default gateway to the local server's address, or add a route to the client machines so that they can route the remote network via the RRAS server in the local site.

  • Hi Chad, I don't have any Cisco routers. All my VPN is done through open ports on BT hubs and RRAS from server to server in both sites. We, at present, have no means of acquiring any. Everything however is working how it should at present. When the VPN is up server to server I can add a printer on Server2 and print to the printer in Site A which server1 is connected. The only issue is the clients connected to Server2, they can't. When the VPN is up should clients be able to ping other clients in the other site? As at present it only looks to be the server that can. – weazel91 Apr 27 '15 at 12:52
  • Ah - OK. I suspect it is a routing issue then. Can I ask a small favour - can you run a tracert from a client machine in Site B to the server in Site A. Can you also run a tracert from a client machine Site B to the printer in Site A. I just want to get an idea of how you are routing traffic from one network to the other. I assume you have your router as the default gateway, and clients will not know to route to the other network via the VPN on the server. – ChadH360 Apr 27 '15 at 12:59
  • Tracing route to 192.168.1.6 over a maximum of 30 hops 1 * BS1-PC.*DOMAINHIDDEN* [192.168.0.6] reports: Destination host unreachable. Trace complete. I get the exact same response for any trace route. I do have the router set to the default gateway and I completely understand that the client and router can't pass through the VPN tunnel without knowing where it is... How's best to solve this? – weazel91 Apr 27 '15 at 13:04
  • By the way - did you set up a Demand Dial interface in RRAS with routing configured? It would be helpful if you could be specific about your RRAS configuration. The correct method here would be to set up a Demand Dial Interface on each side with details about the remote network. You would then need to add a route to the client machines (via group policy would be best) eg in the 192.168.0.0 site - route add 192.168.1.0 mask 255.255.255.0 192.168.0.x (where x is the IP address of your RRAS server). For the printers, just set the default gateway as the RRAS server in the local site – ChadH360 Apr 27 '15 at 13:06
  • Thanks for the traceroute. I have a much better idea of what's going on now, but let me just confirm I understand correctly. Server A make a bog standard VPN connection to Server B and can access everything in Site B. Server B does the same. Apart from the servers, nothing else can access anything in a remote site. Is that correct? See my comment above about adding a demand dial interface and setting up routes on client PCs. That's what you want to do here. – ChadH360 Apr 27 '15 at 13:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.