Re: Cannot Remote Desktop (or ping) between 2 SBS sites

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

From: Frank McCallister SBS MVP (anonymous)
Date: 01/04/05


Date: Tue, 4 Jan 2005 05:41:34 -0600

One addittional requirement is to make dhcp reservations so that client will
always receive same IP

-- 
Frank McCallister SBS MVP
COMPUMAC
"Frank McCallister SBS MVP" <anonymous> wrote in message 
news:eTQebWZ8EHA.2124@TK2MSFTNGP15.phx.gbl...
> Ooops! Forgot to tell you how to connect from outside. Use mstsc /console 
> /V:serveraddress:3390 or port number of WS you want. Must train users and 
> publish list for them. And Marina is right on Firewall. Change the Port!!!
>
> -- 
> Frank McCallister SBS MVP
> COMPUMAC
> "Frank McCallister SBS MVP" <anonymous> wrote in message 
> news:OeEEQNZ8EHA.3840@tk2msftngp13.phx.gbl...
>> First step is to change the listening port on all WS you wish to RDP to. 
>> See http://support.microsoft.com/default.aspx?scid=kb;EN-US;q306759 use 
>> 3390, 91, 92, etc
>>
>> Next in ISA Server Management Expand Access Policy and under Protocols 
>> Select Internet Access Any RPC Service and right click Select Properties 
>> and Create New Protocol for each WS. For simplicity name them same as WS 
>> and assign the Port you set under step one Inbound.
>>
>> Next Expand Publishing and create New Server Publishing Rule for each WS.
>>
>> For Windows Firewall on WS change port to new port or disable Firewall
>>
>> -- 
>> Frank McCallister SBS MVP
>> COMPUMAC
>> "Jimbo" <anonymous@discussions.microsoft.com> wrote in message 
>> news:0e8d01c4f112$752ee750$a401280a@phx.gbl...
>>> Thanks for quick reply.  I will probably opt to change one
>>> of the site's local IP schemas to a different private
>>> range; but we are running ISA - could you elaborate a
>>> little on what needs to be done with ISA to have RDC work
>>> without changing IP schemes?
>>>
>>>
>>>>-----Original Message-----
>>>>Hi Jimbo
>>>>
>>>>Yes for VPN you will have to have a different subnet for
>>> the two networks.
>>>>You could use RDC directly on alternate ports with ISA
>>> However.
>>>>
>>>>-- 
>>>>Frank McCallister SBS MVP
>>>>COMPUMAC
>>>>"Jimbo" <jimbo@nospam.com> wrote in message
>>>>news:0e8301c4f10e$392c3090$a401280a@phx.gbl...
>>>>>I have a client (law office) that recently split into 2
>>>>> clients. They continue to run SBS2K at the original
>>> site;
>>>>> the new site runs SBS2K3 (they are now different
>>> companies
>>>>> with different domain names - not really 1 company
>>>>> w/multiple sites). There is a need for users at the new
>>>>> SBS2K3 site to VPN into the SBS2K site, and then Remote
>>>>> Desktop Connect to a workstation at that site.
>>>>>
>>>>> When I (or anyone else) attempts to vpn into the SBS2K
>>>>> site and then remote desktop connect to workstations -
>>>>> this works no problem from home - but does not work from
>>>>> the SBS2K3 site.
>>>>>
>>>>> When VPN'd in from the SBS2K3 site (VPN connects fine) I
>>>>> cannot ping anything on the other site by either
>>> hostname
>>>>> or IP address.  I did realize, when troubleshooting,
>>> that
>>>>> both sites have the same local IP addressing scheme
>>> (which
>>>>> may be the problem).  I tried fully qualifying the
>>>>> hostnames with the domain name when pinging (domain
>>> names
>>>>> are different between networks ofcourse) - still cannot
>>>>> get a reply from ping.
>>>>>
>>>>> For this to work (vpn in and remote desktop) between 2
>>>>> sites with different domain names, do I still need to
>>> have
>>>>> the 2 networks have different local IP schemes?  I can
>>>>> understand how this might be the case since the hostname
>>>>> will resolve to an IP address that may exist on either
>>>>> network, since both networks use the same ip scheme.
>>>>>
>>>>> If not, can someone suggest what else might cause a ping
>>>>> from a workstation on network A, VPN'd into network B,
>>> to
>>>>> not get a reply from workstations on network B?
>>>>>
>>>>> Thanks for any help that can be supplied.
>>>>
>>>>
>>>>.
>>>>
>>
>>
>
> 


Relevant Pages

  • Re: Yet another Windows XP SP2 Firewall issue
    ... The only suggestion I can come up with is to run gpupdate /force on server ... Frank McCallister SBS MVP ... that is exactly how it was joined to the network. ...
    (microsoft.public.windows.server.sbs)
  • Re: Trend and Spam Updates after ISA 2004
    ... Be sure and change the port from 8080 to 8085 ... > Thanks for the tip re disabling Trend though. ... >> Frank McCallister SBS MVP ...
    (microsoft.public.windows.server.sbs)
  • Re: access exchange on the road
    ... I must need another port opened. ... "Frank McCallister SBS MVP" wrote: ... you up for Outlook over http if you are using a Laptop ...
    (microsoft.public.windows.server.sbs)
  • Re: Trend CSM Install
    ... "Jeff Teel" wrote in message ... > Next there is a choice to use ssl on port 4343. ... > "Frank McCallister SBS MVP" wrote in message ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to send email externally using exchange 2003 in SBS 200
    ... "Frank McCallister SBS MVP" wrote: ... > like Dyndns.org to provide their Maihop outbound on an alternate port. ... >> I can send emails if I use outlook express as a pop account using my ISP ...
    (microsoft.public.windows.server.sbs)