current community

your communities

more stack exchange communities

Stack Exchange
tour help
careers 2.0
Take the 2-minute tour ×
Stack Overflow is a question and answer site for professional and enthusiast programmers. It's 100% free, no registration required.
up vote 0 down vote favorite

I have deployed my C# ASP.NET Visual Studio Express 2013 project via the IIS internal Express webserver service.

Locally its great - I can access it at : http://localhost:56473/hello

However if from another PC on my internal network I try to access it via :http://192.168.0.2:56473/hello it gets an http 400 bad request!?

Any ideas - anything obvious I am missing?

share|improve this question
2  
Yeah, is your machine accessible from the rest of the network? Do you have the site in IIS configured to use that IP address? –  John Saunders yesterday
add comment

2 Answers

up vote 2 down vote accepted

IIS Express isn't for external hosting.

If you want to see your work from an external client, install IIS from the programs and features.

Control Panel > Programs and Features > Turn Windows Features on or off > Internet Information Services.

share|improve this answer
    
Please see this thread : stackoverflow.com/questions/24398285/… –  RenegadeAndy yesterday
add comment
up vote 3 down vote

Are you on a desktop (vs. web server)?

On a desktop, IIS Express doesn't allow external connections (obviously for security reasons). Having said that and if you know what you're getting into, here's Scott Hanselman on how to do that.

share|improve this answer
    
Ok so i tried this - but the command: netsh firewall add portopening TCP 80 IISExpressWeb enable ALL appears to be deprecated - and I am not sure what the new version of this should be? –  RenegadeAndy yesterday
1  
@RenegadeAndy Nice name BTW :) I haven't worn the IT hat in years but that's a command line version of what you can do via Windows UI -> Control Panel -> Security -> Windows Firewall , or like myself, my box is "managed by McAfee" and its firewall. At the end of the day, you need to open Port X (whatever it is you set IIS Express to listen to) in firewall settings...Hth –  EdSF yesterday
    
"EdSF i think its a little deeper than this! The firewall is all good. I followed the article and got that point done. However now this happens : andyworker.hopto.org:56378/default.aspx - a service unavailable http 503! –  RenegadeAndy yesterday
    
@RenegadeAndy Well assuming you got Firewall stuff out of the way. On the PC you are using to connect to (not the one with IIS), does it "know" where andyworker.hopto.org is? It seems to be "real" host on the interwebs, so you have to "intercept" the DNS lookup on that PC by editing it's hosts file (arg my IT brain is hurting!). Or, use the IP (of the box where IIS is) to connect (so no DNS resolution). Hth... –  EdSF yesterday
1  
@RenegadeAndy Cool - proving that even "errors" are welcome sight :) Tip: start with a plain HTML "hello world" so you can isolate between net/connectivity, IIS, and finally application matters. Best~ –  EdSF yesterday
show 1 more comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.