Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

Folks, I am stuck with a weird problem here. I am running a Websphere server locally on my Win 7 machine. Http port is 9081. When I am trying to access my application using localhost it works fine, as soon as I replace it with my IP address it stops responding. Is this a Win 7 quirk? How to fix it?

Works: http://localhost:9081/myApp/first.html

Doesn't work: http://<XX.XX.XX.XX>:9081/myApp/first.html

Where XX.XX.XX.XX is my local IP Address. I have confirmed my IP address again n again with ipconfig

share|improve this question
How does "doesn't work" look? No response or error message? Immediately or after some delay? – dbreaux Jan 29 '13 at 22:22

Your Websphere server could be listening only on the loopback interface. Confirm this using netstat

netstat -an | findstr "9081"

If you see a response like this:

You might need to configure your service to listen on the other interfaces connected to the network.

share|improve this answer

My 1st guess would be some sort of antivirus/firewall software that may possibly shutting down ports.

You might want to verify that by trying to telnet to port 9081 from another machine to your Win7 machine to ensure that it connects.

share|improve this answer

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.