Total Members Voted: 9
It just doesn't work. Ran on Windows Server 2008 R2 (You may have to zoom in on the image).[IMG ]http://i1120.photobucket.com/albums/l489/Pacnet2010/Untitled-13.png[/img ]
And no, Glass-Server isn't needed by you.
I'll investigate Glass server when I get home to see if it's an issue on my end. Make sure you have the alpha zip on the server and not the standard. The server auto-updater isn't in the standard.
Apparently I did whatever it said on Git.rtf, and I surely do need Blockland Glass because Ark needs it for his server, and also I need it if my current remote start / stop doesn't get fixed, because it isn't really working out.
Connection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection 372 disconnectedConnection 372 disconnectedConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge SuccessConnection from 96.248.119.33Challenge Success
Nah, I was just now restarting the server for an update that would allow me to debug further. It appears that the name is being received but auth isn't succeeding. I'll investigate.
It appears that the name is being received but auth isn't succeeding.