Very strange problem for Node

[supercanada1]

I set up a ubuntu vps and a windows vps, on ubuntu VPS I run node, and on windows VPS a run the wallet, I use  port 27341 as the RPC port, but on "getpeerinfo", I found the port changed, what happned? addr's IP is right, but port different, strange.

also, how can I set up a node on windows server? easy? Thanks

[1715123333]

1715123333

[1715123333]

1715123333

[1715123333]

1715123333

[1715123333]

1715123333

[achow101]

There are 2 different ports, the RPC port and the node port. The RPC port allows you to connect to it to issue commands. The node port is a public port which allows you to connect to other nodes and vice versa. The different port number you see in getpeerinfo is the node port so that other nodes can connect to you.

[supercanada1]

Actually the port is none of them, I think maybe windows server will change the port?

[achow101]

It's possible that if you are behind a router that the router would change the port and forward everything to the port on the node.

[supercanada1]

I am using windows 2008 VPS, how to fix this port problem

[achow101]

Since it is a VPS, it is hard to know how to fix the issue. Perhaps try allowing connections through the node port. Go to the management console for your VPS from your provider and allow everyone to connect to whatever port you are using. That may fix the problem, it also may not.

[supercanada1]

thanks
by the way, do you know the standard way to create a windows server node? I have both linux and windows version of wallet. Just not know how to set up a windows node, I have set up linux node it works

[achow101]

The wallet is the node, unless it is SPV. For example, simply installing Bitcoin Core and running it and using it as your wallet means that you are running a full node. You can run the node as a server with bitcoind or as a wallet with a gui with bitcoin-qt.

[supercanada1]

I run the qt wallet on windows server, then the port problem happends, it is the same when you run wallet on local PC, from the lnux Node on server, when you getpeersinfo, you can see the port listed there is also not the P2P port. I think this is the same problem

[achow101]

I'm not seeing this on my nodes. One is a my pc with windows 7, the other is an Ubuntu vps. Where exactly are you seeing the wrong output? Can you post what it says and what it should actually say? That might help us diagnose better.

[supercanada1]

when I getpeerinfo from ubuntu server, it says:
root@supercoin2:~/RevoCoin/src# ./LkouisCoind getpeerinfo
[
    {
        "addr" : "198.144.189.141:49301",
        "services" : "00000001",
        "lastsend" : 1433557701,
        "lastrecv" : 1433557535,
        "conntime" : 1433557534,
        "version" : 60013,
        "subver" : "/Satoshi:1.2.0/",
        "inbound" : true,
        "startingheight" : 13,
        "banscore" : 0
    },
    {
        "addr" : "38.108.79.105:33059",
        "services" : "00000001",
        "lastsend" : 1433557701,
        "lastrecv" : 1433557701,
        "conntime" : 1433557700,
        "version" : 60013,
        "subver" : "/Satoshi:1.2.0/",
        "inbound" : true,
        "startingheight" : 13,
        "banscore" : 0
    }
]

but my rpc port is 23741 and p2p port is 23742
these two address, one is from my local PC and one is from my windows server

[achow101]

So I think what is happening is the NAT (router) is getting in the way. It is port forwarding. The NAT receives the connection from the correct port. But, it forwards all of the data to the node behind it, and the data is coming from a different port. The node still records the IP address as the same since the data is being forwarded, but it does not know what port the data is from, so it uses the port that the NAT is giving the data from. This, I think, is why you are seeing different port numbers from getpeerinfo than what they actually are.

[supercanada1]

thanks, any way to solve this problem?

[achow101]

Not that I know of. It isn't really a problem though.

[supercanada1]

thanks
I think that relates to setup a node on windows server, all the windows server has the same problem