VGOEmulator.net

I have a server up and running. I can see it when I create a new character in the login server, and the new character gets created. However, when I select the character at the character select screen, I just sit at "Waiting on Data From [server]." Also, Account Management shows the server as up.

Can someone give me a hint as to where my problem might be?

VGEMUWORLD.XML
<worldserver
host="192.168.144.21"
externalIp="98.115.70.42"
port="10100"
name="Zinishar"
account="chogra"
password="xxxxxxxx"
/>

<!-- This is the host and port world will connect to the login server on -->
<loginserver host="login.vgoemulator.net" port="10102" />

<!-- Credentials to use to connect to the MySQL server -->
<database host="192.168.144.21" port="3306" user="kaede" password="xxxxxxxx" database="vgo_world" />

TEXT FROM WorldServer
18:32:54.198 I General Starting VGOEmulator WorldServer v0.1 Alpha
18:32:54.200 I Database MySQL database connected to 192.168.144.21:3306
18:32:54.318 I Config Successfully loaded 441 packet structs.
18:32:54.326 I Database Successfully loaded 390 character titles.
18:32:54.516 I Database Successfully loaded 1245 factions.
18:32:54.518 D Rules Loaded 1 Rule Sets
18:32:54.529 I Database Successfully loaded 4 variables.
18:32:54.554 I Database Successfully loaded 469 commands.
18:32:54.555 D Char Setting all players offline
18:32:54.689 I Database Successfully loaded 123 Emotes.
18:32:54.690 I Net Server listening on 192.168.144.21:10100
18:32:54.788 I Net Connected to login server login.vgoemulator.net:10102

See this post about the Waiting on Data issue:
viewtopic.php?f=22&t=904&p=7143&hilit=waiting+on+data#p7137

And here is the post from Jimbo and ArtofWar (do the above first, this one involves router settings and is an edge case):
viewtopic.php?f=28&t=713&p=5440&hilit=+Waiting+on+Data#p5440

Thanks, Lokked! Resetting the UILoginHistory.ini file did the trick.

Bah! Apparently Verizon figured out I had a server on port 10100 and is blocking it. I can portqry to the local IP and get through, but when I try to portqry to the external IP, it is filtered. It was working the first night I put up the server, blocked by the second night.

I guess I'll have to wait till I have a login server I can run inside my firewall before I can play anymore with the server and server code.

Shargash - can you summarize what your issue currently is - are you saying you can't access the login server from inside your network - what do you mean by 'it is filtered'?

Hi,

Can you try this please :

host="98.115.70.42"
externalIp="98.115.70.42"

and restart your server... is it better ?

Jimbo, Windows has a command (from the support tools or somewhere) called "portqry.exe." You give portqry the IP address, endpoint, and protocol, and it attempts to make a connection and reports what it finds. When I enter portqry -n 192.168.144.21 -e 10100 -p udp, I get UDP port 10100 (unknown service): LISTENING. Also, the console output from the VGO server, I get [quote]19:19:05.075 E UDP Received packet with unknown protocol opcode 0x506F (205
91) from 192.168.144.21:54405
0000: 50 6F 72 74 51 72 79 20 - 54 65 73 74 20 4D 65 73 PortQry Test Mes
0010: 73 61 67 65 00 sage.[/quote]

192.168.144.21 is my internal IP. My external IP is 98.115.70.42. When I enter portqry -n 98.115.70.42 -e 10100 -p UDP, the response is UDP port 10100 (unknown service): LISTENING or FILTERED, which is portqry's way of saying it did not get through. Also, there is no response from the VGO server. From this I conclude that I can get to port 10100 on my server from my local network, but I cannot get to port 10100 on my server from outside my local network. In other words, Verizon is blocking port 10100. Note that I could get through from the outside just fine on the first day, but not on any day since then.

Blackstorm,

When I try what you suggested, I get an error starting the server: [quote]19:26:34.556 E Socket Error binding UDP server socket on 98.115.70.42:10100: The requested address
is not valid in its context.
19:26:34.556 I General Shutting down[/quote]

98.115.70.42 is the IP address of my Internet-facing router. It is not an IP address that is owned by my server (192.168.144.21), so I'm not surprised at the error.

Thanks,
shargash

I don't understand why Verizon would do this. Although I'm doubting their involvement, have you contacted them to identify if they actually are the cause or not? It definitely doesn't make sense that one day it worked and the next it would not.

I haven't contacted them yet. It is the policiy of most ISPs to disallow servers for their retail customers, so my assumption is Verizon is monitoring traffic, detected a server, and blocked the port. Just an assumption though.

It looks like it was something on my side after all. It was working, then it wasn't. So I went and deleted all my firewall rules and re-entered them. Then it was working again. I have no idea what happened, but I'm good now.