Ok wenzation, look I'm sorry I was a bit short with you. I can see you're confused about the whole thing, I should be more patient. Sometimes these things are hard to communicate with just messages.
Let's see if we can sort out some of the confusion by starting with the basics of what you want to do. You tell me if I've got the wrong idea, OK? Here goes:
Your company has some files in a network folder and they want you to develop an ASP page that will run on the company intranet and allow users to search for files in this network folder and display links to any files matching the search. That's it right?
OK, lets try and clear up the confusion about IIS. There are two scenarios we have to deal with:
1. you need to develop and test these ASP pages
2. when you've got it all sorted you need to get your ASP on to the company intranet
Your ASP needs to be done in such a way that the code doesn't need to be changed to go from 1 to 2.
For 1. you will need to have IIS so that you can develop and test your ASP pages. IIS can be either on your own PC, or you will need access to a development web server that is already running IIS. Either way lets refer to this PC as DEV.
For 2. there will already be a webserver that hosts the live Intranet, and obviously this PC will already have IIS. Lets call this one LIVE.
I think some of the confusion has arisen because I am talking about DEV but your IS people are talking about LIVE. From your earlier comment "I approached my IS department and they told me to do my stuffs of this intranet website in this network folder because it's already path for our asp." it sounds like LIVE already has a virtual directory set up in IIS which is mapped to this network folder.
What you need to do is get DEV set up so that it mimics the folder structure of LIVE (well, not the whole folder structure just the bit that concerns these network files and the ASP pages that will search/display them). Maybe an example would help here. Let's say, just for the sake of example, that the network folder is mapped to the LIVE IIS as
http://LIVE/subfolders/pages/lanfolder and your ASP pages when finished will go in
http://LIVE/subfolders/pages. In this case DEV just needs a setup like this, but ignoring the subfolders bit, so you need
http://DEV/pages and
http://DEV/pages/lanfolder. To get this set up on DEV the stuff that I posted before about setting up a virtual directory is what you will need. This virtual directory is also the answer to your question "Do you know how to exactly communicate with the two servers?"
Finally UNC paths: UNC stands for Universal Naming Convention. Its a way of referring to network folders (and the PCs which host those folders) without using Windows drive mappings. For example lets say that my PC is called PGTIPS and on that PC I have a folder D:\stuff\goodstuff which I decide to make public, so I set up a windows share named PGSTUFF and give read access to Everyone. Then other people on the network can simply open up Explorer and type \\PGTIPS\PGSTUFF in the address bar and bingo they get a list of the files in that folder. (Other people can also set up a Windows drive mapping to that folder, so they could get windows to map \\PGTIPS\PGSTUFF to say drive H:. But the thing is that H: would only be available to the user that set-up the drive mapping - if another user logged in to their PC they would not have H: available).
So, in summary, I think you need to:
1. find out the set-up of LIVE and where this network folder and your ASP pages fit into this set-up.
2. get access to a DEV webserver and set it up so that the relationship between the folder where your ASP pages will go and the network folder you want to search is the same as on LIVE (this will ensure that your DEV ASP does not need to be changed to fit on LIVE).
I hope this helps you. Let me know If I've misunderstood anything, and please feel free to post other queries about this. :D
rgds
Phil
Server Drives and network folders...
