Outside connections

leslamarch · #1 06-27-2007, 05:32 AM

Hello all,
Just a few questions, I have searched for this topic and found several locations that talked about this topic, but with not much resolve. I have been running the server for a little while and thought all was well when i connect to the server while using the client on the server computer. But when trying to connect inside or outside of the network i have no luck. For the purpose of trouble shooting i DMZ'd the router and yet no connection ever reaches the console. So I'm left to believe that i have missed something minor, on a side note i set up a wow server on same box to see if that it could receive connection and it did flawlessly.
So what component of the server settings makes the Incoming connections actually connect? "eqemu_config.xml"? here is what i have set there
first try
<address>192.168.*.*</address>
<localaddress>127.0.0.1</localaddress>

second try

<address>name.no-ip.com</address>
<localaddress>127.0.0.1</localaddress>

I have also tried other variations like changing the local address to my machine ip.
Any help would be greatly Appreciated.
Best Regards,
LL

techguy84 · #2 06-27-2007, 05:55 AM

Change your local address to your internal ip like 192.168.x.x. See what happens there.

leslamarch · #3 06-27-2007, 06:42 AM

*Face turns red with embarrassment*
It worked just perfect, if i may understand this correctly, is it set to 192.168.1.1 instead of 127.0.0.1 because the login server is hosted elsewhere and It needs to know what computer on the network is running the server? Just trying to figure out why so i can understand eqemu just a bit more.
Thank you very much for your patiences and all the great help
LL

Darkonig · #4 06-27-2007, 07:45 AM

It needs to be other than 127.0.0.1 if the server needs to talk to locations other than localhost. Using the localhost address does seem to work ok if you do not run a local client at all, but can cause problems if you decide to connect locally at some point for testing or whatever.

If you are running only on the local machine and never connect from external then you must use 127.0.0.1. If you do not, it will fail if your network connection dies for any reason. (note: it will work if the network connection is up, but why take chances).

rodorant · #5 06-28-2007, 05:53 AM

I am having a similar issue, I try to connect to my server from another computer on my network and it will not connect.

Could you post what you now have your config ip's set at?




This is what mine is set at now and is not working. Server shows up but cannot connect to it. Should 'my server IP' be set to an actual address?

Anyone have any idea?

Angelox · #6 06-28-2007, 06:32 AM

How about firewalls, you got any of those running?

leslamarch · #7 06-28-2007, 06:56 AM

Well i set it to this after techguys recommendations. First I DMZ'd Router for testing purposes only.

<address>name.no-ip.com</address>
<localaddress>192.168.1.1</localaddress>

and it then let me connect.
Hope this helps you
best regards,
LL

rodorant · #8 06-28-2007, 09:47 AM

so it really does not matter what you set the 'address' field to right?

and that is your gateway address right? not your serving computer IP?

leslamarch · #9 06-28-2007, 02:40 PM

The local address is set to my server computer, sorry i didn't state that earlier.

rodorant · #10 06-28-2007, 02:41 PM

awww man after days and days I figured it out,

I was checking my fire wall settings on my client computer like a slacka and not on my server computer lol, I had firewall on. Working fine now. I will try the DMZ setting off in a bit and see if it works.

techguy84 · #11 06-28-2007, 04:22 PM

Rodorant, make sure you remove the  at the begining and end of those lines you posted. Those things comment the line out so it will not be used by the emulator and can cause problems under some situations like the minilogin.

I had it working fine under public, but when I went to work with the minilogin, I had to remove them to prevent connection timeouts. I belive that there in use for the minilogin because your directly handling the client connections and with the public login, it take care of those things. Could be wrong, but its the conclusion that I come up with.

As far as DMZ'ing goes. I never had to mess with it. All DMZ does is provide a DIRECT connection from the internet to your computer. No firewalls, all ports wide open. This may be good if you cant get port forwarding to work, but I would suggest trying to forward some ports before opening up the flood walls.

Note: DMZ info obtained from my router and DSL modem. May be wrong, but this is what they do when I use the DMZ. Applies to a Belkin Wireless router and to a Linksys VoIP router, have used both.