I am very new to working with ASP, like less than 24 hours new! :)

I created a database in MS Access, I created an HTML Form, and then created an add_to_database.asp page and a database.mdb document. I can run my ASP pages and add information using the computer I created the database and ASP pages with, but when attempting to view the pages from a networked computer in IE, all I get is the actual asp code displayed in IE.

Do I really need to install iis on every networked computer in order to view ASP pages??? I never had to before when viewing an ASP webpage on the internet.

Thanks for any help. - Bob

mmm.. looks like you have other problems.. most probably with the way IIS is configured...

just point a virtual directory of the IIS to the folder you are using in development, and it will work...

HTH

Gonzalo

Ok, my asp files and database are located in c:/inetpub/wwwroot/
I created a virtual directory through the IIS with the alias: database
I then browsed my computer for the path and selected the c:/inetpub/wwwroot/ folder.
I then went to a network computer and typed in http://station1/database/
And it brought up nothing. I do have an index.html file in the wwwroot directory, but I can't get it to pull up. I am on the same workgroup name, and can pull up files from the main computer. If I simply just open up the asp file in IE from my network computer, I continue to just get the asp source code.

Ok,
  Doing just http://station1/database/ *should* give you an error! The reason is because you have an index.html, unless you have edited the default documents in IIS, this will return an error because IIS is setup to look for index.htm, default.htm, index.asp, default.asp etc etc. So try to connect to http://station1/database/index.html

What version of IIS are you using?

What OS is the pc you are trying to connect to?

Just so we are clear, is this .NET 1.1 or Classic 3.0? (Classic should run by default when IIS is installed) .NET on the other hand can get quirky. Consider this secnario:

If you have X machine with the 1.1 framework installed on it and you install IIS AFTER the framework is already installed, you need to register .NET with IIS (if IIS is installed before the framework, the framework will prompt you to register with IIS)

To register .NET with IIS navigate to here in a command prompt:
%systemdrive%\WINDOWS\Microsoft.NET\Framework\<ver sion> (version should be: v1.1.4322 or 1.0.3705) once there type this command:

aspnet_regiis -i

This will register the framework with IIS

hth.

--Stole this from a moderator

I will only tell you how to do it, not do it for you.
Unless, of course, you want to hire me to do work for you.

Thanks for working with me on this.

My IIS version is 5.1
My OS is Media Center 2005 sp2
In c:/WINDOWS/Microsoft.Net/Framework/

I have the following folders:
v1.0.3705
v1.1.4322
v2.0.50727

I did the registration of .NET to IIS as to your instructions with the v.2.0.50727, and it still didn't work. So I tried it with v1.1.4322 and nothing worked still.

I do have an index.htm file in the wwwroot folder. And I can also access the virtual directory from the computer I created it with, which is the Media Center 2005 computer.

But when attempting to pull up http://station1/database/ from a network computer that is running Windows XP Pro sp2 (Station2), I get a "Page can't be found". I can go to my workgroup computers and I can see my Media Center 2005 computer (Station1), and can go to the wwwroot folder that way, but by doing it that way, I can't view the asp files correctly.

Is there some permission settings that I do not have correctly on the wwwroot folder? All I have under that is the options for Administrator and Everyone, which they are both set to full permissions.

Under Control Panel - Folder Options - View, I have the Simple File Sharing disabled, per a tutorial I read elsewhere.

From the pc you are tyring to view the page from, go to a command prompt and type

ping http://station1/database/

See if it pings correctly. (doesnt time out)

Also what happens if you try doing http://station1/database/index.htm

--Stole this from a moderator

I will only tell you how to do it, not do it for you.
Unless, of course, you want to hire me to do work for you.

hmm, when I ping it says it can't find host. That would explain why things aren't working, but what is it that I need to do to make Station1 accessible? When using station2, I can access station1 through the control panel - network - workgroup

thanks

Can you ping the IP address of station2? If you can ping that, just do http://<ip>/database/ let me know.

Also, are you sure that the pc's name is station2? (I am not insulting your intelligence but i have to ask)

Also, on the host machine itself, can you do http://localhost/database/ and view the page?

--Stole this from a moderator

I will only tell you how to do it, not do it for you.
Unless, of course, you want to hire me to do work for you.

:) no problem!

My host computer is Media Center 2005
Host computer name: station1
Host computer IP: 192.168.1.120

From the host computer, I can bring up http://localhost/database/ in IE. As well as http://station1/database/ .

I can also ping the following from the host computer using the following commands:

Ping 192.168.1.101 OK (this is the station2 networked computer)
Ping station2 OK (this is the networked computer)
Ping 192.168.1.120 OK (this is itself)
Ping station1 OK (this is itself)
Ping http://station1/database/ (I get can't find host message)
Ping http://192.168.1.120/database/ (I get same host message above)


My network computer is Windows XP Pro
Network Computer name: station2 (I double checked)
Network Computer IP: 192.168.1.101

From the network computer (station2) I can ping by doing the following commands:

ping 192.168.1.120 OK
ping station1 OK (shows 192.168.1.120)
ping http://station1/database/ (can't find host message)
ping http://192.168.1.120/database/ (can't find host message)

From the remote pc can you do:

http://192.168.1.20/database/

--Stole this from a moderator

I will only tell you how to do it, not do it for you.
Unless, of course, you want to hire me to do work for you.