Remote VPN on my subnet


I have to PPTP/1723 on a 2003 Server to a remote site from my XP machine.  The trouble is the remote site is on the same subnet as my local office.  Consequently all packets stay in my LAN and I can't connect to their server.  This I put down to my machine thinking the is local and it just times out.  I can't change either network Id's.  What is the solution for this?

Cheers Experts :)
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rob WilliamsCommented:
Basic rule, as you are aware, is different subnets. Having said that with the Windows VPN client, if the "use default gateway on remote network" is enabled (it is by default) it 'should' force all traffic through the VPN/virtual adapter, and allow you to connect. This of course disables local access to resources and local access to the Internet. If not familiar with it, the option is located control panel | network connections | properties of VPN/Virtual adapter | networking | TCP/IP properties | Advanced | General | "use default gateway..."
This usually works, but not always. I am not sure why.
robjeevesAuthor Commented:
G'day Rob.  I saw that option and it it already ticked :-(  Anything else I can do? other than pray to the almighty or change one of the networks subnet?

Rob WilliamsCommented:
Sorry Rob, I have never heard of a work around. Wish I had, as it is common.
One option would be to use Hamachi's free VPN software, rather than the Windows. It works differently, and doesn't care about the subnets:

Hamachi is a 3rd part application that allows you to configure a VPN between 2 systems or sites, with no additional hardware or opening/forwarding of ports. To do so the application needs to be installed on on both machines. Then both machines make an outgoing connection to a 3rd party server. Outgoing connections are not blocked by most firewalls. The 3rd party server orchestrates the handshaking and configuration of the tunnel and then drops the tunnel and allows them to continue to communicate. Once connected, like any VPN the tunnel allows the two systems to use services such as file sharing, remote desktop and such. Hamachi is most useful if at least on the "server" machine it is installed as a service, making it available when you wish to connect.
to run it as a service:
batch file to set up service more easily, see near end of thread.   

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
robjeevesAuthor Commented:
Thanks for additional response Rob.  I'll take a look.

Rob WilliamsCommented:
Thanks Rob. Good luck with it.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.