Bill,
my 2 cents!
-use dedicated NT4.0 or 2000 Server box (Linux would be better, only if you
have working knowledge)
-connect directly to a new dedicated DSL modem/line using NIC in dedicated
server (for only inbound traffic)
-connect dedicated server to internal network via second NIC card (keep
database off dedicate server)
-use existing DSL method of access to the internet for existing outbound
traffic (use for access to the dedicate server via internet)
-Secure the IIS and server services(little work here lots of stuff on MS
site about doing this)
-Use software firewall to monitor and control access to dedicated server (if
not secure with only using MS controls)
Performance:
-Check the true bandwidth that you have with the existing DSL connection
(www.dslreports.com)
-if you're getting 90% of rated bandwidth or better then use DSL
-Optional connection to internet use a frame relay or T1 provides true
bandwidth but at a higher cost
sites that may give you little more info about what your trying to do!
http://docs.rinet.ru:8083/NTServak/nt19fi.htm
http://207.207.66.90/isaserver/news/press_partner.asp
Best regards,
Oma
>Bill Downall wrote:
>
>> I am preparing a proposal for an R:Tango solution. The client is
>> interested in the possibility of hosting their R:Tango application from
>> their own office, through a Synchronous DSL line. Does anyone have
>> experience doing this? What are the practical limits for performance
>> for them.
>>
>> They also would like to use the same physical database within their
>> office from R:Base for DOS and R:Base for Windows, through a Novell
>> network, while their customers and associates are inserting, and
>> updating items through the internet.
>>
>> What experience and advice can you share on protecting their internal
>> network from hacking in such a setup?
>>
>> Thanks
>>
>> Bill
