Super User is a question and answer site for computer enthusiasts and power users. 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

I have a Windows Server 2008 R2 Core x64 with node.js. Local adress of my machine is Also i have a NAT, with translated 28966-28999 ports. My external adress is 212.232.xx.xx I have listened to 28969 port.

If i try to connect to my server by http://212.232.xx.xx:28969/ from my local network, then success. But i can't connect to http://212.232.xx.xx:28969/ outside from my network.

the same with 80 port.

I tried command netsh firewall add portopening tcp 28969 "Node.js", and nothing has changed.

Node.js script:


var app = require('express').createServer();
app.listen(28969, '');

var login = require('./login');


function init(app) {
    var socks = require('');


    var io = socks.listen(app);
    io.of('/login').on('connection', socksEventsHandler);


    app.get('/', function (req, res) {

    app.get('/login', function (req, res) {
        res.sendfile(__dirname + '/public/login.html');

    app.get('/login.js', function (req, res) {
        res.sendfile(__dirname + '/public/login.js');

    app.get('/_login.js', function (req, res) {
        res.sendfile(__dirname + '/public/_login.js');


share|improve this question

migrated from Jun 13 '12 at 7:13

This question came from our site for professional and enthusiast programmers.

Show the code where you bind the socket. Maybe you bind to the wrong ip. – ThiefMaster Jun 11 '12 at 14:05
Question updated – ScaV Jun 11 '12 at 14:16
yeah, or wait for this one to be migrated (unless a moderator does it it needs a few people to cast close+migration votes) – ThiefMaster Jun 11 '12 at 14:45

You must log in to answer this question.

Browse other questions tagged .