SMB through Linksys RV042 VPN

[erwjoh]

Godd evening all, this is my first post here and I would like some assist in trying to resolve and issue through a Gateway-to-Gateway VPN Link I have setup with 2 x Linksys RV042's. I even have laptop users (on the road) connecting to it using TheGreenBow VPN Client to either side as required.

I have it all setup and working great, if one has to be rebooted it automatically reconnects and users are using it to print, download files etc. But the connection to download files only works one way and it is stumping me.

I recently installed Windows 2008 Foundation Server and plan to do a DFS between them to allow servers to synchronise data. When I attempted a connection from one of the servers (on Site A) to a workstation (Site B) I get a message back saying that "the computer is online, but is not responding to connection attempts at this time".

The workstation I am attempting connection with is XPP with Firewall disabled. If I try the connection the other way I don't have any problems, can anyone give me some pointers to try and resolve the issue/s??

Thanks in advanced J

 

[YeOldeStonecat]

I had a similar problem with a WAN setup I did a couple of years ago, I was having some issues with active directory replication functions between the sites.

In my issue, I found the issue was related to how a certain version of their firmware back then was handling RWIN (TCP receive window)...the problem was surfacing because one of my sites was on cable broadband (MTU 1500), and the other site was on PPPoE DSL (MTU of 1492). I prefer to setup my WANs on identical type of broadband..but sometimes you're stuck doing WANs using different types. And I've noticed now and then when I'm faced with this I'll run across an issue or two.

I fixed the issue by installing the latest firmware that addressed the issue, and manually setting the MTU on each router instead of leaving it on auto.

No netbios passthrough on the tunnel, since this client was running SBS at the main site the DNS and WINS settings being passed to the PCs on the other end took care of proper name resolution.