PDA

View Full Version : Logging in

BoobsNBoots
08-18-2006, 11:43 PM
How come it doesn't keep me logged in when I tell it to remember me. Before I could close the window and I never had to sign back in but now I do. Any reason?
Argyleskin
08-18-2006, 11:45 PM
How come it doesn't keep me logged in when I tell it to remember me. Before I could close the window and I never had to sign back in but now I do. Any reason?

Might still be a glich in the system. Once Papa or Nutter see this maybe they would be able to help you further or fix that if there is a problem!
PapaSkin
08-19-2006, 12:00 AM
best bet is to blow away all your cookies and temp internet files (cache) - then log in with the box checked again and see how it works - Since we are jumping between names and IP's right now - it really confuses things and needs to cookies - we can probably switch it to name only now ..but best to wait 24 hrs - Hopefully by monday it will all be by www.skinheads.net and clear up any log in issues. :)
PromoteChaos
08-19-2006, 04:38 AM
best bet is to blow away all your cookies and temp internet files (cache) - then log in with the box checked again and see how it works - Since we are jumping between names and IP's right now - it really confuses things and needs to cookies - we can probably switch it to name only now ..but best to wait 24 hrs - Hopefully by monday it will all be by www.skinheads.net (http://www.skinheads.net) and clear up any log in issues. :)


Yep. I cleared out all of my shit this afternoon & it has kept me logged in
PapaSkin
08-19-2006, 01:11 PM
we are 100% on the www.skinheads.net domain name right now - if you are getting here the old way with the IP - you might have problems.
pxscooterskin
08-19-2006, 01:26 PM
I can only log in via http://65.99.207.114 (http://65.99.207.114/forums/../) and not WSN.

Firefox isn't recognising WSN!
PapaSkin
08-19-2006, 01:29 PM
go to start - run - and type cmd

When you get a dos window - type ping www.skinheads.net

If you are getting the 65.99.207.114 then you should be able to reach it by name - if it's giving you some old 209.x.x.x address - then your dns is cached and not getting updated.

Easy fix is to drop your entire internet connection and reconnect - then clear all cache/temp files and cookies and try again.

Another way without dropping all connections is to type in the command window:

ipconfig /flushdns

Either way or both should fix it. :) (i hope)
pxscooterskin
08-19-2006, 02:04 PM
Sorted, but I get timed out from the front page. Can only log in from the forums page. Others may have the same problem.
PapaSkin
08-19-2006, 04:46 PM
Yep, I see the problem...trying to fix that now...thanks!
PromoteChaos
08-19-2006, 08:25 PM
go to start - run - and type cmd

When you get a dos window - type ping www.skinheads.net (http://www.skinheads.net)

If you are getting the 65.99.207.114 then you should be able to reach it by name - if it's giving you some old 209.x.x.x address - then your dns is cached and not getting updated.

Easy fix is to drop your entire internet connection and reconnect - then clear all cache/temp files and cookies and try again.

Another way without dropping all connections is to type in the command window:

ipconfig /flushdns

Either way or both should fix it. :) (i hope)

I tried all of the above & still can't get in through the domain.

Here's what I got after flushing dns
ping www.skinheads.net (http://www.skinheads.net)
Pinging skinheads.net [209.51.144.207] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 209.51.144.207:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
PapaSkin
08-19-2006, 11:44 PM
I tried all of the above & still can't get in through the domain.

Here's what I got after flushing dns
ping www.skinheads.net (http://www.skinheads.net)
Pinging skinheads.net [209.51.144.207] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 209.51.144.207:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Then it's your ISP - not us - your ISP is holding the DNS cache longer than they should be. If you can get a different DNS server - reconnect - or just hold out until their TTL (Time to Live) dies out - it will work.
PromoteChaos
08-20-2006, 04:56 PM
Then it's your ISP - not us - your ISP is holding the DNS cache longer than they should be. If you can get a different DNS server - reconnect - or just hold out until their TTL (Time to Live) dies out - it will work.

Hey sweets,

It seems to be fine today. Disconnecting & re-connecting wasn't making a difference. Chris said he'd tell me what nameservers to try in the future. That's fucked up that I can't reply on B.S.

Thanks