LucaWe've used a simple system for our Intranet application.
- Our Active Directory domain name is ourcompany.internal (actually, we use our real company name, but I'd rather not put that on a public board).
- Our in-house DNS servers are integrated with Active Directory. Our DNS servers query OpenDNS for queries outside our internal network.
- Every machine in our network uses our inhouse DNS servers.
- the home page of every machine is set to http://server, which goes automatically to http://server.ourcompany.internal
Inhouse queries are handled by the Intranet server, and everything else goes to the Internet. There was no need to buy a domain name.
This was easy to set up, and it's worked flawlessly for years.
.. Geoff
Great!
Thank you again :)
As far as a webConnection app is concerned, there really is no difference between an "intranet" and a "internet" user. The same application can be called like this:
http://jkt07 (purely a local server with no outside connections) or via
www.jkt9000.com (a full blown internet web server). Same code, same setup, same everything. Just depends on how it is called.
Kevin
Dear friends,
a customer is aking to me if is possible to develop a "web" application running only through intranet. They would buy their www domain, but they would use the new application disconnected from web, at least during an initial time. They do not want a classical desktop Visual FoxPro application, but rather an intranet application running in browser and prepared to go to web when they will be ready.
Please, is it possible?
Thank you very much