Jump to content
  • Sign Up

Potential fix for the log in server issue


Recommended Posts

> @"Healix.5819" said:

> > @"Celldrax.2849" said:

> > It's touchy though. Doesn't always log in, and don't have access to some things like gem store and TP.

>

> If GW2 is open, close it.

>

> Open the run dialog by pressing WindowsKey+R and open:

> cmd

>

> A command prompt should pop up. Enter the following command, which will clear your DNS cache:

> ipconfig /flushdns

>

> Press WindowsKey+R again and open:

> %temp%

>

> The temp folder should pop up. Delete every folder beginning with gw2cache. It's possible for the trading post to actually cache an error page, preventing it from loading.

>

> If the trading post _still_ doesn't work, ensure that your antivirus, firewall or any other web filtering software you may have isn't blocking it. G DATA and FortiClient for example are also blocking it. You can try visiting the trading post in your browser to see if shows any messages - usually security software will show a warning page. https://tradingpost-dfw-live.ncplatform.net/humans.txt and https://tradingpost-live.ncplatform.net/humans.txt

 

Oh ho ho, it seems we might be onto something here. Did the DNS flush and deleted cache, and seems to all be working now.

 

Thanks mate. Hopefully that's the end of that till we get a proper fix.

Link to comment
Share on other sites

> @"anx.7549" said:

> > @"Bunny.6185" said:

> > Google DNS isn't very practical for Oceanic players. It slows things down considerably.

> > I'm getting a series of issues connecting to the login server today. I'll try to find a 'local equivalent' DNS through trial and error, but I don't have a lot of patience for these sorts of issues...

>

> I'm Australia based and implemented this temp fix yesterday and my game speed is notably faster...loading times are reduced and just a better, faster experience for me. I love it. Not sure if it is a coincidence or what, but I love it!

>

 

Very nice glad i was able to help.

Link to comment
Share on other sites

  • 4 months later...

> @"Silver.2031" said:

> Go into internet settings

> Change adapter settings

> right click and select properties on your internet connection

> Double click Internet Protocol Version IPv4 (TCP/IPv4)

> Switch from Obtain DNS server address automatically to Use the following DNS server address

> Type in the first box 8.8.8.8

> Type in the second box 8.8.4.4

> either validate or not (myself for example I did not validate and it worked as soon as i reloaded the launcher)

> Relaunch the launcher and I was able to log in.

>

> I am on windows 10

>

> https://gyazo.com/4ccd8e5916e6eb711eadf92a39c1c2d3

>

> Here is a visual linked above.

 

Trading Post wasn't accessible for me for the last three weeks. With your solution the problem was fixed in a minute. Thanks a lot :)

Link to comment
Share on other sites

Glad it helped :D> @"SinusBeatle.8294" said:

> > @"Silver.2031" said:

> > Go into internet settings

> > Change adapter settings

> > right click and select properties on your internet connection

> > Double click Internet Protocol Version IPv4 (TCP/IPv4)

> > Switch from Obtain DNS server address automatically to Use the following DNS server address

> > Type in the first box 8.8.8.8

> > Type in the second box 8.8.4.4

> > either validate or not (myself for example I did not validate and it worked as soon as i reloaded the launcher)

> > Relaunch the launcher and I was able to log in.

> >

> > I am on windows 10

> >

> > https://gyazo.com/4ccd8e5916e6eb711eadf92a39c1c2d3

> >

> > Here is a visual linked above.

>

> Trading Post wasn't accessible for me for the last three weeks. With your solution the problem was fixed in a minute. Thanks a lot :)

 

 

Link to comment
Share on other sites

> @"Healix.5819" said:

> If GW2 is open, close it.

>

> Open the run dialog by pressing WindowsKey+R and open:

> cmd

>

> A command prompt should pop up. Enter the following command, which will clear your DNS cache:

> ipconfig /flushdns

>

> Press WindowsKey+R again and open:

> %temp%

>

> The temp folder should pop up. Delete every folder beginning with gw2cache. It's possible for the trading post to actually cache an error page, preventing it from loading.

>

> If the trading post _still_ doesn't work, ensure that your antivirus, firewall or any other web filtering software you may have isn't blocking it. G DATA and FortiClient for example are also blocking it. You can try visiting the trading post in your browser to see if shows any messages - usually security software will show a warning page. https://tradingpost-dfw-live.ncplatform.net/humans.txt and https://tradingpost-live.ncplatform.net/humans.txt

 

**This is the solution.** :+1: Stop using Google DNS server IPs. ;)

 

> @"Silver.2031" said:

> The DNS 8.8.8.8 and 8.8.4.4 is a public google DNS just in case anyone is wondering.

> https://developers.google.com/speed/public-dns/docs/using

 

Therefore, I have to ask: Is it wise to use it? ;)

Link to comment
Share on other sites

> @"Ashantara.8731" said:

> > @"Healix.5819" said:

> > If GW2 is open, close it.

> >

> > Open the run dialog by pressing WindowsKey+R and open:

> > cmd

> >

> > A command prompt should pop up. Enter the following command, which will clear your DNS cache:

> > ipconfig /flushdns

> >

> > Press WindowsKey+R again and open:

> > %temp%

> >

> > The temp folder should pop up. Delete every folder beginning with gw2cache. It's possible for the trading post to actually cache an error page, preventing it from loading.

> >

> > If the trading post _still_ doesn't work, ensure that your antivirus, firewall or any other web filtering software you may have isn't blocking it. G DATA and FortiClient for example are also blocking it. You can try visiting the trading post in your browser to see if shows any messages - usually security software will show a warning page. https://tradingpost-dfw-live.ncplatform.net/humans.txt and https://tradingpost-live.ncplatform.net/humans.txt

>

> **This is the solution.** :+1: Stop using Google DNS server IPs. ;)

>

> > @"Silver.2031" said:

> > The DNS 8.8.8.8 and 8.8.4.4 is a public google DNS just in case anyone is wondering.

> > https://developers.google.com/speed/public-dns/docs/using

>

> Therefore, I have to ask: Is it wise to use it? ;)

 

if there are issues there are other ways as i said in the title its a temp work around that may or may not work but for those that it helps is what matters. and well google is a monopoly they already got Boardwalk and park place.

Link to comment
Share on other sites

> @"Ashantara.8731" said:

> Stop using Google DNS server IPs.

 

There's plenty of alternatives, like the new 1.1.1.1 by CloudFront, which claims to be the fastest and privacy-first. Some people have to do change their DNS, because their ISP's default is actually the one outdated, so flushing their local cache doesn't help.

Link to comment
Share on other sites

> @"Ashantara.8731" said:

> > @"Healix.5819" said:

> > Some people have to do change their DNS, because their ISP's default is actually the one outdated, so flushing their local cache doesn't help.

>

> Really? Didn't know. Wow. Are we talking American ISPs?

 

Could be anywhere in the world.

 

The "ISP default" usually points to the router, and the router then goes "upstream" to get names resolved. Somewhere along the way, there may be a "caching resolver" that remembers (for a time) results it previously got and just parrots back those old answers if it gets the same question again, and if the "true" answer gets changed, those caching resolvers don't automatically get the news. For a span of time, called the "Time To Live" or TTL, of the "cached" answers, the caching resolver will continue to give the outdated answer. If your ISP's caching resolver glitches and thinks the TTL is three weeks instead of a couple of days (or, indeed, if the true answer's TTL really *was* given as three weeks), you're kinda stuck with this outdated information.

 

Using a "public" resolver such as Google's will bypass the glitched TTL in your ISP's caching resolver. _Maybe_. It's possible for ISPs to just catch all requests and direct them to its caching resolver even if the "true" destination was elsewhere. (My company makes equipment that, among many other things, can do this.)

 

Caching resolvers, aside from the problems hinted at above, *are* a good thing. They reduce DNS traffic outbound from the ISPs customers AND reduce the time required for the majority of requests from the ISP's customers. That's their job.

 

Oh, and yes, you did read that right. That "_Maybe_" in italics _**DOES**_ mean that the "solution" presented here might not work for you. If this is the case, the best you can do is to use a VPN and hope the VPN provider's ISP doesn't have the same problem.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...