Re: VPN



Hi Dieter,

RWW is the 'killer app' of SBS2003, I've heard rumours that ENTERPRISE
Network Admins SALIVATE over the possibility of stealing it from SBS space.

Your boss and you have XP workstations at work? Instead of turning them
off at night, leave them on. RWW will give you the ability to connect to
them securely from anywhere in the world (as long as certain ports are
accessible through whatever firewall you are behind).

RWW is actually a set of web pages, available from https://SBSname/remote
when internally connected to the network and https://FQDN/remote when coming
in from 'outside' the network. RWW allows you to read email stored on the
server, connect to XP desktops, connect to terminal servers on the network,
access the CompanyWeb, download a preconfigured VPN client, AND MORE.
Allowed users can observe Performace Reports, control the SBS itself, all
sorts of great stuff.

How does this negate the need for VPN?
Allowed users can establish a secure HTTPS connection to the server, then
take control of their XP workstation in the office through a process known
as RDP Proxy, 'Connect to My Computer at Work'. If you have a Terminal
Server on the network, and the user is correctly permissioned, you can also
'Connect to my Company's Application Server'. Many tasks which are slow or
unreliable over VPN (accessing a large database comes to mind) work quite
well over RDP Proxy, due to the fact that only screen updates move across
the 'external' connection, access to the database happens at local network
speed.

Ports required for RWW:
443 (HTTP SSL) Most remote systems should allow this.
and that's the complete list. If you allow it, incoming requests to port 80
(http://fqdn/remote) will automagically switch to HTTPS.

Additional ports which you may wish to access:
444 CompanyWeb https://fqdn:444 (can be problematic for remote firewall
systems. Not all remote firewalls [ISA included] will allow HTTPS on this
non-standard port). I'd rather, and it can be manually done,
https://fqdn/companyweb (ie. companyweb _appearing_ to be on the standard
HTTP SSL port, port 443)
4125 RDP Proxy. The RDP Proxy is enabled by RWW loading an ActiveX control
into IE. There is a distinct possibility that a remote system (say that in
the 'Business Center' of your hotel) will block the installation of such
controls. This is good, we don't want fully public (viri infested) PCs
accessing our network. However, if we are on a computer we can _reasonably_
trust (Say, Aunt Gladis' PC) we can work 'as if' in the office from
thousands of miles away.
1723 PPTP VPN (IF YOU MUST) I allow VPN into my LoungeAN because I feel I
have 'special needs', I use it on EXTREMELY rare occassions. (actually, I
can't remember a time in the last 6 mths, maybe I should disable it)


"Dieter Visser" <kdv@xxxxxxxxx> wrote in message
news:u1TL%23s0GGHA.2040@xxxxxxxxxxxxxxxxxxxxxxx
> Hello,
>
> Forgive me for braking in this thread, but I'm struggling to get VPN
> working. We have a SBS2003 premium with ISA 2004. I'm the IT guy here, my
> boss and I want to be able to login to the system from home.
>
> "SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
> news:%23x6nSrxGGHA.3320@xxxxxxxxxxxxxxxxxxxxxxx
>> you would be better off forgetting about VPN and using RWW's 'Connect to
>> my computer at work' function.
>>
>> Interested in how?
>>
>
> I tried to setup VPN, read all the white papers, the how to's and the step
> by step's, and still didn't succeed. My fault off course. I am very
> interested in using RWW's function 'Connect to my computer at work'.
> Especially in the 'how side'.
>
> I would be in your debt if you could enlighten me. Considering the amount
> of questions about VPN I'm not the only sucker here.
>
> Thank in advance
>
> Dieter Visser
>
>> "jimmy" <jimmy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:74BA3A66-A9BF-4F96-8698-CEDF92D95468@xxxxxxxxxxxxxxxx
>>>I am a beginner at this, and I need some help. I am trying to be able to
>>> access my server using VPN. Here is my current setup: One server,
>>> running SBS
>>> 2003 Premium, Three client computers, All with Windows XP. I have two
>>> desktops, connected via ethernet and one laptop connect via WiFi, and
>>> one
>>> cable modem plugged into the "Internet" port on the router. I have the
>>> DMZ on
>>> the router enabled. I need to bypass the router to the server to use
>>> VPN. I
>>> will be willing to try any possible setup or configuration to connect to
>>> my
>>> server over the internet via VPN. Any help is much appreciated!!!
>>> Thanks.
>>
>>
>
>


.



Relevant Pages

  • Re: [Full-disclosure] Remote Desktop Command Fixation Attacks
    ... This set of steps is redundant in many places, and it's also enormously expensive, since you're using no less than three different expensive bits of networking hardware (AP, PIX, VPN Concentrator), in addition to a bunch of x86 server hardware, windows server licenses, and at least one ISA license. ... Your computers necessarily don't have full access to your network infrastructure when they aren't logged on, so GPOs, software updates, etc can't be applied at the times you want them to be applied. ... Turning on, enabling, and implementing every possible security setting and device you think of is not defence in depth, and will probably only have two effects - your users won't use your wireless network, and you'll burn so much cash you won't have any left to spend on *useful* security measures. ...
    (Full-Disclosure)
  • Re: VPN with SBS 2003 (not R2) and DSL.
    ... Reading property value for VPN returned OK ... Reading VPN Server Name returned OK ... identical network cards. ... it seems doubtful that SBS will work properly with two NICs ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN Connection Problems
    ... Note that we are able to successfully VPN into the office. ... to browse the network, RDP to the server or even ping the server. ... > This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN clients unable to connect to other resources.
    ... on the SBS 2003 server just not sure where to go for help on it. ... Next time I'm at my home PC, I'll VPN in and see what IP info I'm getting ... client PC on your LAN, you should be able to do so from a remote VPN client, ... get the network path was not found. ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN Error 800
    ... The VPN client IP is 10.0.1.40, this is a private IP address. ... server IP address is 81.137.105.244, this is a Internet IP address. ... not test VPN connection from your perimeter network. ... SBS on your switch to make it work. ...
    (microsoft.public.windows.server.sbs)

Loading