The IIS Licenses only will make you live on water & bread for a
considerable amount of time ... If the developer knew that this app
was to be used by mobile users, why did he/she use ASP ?????
I'd go for a VPN solution (ca. $5000 for a Watchguard firewall/vpn server)
and have them dial-in to your network.
You might be able to create an Access database, that you can fill up through
an XML interface ...
In the regard that it is an app that's used for use with clients, why not
create a secure website that the sales guys/gals can access from any internet
connection ?

Cheers,

W

>===== Original Message From dayseizerexcite.com =====
>I have an asp (Active Server Pages) application that I have to deploy
>locally to laptops. The thought process was, let's people used to seeing
>this app in their web browser, even though they're disconnected. Then it's
>available on the intranet, no learning curve.
>
>Problem is, now I'm faced with a couple thousand new IIS web servers
>(whether they like to admit it or not). Worse off, people are going to take
>these home and plug them into God knows what network. I'm starting to make
>list of things I want installed, disabled, etc, on these laptops. I have
>some questions about some of the things on my list:
>
>1) Configure the web site to only be acessible from 127.0.0.1 Can this
>address be spoofed on a w2k machine?
>
>2) Install a personal Firewall, block everything incoming. Will this
>interfere with requests to the Loopback interface?
>
>Does anyone know of any products that will run asp pages sans IIS/PWS? I
>know I have to point the browser "someplace." I'm wondering if there's a
>creative solution that doesn't require my workstations listening for http
>requests at all.
>
>Thanks in advance,
>-dazed
>
>
>
>
>
>
>_______________________________________________________
>http://inbox.excite.com

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]