How can i setup a bitcoin server in windows 2012 to listen to remote hosts?

[nosdi26]

i have a linux host that im trying to install a script, The bitcoin server is in an another machine with windows 2012 and i cannot connect. my conf is:

Code:

# bitcoin.conf configuration file. Lines beginning with # are comments.
 
 
 # Network-related settings:
 
 # Run on the test network instead of the real bitcoin network.
 #testnet=0
 
 # Connect via a socks4 proxy
 #proxy=127.0.0.1:9050
 
 ##############################################################
 ##            Quick Primer on addnode vs connect            ##
 ##  Let's say for instance you use addnode=4.2.2.4          ##
 ##  addnode will connect you to and tell you about the      ##
 ##    nodes connected to 4.2.2.4.  In addition it will tell ##
 ##    the other nodes connected to it that you exist so     ##
 ##    they can connect to you.                              ##
 ##  connect will not do the above when you 'connect' to it. ##
 ##    It will *only* connect you to 4.2.2.4 and no one else.##
 ##                                                          ##
 ##  So if you're behind a firewall, or have other problems  ##
 ##  finding nodes, add some using 'addnode'.                ##
 ##                                                          ##
 ##  If you want to stay private, use 'connect' to only      ##
 ##  connect to "trusted" nodes.                             ##
 ##                                                          ##
 ##  If you run multiple nodes on a LAN, there's no need for ##
 ##  all of them to open lots of connections.  Instead       ##
 ##  'connect' them all to one node that is port forwarded   ##
 ##  and has lots of connections.                            ##
 ##       Thanks goes to [Noodle] on Freenode.               ##
 ##############################################################
 
 # Use as many addnode= settings as you like to connect to specific peers
 #addnode=static ip of my network
 #addnode=10.0.0.2:8333
 
 # ... or use as many connect= settings as you like to connect ONLY
 # to specific peers:
 #connect=static ip of my network
 #connect=10.0.0.1:8333
 
 
 # Maximum number of inbound+outbound connections.
 #maxconnections=
 
 
 # JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
 
 # server=1 tells Bitcoin-QT to accept JSON-RPC commands.
 #server=1
 
 # You must set rpcuser and rpcpassword to secure the JSON-RPC api
 #rpcuser=Ulysseys
 #rpcpassword=YourSuperGreatPasswordNumber_DO_NOT_USE_THIS_OR_YOU_WILL_GET_ROBBED_385593
rpcuser=user..
rpcpassword=pass...
rpcallowip=*
rpcport=43556
server=1

 
 # How many seconds bitcoin will wait for a complete RPC HTTP request.
 # after the HTTP connection is established. 
 #rpctimeout=30
 
 # By default, only RPC connections from localhost are allowed.  Specify
 # as many rpcallowip= settings as you like to allow connections from
 # other hosts (and you may use * as a wildcard character).
 # NOTE: opening up the RPC port to hosts outside your local
 # trusted network is NOT RECOMMENDED, because the rpcpassword
 # is transmitted over the network unencrypted.
 #rpcallowip=10.1.1.34
 #rpcallowip=192.168.1.*
 
 # Listen for RPC connections on this TCP port:
 #rpcport=8333
 
 # You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
 # running on another host using this option:
 #rpcconnect=127.0.0.1
 
 # Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
 # with Bitcoin -server or bitcoind
 #rpcssl=1
 
 # OpenSSL settings used when rpcssl=1
 #rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
 #rpcsslcertificatechainfile=server.cert
 #rpcsslprivatekeyfile=server.pem
 
 
 # Miscellaneous options
 
 # Set gen=1 to attempt to generate bitcoins
 #gen=0
  
 # Pre-generate this many public/private key pairs, so wallet backups will be valid for
 # both prior transactions and several dozen future transactions.
 #keypool=100
 
 # Pay an optional transaction fee every time you send bitcoins.  Transactions with fees
 # are more likely than free transactions to be included in generated blocks, so may
 # be validated sooner.
 #paytxfee=0.00
 
 # Allow direct connections for the 'pay via IP address' feature.
 #allowreceivebyip=1
   
 # User interface options
 
 # Start Bitcoin minimized
 #min=1
 
 # Minimize to the system tray
 #minimizetotray=1

how can i set up in order to generate address in the site i host to linux server?

Thanks in advance for any help

forwarded ports to the internal ip of the win 2012 server is 8333

[Dare]

You have "rpcport=43556" in the middle of your config file, but you forwarded port 8333. Changing either one so that they both match should solve your problem; I recommend using 8333 for both since it's standard and you're using a private internal network, but it doesn't really matter.

[grue]

how can i set up in order to generate address in the site i host to linux server?

This is impossible to understand because it's poorly worded. If your native language isn't English, consider posting in one of the regional forums instead of here.

[nosdi26]

how can i set up in order to generate address in the site i host to linux server?

This is impossible to understand because it's poorly worded. If your native language isn't English, consider posting in one of the regional forums instead of here.

You are right, ...
I want to install a script in a linux server,(a merchants website will occur here)
I want to set up, in a win 2012 server, the bitcoin server.
The website should be able to communicate with the bitcoin server. Clients should be able to have their unique bitcoin addresses when they pay for something.
Thanks

[nosdi26]

About the windows server:
Its hosted in virtualbox,
, it has an ip address like other computers in my network, like 192.168.178.xxx
I cannot get which ip addresses and where to put in the config file.
My static ip of my isp is lets say 5.5.5.5.

Any help will be appreciated

[Dare]

You'll need to be able to reach your windows server from your linux server in order to connect to the bitcoind instance; if they aren't on the same network, you'll need to port-forward the port for your bitcoin daemon to the windows server from your router, and make sure that your RPC config is secure. Also, if you're hosting the windows server on a home internet connection, you probably have a dynamic IP which you will have to constantly update (manually or through software) to keep it working.

The only part in your config file that matters is this part (everything else is commented out and has no effect):

rpcuser=user..
rpcpassword=pass...
rpcallowip=*
rpcport=43556
server=1

The rpcport is the port that you need to forward to the windows server, and rpcallowip should be set to the IP address of your linux server to help prevent unauthorized access.

[nosdi26]

You'll need to be able to reach your windows server from your linux server in order to connect to the bitcoind instance; if they aren't on the same network, you'll need to port-forward the port for your bitcoin daemon to the windows server from your router, and make sure that your RPC config is secure. Also, if you're hosting the windows server on a home internet connection, you probably have a dynamic IP which you will have to constantly update (manually or through software) to keep it working.

The only part in your config file that matters is this part (everything else is commented out and has no effect):

rpcuser=user..
rpcpassword=pass...
rpcallowip=*
rpcport=43556
server=1

The rpcport is the port that you need to forward to the windows server, and rpcallowip should be set to the IP address of your linux server to help prevent unauthorized access.

Thanks a lot for your support, i will fix it out as soon as i return back,,if some i cannot figure out , i will disturb the forum again