Recenly a network card was intalled on the server so that I can have a new IP address for my application.
Whend deploying the application on the server using IIS (using the "add site" feature) and then test the site , the site works perfectly fine from withtin the server
but when I try to access it from outside the server I get the message saying that the site is not reachable
any reason why this is happening ?
Sounds like a firewall issue. First make sure the windows firewall isn't blocking IIS. Also make sure your IT team has setup that IP address as an external server.
A few other questions about your server
1) What type of services are you hosting and is it on the standard ports? (Exhaustive list of ports on Wikipedia)
2) What version of IIS are you using?
3) Do you have a firewall/load balancer/etc between your server and the web?
Related
I'm running a ASP.NET on my pc and I would like to access to that app from another pc on the same network. I've tried to reach the app writing the URI of my pc on the network followed by the port number as below:
"192.168.X.X:49223/"
But it shows me an 400 error saying that it's an invalid hostname...
Is there something to do with my windows firewall or in IIS to allow access from another PC ?
Thanks for your help.
You may need to an exception in Windows Firewall.
Control Panel > Windows Firewall > Advanced Settings > Inbound/Outbound rules.
Add a new rule to both, specifying your port number and a generic name to identify its purpose.
Install IIS server on your machine, then deploy your application on that IIS server.
Refer this for Deployment assistance
To run the application on IIS instead of ASP.Net dev server you need to
Right click on solution in VS
Click on Start Options..
In Server section, Select "Use Custom Server" and then provide the URL of the application you have added earlier on IIS
Then you can easily access your website from any other machine on the same network.
Is it hosted in iis, or are you running it through Visual Studio. The funny port number (49223) tells me it's the latter.
When you run a VS project, the dev server is designd to only allow local conconnections. If you connect from a network it gets blocked by design. Their is no config around it.
What I do as a hack is run a reverse proxy like Nginx. It's a free download. Run it on your dev machine. You can tell it to listen on a port (eg 88) and then redirect tge traffic to port 49223. Give your mate the same url as before but replace the port with 88
Nb make sure your port 88 is open as per codemans answer
An example of the nginx config would be https://gist.github.com/ekinertac/5524389
This then tricks VS into thinking it came from your local machine.
I have a window server 2008 with an IIS 7.0 and Static IP. The website www.xyz.com (with PORT: http:80 & https:443) is running well on it. Now, I deployed another website on it using same IP address but with Port http:180. The another website is working good locally but not accessible on web.
What are next steps to make website online?
Regards,
Aman
That should be it. If you can access it locally with http://localhost:180, then IIS is listening on the port and should be serving requests. If you are not able to access it remotely via http://the.site.ip.address:180, I would suspect that a firewall somewhere is preventing connections over this non-standard port.
I have application..its runnning on my localhost.. i need one more machine to access that application.. but when in tht link i type my IP address instead of localhost.. it showing cannot find server.. can you plz tell me steps what i need to do in orderr to access appplication to other machine.. as such there is no UAT server as of now...
First off, make sure your firewall allows access through port 80.
Then, check if your IIS allows access from outside IP's.
I can help more if you provide this:
Your OS (XP, Windows 7, etc)
the local link to your app. Is there a port number needed to access the app?
LaterEdit: Ok, then you need to do this:
Now, your app will be served by IIS on port 80 (default). Check your firewall to allow traffic through this port.
If you IIS is set for another port, then use that one.
Checking the port in IIS:
I'm going to assume that you are running the application from Visual studio which allows the localhost to run.
In order for your application to be available to other machines on the network, you have to ensure that IIS is installed on your development machine and then a website is set up for that application as well.
The application existing in IIS is what will make it accessible across your network.
I have 2 servers, server A and server B. Both have IIS7 and same OS. I published through my VS2008 the same website on both servers. the problem is on one the application in IIS7 website works on the other it doesnt.
Server A - IIS7 - WebsiteA - Application (Works)
Server B - IIS7 - WebsiteA - Application (Does not work)
what are the things that i could be missing to configure IIS7 in server B ?
You need to find out what machine the IP Address is referring to.
It's possible you have firewall's, routers, and host configuration files which are effecting this.
Run a tracert to your server, and to the ip address and see where your route is going wrong.
Check you don't have multiple IP Addresses assigned to the same machine.
If you can, ask a member of your network team to help you out.
To help you more, we need to know the details of your infrastructure.
I have Deployed my Asp.net web application on IIS 7.0 on localMachine(Server) and it is working fine there.
But when i try to access it from other machine in LAN, It gives me error that, 'Internet Explorer Can Not find this Page.'
I am accessing it on terminals using server name address and also tried using IP address.
Even I have Shared the Application Folder in network.
Check the Windows Firewall on your Vista PC. You need to let TCP port 80 through.
Make sure that you enable the firewall and bind to IP addresses other than localhost.
You don't need to and should not share the application folder.
This is a security risk as people on the network will be able to access the source code of the application. Also, it won't help with the problems you're having because a network share is not accessed over HTTP and so will never hit IIS and your web application. So you can turn off sharing for the folder and be safe in the knowledge that this isn't the issue.
Next, check your windows firewall and make sure incomming web trafic is allowed ("http" or "port 80").
Next I would have a look at the host headers that the site is running on.
Then maybe update your question with more detail.
Greg
You may also want to ensure that IIS is listening on the correct IP Address. This problem can occur if you switch from a LAN connection to a wireless connection (for example when taking a work laptop home).
To Check this, open inetmgr and right-click on the 'Default Web Site' node. Verify that the IP Address entry is set to the current IP of your machine.