ASP.NET works with IIS. You access ASP.NET applications through a web browser. Whatever you've configured a particular IIS installation's server name to be, is how you access it, via WAN, LAN... whatever.
tgreer
Made Her Cry
2,118 posts since Dec 2004
Reputation Points: 227
Solved Threads: 37
I cannot tell you anymore than I already have:
You access via a browser:
http://servername/appname
The "servername" is the name you've given the IIS server. That's all there is to it - there isn't a big mystery here.
You can also access via IP address:
http://192.168.xxx.xx/appname
tgreer
Made Her Cry
2,118 posts since Dec 2004
Reputation Points: 227
Solved Threads: 37
That should work fine, if IIS is installed properly:
http://server_name/folder/appname.aspx
So, you likely have an IIS configuration issue, which is outside the scope of this forum. You should post in the Site Configuration section.
You need to test first:
1) Can you access your app on the machine itself, using "localhost" as the server name?
If this test fails, you don't have IIS running correctly.
2) Can other machines access the app, using the IP address of the IIS server as the server name?
If the this test fails, then you have a network configuration issue. 192.168 numbers are "local IP" addresses, and your network could be divided into subdomains, you could have a firewall on the machine blocking inbound traffic - all sorts of issues, none of which are ASP.NET questions!
tgreer
Made Her Cry
2,118 posts since Dec 2004
Reputation Points: 227
Solved Threads: 37