Help with server errors (pics)

[Eva Aisling]

Steel - Have you tried using my config settings with the changes that Dev mentioned? I don't know if it's exactly right or not, because I can connect to my server properly, but someone on my same LAN cannot. I haven't had anyone else try outside of my LAN yet.

That dnsalias address is just a Dyndns address that I used to ensure my external IP stays updated. Any time you reset your router, your IP changes if you don't have a static IP. Setting your IP as static in the Control Panel isn't the same thing, although it is still a good idea to do. When you activate a dyndns address, it hosts an address for you that tells everyone you direct to it what your current IP is so that they are still able to connect when it changes. At least that's what I understand, but I am just learning these things too. It's a free service if you want to try it. Just google "dyndns".

People use different settings in different areas where you see clmtyserver.dnsalias.com, so I don't know exactly what will work. All it does is show people my external IP, so you shouldn't use it for areas in config that needs your internal IP. Honestly, I've just been going through forums for more than a week and trying different suggestions to get this far. Good ol' trial and error.

[Eva Aisling]

I had a friend try to join my server and he got the 1017 error as well. I know this is probably obvious to all of you, but could you explain port forwarding to me? Everywhere I read just says it opens ports and directs them to your computer, but does that close those ports off to someone else on your same LAN? If everything is being directed to my computer, will my husband still be able to access it? Do I need to forward those ports to [I]both[I] of our internal IPs? I do know how range forwarding is done on my router.

I cannot, for the life of me, figure out why others can't connect.

[Derision]

Originally Posted by Eva Aisling

could you explain port forwarding to me?

I'll try

Things you need to understand first (which you probably do):

Each device (e.g. PC) on your LAN at home has an IP address, e.g. PC1 has address 192.168.1.100, PC2 has address 192.168.1.101, etc).

These are your internal IP addresses.

Your router will also have an internal IP address, e.g. it might be 192.168.1.1. This is the address your PCs forward packets to that need to get to the Internet.

Usually, your router will only have one external (Internet facing) IP address, e.g. it might be 88.50.30.20.

Packets leaving your LAN and heading out onto the Internet undergo Network Address Translation (NAT), i.e. when your PC1 sends a packet to, say google, before your router transmits that packet out onto the Internet, it replaces the source address of PC1 (192.168.1.100), with it's own Internet facing address (88.50.30.20 in my example). It also puts a unique source port address, so it knows, when Google replies to the packet, that it is PC1 that the reply has to go to.

OK, now, when you are running an EQEmu server, each component of the server 'listens' for incoming connections on specific ports, e.g. the LoginServer on 5998, world on 9000, zones on 7000+.

Because the connection to these components is initiated from outside your network, when your router receives a packet from the Internet, it will have your routers IP address (80.50.30.20 say) as the destination address, and, say destination port 5998, if someone wants to connect to your login server.

You need to tell the router which PC on your local LAN is to deal with incoming requests on port 5998. This is what people refer to as 'port forwarding' or 'opening ports'. In most cases you will have one PC running the loginserver, world and the zones, so you would tell your router to forward incoming traffic to all these ports to the internal IP address of your server.

Hope that makes sense. For PCs within your home network, accessing your local server, no port forwarding is required, it is only for inbound connections from the Internet to your server.

[Eva Aisling]

Thanks, Der. I think I understand.

It seems like my config has the correct addresses in all the correct places, but no one but me can connect. I tried disabling my firewall, anti-virus, and setting my comp as DMZ and it [I]still[I] didn't work. I also tried disabling the "Block Anonymous Internet Requests" option on my router. I added my IP and dyndns address in my husband's hosts file as suggested, but even he can't connect. I've tried different settings in my config file, but there's really not that much in there to change. I've tried to find a reason why dyndns might not be reporting my external IP correctly, or just not linking to it, but I can't find information about that.

I am completely out of ideas and am suffering from eyestrain, so I have resorted to using hamachi (which works, for whatever reason). I'd rather not have to use an external application, so I will be checking here if anyone has a clue. I'm tapped. Perhaps I will try posting at dyndns forums soon, but I just don't have it in me atm. On the bright side, I did learn a few things! I think I'm a techie at heart!

Thanks all for your time! Let me know if you think of anything please!

Also, let me know if I can fix those debug errors. There are links above that give examples. They report a HEAP CORRUPTION in C++, so I wonder if maybe something didn't compile correctly. I'm using the rev1180a-Bots version already made available. I have C++ installed, but I don't know how to use it.

[Eva Aisling]

My husband can connect with hamachi, but my friend crashes at character select. He can make a char, but not enter world. I received a message in my server window that said "Unhandled server packet 0x3007" right before his client closed. His status in hamachi is good. I am running it thru a separate port. Any ideas?

When he first tried to join, the enter world button wasn't even clickable. he would click it, it would stay popped up, then he would hang. I noticed in server window that it tried to send him to tutorialb right before he crashed, so I used Navicat to disable tutorial button and that's when the unhandled packet happened. I did restart the server after changing settings.

We are both running SoF on a fresh install and I installed EQEmu-Rev1180a-Bots this morning with a new database.

[Eva Aisling]

Hamachi only worked for us through the weekend, then wouldn't get a stable enough connection for husband to log in. I uninstalled it and changed my husband's Window hosts file from:
< my internal IP > clmtyserver.dnsalias.com

To:
< my internal IP > < my external IP >

My config looks like this:

<?xml version="1.0">
<server>
<world>
<shortname>clmty</shortname>
<longname>Calamity</longname>

<!-- Only specify these two if you really think you need to. (read: You don't) -->
<address>clmtyserver.dnsalias.com</address>
<localaddress>192.168.x.xxx</localaddress>

<!-- Loginserver information. -->
<loginserver>
<host>clmtyserver.dnsalias.com</host>
<port>5998</port>
<account></account>
<password></password>
</loginserver>

Both of our eqhost files read:
[LoginServer]
Host=clmtyserver.dnsalias.com:5998

My husband and I can both finally log in! I have no idea if anyone outside of our LAN can connect yet, because my friends are at work. Using my dyndns address in his Windows hosts file did not work for some reason. I don't entirely understand what goes on with the host file, to be honest.

I am still getting a Debug Error nearly every time either of us log in or out, but at least it works. I find it best to let him log in first before I log in, so that I can go ahead and watch for the error message. I'm going to post about it in another section of forum to see if I can get it worked out.

Hope this helps someone else out there!

[Dunmord]

Originally Posted by Eva Aisling

My husband can connect with hamachi, but my friend crashes at character select. He can make a char, but not enter world. I received a message in my server window that said "Unhandled server packet 0x3007" right before his client closed.

When that "Unhandled packet" occurs. Does the server crashes too or just the client?

I had a similar problem, only difference is that I was crashing when I tried to create an LDoN adventure(inside game). Here is my post: http://www.eqemulator.org/forums/sho...highlight=ldon.

[Eva Aisling]

Just the client crashes.

[Phoenix_79]

Originally Posted by Derision

I'll try

Things you need to understand first (which you probably do):

Each device (e.g. PC) on your LAN at home has an IP address, e.g. PC1 has address 192.168.1.100, PC2 has address 192.168.1.101, etc).

These are your internal IP addresses.

Your router will also have an internal IP address, e.g. it might be 192.168.1.1. This is the address your PCs forward packets to that need to get to the Internet.

Usually, your router will only have one external (Internet facing) IP address, e.g. it might be 88.50.30.20.

Packets leaving your LAN and heading out onto the Internet undergo Network Address Translation (NAT), i.e. when your PC1 sends a packet to, say google, before your router transmits that packet out onto the Internet, it replaces the source address of PC1 (192.168.1.100), with it's own Internet facing address (88.50.30.20 in my example). It also puts a unique source port address, so it knows, when Google replies to the packet, that it is PC1 that the reply has to go to.

OK, now, when you are running an EQEmu server, each component of the server 'listens' for incoming connections on specific ports, e.g. the LoginServer on 5998, world on 9000, zones on 7000+.

Because the connection to these components is initiated from outside your network, when your router receives a packet from the Internet, it will have your routers IP address (80.50.30.20 say) as the destination address, and, say destination port 5998, if someone wants to connect to your login server.

You need to tell the router which PC on your local LAN is to deal with incoming requests on port 5998. This is what people refer to as 'port forwarding' or 'opening ports'. In most cases you will have one PC running the loginserver, world and the zones, so you would tell your router to forward incoming traffic to all these ports to the internal IP address of your server.

Hope that makes sense. For PCs within your home network, accessing your local server, no port forwarding is required, it is only for inbound connections from the Internet to your server.

I just wanted to send a "Thank You!" your way for this excellent post!