| Groups | Blog | Home |
inetserver asp db : ASP on local network?
Hello. Sorry if this doesn't sound like much sense but is it possible to
run .asp pages on a local internal network server (not the development \localhost\ address and not on the public internet)? I have a bunch of .asp pages and was wondering if it was possible to make use of all of the written ..asp code (including calls to SQL Server stored procedures) instead of putting them on the webserver could i put them on a local internal network server for users to access?...or does it need to have IIS to run these on the web server only. Thanks in advance. J
[quoted text, click to view] "J" <IDontLikeSpam@Nowhere.com> wrote in message news:%23D7KmVLRHHA.1208@TK2MSFTNGP03.phx.gbl... > Hello. Sorry if this doesn't sound like much sense but is it possible to > run .asp pages on a local internal network server (not the development > \localhost\ address and not on the public internet)? Not quite sure where to start to unravel the confusion... Consider that "localhost" is sort of a built-in host name (by virtue of its inclusion by default in each system's HOSTS file) that resolves to the IP address 127.0.0.1, aka, the loopback address. Every system with working IP stack has a loopback address, using which, IP-enabled software can communicate within the confines of a single system. Beyond that, "localhost" is treated as any other host name -- if you wanted to (and you were insane) you could configure a DNS server to return some other address for that name -- but you'd need to alter HOSTS for every machine you wanted to use it, because entries in HOSTS take precedence over external DNS. There are 3 sets of IP addresses defined by RFC1918 that are called "non routable" because they are designated for local use only. The most commonly used ones are 192.168.*.* and 10.*.*.*. Any host using an address defined by RFC1918 is not accessible to the public Internet USING THAT ADDRESS. Note that there are any number of DMZ and/or NAT/PAT schemes that translate private addresses to public ones, but those are the exception, not the rule, and must be explicitly set-up that way. Point being that if a host, be it "server" or "workstation" has an address that starts with 192.168. or 10., I cannot reach it using that address, via the public Internet. (My gut instinct at this point is to scratch this reply and leave it to someone else.) The short answer is, yes, it's possible, using a private address (and an internal DNS server, if you want people to be able to browse to a host name, instead of an IP address.) [quoted text, click to view] > I have a bunch of .asp pages and was wondering if it was possible to make > use of all of the written .asp code (including calls to SQL Server stored > procedures) instead of putting them on the webserver could i put them on a > local internal network server for users to access?...or does it need to > have IIS to run these on the web server only. More semantics confusion: a "local internal network server" can be a "web server" these terms are not mutually exclusive. Your local system is technically a "web server" if it answers HTTP requests on any address, not the least of which being the loopback. Yes you need IIS running. No the server does not need to be publicly accessible. These details are not interconnected, IIS doesn't care about RFC1918, it only needs an IP address, it doesn't even care if any other host can reach it, that's not its concern. It only knows that if, perhaps by random chance, perhaps by design, some other host actually does reach it, to send it a request that fits the HTTP protocol, it needs to answer it, based on the configuration/content defined for it. Making that HTTP server's address reachable by anybody or everybody is a completely separate matter; making it reachable using a friendly name, yet again another separate matter. Hopefully (though I realize odds are against) I haven't added to your confusion -- apologies if that is the case (it may be hard to believe, but that was surely not my intent!) :-) -Mark [quoted text, click to view] > Thanks in advance. > > J >
Will look into this. So sorry for the weird question. Thanks a bunch for
your quick and descriptive reply Mark. Much appreciated. Take care. J [quoted text, click to view] "Mark J. McGinty" <mmcginty@spamfromyou.com> wrote in message news:%23Y7XdEMRHHA.4404@TK2MSFTNGP03.phx.gbl... > > "J" <IDontLikeSpam@Nowhere.com> wrote in message > news:%23D7KmVLRHHA.1208@TK2MSFTNGP03.phx.gbl... >> Hello. Sorry if this doesn't sound like much sense but is it possible to >> run .asp pages on a local internal network server (not the development >> \localhost\ address and not on the public internet)? > > Not quite sure where to start to unravel the confusion... Consider that > "localhost" is sort of a built-in host name (by virtue of its inclusion by > default in each system's HOSTS file) that resolves to the IP address > 127.0.0.1, aka, the loopback address. Every system with working IP stack > has a loopback address, using which, IP-enabled software can communicate > within the confines of a single system. > > Beyond that, "localhost" is treated as any other host name -- if you > wanted to (and you were insane) you could configure a DNS server to return > some other address for that name -- but you'd need to alter HOSTS for > every machine you wanted to use it, because entries in HOSTS take > precedence over external DNS. > > There are 3 sets of IP addresses defined by RFC1918 that are called "non > routable" because they are designated for local use only. The most > commonly used ones are 192.168.*.* and 10.*.*.*. Any host using an > address defined by RFC1918 is not accessible to the public Internet USING > THAT ADDRESS. Note that there are any number of DMZ and/or NAT/PAT schemes > that translate private addresses to public ones, but those are the > exception, not the rule, and must be explicitly set-up that way. Point > being that if a host, be it "server" or "workstation" has an address that > starts with 192.168. or 10., I cannot reach it using that address, via the > public Internet. > > (My gut instinct at this point is to scratch this reply and leave it to > someone else.) The short answer is, yes, it's possible, using a private > address (and an internal DNS server, if you want people to be able to > browse to a host name, instead of an IP address.) > > >> I have a bunch of .asp pages and was wondering if it was possible to make >> use of all of the written .asp code (including calls to SQL Server stored >> procedures) instead of putting them on the webserver could i put them on >> a local internal network server for users to access?...or does it need to >> have IIS to run these on the web server only. > > More semantics confusion: a "local internal network server" can be a "web > server" these terms are not mutually exclusive. Your local system is > technically a "web server" if it answers HTTP requests on any address, not > the least of which being the loopback. > > Yes you need IIS running. No the server does not need to be publicly > accessible. These details are not interconnected, IIS doesn't care about > RFC1918, it only needs an IP address, it doesn't even care if any other > host can reach it, that's not its concern. It only knows that if, perhaps > by random chance, perhaps by design, some other host actually does reach > it, to send it a request that fits the HTTP protocol, it needs to answer > it, based on the configuration/content defined for it. > > Making that HTTP server's address reachable by anybody or everybody is a > completely separate matter; making it reachable using a friendly name, yet > again another separate matter. > > > Hopefully (though I realize odds are against) I haven't added to your > confusion -- apologies if that is the case (it may be hard to believe, but > that was surely not my intent!) :-) > > > -Mark > > >> Thanks in advance. >> >> J >> > >
Thanks for the info Athony. Much appreciated.
Take care. J [quoted text, click to view] "Anthony Jones" <Ant@yadayadayada.com> wrote in message news:eGBcoOSRHHA.3996@TK2MSFTNGP04.phx.gbl... > > "J" <IDontLikeSpam@Nowhere.com> wrote in message > news:%23D7KmVLRHHA.1208@TK2MSFTNGP03.phx.gbl... >> Hello. Sorry if this doesn't sound like much sense but is it possible to >> run .asp pages on a local internal network server (not the development >> \localhost\ address and not on the public internet)? I have a bunch of > .asp >> pages and was wondering if it was possible to make use of all of the > written >> .asp code (including calls to SQL Server stored procedures) instead of >> putting them on the webserver could i put them on a local internal >> network >> server for users to access?...or does it need to have IIS to run these on >> the web server only. >> > > You need an IIS server. > > If you can access them as a developer as http://localhost/ then you can > also > access them as http://<yourmachinename>/ > > Other users on your LAN can also access those pages as > http://<yourmachinename>/. > > If you don't want others accessing your machine as an IIS server since > it's > the development machine the you can probably pick on any XP Pro machine > with > IIS installed to act as the server. Just don't try to use it too heavily > since XP has the number of inbound connections it will serve capped pretty > tightly. > > >> Thanks in advance. >> >> J >> >> > >
[quoted text, click to view] "J" <IDontLikeSpam@Nowhere.com> wrote in message news:%23D7KmVLRHHA.1208@TK2MSFTNGP03.phx.gbl... > Hello. Sorry if this doesn't sound like much sense but is it possible to > run .asp pages on a local internal network server (not the development > \localhost\ address and not on the public internet)? I have a bunch of ..asp > pages and was wondering if it was possible to make use of all of the written > .asp code (including calls to SQL Server stored procedures) instead of > putting them on the webserver could i put them on a local internal network > server for users to access?...or does it need to have IIS to run these on > the web server only. > You need an IIS server. If you can access them as a developer as http://localhost/ then you can also access them as http://<yourmachinename>/ Other users on your LAN can also access those pages as http://<yourmachinename>/. If you don't want others accessing your machine as an IIS server since it's the development machine the you can probably pick on any XP Pro machine with IIS installed to act as the server. Just don't try to use it too heavily since XP has the number of inbound connections it will serve capped pretty tightly. [quoted text, click to view] > Thanks in advance. > > J > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |