eq patch?
 

could the most current EQ patch cause compatability issues with trying to login to emu servers? or your own on mini login?

I am pretty sure the latest patche broke loging into EQEmu I don't patch unless a new EQEmu is released :)

oh, so thats why i cant login grr

latest patch works fine.

I can login to other peoples servers fine, when I try and host my own, it sppears on the list, but when I try and log in it gives me the (you must re run everquest patch - 1017 error)

---eqhost---

[Registration Servers]
{
"eqlogin.eqemu.org:5999"
}
[Login Servers]
{
"eqlogin.eqemu.org:5999"
}

---END---


---Boot5zones.bat---

REM:--------------Start-----------------------


@echo off
start zoneNT . 63.228.50.206 7995 127.0.0.1
start zoneNT . 63.228.50.206 7996 127.0.0.1
start zoneNT . 63.228.50.206 7997 127.0.0.1
start zoneNT . 63.228.50.206 7998 127.0.0.1
start zoneNT . 63.228.50.206 7999 127.0.0.1
exit
cls


REM:---------------END------------------------



---Loginserver.ini---

[LoginServer]
loginserver=eqlogin.eqemu.org
worldname=sharky
locked=false
account=
password=
worldaddress=63.228.50.206
loginport=5999

---END---



---db.ini---

[Database]
host=localhost
user=caravelle
password=*****
database=eq

---end---


*Both my World.exe and Zonebat.exe run error free, im on windows XP.
ive been trying to get this to work for a few days now so im kinda tired out, any help would be great.

make sure to read and try all the 1017 windows xp stuff on this board...

also 63.228.xxx.xxx??? You on Quest DSL? If so what modem do you have... If you have cisco 675-678 it most likely is an issue with your NAT table as it was on mine.

If everything in that last paragraph confused you... I can't help. If it made alot of sence.. I may be able to help you on that side of it.
P.S. Last EQ patch did not effect the functionality of eqemu any.

yes yes! I have sisco 678 and am with Qwest DSL, did you get yours to work by messing around with it? and if so, what do I have to do?

First off, please specificaly address each point of my post.

Second you must be near SF, SD. Am I right? Reason being is that is the same ip set I get in time to time for my WAN address. 63.228.xxx.xxx

Im Minnesota, Minneapolis

Ive tried alot of the 1017 error fixes on the boards, but none work for me, whatever I do It always gives me the 1017 error when I try and host a server and log into it.

-- sorry that i didnt respond to each one of your points

First off all your *.ini's and *.bat's look fine.
/em applaud

Your at least far enough ahead of the rest that I'll try and help you out.

Second read THIS post.... whether or not your realize it.. your question is answered here.

Next after this is going to take a little work do to we are going to have to make config changes in your router.. also I will have to explain exactly what we are doing as. The config changes we make in your router have a good chance of breaking as soon as your IP changes.

Please say your a computer tech....?????

unfortunatlly I am not a computer tech, I am better with computers than most though.

I went into LAN options in control panel and set firewall for off, I read in the other thread that 9000, AND 7999-7995 all MUST be open on your firewall, does turning off firewall in my LAN options do this for me?

long! but detailed and fun to read :-)
 

That is important yes... but not what is causing your problems.

Your problem is occurring before WINxp's fire wall an even get its hand on the data...

short lesson:

NAT = Network Address Translation.

What NAT does... it allows you to have one real IP (your 63.228.xxx.xxx) for many None real IP's (all your PC's you have running at home on your "guessing" 192.168.0.0 network.) FYI 192.168.0.0 is a private address.. No router will pass that address. But that isn't a bad thing.
This isn't so un-similar to the concept behind routing.

Here inlays the problem.
For ease sakes. Lets say this. You have 2 puters in your lan. Your eqemu server has an ip address of 192.168.0.2 and your Ever Quest playing computer (or client I will call it) has an ip address of 192.168.0.3. Also lets say your Cisco 678

:( /cry if only someone knew about DI-804 routers i would have a server up n running!

Hey Mell - Im on a cisco 675, same problem I believe. I followed your instructions, but heres what my show nat is telling me now.
I placed the x's there to protect my IP:

Inside Local Inside Global Timer Flags Protocol
192.168.0.2: 9000 63.228.xx.xxx: 9000 30 0x2041 ***
192.168.0.2: 9000 63.228.xx.xxx: 9000 0 0x41 tcp
192.168.0.2: 9000 63.228.xx.xxx: 9000 0 0x41 tcp
192.168.0.2:*****63.228.xx.xxx:***** 0 0x3041 ***
192.168.0.2: 9000 63.228.xx.xxx: 9000 0 0x41 tcp
192.168.0.2: 9000 63.228.xx.xxx: 9000 0 0x41 tcp
192.168.0.2: 7990 63.228.xx.xxx: 7990 0 0x41 tcp
192.168.0.2: 7991 63.228.xx.xxx: 7991 0 0x41 tcp
192.168.0.2: 7992 63.228.xx.xxx: 7992 0 0x41 tcp
192.168.0.2: 7993 63.228.xx.xxx: 7993 0 0x2041 ***
192.168.0.2: 7994 63.228.xx.xxx: 7994 0 0x2041 ***
192.168.0.2: 7995 63.228.xx.xxx: 7995 0 0x2041 ***
192.168.0.2: 7996 63.228.xx.xxx: 7996 0 0x2041 ***
192.168.0.2: 7997 63.228.xx.xxx: 7997 0 0x2041 ***
192.168.0.2: 7998 63.228.xx.xxx: 7998 0 0x2041 ***
192.168.0.2: 7999 63.228.xx.xxx: 7999 0 0x2041 ***
--------------------------------

This part happened after the Boot5Zones, once I went back into telnet:

10.0.0.2: 1124 63.228.xx.xxx:20507 30 0x66 tcp
10.0.0.2: 1143 63.228.xx.xxx:20515 30 0x46 udp
10.0.0.2: 1145 63.228.xx.xxx:20516 90 0x46 udp
10.0.0.2: 5999 63.228.xx.xxx: 5999 30 0x46 icmp

-----------------------------------------------------------------------------------

Please let me know what I need to do in order to fix the problem (if you can help).
Or if anyone else has an answer for this, let me know!

Thanks.
-Sharky

So far it looks like your headed in the right direction... But do this for me... Telnet into your router after a long period of NO internet activity (90 + seconds) and do a show NAT.
Post that here. So I can see what your blank NAT looks like. It should have these new static NAT entries in there if all is well... But looking at what you posted, a few things worry me. Mainly these four lines:

192.168.0.2: 9000 63.228.xx.xxx: 9000 30 0x2041 ***
192.168.0.2: 9000 63.228.xx.xxx: 9000 0 0x41 tcp
192.168.0.2: 9000 63.228.xx.xxx: 9000 0 0x41 tcp
192.168.0.2:*****63.228.xx.xxx:***** 0 0x3041 ***


I'm worried you accidently put the same thing in too many times.. plus you stumbled accross that last one... Well the last one just aint right! :-)

Either way if that is the case.. No biggy we can just blow them ALL out and I will just cut and Paste exactly what you need to input.

P.S. How is you eqemu failing at this point exactly?