autopia car care forums...

It works with Vista, I'm using it right now. You need to turn off User Account Control. Click Start--Control Panel--click User Accounts and Family Safety title--click User Accounts title--click Turn User Account Control On or Off. After you turn this off try to launch the command prompt again and run that command. I really hope this works for you after all this!
 
If you are using vista or win 7 and you receive the elevation message:

Click Start and in the Search bar type "CMD".

Once the search returns the CMD result, right click on the entry and choose "Run As Administrator".

A command window will open with elevated priveledges and you can run the necessary commands. A few to try:

nbtstat -R
ipconfig /flushdns *then* ipconfig /registerdns

Edit: you can also attempt to use a different DNS server in your testing. A few public servers are:

4.4.4.4
4.4.8.8
4.2.2.1

To change your DNS settings:

Start > Control Panel > Network and Internet > Network and sharing center > Manage network connections

Right click your local area network connection and choose 'Properties'.

Click the 'Networking' tab and then 'Internet Protocol version 4 (ipv4)'

You will see an area to specify DNS settings. To manually set a server, click 'Use the following DNS server addresses' and enter one of the addresses above.

Save your settings and exit all windows. Then try the forums again.

Sent from my SPH-D700 using Tapatalk
 
Last edited:
I thought you already tried other browsers?

In post number 11 I said that I had other browsers. I hadn't tried them until a minute ago. Firefox will open the home page, but not the forum itself. I'll try your other suggestion next.
 
It works with Vista, I'm using it right now. You need to turn off User Account Control. Click Start--Control Panel--click User Accounts and Family Safety title--click User Accounts title--click Turn User Account Control On or Off. After you turn this off try to launch the command prompt again and run that command. I really hope this works for you after all this!

I did this and then tried the prompts given in your post number 14. It said it was succesful, but I still could access the forum.

I had to click on a checked box, as there was no off/on. It just said it was on at the top off the page and I assumed unchecking the box would work. It promted me to restart when I unchecked it.

Won't I need to go back and make sure to check the box again? I assume the box has been checked for who knows how long and that it should be rechecked to go back to previous settings.


I can get to the above link, but when I click on the forum tab to open the forum it will not open the page. It's white and blank forever until it says it can't make the connection.
 
It still doesn't make sense that I can open every other forum I get on, except for autopia car care.
 
What is the exact error code that is returned?

Also, please try the custom DNS settings I detailed in my previous post. The forum link is different than the main page, and service providers can sometimes have corrupted DNS entries.

Sent from my SPH-D700 using Tapatalk
 
No error code is given. See post 13 for what the blank page ends up saying. Reseting the local area network is done, but there's still a problem with the connection at autopiayadayadayada (72.284.yada, yada, yada), though I don't think that's the error code. Wouldn't it say, "error code ...(numbers here)?"

I've had enough for this evening.

How about you Flash? You get in yet?
 
I hear ya. Take a stab tomorrow. Ensure that you do try an alternate DNS server and let me know what happens. You can PM me and tomorrow night I can try some phone support if needed. If you are seeing a reset connection, it can be a number of things and trying to go around your service provider may help.

Sent from my SPH-D700 using Tapatalk
 
what url are you using?

I don't know the same one I've been using I guess. You mean the address right?

All of my settings are back as they were before all of this started. I just came home from being gone all day, I went the autopia home page, clicked on the forum link to go to the forum...

...and it loaded without a hitch. Go figure. As a result I still don't think the issue was on my end.
 
I should tell you I'm running Vista.

Well there you go! :D

More seriously, if the problem wasn't on your machine, it was still likely close to your end. Either between you and your ISP or between your ISP and autopia.org. You might want to do a tracert autopia.org from a cmd line to get an idea of the multiple steps (hops in IT lingo) your data takes between you and autopia. Then if things go bad again, run the same command and compare. That way you can get an idea if one of your ISP's routers is having a brain fart or if the problem is on the other side of your ISP. In any event, if a lot of other people report success reaching the site, it's not very likely that there's a server problem with that site, is it? Another tool to use is nslookup. nslookup autopia.org should spit out a 32 bit address (shown as xxx.xxx.xxx.xxx where xxx=a number between 0 and 254). You can also run tracert on this number. Or tracert -d (this takes DNS out of the picture.) With these tools you should be able to get an idea if a problem is DNS related or a problem somewhere along the path between you and the site ou want to reach.
 
Well there you go! :D

More seriously, if the problem wasn't on your machine, it was still likely close to your end. Either between you and your ISP or between your ISP and autopia.org. You might want to do a tracert autopia.org from a cmd line to get an idea of the multiple steps (hops in IT lingo) your data takes between you and autopia. Then if things go bad again, run the same command and compare. That way you can get an idea if one of your ISP's routers is having a brain fart or if the problem is on the other side of your ISP. In any event, if a lot of other people report success reaching the site, it's not very likely that there's a server problem with that site, is it? Another tool to use is nslookup. nslookup autopia.org should spit out a 32 bit address (shown as xxx.xxx.xxx.xxx where xxx=a number between 0 and 254). You can also run tracert on this number. Or tracert -d (this takes DNS out of the picture.) With these tools you should be able to get an idea if a problem is DNS related or a problem somewhere along the path between you and the site ou want to reach.

Dude you're going to have to slow down and speak english if you're wanting to help me. LOL! If it isn't do this, do that, or click this, then that, I am totally lost. Besides, if it's working now, why try and fix what isn't broken.

Am I supposed to type in "nslookup autopia.org" somehwere? What the heck is a tracert anyway? Am I suppose to type in "tracert autopia.org...never mind I think I got that one. I can follow is just like I did last night.

How do you guys know all of this stuff?

EDIT:
12 steps in the tracert.

nslookup...what do I do with the numbers, I wrote them down? xxx.xxx.x.x and xx.xxx.xxx.xx

tracert -d ... Not sure I understand how to do that one.
 
Last edited:
Back
Top