I have a PC (XP Pro) in an office some miles away which has an
application which I want to use remotely. We have a VPN set up via the
broadband modem/router there, accessed through the native Windows
support (Vista business). The local printer (Sharp) is on the network
at 192.168.1.50. I can ping that from my local machine.
When connected to the remote XP box, I can run the application but I
can't see or ping the printer - even though I can "see" the "Fax
printer" on my local machine. I can't ping my local printer.
Using netstat on the remote XP box I could see that there was a
connection on port 3389 via 10.0.0.220 (which can only be the
termination of the VPN there). When I tried tracert I found it trying
to go out through the Default Gateway and unable to reach the printer or
my local PC at 192.168.1.101.
Of course I'd love to be able to print locally from the remote machine -
what would I have to do? I mused over the "route add" command-line
utility, wondering if that might do the trick, but I've no way of being
sure that the VPN will always terminate at the same IP address
(10.0.0.220) and I'd be getting into some cumbersome scripting to detect
it locally (although I don't rule that out).
I bet this is a common problem - hopeful for some smart advice!
Bookmarks