Re: locking down Terminal Server in SBS2003 environment (regular users)...not a duplicate question

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Claus,

You probably thought that you do not understand my question because of my
lack of verbiage. I just can not help myself sometimes! I guess, this time
I could!!!!! And, it is a bit of a weird situation.

One Forest (SBS32003) with the "HQ" in Richmond and a couple of "remote"
locations (no DCs in those remote locations just yet....). There is a
Firewall-to-Firewall VPN between Richmond and each location.

Now, the previous consultant placed another Forest in the Richmond office
that consists of one Server (naturally, a Domain Controller) that is also
the Terminal Server.

If - in the SBS2003 forest - there is a user account object with the user
name "UserA" and a password of "ABC123" then there is also a user account
object with the user name "UserA" and a password of "ABC123" in the "TS"
forest. Kinda silly....

The users in the remote offices have a hard time connecting to documents
located in the Shared Folders over the VPN. For example, there is a
spreadsheet that is 2.5MB in size. This is the main spreadsheet (again, we
inherited all this). If UserA is sitting at her desktop and goes to a
mapped network drive (pointing to a shared folder on the SBS2003
machine...over the VPN) it takes some two or three minutes for that file to
open. Then, once it is opened, if they try to do anything there are issues
saving those changes. I have seen this myself with several files. I
specifically asked three people to show me how they do things as we were
confused why they would access a TS over the VPN when they *should* be able
to do all of the same things from their desktop. Nope! Now, specifically
with the Accounting Software, the users have a hard time entering data as -
again, while sitting at their desktops connected over the VPN - the
connection is so slow that the users get way ahead of themselves when
entering data (they are on "Field 14" but the cursor is only on "Field
5"...they have to stop every 30 seconds or so and let it "catch up"). If
they are connected to the terminal server (which is sitting right next to
the SBS2003 server in Richmond) there are no issues what-so-ever. And,
naturally, the Accounting Software is indeed installed on the SBS2003
machine and the "client" part is installed on each workstation -AND- the
Terminal Server. Nothing unusual here.

They had Netgear Firewalls. We replaced them with SonicWalls. No change in
the VPN "speed" issues.

Once we are finished the users will typically make use of RWW (one of my
favorite toys in SBS2003) when working away from the office (there are
several that do not have an office!...so they make exclusive use of the TS)
as well as when they are in the office. I am not sure how they are going to
like having "all those clicks" with RWW (you know how end-users can be...)
when all they have to do right now is double-click the "Connect to Richmond"
RDP shortcut....We will probably have to train them!!!!

Thanks,

--
Cary W. Shultz
Roanoke, VA 24012

"Claus" <cjobes@xxxxxxxxxxxxx> wrote in message
news:efXQSFr$HHA.4956@xxxxxxxxxxxxxxxxxxxxxxx
There is no difference between SBS-land and enterprise networks. I'm not
sure I understand your question fully. When in the office they would
connect to the TS for the accounting. When they are on the road, they
would either connect to TS over RWW (preferred) or to their desktop in the
office (again RWW).

--
Claus
"Cary Shultz" <cwshultz@xxxxxxxx> wrote in message
news:eipEa1p$HHA.4496@xxxxxxxxxxxxxxxxxxxxxxx
Okay,

This is a second post....not a duplicate of the one I just created
regarding the Sales Force...

Anyway, kinda same situation, different client. We are going to be
putting in a TS in another environment where *regular* users will be
accessing the TS. That means, they will log into Windows to do the
majority of their stuff *BUT* the Accounting Package that they use will
be on the TS so that they can access it while away from the office (yes,
very familiar with RWW...this unfortunately will not work.....).

Again, very familiar with locking down a TS in "normal" Windows.

Several users (not all of them...just some) will log into their "office"
machine and - from the office usually - access the TS to do the
Accounting work. How do people do this in SBS-land?

Thanks again,

--
Cary W. Shultz
Roanoke, VA 24012





.

Relevant Pages

  • TS and/or RAS
    ... Terminal Services does NOT require the use of RAS ... unless you are connecting users via Dial-up (directly to ... many minutes over DSL w/ VPN. ... You can do this connected to a Terminal Server just like ...
    (microsoft.public.windows.terminal_services)
  • Re: COnnecting to Terminal Services with my PPC
    ... When connecting to with tS are you using the IP or fdqn of the computer to ... If so you need to add those ip's/fdqn's to the exceptions in the ... allow those addresses to be access through the vpn. ... > How can I connect to my Terminal Server using a VPN on my iPaq 2210? ...
    (microsoft.public.pocketpc)
  • Re: COnnecting to Terminal Services with my PPC
    ... When connecting to with tS are you using the IP or fdqn of the computer to ... If so you need to add those ip's/fdqn's to the exceptions in the ... allow those addresses to be access through the vpn. ... > How can I connect to my Terminal Server using a VPN on my iPaq 2210? ...
    (microsoft.public.pocketpc.activesync)
  • RE: SBS 2003 and shared folders through VPN
    ... SBS 2003 Shares over VPN ... Corporate information is shared on folder "Main" there is also the network ... Firewall is providing the VPN over a T1 circuit. ... | has no problems connecting to the internet nor is the share drives not ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN with MN-700 router. How to set up the Broadband Utility?
    ... What do you mean "you only know of connecting to a VPN through a dial-up ... > can't ring another number through a broadband modem. ... >> My suspiscion is that the Microsoft MN-700 router is not properly ...
    (microsoft.public.windowsxp.network_web)