Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a small web application on our network that we need to make available for a few people through the internet.

I thought port forwarding to the webserver would be simple enough, but when I try to access the IP (204.34.??.254, for example), I get the login prompt for the switch.

What could be the problem?

Sorry if it sounds like some dumb question, but I have no knowledge of networks, my focus has always been coding, and the IT support staff doesn´t know what is the problem either.

share|improve this question

Check on which port the admin-panel is running. If this is also on port 80, change it to something else like 8080.

If you configured NAT the right way, you should be able to access it.

share|improve this answer
Thank you for the answer, but in the end the problem was between chair and keyboard. – Carlos Negrão Feb 16 '11 at 16:51
I spoke too soon. No matter what I do or which port I try to use, I get a login prompt from the switch, unless I´m already logged in, which masked my last try as a sucess. – Carlos Negrão Feb 16 '11 at 17:54
A few questions: What is the internal IP of the webserver? What happens if you change the port of the networkapp to 8080 and pass it along? Does it work OK internally? – Bart De Vos Feb 16 '11 at 18:50
The internal IP is It works perfectly internally. – Carlos Negrão Feb 16 '11 at 19:02
Trying to use ports 8080, or even 81 still worked internally, but the switch still asked for its login for its control panel. – Carlos Negrão Feb 16 '11 at 19:04

Your Answer


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.