External can connect - Internal cannot connect?
 

Here's my spill. I've searched the forums extenstively, fixing most of my problems, creating a running server. I have set up using minilogin, server works great- no problems nor errors. I have changed all the settings so that the server is hosted via EQemu login servers. My server appears on the list, people have been connecting and playing, but when I attempt to connect to the server from inside the network that the host is on, I cannot connect and receive 1017.

I am using a Linksys BEFSR41 (standard Linksys router). DMZ hosting is enabled for the IP with the server. Judging by the server dialog, my Internal computers are going to the Internet to connect to my server blocking a link between my server and internal computers. I have tried connecting on multiple computers that all worked with minilogin and receive the same thing. Obviously, a NAT issue.

Server World.exe Dialog
My routers IP address is 192.168.1.1 so I'm guessing that the router is blocking the connection to my own server being that my computers internal address is 192.168.1.110. I plan on having the server online for a LAN party this upcoming weekend so I have to have all the users within the Internal network to be able to connect and wish to allow others to join if they like as well as use EQemu's uber login server so everyone has own accounts and user levels.

Please keep in mind that the server is configured perfectly at this point in time being that external users can connect. The server name specfically is crackerfest.com [Alpha Testing] if you wish to see for yourself. Any one have a remedy?

Thanks in advance,



Yeormom

I'm not sure if setting a host as DMZ properly directs traffic to it from the internal network -- if it does, ignore the rest of the post. You may want to try using port forwarding. I'm not sure if this will solve the problem or not, but I believe that I have seen Linksys routers direct traffic from the internal network correctly with it. Also, afaik, all redirected traffic, incoming from external or internal, will be seen as coming from the router (192.168.1.1).

Why would internal traffic state that it was coming from the router? It's operating in gateway mode.

Because if you are receiving an external address from the login server, your computer will try to connect to that. When you try to connect to that external ip, your router will see that it is itself, and reroute it back locally. It will be seen as coming from that router internally. I could be wrong, but that is how I understand that it operates.

same as m0oni9 said here.

most routers, if not all, wont allow an outgoing packet (from EQ client) to re-enter and be processed to the LAN (your DMZ / forwarded-to EQEmu server).

If you're lucky enough to have such router (i don't know them), ok.

Else the solution is to use hosts.txt in windows configuration files to map your External ip (as known and told by EQEMu loginservers) to internal ip (this will allow direct addressing, without round trip by the router. EQ client will ask system for external, but now system knows how to translate to internal). It's been described in one of the LAN or NAT guides.

Note the previous solution is quite unpleasant when using dynamic ip. But it's a solution. Still better than to set up an external proxy :)

Thanks for pointing that out melquiades. I'll be sure to do some more searching and try it out. I'll post a guide back here if I get it going.