Re: VPN & FTP Question
From: Richard Wagstaff (rwagstaff_at_dsl.pipex.NOTTHISBIT.com)
Date: 08/29/04
- Next message: Chris: "Company Web"
- Previous message: Fred Orcutt: "Re: SBS Monitoring Issues"
- In reply to: David Copeland [MSFT]: "Re: VPN & FTP Question"
- Next in thread: David Copeland [MSFT]: "Re: VPN & FTP Question"
- Reply: David Copeland [MSFT]: "Re: VPN & FTP Question"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 29 Aug 2004 18:27:18 +0100
Many thanks, your first option worked a treat! Sorry, I forgot to mention
that the remote client is XP Pro SP2.
Just one more silly question if I may.... What is a "persistant route"?
I'm guessing that it is somethint to do with retaining the "route add"
command after a reboot.
Regards,
Richard
"David Copeland [MSFT]" <davidcop@online.microsoft.com> wrote in message
news:uSv1SobjEHA.2812@tk2msftngp13.phx.gbl...
> Richard,
>
> Sounds like what is happening is that by default the client machines
> default gateway will be changed to the VPN connection once the VPN
> connection is established which is then causing the traffic to be routed
> through the VPN instead of using it's previous default gateway. Depending
> on the OS of the client you should be able to add a route so that even
> after the VPN is connected the FTP traffic would still be routed using the
> other default gateway. If you know the FTP server's IP address you could
> try adding the route using the following from a command prompt
>
> route add x.x.x.x mask 255.255.255.255 y.y.y.y
>
> where x.x.x.x is the IP address of the FTP server
> y.y.y.y is the default gateway address being used on the client (while the
> VPN is not connected)
> Note that this would add a host specific route.. if there were more IP's
> in the same subnet you needed to access you could change x.x.x.x to be say
> x.x.x.0 and mask 255.255.255.0 which would allow routing to anything on
> the x.x.x subnet.
>
> If that works then if the client is 2000 Pro/XP Pro/NT etc. then you
> could make the route a persistent route by changing the above command to
> add a -p between route add.. (route -p add)
>
> If the IP address the client gets on the VPN interface is on the same
> subnet as the SBS server's internal subnet then another option may be to
> simply turn off the Use default gateway on remote host in the TCP/IP
> properties for the VPN connectoid.
>
>
> --
>
> Hope that helps,
> David Copeland
> Microsoft Small Business Server Support
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> Newsgroups:
> SBS v4.x : microsoft.public.backoffice.smallbiz
> SBS 2000: microsoft.public.backoffice.smallbiz2000
> SBS 2003: microsoft.public.windows.server.sbs
>
>
> "Richard Wagstaff" <rwagstaff@dsl.pipex.NOTTHISBIT.com> wrote in message
> news:Ob29PKbjEHA.2908@TK2MSFTNGP10.phx.gbl...
>>I have a remote machine in a branch office that I have just established a
>>VPN to our Small Business Server 2003 Premium (2 NIC & ISA 2000 running).
>>
>> Everything works fine except the remote can no longer connect to an FTP
>> host outside of our LAN (The host has a webcam that FTP's it's image to a
>> website hosted on a virtual server).
>>
>> I have tried connecting to the FTP host from the server with no problems
>> and the remote can connect when the VPN is off.
>>
>> I'd be really grateful if someone could point me in the right
>> direction...... I'm guessing it's something to do with ISA but I haven't
>> a clue what!
>>
>> Richard
>>
>
>
- Next message: Chris: "Company Web"
- Previous message: Fred Orcutt: "Re: SBS Monitoring Issues"
- In reply to: David Copeland [MSFT]: "Re: VPN & FTP Question"
- Next in thread: David Copeland [MSFT]: "Re: VPN & FTP Question"
- Reply: David Copeland [MSFT]: "Re: VPN & FTP Question"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|