On Fri, Feb 18, 2011 at 4:51 PM, BobRoyAce <[email protected]> wrote: > We have a SQL Server 2005 database, on a server, that is currently > referenced by multiple Windows application clients who are running an > application on desktop PC’s that are on the same network as the server > that is running SQL Server. > > What we want to do is create an ASP.NET application that is running on > a web server box at our location. However, this box will be on a > different subnet. This application needs to be able to make database > calls to the database on the server that is running SQL Server. This > ASP.NET app/site would need to be visible to the “outside world” (i.e. > customers not at our location…anywhere in the US, really). So, > basically, customers would browse to the web site, and log in to the > ASP.NET application. The application would then run queries, sending > data back and forth to and from the database that resides on the > database server; a server that is on a different subnet. > > Could anyone give insights as to how to set something like this up? ----------------------------------
Do you have Network engineers or an Admin available? They will have to tweak the environment for you to do this easily. I operate in this same environment but I put in a work order and they give me the new address for the seerver for me to reference in my web.config file. >From the outside word that server fails to exist. HTH -- Stephen Russell Sr. Production Systems Programmer CIMSgts 901.246-0159 cell
