Lots of possibilities here... But probably the most obvious one would be to expose your private services in IIS on a different port, and don't expose that port through your firewall to the internet.
Greg Reinacker Reinacker & Associates, Inc. http://www.rassoc.com -----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf Of franklin gray Sent: Friday, April 26, 2002 4:42 PM To: [EMAIL PROTECTED] Subject: Web Service Design Can a IIS Server that is open to the public have web services on the same machine that are only accessable from the public web service? We are trying to design our app that it can be scaleable to a web farm, and the first web service determines which server to send the client, depending on who the client is. However, I would like to keep the same design for customers who don't have a web farm, which would mean that I would be sending them to a web service on the same machine and I would like that one to be private. I took a quick look at IIS manager and didn't see anything to set the V.D. to private. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
