It is possible, but how you do it really depends on how your VPN
connections are configured. In my opinion, the move from NT to W2k3 will be
the big thing rather than the VPN question.
If you have site to site VPNs configured so that any machine on your WAN
can directly "see" the server (which appears to be the case), you can do
this quite simply. It works the same way as if the machines were on the same
LAN (only slower). You would not need terminal services.
The big difference (from NT) is that Active Directory in W2k/2k3 is
tightly integrated with DNS. You will need to have the machines in the
satellite offices using the DNS service associated with your AD setup for it
to work smoothly. AD uses DNS for all sorts of things which were handled by
Netbios names in NT (like finding a DC to log on).
As with NT, clients can access shares without actually being domain
members, but you may need to relax the security settings on the server if
you have older (or non-Microsoft) clients. By default Server 2003 requires
MS-CHAP v2 I think. I would certainly aim at making all client machines
domain members. Is that how your current setup works?
The main reason for using Terminal Services is to avoid problems of
latency in VPN connections. Some tasks (such as database operations) can
time out when performed across a VPN link. The solution is to use Terminal
Services, so that the client and server side of the database app are both on
the high-speed LAN. Only the KVM data has to cross the slower VPN link.
"neves7" <(E-Mail Removed)> wrote in message
news:9D239CF2-22E3-436B-9BBF-(E-Mail Removed)...
> Basically, I would rather not use terminal services. The satellite
> computers
> are currently using the VPN to tunnel through to shared folders on my
> current
> NT 4.0 server. I would like them to be able to log in and use the security
> features of 2003 server through the VPN without using Terminal Services.
> Is
> this possible?
>
>
> "Robert L [MVP - Networking]" wrote:
>
>> Not sure I understand the question. What you need to do is install
>> terminal Services. The remote users can access the TS using RDC after
>> establishing the VPN.
>>
>> Bob Lin, MS-MVP, MCSE & CNE
>> Networking, Internet, Routing, VPN Troubleshooting on
>> http://www.ChicagoTech.net
>> How to Setup Windows, Network, VPN & Remote Access on
>> http://www.HowToNetworking.com
>> "neves7" <(E-Mail Removed)> wrote in message
>> news:7890E176-04F7-405D-940D-(E-Mail Removed)...
>> Hi,
>>
>> I have 9 satellite offices and 1 main office. Each office is connected
>> through VPN via routers to my main office router. the 9 office have
>> about 2
>> to 3 employees in each office
>>
>> I am going to be installing Server 2003 next month and would like the
>> employees in the satellite offices to be able to login to the new
>> server
>> through the VPN.
>>
>> My question is: Do I need terminal services to accomplish this, or can
>> the
>> employees login with only the VPN connection to the main office to the
>> new
>> server. Thanks in advance