logon authintication failure

WinEQ 2.0 Lite discussion

Moderators: Lavish Software Team, Moderators

Post Reply
Pulgrey
Non-Subscriber
Posts: 2
Joined: Tue Jan 17, 2006 6:55 am

logon authintication failure

Post by Pulgrey » Wed Oct 17, 2007 12:02 am

only use WinEQ 2.0 for EQ1 , today while using 2 sessions and attempting to load a 3rd session I got the Lavish logon pop up window , which I hadn't seen since installing and clicking log in automatically. I re-entered my account info and got a failure message. Tried using some of my other account info's incase I misremembered changing the information from what I had written down.

I came to the posting boards here , had no issues with logging in. I changed my password and e-mail addy to a secondary account , clicked the link from the e-mail sent , relogged in the board , but the logon for WinEQ still gives me :

" Authentication failed (-114 ). You will need to successfully authenticate to use WinEQ "

I had been using 2 instances of WinEQ most of the day , and then this afternoon hit this problem.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_gdr.070227-2254
System Physical RAM: 1551/2045MB
Page File: 3949/4594MB
Virtual Memory: 903/2047MB (Extended: 0MB)
CPU 1: Intel(R) Pentium(R) 4 CPU 3.20GHz @ 3200MHz
CPU 2: Intel(R) Pentium(R) 4 CPU 3.20GHz @ 3200MHz
CPU Affinity Mask: 1
Video 1: \\.\DISPLAY1/RADEON X300/X550 Series
Video 2: \\.\DISPLAY2/RADEON X300/X550 Series Secondary
Video 3: \\.\DISPLAYV1/NetMeeting driver
Video 4: \\.\DISPLAYV2/RDPDD Chained DD
Monitor 1: \\.\DISPLAY1 (0,0,1152,864) (1152x864) PRIMARY
Sound: ?
DirectX: 4.09.00.0904
Internet Explorer: 7.0.5730.11
WinEQ: 2.15

Loaded Modules:
-----------------------------------
Module 0: C:\Games\everquest\eqgame.exe
Module 1: C:\WINDOWS\system32\ntdll.dll
Module 2: C:\WINDOWS\system32\kernel32.dll
Module 3: C:\Games\everquest\mss32.dll
Module 4: C:\WINDOWS\system32\USER32.dll
Module 5: C:\WINDOWS\system32\GDI32.dll
Module 6: C:\WINDOWS\system32\WINMM.dll
Module 7: C:\WINDOWS\system32\ADVAPI32.dll
Module 8: C:\WINDOWS\system32\RPCRT4.dll
Module 9: C:\WINDOWS\system32\WSOCK32.dll
Module 10: C:\WINDOWS\system32\WS2_32.dll
Module 11: C:\WINDOWS\system32\msvcrt.dll
Module 12: C:\WINDOWS\system32\WS2HELP.dll
Module 13: C:\WINDOWS\system32\DINPUT8.dll
Module 14: C:\WINDOWS\system32\d3dx9_30.dll
Module 15: C:\Games\everquest\DSETUP.dll
Module 16: C:\WINDOWS\system32\VERSION.dll
Module 17: C:\WINDOWS\system32\ole32.dll
Module 18: C:\WINDOWS\system32\WININET.dll
Module 19: C:\WINDOWS\system32\SHLWAPI.dll
Module 20: C:\WINDOWS\system32\Normaliz.dll
Module 21: C:\WINDOWS\system32\iertutil.dll
Module 22: C:\Games\everquest\xul.dll
Module 23: C:\Games\everquest\js3250.dll
Module 24: C:\Games\everquest\nspr4.dll
Module 25: C:\Games\everquest\MSVCR71.dll
Module 26: C:\Games\everquest\plc4.dll
Module 27: C:\Games\everquest\plds4.dll
Module 28: C:\WINDOWS\system32\SHELL32.dll
Module 29: C:\WINDOWS\system32\WINSPOOL.DRV
Module 30: C:\WINDOWS\system32\comdlg32.dll
Module 31: C:\WINDOWS\system32\COMCTL32.dll
Module 32: C:\WINDOWS\system32\IMM32.dll
Module 33: C:\WINDOWS\system32\LPK.DLL
Module 34: C:\WINDOWS\system32\USP10.dll
Module 35: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03\comctl32.dll
Module 36: C:\WINDOWS\system32\uxtheme.dll
Module 37: C:\Games\WinEQ2\EQPlayNice.dll
Module 38: C:\Games\WinEQ2\Lavish.dll
Module 39: C:\WINDOWS\system32\iphlpapi.dll
Module 40: C:\WINDOWS\system32\MSCTF.dll
Module 41: C:\Games\WinEQ2\WinEQ2.dll
Module 42: C:\WINDOWS\system32\PSAPI.DLL
Module 43: C:\WINDOWS\system32\mswsock.dll
Module 44: C:\WINDOWS\system32\hnetcfg.dll
Module 45: C:\WINDOWS\System32\wshtcpip.dll
Module 46: C:\WINDOWS\system32\DNSAPI.dll
Module 47: C:\WINDOWS\System32\winrnr.dll
Module 48: C:\WINDOWS\system32\WLDAP32.dll
Module 49: C:\WINDOWS\system32\rasadhlp.dll
Module 50: C:\Games\WinEQ2\WinEQ2-EQ.dll
Module 51: C:\WINDOWS\system32\MSIMG32.dll
Module 52: C:\Games\WinEQ2\WinEQ2-D3D9.dll
Module 53: C:\Games\WinEQ2\WinEQ2-D3D8.dll
Module 54: C:\Games\WinEQ2\WinEQ2-DI8.dll
Module 55: C:\WINDOWS\system32\msctfime.ime
Module 56: C:\WINDOWS\system32\OLEAUT32.DLL
Module 57: C:\WINDOWS\system32\NTMARTA.DLL
Module 58: C:\WINDOWS\system32\SAMLIB.dll
Module 59: C:\Games\everquest\EQGraphicsDX9.DLL
Module 60: C:\WINDOWS\system32\d3d9.dll
Module 61: C:\WINDOWS\system32\d3d8thk.dll
Module 62: C:\Games\everquest\dpvs.dll
Module 63: C:\WINDOWS\system32\HID.DLL
Module 64: C:\WINDOWS\system32\SETUPAPI.DLL
Module 65: C:\WINDOWS\system32\WINTRUST.dll
Module 66: C:\WINDOWS\system32\CRYPT32.dll
Module 67: C:\WINDOWS\system32\MSASN1.dll
Module 68: C:\WINDOWS\system32\IMAGEHLP.dll
Module 69: C:\WINDOWS\system32\MSACM32.dll
Module 70: C:\WINDOWS\system32\wdmaud.drv
Module 71: C:\WINDOWS\system32\msacm32.drv
Module 72: C:\WINDOWS\system32\midimap.dll
Module 73: C:\WINDOWS\system32\DSOUND.DLL
Module 74: C:\WINDOWS\system32\KsUser.dll

Direct3D9:
-----------------------------------
Driver: RADEON X300/X550 Series/ati2dvag.dll/6/14/10/6683
Adapter Display Mode: 1152x864 D3DFMT_X8R8G8B8
Game Display Mode: 1152x864 D3DFMT_UNKNOWN (Windowed)
Current Adapter: 0
Available Texture Memory: 621MB
Direct3D8:
-----------------------------------
Adapter Display Mode: 0x0 D3DFMT_UNKNOWN
Game Display Mode: 0x0 D3DFMT_UNKNOWN
Current Adapter: 0
Available Texture Memory: (not currently available)
DirectInput8:
-----------------------------------

EQPlayNice:
-----------------------------------

EverQuest:
-----------------------------------
Profile 3: full options
EQ Path: C:\Games\everquest
EQClient.ini: .\eqclient.ini
Patch: OFF Server Type: Normal Locale: us
Video Adapter: Application Controlled
Luclin models: 29 (+145 min RAM)
MipMapping: ON (+4 min RAM)
Sound: ON (+22 min RAM)
Dynamic Lighting: ON (+4 min RAM)
Texture Caching: ON (+0 min RAM)
Texture Quality: 2. MEDIUM (+30 min RAM)
Calculated minimum RAM: 488MB (BASE+205MB)
Level of Detail: 1
MaxFPS: 68
Additional setting: HardwareTnL=false
Additional setting: VertexShaders=0
Additional setting: 20PixelShaders=TRUE
Additional setting: 1xPixelShaders=TRUE

blahblah45
GamingTools Subscriber
Posts: 2
Joined: Sat Sep 08, 2007 5:05 am

Post by blahblah45 » Fri Oct 19, 2007 7:16 pm

I'm getting the same problem on two machines.

kuddel
GamingTools Subscriber
Posts: 2
Joined: Thu Aug 11, 2005 8:06 am

Post by kuddel » Sat Oct 20, 2007 12:09 am

Have same Problem Today.

kuddel
GamingTools Subscriber
Posts: 2
Joined: Thu Aug 11, 2005 8:06 am

Post by kuddel » Sat Oct 20, 2007 12:16 am

Eventually this Problem comes from a Everquest Patch done on 19. October 2007 ?

Kate6395
Non-Subscriber
Posts: 1
Joined: Fri Jan 18, 2008 8:28 pm

Post by Kate6395 » Thu Mar 06, 2008 9:35 am

I am having this problem too for a number of days.

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Fri Mar 07, 2008 10:14 am

Error code -14 (or -114) indicates that you were disconnected from the server before the software received all of the information it needed. This could be due to ISP issues and may solve itself in a matter of minutes, hours or days. It could also be due to network issues on your local network, for example if the bandwidth is saturated or if you're on a poor wireless connection.

Unfortunately I don't have a specific thing or things you can try with this one, but I will be working on making the system a bit more robust when it comes to this particular error. I can't promise anything in the next few weeks but it will definitely be fixed as soon as I can. In the meantime, it never hurts to try again.

Manni
GamingTools Subscriber
Posts: 5
Joined: Wed Dec 08, 2004 10:47 am

Post by Manni » Sun Apr 27, 2008 3:13 pm

Everquest 1:
mh. had the same problem for weeks and today I couldnt even log on half of the accounts... the problem could also be that WinEq always has to login at the WinEQ-Server. I have NO problem to work with EQ, its more a problem that the WinEQ has no connect to the WinEQ-server. How would be a solution, when WinEQ doesn't find a connect for an update that he would mention that but ignore this fact and nevertheless boot up EQ or another system. Instead of doing this it only stops with an error message and let me put in the name and password and that twice for one account sometimes, only to tell me AFTER EQ HAS ITS LOGIN DONE AND LOADING that it doesn't work and stops also EQ from loading. Even if you say that WinEQ should remember the password it ignores it without contact and stops loading. It is so annoying working over an hour to get the 6 chars online that it is easier to work without WinEQ. So if that works than the bug is not the ISP but the WinEQ-Server. That sounds harsh but today was really nasty with that problem. Perhaps this possibility in changing how WinEQ works helps a bit.
You have to think about that meanwhile nearly every little tool needs a safe connect to the Internet and that means that all depends on the servers they need for a connection. So the chance decreases for a working system the more tools you run. Normally I cancel all connection to the net with firewalls but some need this connection but if a single one does not get it then the tool is not working.

Manni
GamingTools Subscriber
Posts: 5
Joined: Wed Dec 08, 2004 10:47 am

EQ 1 - Problems - forgotten things

Post by Manni » Sun Apr 27, 2008 3:15 pm

oh I should tell that I have started EQ again some weeks ago after a longer break period and I cannot remember to had that problem in that way over a year ago.

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Sun Apr 27, 2008 3:21 pm

I'm not really sure what you're saying, Manni. Are you having a problem? If you are, please explain the problem with as much detail as you can. If you are launching sessions on 4 different PCs at the same moment, that would be useful to know, for example.

Manni
GamingTools Subscriber
Posts: 5
Joined: Wed Dec 08, 2004 10:47 am

Post by Manni » Sun Apr 27, 2008 4:36 pm

Sorry Lax,
english is not my native language, I hope, I explain this right.
I have 3 different systems, launching them with 6 clients. I have a very good ISP-Connection. I will change it soon into 30MB with Fastpath that would be surely better as 6MB/s atm. But this part seems stable.

One system with one client, one with 2 clients, one with 3 EQ-Clients. All run at WinXP Pro SP2. Today it works like intended but yesterday e.g. there was no connection possible on all 6 clients. Only three were OK. With WinEQ I only got a message something like "there is no connection possible at moment, try it again later". Today the message didnt came so I am not sure about the exact message. When I quit WinEQ and tried it without, I had no problems to connect to EQ-Servers. So if this problem occurs again, I will notice the text more exactly.
I know for a developer it is difficult to get such inappropriate information but I thought that this problem could be not the ISP but the WinEQ-Server and the connection of WinEQ to that server. Perhaps there is some kind of too much traffic which cannot be handled properly. I only assume. Maybe you can analyze it better.

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Sun Apr 27, 2008 6:51 pm

Nah, our server doesn't come under that much load. eqjoe replied to another thread in recent days complaining about lack of connectivity to explain that there were problems in one or more internet backbone routers at the time the problems were reported:
There was a lot of Internet connectivity issues today. Yes, the interweb was broken. And, this probably explains why you had this issue.
http://www.lavishsoft.com/forum/viewtop ... 6036#16036

eqjoe works with major ISPs, and if I could name anyone that would know when something major is broken with the internet, it's him. Your ISP interconnects with other ISPs in order to connect you to your destination. The ISP hosting EQ is different from the ISP hosting our authentication server.

Also, to explain why you would get the box after EQ has successfully launched, the EQPlayNice product is authenticating later in the session, for compatibility reasons. If you were to disable EQPlayNice, you could only possibly get the connection error box before WinEQ launches.

With that said, we do process thousands of connections daily, and if this were a fundamental problem with our product, I would very much expect to experience the problem myself (I am about 1000 miles away from the server, not exactly local), or for many more posts. The forum posts here complaining about connection issues are consistent with problems at the network level beyond our control.

I apologize for the inconvenience. Welcome to the internet :)

Manni
GamingTools Subscriber
Posts: 5
Joined: Wed Dec 08, 2004 10:47 am

Post by Manni » Sun Apr 27, 2008 7:52 pm

OK, then i disable EQPlayNice. The stuff works if I simply ignore the requester with the password section. So only the Problem with EQPlayNice is left. That is what I meant. If a software tool relies completely on the internet and some more tools are involved with the same behavior then the chance of having problems are much higher when the connection is a MUST.
It is not a problem of the internet but of the software which forces the connection because it doesn't work without. It may a reason of compatibility if EQPlayNice does the connect but this connection is not always necessary if no patch has been done. If there would be an option for not checking everytime and updating but simply starting the tool, that would avoid these problems (only an idea).

Today it works. Many thanks for the reply.

Post Reply