Re: Outgoing Remote Desktop/TS Web client from SBS2K LAN?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: David Elders (david_elders_at_nospam.hotmail.com)
Date: 02/19/04 

Date: Thu, 19 Feb 2004 11:43:11 -0000

Here's a wee summary of the setup:

Site A - Edinburgh - SBS2K - cable modem connection to Internet
Site B - Glasgow - SBS2K - adsl connection to Internet
Site C - my house - cable modem connection to Internet

My laptop - XP Pro - member of Site A domain - local and domain
Administrator rights.

Packet Filters enabled for 3389 TCP at Site A as noted below:
Outgoing - all local ports - fixed port 3389
Incoming - fixed local port 3389 - all remote ports

When my laptop is on the SBS LAN at Site A, I can VPN to Site B no problem.
I can browse files on the SBS Server there no problem. I can ping any of the
Site B PCs by name and name resolution occurs fine. I cannot however use
either RDP or TSWeb to remotely manage the Site B SBS Server. It just times
out when I try.

If I connect the same laptop either outside the SBS LAN at Site A or from my
home [with the Proxy and Firewall Client not utilised in these scenarios,
obviously], I can connect to Site B's SBS Server using RDP or TSWeb fine.

Therein it's clear that 'something' needs configuring on our SBS box to
allow this to happen successfully. Problem is, we don't know what! There's
nothing in the ISA logs to suggest what [if anything] is being blocked.
Doing my head in now to be honest as I'm sure we're being daft somewhere
down the line!

Cheers for the help,

David

"Mark Barnes (Jao)" <anonymous@discussions.microsoft.com> wrote in message
news:241CF030-2E7D-4949-A7C9-EBFCE305DD10@microsoft.com...
> Sorry bout the mix up I read your original post back to front.
>
> So my reevaluation of your original question gives me this.
>
> You have a LAN at site A
> You have broadband access of some kind at site B
> You have a customer who wants supporting at site C
>
> site A connects to C via a VPN
> site B connects to C without passing through the VPN
> You can connect B to C using RDP no problems
> You cannot connect A to C using RDP
>
> Am I correct here?
>
> If so then it would appear that RDP traffic isn't passing down the VPN
tunnel correctly. Have you tried disabling the VPN and passing RDP directly
over the internet. Are your routing tables configured correctly so that
data passes down the VPN tunnel? What are you using to create your VPN
tunnel? What is your LAN ip range, what is your customers internal IP Range?

Relevant Pages

  • Re: ISA2004
    ... I understand that you cannot establish the RDP ... Internet Connection wizard' to configure the server networking settings? ... SBS server itself or other workstations through the normal RDP method? ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Outgoing Remote Desktop/TS Web client from SBS2K LAN?
    ... > either RDP or TSWeb to remotely manage the Site B SBS Server. ... > If I connect the same laptop either outside the SBS LAN at Site A or from ... I can connect to Site B's SBS Server using RDP or TSWeb fine. ... >> site A connects to C via a VPN ...
    (microsoft.public.backoffice.smallbiz2000)
  • Outlook over VPN - external firewall
    ... I've been pulling my hair out trying to get an Outlook client to connect to an SBS server via the Internet over a VPN. ... I do not have the option of Outlook over RPC-HTTP as most of the remote clients wanting access to e-mail via Outlook are still running Windows 2000 Pro, and OWA is a little slow. ...
    (microsoft.public.windows.server.sbs)
  • Cannot RDP using ISA 2004 PPTP VPN
    ... internet gateway and VPN server. ... networks by using RDP through a PPTP VPN terminated on the ISA server. ...
    (microsoft.public.isa.vpn)
  • RE: Terminal Service Internet Connection.
    ... Since the RDP Traffic on port 3389 is natively encrypted there's no need for a VPN ... I have RRAS setup on another server do allow 2 users living in the stone ages w/o Internet Access to dial-into my RRAS Server then open a RDP Session to my Terminal Server. ...
    (microsoft.public.win2000.termserv.clients)