Unable to log on to login server

[Kyndriana]

<p>Well poop! I've had computer issues for several months - severe lag, LD on zones, etc., that I figured was stemming from my available memory. Seeing as I know absolutely nothing about the back end/hard drive areas I had our office network company install some new RAM and clean up my computer a little bit.</p><p>I got it back today. Lots more memory, all my start up stuff is gone (thank goodness!) and they cleaned out a bunch of old registry stuff that was dead - but now I can't log into EQ2 which was the whole dang reason for getting this done in the first place! lol</p><p>I log in fine, get the TSO splash screen fine, then I start cycling through the login servers 1-9, again, too bad! =(   I'm not running an antivirus or firewall. My eq2info.txt paste ...Help?</p><p>Windows IP Configuration        Host Name . . . . . . . . . . . . : HOME        Primary Dns Suffix  . . . . . . . :         Node Type . . . . . . . . . . . . : Unknown        IP Routing Enabled. . . . . . . . : No        WINS Proxy Enabled. . . . . . . . : No        DNS Suffix Search List. . . . . . : hsd1.ms.comcast.net.Ethernet adapter outside:        Connection-specific DNS Suffix  . : hsd1.ms.comcast.net.        Description . . . . . . . . . . . : Marvell Yukon 88E8050 PCI-E ASF Gigabit Ethernet Controller        Physical Address. . . . . . . . . : 00-11-11-84-A8-7B        Dhcp Enabled. . . . . . . . . . . : Yes        Autoconfiguration Enabled . . . . : Yes        IP Address. . . . . . . . . . . . : 192.168.1.133        Subnet Mask . . . . . . . . . . . : 255.255.255.0        Default Gateway . . . . . . . . . : 192.168.1.254        DHCP Server . . . . . . . . . . . : 192.168.1.254        DNS Servers . . . . . . . . . . . : 192.168.1.254        Lease Obtained. . . . . . . . . . : Friday, August 28, 2009 8:11:57 PM        Lease Expires . . . . . . . . . . : Friday, August 28, 2009 9:11:57 PMTracing route to ableq2-02-01.everquest2.com [199.108.202.65]over a maximum of 30 hops:  1  Transmit error: code 65.Trace complete.Tracing route to ableq2-02-01.everquest2.com [199.108.202.65]over a maximum of 30 hops:  0  HOME.hsd1.ms.comcast.net. [192.168.1.133]   1  Transmit error: code 65.Transmit error: code 65.Transmit error: code 65.Computing statistics for 25 seconds...            Source to Here   This Node/LinkHop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address  0                                           HOME.hsd1.ms.comcast.net. [192.168.1.133]                               100/ 100 =100%   |  1  ---     100/ 100 =100%     0/ 100 =  0%  HOME [0.0.0.0] Trace complete.</p>

[Kigneer]

<p><cite>Kyndriana wrote:</cite></p><blockquote><p>        DNS Servers . . . . . . . . . . . : 192.168.1.254</p></blockquote><p>That is the problem. That's an internal IP, not the DNS IP (ISPs would have at least 2, some 3, and auto-configuring your network settings will help to obtain it from Comcast).</p><p>Try ipconfig/release and ipconfig/renew and see if that works. Then, ipconfig/flushdns and ipconfig/registerdns, to clear and reregister the DNS resolver cache.</p>

[Kyndriana]

<p>I went into the Network Connections, had Knowledge Base open to routers, to ports, and to proxy - I ran pathpings and tracerts ... to make a long story short, it's working now, but I have absolutely no idea what it was, or how it got fixed. lol ... oh boy</p><p>~Kyn</p>

[Wingrider01]

<p><cite>Kigneer wrote:</cite></p><blockquote><p><cite>Kyndriana wrote:</cite></p><blockquote><p>        DNS Servers . . . . . . . . . . . : 192.168.1.254</p></blockquote><p>That is the problem. That's an internal IP, not the DNS IP (ISPs would have at least 2, some 3, and auto-configuring your network settings will help to obtain it from Comcast).</p><p>Try ipconfig/release and ipconfig/renew and see if that works. Then, ipconfig/flushdns and ipconfig/registerdns, to clear and reregister the DNS resolver cache.</p></blockquote><p>Not always, if the OP is on a router(given the base fact that the internal address is non-routable this is a good possibliity), the router can hold the external routable IP's for the DNS primary and secondary, the machine would then use the router address for the DNS, and WINS entries. I do that, my router points to OpenDNS addresses for security and the machines point at my router address for DNS</p><p>To the OP, when your tech people cleaned up the machine it sounds like they reset the firewall to default, what you did was open them back up</p>

[TSR-DanielH]

<p><cite>Kyndriana wrote:</cite></p><blockquote><p>I went into the Network Connections, had Knowledge Base open to routers, to ports, and to proxy - I ran pathpings and tracerts ... to make a long story short, it's working now, but I have absolutely no idea what it was, or how it got fixed. lol ... oh boy</p><p>~Kyn</p></blockquote><p>Your 'to make a long story short' skipped all the good parts!  Anyway, I'm glad to hear that you got it working.  Let us know if you need any help in the future.</p>