I have recently configured RVS4000 for VPN use. The office LAN is the RVS4000 (IP 192.168.1.1) behind a Thomson 516 (in bridge mode, the RVS handling PPPoE authentification), 1 machine running xp pro used as a file and print server, 3 xp workstations.
I just want to be able to access the server, which has a fixed IP of 192.168.1.50. I don't care about accessing the workstations. Windows firewal on the server is off.
Trying to connect from home machine which is another xp pro machine behind a d-link 524 and cable modem. windows firewall on home computer is off (di-524 firewall is on, I've lost the password and the unit is refusing to hard reset to defaults...).
quickvpn will connect to the RVS4000 (as long as port is set to auto) (though sometimes the remote gateway will stop responding...don't know what's up with that), and I can ping each and every device on the office LAN, including the server and the networked multifunction office machine (which prints, scans and faxes beautifully over the office LAN). I can log into each and every web interface connected to the office LAN
The RVS4000 is meticulously set up with each and every firewall rule I've seen mentioned re. quickvpn.
I understand that quickvpn does not give you a local IP on the target LAN, and that it does not support netbios. However, I have read and been told that it should allow to access fileshares and printers. But these do not work.
After some research, I set up a networked drive by IP address and folder on the server. It looks right, displays correct size and capacity info and browses nice and fast. However, any attempt to save to the file server results in a file save error, data lost, connection may have been lost error message out of the windows taskbar.
Also, trying to set up printer (either as standalone network device by IP address, which worked great when setting up the office LAN, or via the server (to which it is locally connected) results in a bad hang and/or ultimately, the printer cannot be found error message.
I've tried running remote desktop on the server (by IP). It connects great, but then hangs, useless.
Phone tech support says that must be a windows file permission problem, but the file server is using plain vanilla full file sharing that works real well on the office LAN. I've even assigned the home machine the same workgroup and domain as the office LAN (though since netbios isn't supported, didn't think it would do anything, and it didn't).
Any thoughts on making this work, or have I just wasted our money and nearly an entire week of my time?