HTTP webservice Access

Question

0.00/5 (No votes)

See more:

, +

Hey guys.
Assume that I have created a ASP.NET webservice(or XML webservice) and hosted on IIS web server. I dont have client-server architecture within my network. All computers are connected to router. The question is how a webservice can be accessed outside LAN network? Webservice works on HTTP and router/firewall does not block port 80.so outside a LAN, can anyone access the service from my computer? Does this also needs port forwarding?

Posted 18-Feb-12 23:05pm

tonydsouza1987

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Accepted Answer · 2012-02-19T04:14:00

"Client/server" has nothing to do with the architecture of your network or how your clients are connected to whatever. Googe it.

This question has nothing to do with the configuration of your web server, but of your network. If the outside world has a route to your web server, they can see the web service. If not, then they can't. It's that simple.

Now, if you need, but don't have, a server dedicated to the outside internet, you have a rather large design problem with your network. The server should be firewalled off so it's the only thing that an external client can see, and only on certain ports. You also have to make sure your router config is correct to support this.

If you just expose your entire network to the internet, including your server, you're exposing your client machines to a VERY hostile world.