Ravenloft: Prisoners of the Mist

Public (OOC) => Tech discussion => Topic started by: Song of Danta on May 03, 2017, 11:46:56 PM

Title: Relogging Issues
Post by: Song of Danta on May 03, 2017, 11:46:56 PM
I am connecting to the server with a nwmain shortcut that has the IP address in the target line (+connect 46.4.59.55). Until a couple of days ago, this has been working fine.
Nothing in my configuration has changed.
All the sudden, if I exit the game, I have to restart the computer in order to log on again, otherwise I simply get a timeout message when NWN attempts to connect to the PotM server. It doesn't matter if I am changing accounts, or using the same account. This happens every time I close and re-open the game.
Everything works fine, however, if I use the NWN launcher and go through the whole 'multiplayer -> Direct Connect/LAN -> Blah, blah' process.

Here is what I have tried so far:
- Power cycle on modem/router.
- Changing Client Port in the nwnplayer.ini
- DNS flush, IP release/renew.
- Resetting Wi-Fi card thing.

It's more of a minor nuisance, but I'd like to sort it out. Please help!
Title: Re: Relogging Issues
Post by: Iluvatar / Madness on May 04, 2017, 12:16:24 AM
+connect 46.4.59.55

The port number seems to be missing...

Perhaps try like this

+connect 46.4.59.55:5121

OR

You can try making a batch file with this command line in it
nwmain.exe +connect 46.4.59.55:5121

Obviously, put the file in your nwn directory and you can make a shortcut to that file for it to be accessible from the desktop.

Title: Re: Relogging Issues
Post by: Phantasia on May 04, 2017, 12:30:21 AM
This has happened to me before. I believe it is a problem of the host, similar to the lag issues. I would not be able to connect to the server for upwards of an hour or so at a time, but these instances are rare for me as far as I've noticed.
Title: Re: Relogging Issues
Post by: Song of Danta on May 04, 2017, 12:46:34 AM
Oops, must have cut off the port number! It was there and not working.

Made a .bat, this seems to have solved the issue. Thanks!