I will be running a server on each of my systems to test them. I've been having problems with allowing people to connect to them lately. One of the machines is being a pain and producing ActiveX runtime errors with a few Visual Basic programs, probably to do with WinSock or IOCP since it's only occuring on multi-player gaming software.

However, there will be 2 servers set up today, and i'll try and get the other one up and running later this evening before work. Below are some instructions on how to connect, and details on each of the server machines.

If you can't connect, then post in here, if you can connect, then it'll show up on the server logs hopefully.

HOW TO CONNECT
Load up your Quest application, and click the Network tab.

In the Host Name textbox, type questnet.servegame.com.

Change the Port to one of the port numbers listed below with the system information.

||||| Server: VAIO - PORT: 4000
2mb Cable Broadband
512 MB RAM
Pentium 4, 3.20 GHz
Running on Windows XP Home

||||| Server: Antec - PORT: 5000
UNAVAILABLE WHILE UPGRADING OPERATING SYSTEM

||||| Server: Timmy - PORT: 6000
UNAVAILABLE AT THIS TIME

Results
Both machines allow connections fine. I'll leave the servers up so that you can all test them.

You could always start up a few VM-machines and have them all running questnet servers..

What I'd love to do is be able to network some questnet server's together - so they can all talk to each other.
So - for example - one game (Echelon's Adventure) could roam in the next evolutionary world (Wain's Adventure).

not so hard to do with real programming. You simple have this...

Main Server - Server 1
              Server 2
              Server 3
              Server 4

The main server holds all of the account data for characters etc. Each server simple pulls that data from the main server, and passes it to the clients for each sub server. I think you'd need something a lot more powerful than WinSock to handle the amount of connections for the main server. Something like this for QuestNet isn't really necessary though, considering my version of QuestNet Pro allows 30 connections, which is fine for games like these.

Testing is over, servers have been turned off. No problems with people connecting, and the servers seemed to stay active solidly for 24 hours.

I tried last night but wasn't able to connect... did you have many successful external connections?

I don't see why winsock wouldn't be able to cope with it... But I've never used winsock that much.

hmmm, I've just been using it a little bit at work (clustering that is), that's all.. It's sort of un-needed here.

Alex wrote:I tried last night but wasn't able to connect... did you have many successful external connections?

I will boot up the Antec server machine, and leave it running. Try again when you're ready.

1 person connected to both servers successfully (Externally), and somebody logged into the Antec server last night using the name "GetInfo" (With a couple of symbols at the end of their name).

Doesn't seem to be letting me connect.

I can't help but wonder if the "GetInfo" user was some kind of port scanner. Did they actually do anything other than connect?

lol. I took it down when I went to sleep. No, they didn't do anything apart from connect.

VAIO Server will be open for you Alex, until you can connect successfully.