Issues with logging in after patching. [Archive]

View Full Version : Issues with logging in after patching.

sneakykatze82

05-31-2010, 07:58 PM

System Information report written at: 05/31/10 17:33:27System Name: KATZE-PC[System Summary]Item Value OS Name Microsoft Windows 7 Home Premium Version 6.1.7600 Build 7600 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name KATZE-PC System Manufacturer HP-Pavilion System Model AY747AA-ABA p6310y System Type x64-based PC Processor AMD Athlon(tm) II X4 630 Processor, 2800 Mhz, 4 Core(s), 4 Logical Processor(s) BIOS Version/Date American Megatrends Inc. 5.13, 11/12/2009 SMBIOS Version 2.5 Windows Directory C:Windows System Directory C:Windowssystem32 Boot Device DeviceHarddiskVolume1 Locale United States Hardware Abstraction Layer Version = "6.1.7600.16385" User Name Katze-PCKatze Time Zone Central Daylight Time Installed Physical Memory (RAM) 6.00 GB Total Physical Memory 6.00 GB Available Physical Memory 4.67 GB Total Virtual Memory 12.0 GB Available Virtual Memory 10.2 GB Page File Space 6.00 GB Page File C:pagefile.sys [Hardware Resources][Conflicts/Sharing]Resource Device I/O Port 0x00000000-0x0000000F Direct memory access controller I/O Port 0x00000000-0x0000000F PCI bus I/O Port 0x000003C0-0x000003DF PCI standard PCI-to-PCI bridge I/O Port 0x000003C0-0x000003DF NVIDIA GeForce 210 IRQ 21 NVIDIA nForce Serial ATA Controller IRQ 21 Standard OpenHCD USB Host Controller IRQ 21 High Definition Audio Controller IRQ 22 Standard Enhanced PCI to USB Host Controller IRQ 22 Standard Enhanced PCI to USB Host Controller Memory Address 0xFD000000-0xFEBFFFFF PCI standard PCI-to-PCI bridge Memory Address 0xFD000000-0xFEBFFFFF NVIDIA GeForce 210 Memory Address 0xFEC00000-0xFFFFFFFF System board Memory Address 0xFEC00000-0xFFFFFFFF Motherboard resources IRQ 16 PCI standard PCI-to-PCI bridge IRQ 16 LSI 1394 OHCI Compliant Host Controller IRQ 17 PCI standard PCI-to-PCI bridge IRQ 17 High Definition Audio Controller IRQ 17 NVIDIA GeForce 210 Memory Address 0xDE000000-0xEFFFFFFF PCI standard PCI-to-PCI bridge Memory Address 0xDE000000-0xEFFFFFFF NVIDIA GeForce 210 Memory Address 0xD0000-0xDFFFF PCI bus Memory Address 0xD0000-0xDFFFF Motherboard resources Memory Address 0xA0000-0xBFFFF PCI standard PCI-to-PCI bridge Memory Address 0xA0000-0xBFFFF PCI bus Memory Address 0xA0000-0xBFFFF NVIDIA GeForce 210 I/O Port 0x000003B0-0x000003BB PCI standard PCI-to-PCI bridge I/O Port 0x000003B0-0x000003BB NVIDIA GeForce 210

Shareana

05-31-2010, 08:17 PM

Since it seem sto be a connection issue... a few things to try....<ul><li>Remove and add any exceptions that you may have added to your Firewall or av program then add them again.</li><li>Power cycle your modem.</li><li>Be sure that you are running as admin.</li></ul>If those do not help, then posting a tracert may give an idea of where the issue is...<a href="list.m?topic_id=353617">*** Read before posting ***</a>Good luck!

sneakykatze82

05-31-2010, 09:56 PM

Well after trying the suggestions three times nothing is working. Posted what I've been told I've needed to post and such but still, not getting anywhere. After seeing several other posts, I don't think this is a problem on my end or theirs. I'll just wait till it's fixed.

sneakykatze82

05-31-2010, 10:04 PM

After looking at several other posts I can see it is a problem with the Halas update. I don't know what went wrong but I can't pay for a game no one is able to play and with no one around to help on the day no one can play it makes it pretty frustrating. Hopefully this is resolved soon and they stop blaming the players and their computers for problems with an update.

Shareana

05-31-2010, 10:41 PM

Actually, you did not post a tracert like I suggested or like the Link that I posted suggested for connection issues, so therefore, you have not posted all the info... <img src="/eq2/images/smilies/8a80c6485cd926be453217d59a84a888.gif" border="0" />Someone else had connection issues after the Halas update and posted how he fixed it... <a href="http://forums.station.sony.com/eq2/posts/list.m?start=0&topic_id=479884#5336442" target="_blank">here</a>

sneakykatze82

06-01-2010, 05:21 AM

Tracing route to sdkeq2-01-01.everquest2.com [199.108.12.33]over a maximum of 30 hops: 1 2 ms 2 ms 2 ms 10.0.0.254 2 * * * Request timed out. 3 72 ms 19 ms 24 ms 24.164.209.29 4 60 ms 98 ms 20 ms gig4-0-0.dllatxchn-rtr6.tx.rr.com [70.125.217.101] 5 28 ms 44 ms 50 ms gig2-0-2.hstntxl3-rtr1.texas.rr.com [72.179.205.50] 6 124 ms 31 ms 25 ms ae-2-0.cr0.hou30.tbone.rr.com [66.109.6.108] 7 37 ms 78 ms 27 ms ae-0-0.pr0.dfw10.tbone.rr.com [66.109.6.181] 8 65 ms 35 ms 91 ms xe-10-1-0.edge4.Dallas3.Level3.net [4.59.32.13] 9 38 ms 34 ms 32 ms ae-72-70.ebr2.Dallas1.Level3.net [4.69.145.115] 10 61 ms 71 ms 68 ms ae-4-4.car2.SanDiego1.Level3.net [4.69.133.213] 11 96 ms 79 ms 71 ms ge-1-1.hsa1.SanDiego1.Level3.net [4.69.134.86] 12 84 ms 234 ms 86 ms vl861.sdtermswitch-1.sonyonline.net [63.215.251.130] 13 2540 ms 71 ms 76 ms vl831.sdkollsw-1.sonyonline.net [64.37.144.82] 14 60 ms 80 ms 66 ms sdkeq2-01-01.everquest2.com [199.108.12.33] Trace complete.Tracing route to ableq2-01-01.everquest2.com [199.108.202.33]over a maximum of 30 hops: 1 3 ms 2 ms 2 ms 10.0.0.254 2 * * * Request timed out. 3 165 ms 45 ms 22 ms 24.164.209.29 4 49 ms 17 ms 40 ms gig4-0-0.dllatxchn-rtr6.tx.rr.com [70.125.217.101] 5 95 ms 78 ms 67 ms gig2-0-3.hstntxl3-rtr1.texas.rr.com [72.179.205.46] 6 27 ms 28 ms 79 ms ae-2-0.cr0.hou30.tbone.rr.com [66.109.6.108] 7 25 ms 31 ms 33 ms ae-0-0.pr0.dfw10.tbone.rr.com [66.109.6.181] 8 25 ms 24 ms 31 ms tge8-1.fr3.dal.llnw.net [68.142.120.225] 9 82 ms 41 ms 101 ms tge7-1.fr4.atl1.llnw.net [69.28.172.38] 10 85 ms 61 ms 63 ms tge1-2.fr4.iad.llnw.net [69.28.172.34] 11 61 ms 70 ms 68 ms sony.ge4-12.fr4.iad.llnw.net [69.28.156.214] 12 116 ms 81 ms 77 ms vl47.ashaens-2.sonyonline.net [64.37.144.181] 13 109 ms 70 ms 92 ms ableq2-01-01.everquest2.com [199.108.202.33] Trace complete.Tracing route to amseq2-01-01.everquest2.com [195.33.135.161]over a maximum of 30 hops: 1 4 ms 2 ms 2 ms 10.0.0.254 2 * * * Request timed out. 3 87 ms 18 ms 26 ms 24.164.209.29 4 19 ms 24 ms 19 ms gig4-0-0.dllatxchn-rtr6.tx.rr.com [70.125.217.101] 5 52 ms 25 ms 24 ms gig0-1-0.hstntxl3-rtr1.texas.rr.com [72.179.205.74] 6 89 ms 54 ms 81 ms ae-2-0.cr0.hou30.tbone.rr.com [66.109.6.108] 7 56 ms 39 ms 49 ms ae-0-0.pr0.dfw10.tbone.rr.com [66.109.6.181] 8 89 ms 28 ms 54 ms xe-8-0-0.edge4.Dallas3.Level3.net [4.59.32.25] 9 32 ms 82 ms 46 ms ae-63-60.ebr3.Dallas1.Level3.net [4.69.145.52] 10 77 ms 63 ms 51 ms ae-7-7.ebr3.Atlanta2.Level3.net [4.69.134.22] 11 61 ms 87 ms 89 ms ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86] 12 57 ms 60 ms 66 ms ae-61-61.csw1.Washington1.Level3.net [4.69.134.130] 13 66 ms 59 ms 78 ms ae-62-62.ebr2.Washington1.Level3.net [4.69.134.145] 14 159 ms 145 ms 172 ms ae-44-44.ebr2.Frankfurt1.Level3.net [4.69.137.61] 15 149 ms 157 ms 152 ms ae-46-46.ebr1.Dusseldorf1.Level3.net [4.69.143.169] 16 193 ms 156 ms 183 ms ae-1-100.ebr2.Dusseldorf1.Level3.net [4.69.141.150] 17 157 ms 163 ms 146 ms ae-48-48.ebr1.Amsterdam1.Level3.net [4.69.143.209] 18 153 ms 146 ms 149 ms ae-1-51.edge3.Amsterdam1.Level3.net [4.69.139.137] 19 157 ms 146 ms 209 ms vl155.amsixsw-1.sonyonline.net [213.244.164.38] 20 149 ms 146 ms 149 ms amseq2-01-01.everquest2.com [195.33.135.161]

Shareana

06-01-2010, 08:37 AM

Well then, we now know that Hop 2 is your issue... I am not positive, but I think that is the users end ot the Tracert. Perhaps your modem?