Deprecated Darkstar fourms

Yes zone_setting.sql is set to public IP 75.xxx.xx.148 for all zones which is then fowarded to the server (which we are able to get to the login server at least) I'm 99% sure something changed in a pfSense update a while back... But I've been yet able to figure exactly what and was hoping that is wa...

Thanks for trying!
You need to take --hairpin out of your config as my system is remote from yours.
If you can, please try again ^_^

So after a few months of down time I have finally decided to sit down and try and figure out my pfSense NAT Reflection issues which I ran into a while back over here. ( https://forums.dspt.info/viewtopic.php?f=14&t=21166 I would greatly appreciate it if someone could try and connect to my server at ...

Tried logging in today and was unable to with old account. Also, unable to make new account. Server needs the fixing? (trying to fix and test some things on a new Win10 FFXI client build that is giving me issues so it may be me) Have you tried lately? Finally sat down today for some testing and sam...

Looks like I am at a complete loss for now...

For both Win7 and Win10
-------------------------------------------
Retail server works.
Local server with --hairpin fails at socket closed.
Remote servers fail at socket closed.

Have checked router, proxy and firewall logs and no clues there either.

Current Win10 copy to Win7 box has same issue... Commencing complete reinstall and patch... Will update thread tomorrow.

I just updated my gaming machine to Windows 10 and am running into the same issue where I can connect to private server lobbies (mine using --hairpin and others) with both Windower and Ashita, but eventually get the closed socket problem. Am copying my setup to a spare Windows 7 machine and will try...

Tried logging in today and was unable to with old account. Also, unable to make new account. Server needs the fixing?

(trying to fix and test some things on a new Win10 FFXI client build that is giving me issues so it may be me)

Necro fix for necro post....

Had some longtime away users run into this problem today...
Ended up being and easy fix where you just have to log in with a second character (mule) and then log back in with you main.

Has worked 3 of 3 users so far.

Did you change the below in "login_darkstar.conf" to your servers intenal/LAN IP?

#--------------------------------
#TCP/IP parameters
#--------------------------------

login_data_ip: 10.0.0.11
login_view_ip: 10.0.0.11
login_auth_ip: 10.0.0.11