Re: Question about Home PC connected to SBS via VPN....

From: Jeff Middleton [SBS-MVP] (jeff_at_cfisolutions.com)
Date: 03/04/04


Date: Thu, 4 Mar 2004 11:46:48 -0600

As Les suggested, it is far easier to address this idea if you use an RDP
session to gain control of the PC at your office, or use a TS Apps server to
RDP into. Making the remote link is easier with RWW than creating a VPN and
then doing RDP....the SBS RWW solves it for you automatically.

Now, for the specifics of what you indicated.....

If you have your home computer as not a member of your office domain, then
you can't really use a remote logon to give you the shared resources for My
Docs, Desktop, Apps Data, etc. The reason is that those folders are part of
the profile that is loaded into your user session (at your home computer) at
the time you first authenticated and logon at the local machine. That's why
if you were part of a domain with the home computer, you could potentially
configure it, but if you are not....you can't.

For the moment, let's assume that you are using computer at home that is a
domain member. If the DSL link is always on, you could configure the VPN as
a Dialup Networking option, and then at the primary logon configure "Logon
with Dialup Networking" so that your intial logon is authenticated by the
SBS in the manner that your PC at home first builds the VPN before beginning
the user logon itself. Once the VPN is present, you computer now
authenticates your logon session. If you have your workstation configured as
part of a domain Group Policy control to redirect folders, or to do roaming
profiles, now those processes can occure because the domain is actually
processing the logon. The only problem now is if your system is going to
behave well with the profile information located over a low-bandwidth DSL
link. Some things that are in AppsData are going to make the session
sluggish. If you just redirect your MyDocs and Desktop, this isn't too
horrible until you go to open something other than a link on the desktop.
For instance, if you have that 2.5 Mb JPG photo of your dog sitting on the
desktop, when you click to open it.....slowly.....it.....comes.....over
....the ....DSL.

That's why it is better to RDP, or VPN and RDP, or RWW to take control of a
workstation that is locally in the LAN at your office and just run a session
that remains entirely local in that LAN.....only the RDP session screen and
keystrokes move back over the wire.

Returning to the other idea of configuring Outlook if you have a home
computer that is a domain member, you could use the normal Outlook process,
or better would be to configure the profile as RPC over HTTP if that's all
you need, but either way, you can get Outlook to work remotely okay as long
as you don't try to sync massive amounts of stuff over the wire, or cache
things on both ends with Offline folders. Outlook 2003 is better at handling
this than previous versions.

"Cassandra" <cassandramiller@ureach.com> wrote in message
news:7636d3c0.0403032154.5156ca9c@posting.google.com...
> Hi All,
>
> I have a quickie question about setting up a Home PC and remotely
> connecting it to an SBS 2003 server via a VPN. I created and used the
> remote connection disk on my Home PC, and now the Home PC connects to
> the office SBS Server via an aDSL connection. I got Outlook to
> connect with Exchange which is very kewl. But I still haven't quite
> figured out how to have the Home PC's My Documents & My Desktop &
> AppsData folder link to the same one's that reside on the server which
> my User Profile plugs into. Is this at all possible???
>
> Or in fact, would be even better, would be to simply log in on my Home
> PC upon start up as I would on a workstation directly connected to the
> SBS lan, and have all my same files in the same places on my computer.
> I tried doing this already, but it tells me after I log in, that the
> connection to the SBS server is not available...thus I'm stuck logging
> into my Home PC profile, and double clicking the "connect to SBS
> Server" on my desktop to establish a VPN connection.
>
> Are there any instructions anywhere on how to accomplish this?
>
> ~ Hugs & Kisses ~
>
> ** CaSsIe **



Relevant Pages

  • Re: Spurious TermDevServices Event 1111
    ... Thanks, Les, but I rather like the option to use my local printer in the RDP ... > the option to connect printers in the RDP session. ... > SBS Rocks! ... ActiveTouch Document Loader is a pseudo print driver ...
    (microsoft.public.windows.server.sbs)
  • SBS 2008 - Multiple RDP Sessions?
    ... I've done 2 SBS 2008 rollouts now and neither of them will ... allow me to RDP in with more than 1 session. ...
    (microsoft.public.windows.server.sbs)
  • [NT] Cryptographic Flaw in RDP Protocol Can Lead to Information Disclosure
    ... The Remote Data Protocol (RDP) provides the means by which Windows systems ... The first involves how session encryption is implemented in certain ... An attacker who was able to eavesdrop on and record ...
    (Securiteam)
  • Re: Windows logoff bug possible security vulnerability and exploit.
    ... To reproduce the problem, I just use the computer normally, and at each logon check the event viewer and running processes to see if a profile unload failed. ... I find that if I wait for a little bit after logging off before logging on again, no running programs from the previous logon are present, but if I log on just after logging off, they will be if the profile unload fails. ... When logging on, the first logged on user is given session ID 0, as shown in task manager, but if I 'switch' to another user, the user is given a different session ID. ... A few moments ago I logged in as administrator to do some minor changes, and I ran EPIM to take some notes of things. ...
    (Bugtraq)
  • RE: TS disconnects when minimized a couple minutes
    ... Here's what I have set up recently to try to resolve my terminal services ... End a disconnected session - Never ... >> When I open a remote desktop session from any computer within my SBS 2003 ... >> As I mentioned in my last question, if the remote server is win2003 it will ...
    (microsoft.public.windows.server.general)