Go Back   EQEmulator Home > EQEmulator Forums > Support > Support::MiniLogin

Support::MiniLogin Support forum for problems with the official MiniLogin release.

Reply
 
Thread Tools Display Modes
  #1  
Old 08-20-2008, 11:29 AM
laxative
Hill Giant
 
Join Date: Aug 2008
Location: NorthEast
Posts: 115
Default Hanging after Server Select (long post) -- fixed mid post

Greetings,

First off I'm new, but not new to EQ type forums, I have searched extensively and will first provide my environment, and answers to the searches I did on the forums.

Environment:

Server Computer: Dual Core 2.4 GHZ, 4 GB RAM Windows Vista (32) Machine. It's connected to a Linksys10/100 Wireless Router with a 10Mb internet connection.

Router: The router has the PC as a DMZ host. I can connect to services on the PC easily, RDP etc and my EQ login works partially (more on that later)

Client: DellD630 Laptop, Connecting from Outside, Windows Vista(64), Fresh, Unpatched Titanium installation from the 5 Disks. eqhost file properly updated to the public interface on the Linksys router, and the patchme suffixed to my eqgame shortcut

EQEmu Environment: MiniLogin, running, Server running, 5 instance of zone.exe running, Angelox Database setup, two accounts have been created one for the local lan, and one for my outside connection, which always comes from the same IP, and is verified in the minilogin window.

PROBLEM: Client Connects appropriately to Minilogin, Logs in successfully, Sees server list EVERY TIME. (I've left out my results to the no server list searches as I'm not having that). What Im seeing is an unknown packet in the minilogin window here it is:

1994763 New client from ip: 204.61.205.150 port: 58303
Unknown packet: .8564080 [176.237.144.0:16->0.0.0.0:0]
[OpCode 0x0003 (OP_Unknown) Size=11]
00000: 00 06 00 00 00 00 00 00 - 00 00 00

3294528 New client from ip: 127.0.0.1 port: 55347
Unknown packet: .8572680 [176.237.144.0:16->0.0.0.0:0]
[OpCode 0x0003 (OP_Unknown) Size=11]
00000: 00 06 00 00 00 00 00 00 - 00 00 00

What's strange is that when I connect with my patched client (using eqgame.exe and the modified eqhosts) I get connected to minilogin, I enter the appropriate account, then I see the expected errors for having the wrong client:
[Debug] [NET__IDENT_TRACE] 10.1.1.101:55348: First opcode 0x4892 did not match e
xpected 0x7213
BUT, when connecting from outside,(with a good titanium client) I do not see anything happening in World.exe window.

What I've tried:

Router enabled port forwarding for all ports, 7000 - 65535 to my EQ server.

That didnt work, so I enabled the eq server computer as dmz host (allowing all traffic through) I can map drives to the sucker so I know that the connection is valid, and fast.

Running EQGAME from the internal client, and external client in compatibility mode.

>>>>>>
Well Crap...

FIXED..

I had to add my LinkSys Router External IP address into the Address Component of the xml file and restart the wolrd... I will post anyway if this might be useful to someone else.
Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

   

All times are GMT -4. The time now is 11:05 PM.


 

Everquest is a registered trademark of Daybreak Game Company LLC.
EQEmulator is not associated or affiliated in any way with Daybreak Game Company LLC.
Except where otherwise noted, this site is licensed under a Creative Commons License.
       
Powered by vBulletin®, Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Template by Bluepearl Design and vBulletin Templates - Ver3.3