Hey i have some questions about the useage of vaultster how did you set up is it lan or is it wan? how did you get the chr bics to trasnfer ? and if you play lan how do you double back on your ip? ie say go threw a portal to another server than come back threw to your own server you host?

olag55 wrote:Hey i have some questions about the useage of vaultster how did you set up is it lan or is it wan? how did you get the chr bics to trasnfer ? and if you play lan how do you double back on your ip? ie say go threw a portal to another server than come back threw to your own server you host?

Dunno about the rest, but TCP/IP handles address translation... you just plug your own IP into the server field and the Magic of the IP Stack handles the rest.

Note that if all the servers you're connecting are on the same LAN you won't need VaultSTER. Avlis had interconnected modules up before we had this technology come along. You will only need it if you are connecting to other systems/servers outside of your own LAN, in which case it indeed uses the TCP/IP protocol to transfer the correct character file (.bic) to the remote vault.

If your mods share the same machine or the same LAN, you're better off with a shared servervault via SMB or NFS than using VaultSTER, mostly because it's a lot simpler. You only need VaultSTER when you're transferring characters between two remote servers where file sharing would be impractical.

well one part of the mod will be hosted in the usa and the other in england so yes wan is what we will be doing so that is why where using vaultster. the reason i asked the lan question is i could not go to my server threw the portal from the server in england i could only leave my server in the usa and go to the one in england. the other problem where having is the bic trasfer from server to server.

I'm helping Olag55 to split our mod, part of which will be running on his server in the U.S. and the other on mine in the U.K.

Below I have listed what I put on the NWNX2 forum (to which I received little response, unfortunately):

We're trying to do the following: use vaultster to port a player's BIC file to another server and then port the player him/herself to that same server.

I have installed NWNX2 and also Vaultster to each server's main NWN folder.
Following that, I have made two test modules. Each setup to allow a player to click on an area transition. Once clicked on, the script tries to use vaultster to export the player's .BIC file and then follow that up with a ActivatePortal command to forward the player to the server.
Pretty much what vaultster is designed to do.

Unfortunately, all I get is Failed to portal the character file.
When I look into the vaulster log I see:

o Using WinSock 2.2.
o Loading in 0 known servers.
o Server started on port 5100.
o Start searching for porttest*.bic
o Searching for .\BanedonSkyRider\porttest*.bic
o Could not find latest file for BanedonSkyRider\porttest!
o There was an error during the transmission.
o Retreived status for BanedonSkyRider\porttest = 3

Each server is stored in C:\NWNserver\<nwn executables>
I have tried this on the internet with the same values and now am trying it across a LAN.
Here's the details of each server:

Not 100% sure that this will bring the solution, but it is at least part of the problem: you're using internal IP addresses. If you give vaultster only the internal IP addy of a server, it will try to find it on your network, and of course not find it.
Solution: Use global IP addresses and configure both of your routers properly to allow for forwarding to the right internal IP Your global IP address can be found by checking your router settings, or by asking an outside source to check it for you (for example: http://www.whatismyip.com/).

well bradeon is using his internal ip for testing till i can get my other server online as not to distirb our main server. so the internal ip thing wont be problem there soon enough. when we tested it bettween his system and mine i could portal to his and but not back to mine he had the same problem as we could not double back on our ips. not sure if you any of you guys play lan but try this put your external ip in for a dc to your lan game you just can't do it ??? is there a way around that? oh we also have dns set up to mimic static ips for the vaultSTER as well. Thank you guys for any help you can give.

Olag's right on that. The internal IPs will be replaced with DNS names when we succesfully sort this problem out.

The porting that Olag reports was a test I did with ActivatePortal() just to see if we could move between servers - it did not involve vaultster.

One thing that comes to mind is that in the vaultster log it says:
o Loading in 0 known servers.
o Server started on port 5100.
which seems to indicate that it no other vaultster servers are found and also for some reason it's uisng port 5100. We'rfe not using 5100....

I'm not a member here.. but our PW is wanting to use the Vaulster plugin to connect our servers... (only a couple)

We're having difficulties getting them to talk to each other because there are only 2 servers and they are both on non static IPs... because the IPs change on occasion... we want to use the DNS.. that doesnt' change.. but we're having trouble getting them to connect because of neither having a numerical IP.

What we're trying to do... is to get the bic file to go from one server... to another... when the player triggers the area change that is used to link the two of them. (in this case.. a ship)...

What we want to transfer is all of the info for the bic.. including crafting XP from the CNR... all of the equiptment on the character... and all the stats from our use of the PRC.

We only are using 2 servers... so we want it to tranfer from the mysql database of one server.. to the database of another server. (Instead of a central character vault at another location.).. We're using NWNx2 (I believe it is version 2) to run our servers on.

It's my understanding that the issue is... that the connection can't be maintained using only the servegame.com id's. (Those remain the same)... but, the computers who host them... are both on broadband connections that have Dynamic IPs.... the fact that they are Dynamic IPs... is what is causing the issue.

I was hoping for some help in getting vaultster to work with servers who are wanting to connect.. but are only on dynamic ips.... but use the service that was suggested above.