i am deploying an ASP.NET 4.0 Application to a production server .
The server is an intranet server. In the binding of the site, I assigned an IP Address and a port number and it works fine in the form http://xx.x.xx.x:888/. Then I would like our user to use a friendly URL to access to the website. So I asked our IT manager to assign a friendly URL to this url. the friendly URL is like this http://sitename.mycompanyname.ca:888.
The problem is when I try accessing the site with the friendly URL it keeps pop-asking me for my credential and never lets me get into the site. Thanks for your helping.
Server environment:
Windows 2008
IIS 7.5
Server and users are all in intranet.
*Update:
If I stop the site, it gives me another "Internet explorer cannot display the page" error. So I guess this site is taking care of the request for this host name
I found that I can browse this site using host name if I am on the production server.But it doesn't work if I try on another computer.
Just found that It doesn't work with IE 9 32 bit but it works with Chrome and firefox, which is very weird...
*
The site's authentication and authorization is like below
I don't see that you mentioned this, but did you try adding the port to your friendly URL? ie. http://sitename.mycompanyname.ca:888 ?
Let us know!
Ricky
Enable anonymous authentication. That's it ;)
http://technet.microsoft.com/nl-nl/library/cc770966%28v=ws.10%29.aspx
Related
My workplace (~10 workstations and a server) serves a site via IIS 7 on Windows Server 2008 R2. (It's a MediaWiki wiki, nothing to do with ASP or .NET; and it's HTTP, not HTTPS.)
Users logged onto the Windows domain can visit the site by Intranet URL — OUR_MACHINE_NAME.local — and this works fine. However, the site is also accessible from the wider Internet (if you happen to know or guess the server's IP address), and for security reasons I want to prevent this. Only users logged into our Windows domain should be able to access the site.
I've spent a while experimenting with the Authorization settings in IIS, but nothing seems to have any effect. I also found some HTTP settings under "Windows Firewall with Advanced Security", but am not sure what I would need to change.
Can someone advise please? (Apologies for any wrong assumptions: I'm a programmer and have little experience of network configuration.)
I have a SharePoint site (http) hosted in IIS and it works fine on the intranet but when accessing through internet the prompt to key in the credentials keeps on popping and user is unable to login. I tried the suggestions mentioned here but those didn't help.
http://expertsharepoint.blogspot.sg/2013/10/sharepoint-site-is-prompting.html
Also I tried to add the website to "trusted sites" as mentioned in some of the links but that also didn't help.
So I enabled the https and now I am able to access through the internet but this way the app using the web services and SharePoint csom fails because of invalid certificate. Please know that I am aware of the workaround to ignore the invalid cert but that will require the code change in the whole app and I am not in position to do that.
My question is what else can I try and is there a way to access a SharePoint site by HTTP through the internet?
Thanks!
I am new to the web world, so I apologize if this question is silly.
I have an ASP.NET web site I wish to deploy.
The server has IIS 7 deployed on it, and I've added the site
to that IIS server as a web site.
For the time being I don't have a domain mapped to the site,
I would like the users to browse for the site directly by using the server's IP.
Is that even possible? because I failed to do it.
The only option that worked so far is using the hosts file to declare
a fake domain.
It would be nice if someone could clarify that issue for me.
Thanks a lot,
Omer
If you set the site bindings to IP address: All Unassigned on port 80, and do not provide a host name, then any request that makes it through to IIS should be served by that site. Make sure you stop any other sites that might have that binding (e.g., "Default Web Site" is normally bound to this).
In order to access the site by IP, you can't have the host name populated in IIS. Your best bet would be to use the "Default Web Site" that's already in IIS, and point that to your application.
Using IP is possible, but you need to make sure your users can see this ip from their machines.
I have a web site opened in VS 2008 . I try to run it from VS2008 and the asp.net development server starts up.But the browser returns the following error
Firefox can't find the server at www.localhost.
The web address in browser is http://localhost:2921/WebSite2/Default2.aspx
There is no such thing as www.localhost, and nothing built-in to asp.net will redirect you automatically (unless you tell it to). Sounds like you have code that looks at the url and redirects to a www version if you're not there. You shouldn't do that, and instead use relative urls internally that work no matter which way a user hits a page.
Check following :
Are your proxy settings correct in your Firefox browser. Firefox->Tools->Options->Network->Settings.
Are you browsing the correct address, everytime you run/debug your website a dynamic port is assigned unless explicitly specified.
I added the following entries in the HOSTS file.
127.0.0.1 abc.localhost.com
127.0.0.1 xyz.localhost.com
Using the VS2010 ASP.NET Development server I am unable to run or execute the website.
When browsing http://localhost:2687/TestProject/ it shows up the default.aspx page. But when accessing http://abc.localhost:2687/TestProject/ it shows a website cannot be found page.
Is there anything else to be done when setting up subdomain on localhost.
EDIT: To make this work I removed the .com and in IE-->Connections-->LAN uncheck everything. Subdomains with port works are correctly getting forwarded. Nothing else need to be configured.
Obvious mistake is that in your hosts file you have abc.localhost.com, whereas you are browsing to http://abc.localhost/folder
Not the same thing.
Not sure this will work as you intend anyhow. I would also recommend IIS Express, part of WebMatrix, which I think is still in beta, or just use IIS. IIS 7+ on Vista, W7, Server 2008 is all really easy to use.
Use IIS or IIS express, rather than Cassini. (For several reasons, which you can google or look for on stackoverflow)
With the IIS you can easily add a hostheader entry to you webapplication with just 2 clicks.
Be aware, that you are assigning both a Url and a port.
So adding abc.localhost won't allow you to browse abc.localhost2687, just the default port (80). If you also want to browse to abc.localhost:2687 you need to a a hostheader entry according to that that Url and port.
This screenshot shows you the dialog to add hostheaders (the picture is from IIS 6, but in IIS 7 or IIS 7.5 it looks very similar)