Windows Server RRAS

SP,

If your client is a Windows shop, note that Windows Server includes "Routing
and Remote Access Server" (RRAS). In fact, RRAS is automatically installed
with Windows Server 2003. RRAS is very easy to configure, and it easily
handles authentication, even if the client is using a RADIUS solution for
authentication.

Depending on your dial-in capacity needs, you then install one-to-many
multi-modems in the server, such as the RocketModem III from Comtrol
Corporation. Of course, how you supply discrete dial-tone to each modem
port is just another piece of the overall solution.

From a software architecture perspective, I would still build an
"Internet-capable" application (i.e., use standard Internet protocols).
Just because an application is Internet-capable does not necessarily mean
the application must "face" or be exposed to the public Internet. I would
control access to the application via routing configuration and Access
Control Lists (ACLs) where appropriate. I suggest this because, regardless
of what the client specifications are *right now*, there will eventually be
that one influential road-warrior that says, "Hey, can I access the
application using my hotel's broadband connection...wouldn't that be faster
that dial-up...can you configure it that way before my trip tomorrow?"

Of course, your client's security needs and/or policies will ultimately
influence the design. Regardless of speed, many organizations still mandate
dial-in for certain security-sensitive applications. Your client seems to
be one of them...again...for right now.

Chris

"SP" <spasp_net@xxxxxxxxxxx> wrote in message
news:1147809319.388533.184200@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello All,

Thnaks in advance!

My clients have asked me to develop an application which will enable
them to access and view the data
over telephone lines without using internet as a media...

All help here will be appreciated!

Thanks,
sp



.

Relevant Pages

  • I receive odd queries from unknown remote systems.
    ... It was recently revealed to me that strangelooking queries like these are known to be generated in a Windows server Active Directory environment, with which I am completely unfamiliar and therefore seek your opinion. ...
    (microsoft.public.windows.server.dns)
  • Re: MVPs and Terminal Services
    ... Printer group is in the Windows Client org not in the Windows Server org ... Keep in mind that Windows Server 2003 is almost three years old, ... a TS environment is widely frowned upon). ... Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: 2nd route to LAN added when client connects
    ... RRAS may modify the routing table but should not create another default gateway. ... the RRAS on the server adds a 2nd route for the local LAN ... Before the VPN client connects, the routing table contains 10.0.0.0/24 with ...
    (microsoft.public.win2000.ras_routing)
  • RE: Cannot update SBS server with Microsoft or Windows Update services
    ... Windows Server 2003 Small Business Edition and on a Windows XP Professional ... tasks and was chatting with my client. ... all she does own the equipment and I have not solved her problem. ... Nobody mentioned MTU values and DSL in the ...
    (microsoft.public.windows.server.sbs)
  • RE: "Unable to obtain Access Token for machine name" every time I
    ... Security from Windows Server 2003 to Windows Server 2003 SP1? ... When I push the client ... Gave "system" temporary admin rights to problem pc. ... Reset the client push accounts and moved the remotedomain\domain ...
    (microsoft.public.sms.admin)