Cookie Problems
If you enter your email address and password and the login page
reloads with blank fields, this indicates a problem with cookies. If you
had your email address or password incorrect, or if you were not registered
at the site at all, then you would instead get an error message. The absence
of an error message and the blanking of the login fields points instead
to a cookie problem.
In case you do not know, a cookie is a small text file
that gets sent from our site to be stored in your browser’s files.
When you request any web page from our site in the future, this cookie
will be sent back to us. It will contain your login information so you
don’t have to log in again.
If you log in correctly, but then are sent right back to the login
page with blank fields (or if you are sent to the login page after registration),
this indicates that we are not receiving the cookie back. There could be two
possibilities:
1. Problem: the cookie is not being
stored properly on your computer
Solution: enable cookies in your
browser’s settings See our
Cookie Policy
for more information about cookies, and about the use of cookies at dvGarage.
2. Problem: the cookie is being
stored on your computer, but not being sent back to us
This is a more complicated problem. One of the symptoms that
you may notice is that the URL (www.dvgarage.com) in the “location”
window of your browser is changed to an IP address (such as
“192.99.108.11”). If this happens, then the browser looks
for a cookie labeled “192.99.108.11”
instead of “www.dvgarage.com” and since the label on our cookie is
“www.dvgarage.com” it does not send the cookie back.
Our theory on this is that somehow you request a page from your
local web proxy or an intervening web cache, and the content is delivered to your
browser. Meanwhile the domain name service (DNS) process is still waiting for the
domain name (www.dvgarage.com) to be resolved to the IP address
(“192.99.108.11”), so the browser just displays the numbers in
the location bar so you have something to look at. Next you click a link,
which is a standard relative link, saying something to the browser like: go
to the same server from where you got this page, and get this other
page. It knows the server as the numerical info (“192.99.108.11”)
instead of the domain name (“www.dvGarage.com”), and therefore
it looks for the numbers in the cookie file and doesn’t find anything.
Solution: Check that your
DNS server entries are correct. In particular, make sure that the first
server listed isn’t down, and that all servers are “close”
on the network. Sometimes people move machines around but forget to change
the DNS when they change the IP address, and then end up
trying to use a DNS that is physically far away. | 
PRODUCTS